xargs;163064 Wrote: > I found something that may be a clue to this problem. When my > Squeezebox was in the "can connect to SlimServer/can't connect to > SqueezeNetwork" mode, I sniffed the traffic on my SlimServer box. > Traffic from the Squeezebox was using a 169.254.x.x IP address, and my > wireless router/DHCP server did not show the Squeezebox as a DHCP > client (it gives out addresses on 19.168.11.x). I couldn't understand > how 169.254 traffic could even get routed to my SlimServer box, until I > noticed it had a route for 169.254. I think this route, and the > Squeezebox's bogus IP came from a VMWare installation running on the > SlimServer box. > > I've reconfigured VMWare to remove its DHCP server and deleted the > suspect route. I'm hoping this is the solution.
? 169.254.XXX.XXX is the Squeezebox's fallback address - one it uses when it can't get a response from the DHCP server. -- Mark Lanctot ------------------------------------------------------------------------ Mark Lanctot's Profile: http://forums.slimdevices.com/member.php?userid=2071 View this thread: http://forums.slimdevices.com/showthread.php?t=27977 _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/squeezenetwork
