I just received a pair of Slimserver 3s and opened one of them up.
When I configured it for my wireless network, it quickly configured
itself with DHCP and downloaded new firmware, version 28. It then came
back up, auto-configured itself again and worked fine for a while.
Then I unplugged it to move it into another room. I also enabled
Ethernet bridging, to try it out.
This time the unit was unable to complete DHCP.
Some packet tracing showed why. The unit sent out a DHCP request with
its factory-assigned MAC address 00:04:20:06:1a:50 in the Ethernet
source field but the sender hardware address in the DHCP request was the
unusual value 20:05:73:00:00:0c. When my DHCP server responded, it put
this second MAC address into the destination field. Since the Squeezebox
was presumably listening for its factory-assigned MAC address, it never
heard the response. So it kept resending its request and my server kept
sending the same unheard answer.
Eventually the Squeezebox timed out of DHCP and gave itself a
self-assigned IP address in the 169.254 block, which I do not use.
If I manually set the appropriate IP addresses, all works fine. Only the
DHCP client appears to be broken.
The DHCP server is ISC dhcpd running on Linux. It works fine with
everything else in my house.
Anybody else see anything like this?
Phil
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
