Project

General

Profile

Actions

Feature #1477

closed

IGMPPROXY spamming the main systemlog

Added by M Schweitzer over 13 years ago. Updated almost 9 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

Also available in: Atom PDF