#the other subscribers on the same cable broadcast segment can send a #224.0.0.1 multicast packet but your pc/hardware router will not forward it #to your lan even if its time-to-live value is greater than 1 (assuming #the router implements multicast routing correctly). so only the router can #see that multicast packet, but the internal hosts in your lan will not. #
I just found out that 192.168.100.1 is the IP address of my cable modem -- Apparently, it has an HTTP-based management interface which is accessible at (as you might have guessed) 192.168.100.1. #to isolate further, you can turn off any 'ip multicasting' #capabilities/software on your router which connects to your cable #internet. this will prevent all outside multihop multicast packets from #reaching your lan. this also ensures that it's not your router itself #sending that packet. then use tcpdump (on the host where you received the #log msg you posted) to get the source mac address of that packet in #case it persists. if you have a manageable switch/hub, you can lookup the #src mac address from its mac address cache so you can pinpoint which #switch/hub port it received the packet from (even if the src mac addr is #spoofed). IP multicasting has never been enabled in the box (it's my LAN gateway, and router to the inet). I'm still trying to figure out how to turn it off at the cable modem level.. and if the multicast packets are needed by my inet-over-cable provider at all (perhaps AT&T is used it as a keep-alive signal?) stay cool. jeff -- -- Jeff Gutierrez Pinoy Ako! May reklamo? Mapua Online! http://www.mapua.org http://www.mapua.com http://www.mapua.net Intertainer, Entertainment On Demand http://www.intertainer.tv _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
