Bugzilla – Bug 2620
SB3 sitting on two ip addresses. Assigned dhcp addy and one other...
Last modified: 2008-12-18 11:38:58 UTC
One of my SB3's is sitting on an extra address, and neither the s/w side of the SB3 nor the DHCP server displays it. What do I mean? The dhcp server shows ip addy 100 leased to the SB3 (i.e. to it's mac address). The home/player setting page shows the same thing: Player Firmware Version: 28 The IP address for this player is: 192.168.0.100:33373 The ethernet MAC address for this player is: 00:04:20:06:03:16 Wireless Signal Strength: 62% But the SB3 is _also_ sitting on 192.168.0.106 (tests: responds to pings on this addy, sniffer shows SB3 mac address responding to ping, turning off SB breaks ping.) Bouncing the SB3 shows it reclaiming its proper 100 adress in the dhcp log, but no mention of the 106 address. The dhcp function is now broken as the server tried to lease 106 to new devices, but leases fail as adddress is already in use. Sorry if I missed something in the docs : 1. Are two IP addy's normal? For what function? 2. If not normal - Can I get the device to let go of the 106 address? 3. I don't have dhcp logs going back far enough to show whether or not 106 was ever leased to the SB3 or not. Is there any other way it could have grabbed this IP? Thanks, Dan
I am seeing the same problem with a squeezebox2. The SB2 is not connected through a wire, only a wireless connection. Running arp -a I see the following for this SB2: d114.xxxx.com (192.168.129.114) at 00:04:20:05:A5:A4 [ether] on eth1 d117.xxxx.com (192.168.129.117) at 00:04:20:05:A5:A4 [ether] on eth1 Both addresses are pingable so it is not just a left over entry in some arp table.
I've also been seeing this for some time. SB2, FW33, connected via wireless to a Netgear DG834G router with firmware 3.01.25. The router is configured as a DHCP server, and I've told it to give the SB2 a particular IP address. The SB2 is set to use DHCP. The router assigns the correct IP address to the SB2, but it also assigns another IP address as well. (this can be seen on the router's web interface).
Could this additional IP be related to Squeezenetwork access? (Is the second IP addy used to access the Squeezenetwork?) -Dan
This is definitely a cache problem. If I tell my router to assign various different addresses via DHCP, the SB2 will always sit on the correct address and the same wrong address. I'm not sure whether the wrong address was previously assigned by DHCP, or whether it was an address I entered manually. But its definitely been cached somewhere inside the SB2. To solve the problem, I did a factory reset on the SB2 (unplug the power, and then replug while holding "add" on the remote), and everything now works perfectly.
I think this may be related to bug 2302 ??
Chris: please update to the soon-to-be-released 6.2.2 release of SlimServer. It includes a version of the firmware that has some signficant bugs fixed, including some DHCP issues. If the issue is still there with the new firmware, please reopen the bug. thanks!
I'm not sure why this bug got closed as this is still a known issue.
Same problem on my sb3 with the latest firmware. The device has apparently cached 10.0.1.4, since when I moved it to 10.0.1.5, it started responding on both, causing much network confusion. I will try the factory reset trick tonight, since currently it's unuseable (since putting it on the network causes problems). I'm wonder how many ips it will cache and use....
I think I can reproduce this very consistently with some of my desktop equipment now, Richard. Did you say you have a lead on fixing this, or do you need additional info from me?
Chris, I have already fixed this and it will be include in the next test release of the firmware later this week.
This bug is fixed in firmware 56. It is currently undergoing internal testing. You will be notified again when it is made part of a nightly release.
Firmware 58 only fixes this bug on the wireless interface. Firmware 59 additionally fixes this bug on the wired interface. It is currently undergoing internal testing. You will be notified again when it is made part of a nightly release.
This fix is now available in the 6.5 nightlies ONLY. FW59 will not work with Slimserver versions 6.3.x and below. Please give it a try and let us know how it goes.