Menu

#12 Prevent internal IPs from broadcast attempt?

open
nobody
None
6
2018-06-18
2010-01-17
Anonymous
No

Firstly, here's my network setup:

ISP (upstream if) => NAT ROUTER (downstream IFs) => Internal LAN

My internal LAN has got several types of computers running Linux, Windows XP, Windows Server 2003 and Windows 7.

I've noticed that I constantly get those messages in syslog:

Jan 17 13:11:21 pinstrate igmpproxy[4225]: The source address 192.168.2.9 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 17 13:12:39 pinstrate igmpproxy[4225]: The source address 192.168.3.6 for group 239.255.255.250, is not in any valid net for upstream VIF.

The 192.168.3.6 and 192.168.2.9 are computers on my Internal LAN running Windows 7. And they even don't subscribe to the multicast or have anything to do with igmpproxy. But htose messages appear in syslog constantly. I guess this has something to do with SSDP or UPnP.

Is there any workaround for that?

Discussion

  • Anonymous

    Anonymous - 2010-01-22

    This is my config file for reference:

    quickleave
    phyint eth2 upstream ratelimit 0 threshold 1
    altnet 10.10.2.11
    altnet 10.10.13.3
    altnet 10.15.2.1
    altnet 10.70.70.1
    altnet 10.157.71.64/26
    phyint eth1 downstream ratelimit 0 threshold 1
    phyint eth0 downstream ratelimit 0 threshold 1
    phyint eth3 disabled
    phyint lo disabled

     
  • Frank Seidel

    Frank Seidel - 2018-06-18

    Hi, i have the very same problem/question.
    Constantly getting those messages filling up my log from not related clients on my lan.
    Is there any way to silence this out or tell igmpproxy to ignore those hosts?

     

Log in to post a comment.