Re: [slim] SB2 DHCP Problems
Not sure if the optical port on the A/V receiver is the problem or the SB2 but I moved to the analog ports and there are no problems with the pausing. Still no luck with DHCP though. Regards-Michael G. -- mgerbasio mgerbasio's Profile: http://forums.slimdevices.com/member.php?userid=926 View this thread: http://forums.slimdevices.com/showthread.php?t=55698 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
[slim] SB2 DHCP Problems
Hi, I'm running the SqueezeCenter 7.2.1 and have two SqueezeBoxs, a V1 with firmware 40 and V2 with firmware 113, both connected to the same router via Ethernet. I'm having problems with the V2 device getting a network IP via dhcp. It always fails and I need to manually set it. Otherwise it works fine. Any idea what might be wrong? I also get occasional dropouts on the optical port, but really haevn't spent much time troubleshooting it yet. Thanks. Regards-Michael G. -- mgerbasio mgerbasio's Profile: http://forums.slimdevices.com/member.php?userid=926 View this thread: http://forums.slimdevices.com/showthread.php?t=55698 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
[slim] sb2 DHCP problems
It seems to me that the sb2 does not honor the lease-time of a DHCP lease, i. e. when a lease has run out it won't rerequest a lease or stop using the address. Rather, it will continue using the IP it got during network setup indefinitely. IIRC I've reported the problem some time ago. In the meantime I've changed the lease to never run out :) But today I had to restart the sb2 because of an access point update. It took quite some time for the DHCP request (normally it's instant) and then obtained the IP 169.254.188.141. It's just that this address is in a reserved address space that I'm _not using_ and my own DHCP server did not log a request for an address. So either: 1) I have a rogue DHCP server on my network - worrisome 2) The sb2 gave up on the DHCP and fell back to a default address - please don't. If this is really useful to anyone, please change the message in that case from obtained from DHCP to fell back to default IP In any case, my sb2 shows this behaviour every second reset. C. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] sb2 DHCP problems
On May 12, 2005, at 5:16 AM, Christian Pernegger wrote: It seems to me that the sb2 does not honor the lease-time of a DHCP lease, i. e. when a lease has run out it won't rerequest a lease or stop using the address. Rather, it will continue using the IP it got during network setup indefinitely. IIRC I've reported the problem some time ago. In the meantime I've changed the lease to never run out :) But today I had to restart the sb2 because of an access point update. It took quite some time for the DHCP request (normally it's instant) and then obtained the IP 169.254.188.141. That's a link-local address. If the DHCP request times out, it will use a 169.254.x.x address until DHCP succeeds, at which point it will switch to the new address. Some questions for you: 1. What DHCP server are you using? (Built into a router or running on a server somewhere? Version number?) 2. Do you have the ability to capture a packet trace of the DHCP request/response? 2) The sb2 gave up on the DHCP and fell back to a default address - please don't. If this is really useful to anyone, please change the message in that case from obtained from DHCP to fell back to default IP This is a good suggestion, there should be some visible feedback when this happens. -dean ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] sb2 DHCP problems
Is there a suitable sniffer for this in Debian testing / could you give me an appropriate command line for the info you need? Sure: sudo tcpdump -w dhcplog.pcap Will dump all the TCP traffic to the file dhcplog.pcap If you can capture the DHCP failure there, we can look at that file and see what's going on. It refuses to misbehave in front of the camera :( I have a nice capture of the worked flawlessly case now, though, including a syslog fragment. Will keep trying. C. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
