Bugzilla – Bug 8258
Possible DHCP lease renew issue in receiver ????
Last modified: 2008-10-17 04:54:32 UTC
I don't know if this is real, and I haven't actually seen any trouble caused by it. I have a linksys WRT54G V2. It will display the DHCP clients. If everything is restarted - including the receiver by power cycle - then I see both the receiver and controller (and my laptop) as DHCP clients. After a router reboot, the controller and my laptop show up again reasonably quickly, but the receiver usually disappears from the list and does not reappear. I assume this means that the linksys doesn't know about the receiver's lease on its ip address. I don't have any other devices which I can use to see if the linksys will give out that address to someone else. And I don't know for sure what hidden state the linksys might have. So as I said above, I don't know if this is a bug but if you see other people having IP collision problems, you might look at the receiver logic for reacquiring a lease. In my ignorance, I don't even know how that works after a router reboot!
We've noticed that the Linksys table doesn't always seem to report active leases., but thanks for the note! If this is causing a problem for someone please re-open.
I've just experienced an IP address conflict. But I'm not sure its receiver's fault. Facts: I reset my router every night - superstition after I was seeing router crashes after installing Duet. Often, the DHCP list has the receiver, and sometimes my laptop, missing! So far, the controller is always listed. Over night, the receiver was in either off of stopped state - not sure which. It is now stopped, but the power off pluging should have turned it off - don't know if it would turn itself back on. Over night, the laptop was suspended. On resume of the laptop, it reported IP conflict. What I saw looking at the network was that the receiver had moved from the IP is used to have to the same IP as the laptop. This presumably happened while the laptop was suspended. The laptop, on resume, didn't renew and move, of course. I suspect part of the issue is that the router reset lost the suspended laptop's lease, which is not your fault. But why did the receiver move. After the router reboot, it apparently did get a new lease. But I believe it should request the same IP address it used to have in the DHCP request. Is that logic in the receiver? Bottom line - I still don't have evidence of anything wrong, but am reporting the latest result.
I'm out of this game - I've moved to a linux dhcp server which supports ip address assignment. In the change, it appears that the receiver did NOT request its previous address when I powered it down and back up.
According to my sysadmin friends, DHCP clients typically request the same address again. However, I have no idea if our IP3K firmware supports that. We don't have many bytes to spare. I'm not sure I care about that issue, really. It seems like the network should continue working no matter if the Squeezebox requests the same old address or a new one. But I am interested in the possibility that perhaps it is not requesting a DHCP address from the server at all. This seems like perhaps what it means if it's not listed in the router's client table. We should probably do an experiment with a better DHCP server than a $35 router to investigate this, but that will take some time to put together. I'm going to mark this as 'future' for now, but anyone running across this and seeing these symptoms, please feel free to add comments and votes so this will stay on our radar.
I did some investigation and ip3k DHCP client implementation in fact tries to get the same ip address again when asking for a renewal of the lease. And if granted continues to use it. But it also continues to work if the DHCP server assigns it a different ip address.
I've got some extra information for my situation. After a lot of experimentation I found out that it's the ogg-files that cause the errors. It doesn't matter whether it's an ogg-file I encoded myself, or one I downloaded from the internet. Whenever I have ogg-files in my library, eventually the receiver will stop playing. Though not immediately at the start, during, of after playing an ogg-file. (That would be way to simple!) For some ogg-files I I ripped the cd again in flac and some ogg-files I just converted to mp3. The mp3's and flac's I had I kept the same. Now the system is working flawless for several weeks. This is a workaround I am ok with, so thats the end for the bug for me. But if you want, I can experiment a bit more an provide you with some log-files. Just tell me what you would like to see.
Damnit, I meant to post to bug 7916. Can a moderator delete this and my previous comment?