Thanks guys, sorry I didn't mention wired network. Since the DHCP requests are handled correctly it doesn't make sense the 169.254 addresses continue to be used for the UPNP messages.ĭoes this make sense? Any ideas why these boxes which have just been restarted are using these 169.254 even after DHCP requests have been made and filled?
DAEMON.WARN MINIUPNPD PACKET SENDER IGNORING MAC
The duplicate entries per MAC doesn't look good! 212 are the receivers.īut the UPNP messages continue using the 169.254 addresses which continue to be ignored.īut after a while, these addresses make their way into the ARP table and the entries include:ġ69.254.181.103 00-26-24-xx-yy-zz dynamicġ69.254.220.111 00-18-9b-qq-rr-ss dynamicġ69.254.231.147 70-76-30-aa-bb-cc dynamic While this is happening the receivers are still starting up and haven't yet made DHCP requests.Īfter a while I see the DHCP request traffic for each of the receivers:Įverything looks good when check the ARP entries I see: May 3 01:00:11 unknown daemon.warn miniupnpd: SSDP packet sender 169.254.181.103:49152 not from a LAN, ignoring May 3 00:47:02 unknown daemon.warn miniupnpd: SSDP packet sender 169.254.231.147:49152 not from a LAN, ignoring May 3 00:45:59 unknown daemon.warn miniupnpd: SSDP packet sender 169.254.220.111:49152 not from a LAN, ignoring I get lots of these PNP SSDP messages from each of the receivers, but the router ignores because of the address being used: If I reset a receiver the traffic on the net doesn't make a lot of sense. Here's the situation, I'm having a problem with my network due to the DirecTV (DTV) receivers and what they do on the network. Sorry if this is covered elsewhere, but you can't search for "169.254" because the search engine filters out the '.'s
0 kommentar(er)
