Project

General

Profile

Bug #10139

IGMPPROXY spamming the main systemlog

Added by Roy Krikke about 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Logging
Target version:
Start date:
12/31/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.4-p3
Affected Architecture:
All

Description

Igmpproxy is massivly spamming the main systemlog making it "completly" unusable.

This bug is connected to:
https://redmine.pfsense.org/issues/1477

"
Dec 31 11:57:44 igmpproxy 39848 The IGMP message was from myself. Ignoring.
Dec 31 11:57:44 igmpproxy 39848 RECV V2 member report from 192.168.1.1 to 224.0.0.2
Dec 31 11:57:43 igmpproxy 39848 RECV Membership query from 192.168.1.1 to 224.0.0.1
Dec 31 11:57:40 igmpproxy 39848 Adding MFC: 216.146.225.162 -> 224.0.251.162, InpVIf: 1
Dec 31 11:57:40 igmpproxy 39848 RECV V2 member report from 192.168.60.100 to 224.0.251.162
Dec 31 11:57:39 igmpproxy 39848 The IGMP message was from myself. Ignoring.
Dec 31 11:57:39 igmpproxy 39848 RECV V2 member report from 192.168.1.1 to 224.0.0.2
Dec 31 11:57:35 igmpproxy 39848 Adding MFC: 214.75.127.23 -> 224.3.2.6, InpVIf: 1
Dec 31 11:57:35 igmpproxy 39848 RECV V2 member report from 192.168.60.100 to 224.3.2.6
Dec 31 11:57:35 igmpproxy 39848 RECV Membership query from 192.168.1.1 to 224.0.0.1
Dec 31 11:57:29 igmpproxy 39848 Adding MFC: 216.146.225.162 -> 224.0.251.162, InpVIf: 1
Dec 31 11:57:29 igmpproxy 39848 RECV V2 member report from 192.168.60.100 to 224.0.251.162
Dec 31 11:57:29 igmpproxy 39848 The IGMP message was from myself. Ignoring.
Dec 31 11:57:29 igmpproxy 39848 RECV V2 member report from 192.168.1.1 to 224.0.0.2
Dec 31 11:57:27 igmpproxy 39848 Adding MFC: 214.75.127.23 -> 224.3.2.6, InpVIf: 1
Dec 31 11:57:27 igmpproxy 39848 RECV V2 member report from 192.168.60.100 to 224.3.2.6
Dec 31 11:57:26 igmpproxy 39848 RECV Membership query from 192.168.1.1 to 224.0.0.1
Dec 31 11:57:20 igmpproxy 39848 The IGMP message was from myself. Ignoring.
Dec 31 11:57:20 igmpproxy 39848 RECV V2 member report from 192.168.1.1 to 224.0.0.2
Dec 31 11:57:19 igmpproxy 39848 RECV Membership query from 192.168.1.1 to 224.0.0.1
Dec 31 11:57:16 igmpproxy 39848 joinMcGroup: 224.3.2.6 on vtnet0.4
Dec 31 11:57:16 igmpproxy 39848 Adding MFC: 214.75.127.23 -> 224.3.2.6, InpVIf: 1
Dec 31 11:57:16 igmpproxy 39848 RECV V2 member report from 192.168.60.100 to 224.3.2.6
Dec 31 11:57:15 igmpproxy 39848 RECV Membership query from 10.60.118.15 to 224.0.0.1
Dec 31 11:57:13 igmpproxy 39848 The IGMP message was from myself. Ignoring.
Dec 31 11:57:13 igmpproxy 39848 RECV V2 member report from 192.168.1.1 to 224.0.0.2
"
....

Igmpproxy logs should either be moved to a separate log tab or at least it should be possible to disable them.

Associated revisions

Revision d30d2108 (diff)
Added by Jim Pingle about 2 months ago

Move igmpproxy logs to routing.log. Fixes #10139

Revision e50335e9 (diff)
Added by Jim Pingle about 2 months ago

Move igmpproxy logs to routing.log. Fixes #10139

Revision 7f5cb422 (diff)
Added by Jim Pingle about 2 months ago

Relocate IGMP proxy verbose setting. Fixes #10139

Revision 7fa8c0dd (diff)
Added by Jim Pingle about 2 months ago

Relocate IGMP proxy verbose setting. Fixes #10139

Revision e63373a6 (diff)
Added by Jim Pingle about 2 months ago

Fix function case. Issue #10139

History

#1 Updated by Jim Pingle about 2 months ago

  • Category set to Logging
  • Assignee set to Jim Pingle
  • Target version changed from Future to 2.5.0

There is already a verbose setting for it under Status > System Logs on the Settings tab. Try unchecking the box there.

If that is already unchecked, try editing the invocation of igmpproxy in services.inc to include -d4, as mentioned in #1477, and see if that helps.

Either way this should be moved into the routing.log and not the main system log, so I'll work on that.

#2 Updated by Jim Pingle about 2 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#3 Updated by Jim Pingle about 2 months ago

  • Status changed from Feedback to In Progress
  • % Done changed from 100 to 50

On second thought I'm also going to move the igmpproxy verbose logging option to services_igmpproxy.php since it makes more sense there. It requires the igmpproxy daemon to restart to activate, which doesn't happen when the setting is changed on the syslog settings anyhow.

#4 Updated by Jim Pingle about 2 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 50 to 100

#5 Updated by Jim Pingle about 2 months ago

  • Target version changed from 2.5.0 to 2.4.5

#6 Updated by Roy Krikke about 2 months ago

Hello Jim Pingle,

Great to see that you already taken action. I have overlooked the option under Status > System Logs on the Settings tab, thanks for the feedback. In addition, it seems "to me" a good idea what you are proposing about move the igmpproxy verbose logging option to services_igmpproxy.php

Do I understand correctly that if you move de option and the log option is changed; igmpproxy will be restarted automatically to activate it?

#7 Updated by Jim Pingle about 2 months ago

When you toggle the setting on services_igmpproxy.php and save it will offer to apply changes as with any other change on that page. When you click apply, the service will restart with the new option.

#8 Updated by Jim Pingle about 2 months ago

  • Status changed from Feedback to Resolved

The verbose option is present on the main IGMP proxy config page and is working as expected.

The logs for igmpproxy are now located in routing.log instead of system.log

Tested on 2.4.5.a.20200102.0720

Also available in: Atom PDF