Project

General

Profile

Actions

Feature #1477

closed

IGMPPROXY spamming the main systemlog

Added by M Schweitzer over 10 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
IGMP Proxy
Target version:
-
Start date:
04/24/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

Since Igmpproxy is finally working now theres only one big problem left:

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

"Apr 24 20:56:11 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:57:00 igmpproxy: Note: RECV Membership query from 93.228.31.254 to 224.0.0.1 (ip_hl 24, data 12)
Apr 24 20:57:02 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 48)
Apr 24 20:57:02 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 24 20:58:01 igmpproxy: Note: RECV Membership query from 93.228.31.254 to 224.0.0.1 (ip_hl 24, data 12)
Apr 24 20:58:06 igmpproxy: Note: RECV Membership query from 192.168.0.10 to 224.0.0.1 (ip_hl 24, data 8)
Apr 24 20:58:06 igmpproxy: Note: RECV Membership query from 192.168.0.10 to 224.0.0.1 (ip_hl 24, data 12)
Apr 24 20:58:06 igmpproxy: Note: RECV V2 member report from 192.168.0.2 to 224.0.0.252 (ip_hl 24, data 8)
Apr 24 20:58:06 igmpproxy: Note: RECV V2 member report from 192.168.0.2 to 239.255.255.250 (ip_hl 24, data 8)
Apr 24 20:58:06 igmpproxy: Note: joinMcGroup: 239.255.255.250 on em1_vlan8
Apr 24 20:58:06 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:58:06 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 24 20:58:06 igmpproxy: Note: RECV V2 member report from 93.228.5.254 to 224.0.0.252 (ip_hl 24, data 8)
Apr 24 20:58:06 igmpproxy: Note: The IGMP message was from myself. Ignoring.
Apr 24 20:58:06 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:58:06 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 24 20:58:06 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:58:06 igmpproxy: Note: The IGMP message was from myself. Ignoring.
Apr 24 20:58:07 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 56)
Apr 24 20:58:07 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 24 20:58:08 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:58:08 igmpproxy: Note: The IGMP message was from myself. Ignoring.
Apr 24 20:58:12 igmpproxy: Note: RECV V2 member report from 192.168.0.103 to 239.35.10.1 (ip_hl 24, data 8)
Apr 24 20:58:12 igmpproxy: Note: Adding MFC: 193.158.35.198 -> 239.35.10.1, InpVIf: 1
Apr 24 20:58:12 igmpproxy: Note: RECV V3 member report from 93.228.5.254 to 224.0.0.22 (ip_hl 24, data 16)
Apr 24 20:58:12 igmpproxy: Warn: unknown Mode in V3 report (673189920)
Apr 24 20:58:12 igmpproxy: Note: RECV V2 member report from 93.228.5.254 to 239.35.10.1 (ip_hl 24, data 8)
Apr 24 20:58:12 igmpproxy: Note: The IGMP message was from myself. Ignoring."
....

Igmpproxy logs should either be moved to a seperate log tab or atleast it should be possible to disable them...

http://forum.pfsense.org/index.php/topic,28477.0.html

Actions #1

Updated by Chris Buechler over 10 years ago

  • Priority changed from High to Normal
  • Target version deleted (2.0)
Actions #2

Updated by Chris Buechler over 10 years ago

We're not running igmpproxy with verbose logging enabled, not sure if that log level is from something in the pfport or igmpproxy.

Actions #3

Updated by Charles Orus over 9 years ago

It's igmpproxy doing it. I get it too. As a workaround for myself I have just added igmpproxy to syslog and yes I agree that this is very annoying. Please give igmpproxy its own log file, it's pretty trivial to do isn't it?

Actions #4

Updated by Ermal Luçi almost 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #5

Updated by Willy Tenner almost 8 years ago

The patch from https://github.com/pfsense/pfsense-tools/blob/master/pfPorts/igmpproxy/files/patch-verbosity-logs does not really solve the problem. The level number for the debug mode must immediately follow the option character d! No space between.

For testing I changed line 1217 in /etc/inc/services.inc to (space between -d and 4 removed):

mwexec("/usr/local/sbin/igmpproxy -d4 -c {$g['tmp_path']}/igmpproxy.conf");

Restart igmpproxy and everything is silent now.

Kind regards.

Actions #6

Updated by Willy Tenner almost 8 years ago

Sorry, I forgot to mention. I am using pfSense 2.1-RELEASE (i386) built on Wed Sep 11 18:16:44 EDT 2013 FreeBSD 8.3-RELEASE-p11.

Actions #7

Updated by Phillip Davis almost 8 years ago

If you make a pull request in GitHub it makes it really easy for the devs to take a look and commit the fix.

Actions #8

Updated by Chris Buechler almost 6 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF