Bug 2730 - Getting allocated 169.254.x.x addresses
: Getting allocated 169.254.x.x addresses
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 28
: PC Windows XP
: P2 major (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks: 2997
  Show dependency treegraph
 
Reported: 2005-12-19 10:08 UTC by Jim Willsher
Modified: 2008-12-18 11:38 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Willsher 2005-12-19 10:08:00 UTC
DHCP server on my LAN (DrayTek Vigor 2800). All other devices (2 wireless laptops, SB1, Sony PSP, 2 hard-wired desktops) all get DHCP addresses correctly. SB3 frquently accepts a 169.254.x.x address, and the DrayTek shows that no attempts were made to request an address.

With the 169.x address the player is unusable.

Wireless strength is excellent (around 88%).

Rebooting etc. changes nothing. I have seen slight improvements by adding a DHCP Reservation to the DHCP server.

Jim
Comment 1 Matt Sisk 2006-02-13 12:46:05 UTC
I'm seeing this behavior as well, sometimes. I've made the problem go away sometimes by rebooting my router, but this doesn't work always. I eventually gave up and hard-coded the info into the squeezebox.

My theory is that maybe the squeezebox is binding to a neighbor's wireless network for DHCP info.

Is there an easy way to verify what the squeezebox is actually doing during the DHCP request?

Cheers,
Matt
Comment 2 KDF 2006-02-13 12:50:14 UTC
Please make sure you have tried the 6.2.2 nightly builds with FW v29 and not just fw28 as selected above on this report.  Also, contact support@slimdevices.com so that they may collect details about your setup.
Comment 3 Blackketter Dean 2006-02-15 12:08:23 UTC
The issue here is that the player thinks its connected to the wlan before authentication has completed and this is causing DHCP to start before there's connectivity.  Awaiting a patch from Ubicom to notify the UI that the link is actually up and we have authenticated.
Comment 4 Richard Titmuss 2006-04-05 13:22:47 UTC
I have a fix that should appear in firmware 37.  Will update this bug when it's available for download.
Comment 5 Richard Titmuss 2006-04-06 06:05:26 UTC
Please try the latest nightly build with Firmware 37 and reopen if you have
issues.  Also, please note details of your configuration if you have not
already.