Feature #1477
IGMPPROXY spamming the main systemlog
| Status: | Feedback | Start date: | 04/24/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | IGMP Proxy | |||
| Target version: | - | |||
| Affected version: | 2.0 | Affected Architecture: |
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...
Associated revisions
Fixes #1477. Use the new parameter to reduce igmpproxy logging level
History
#1
Updated by Chris Buechler about 2 years ago
- Priority changed from High to Normal
- Target version deleted (
2.0)
#2
Updated by Chris Buechler about 2 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.
#3
Updated by Charles Orus 12 months 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?
#4
Updated by Ermal Luçi about 1 month ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset d6307bd38ef0d50caf1d0224a845a206f00da1aa.