Bug 2663 - Strange IP address/settings
: Strange IP address/settings
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:
  Show dependency treegraph
 
Reported: 2005-11-30 19:35 UTC by Brett Stark
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 Brett Stark 2005-11-30 19:35:57 UTC
See post to forums and possible suggestion:

Hi,

As posted separately, i do have probs with my wireless signal strength. However, i have noticed a couple of times now the squeezebox losing connection and then when i try to re-connect again; i check the settings and see that the squeezebox has some very strange settings:
- IP address not in my private subnet, 192.168.x.x
- mask 255.255.0.0 instead of 255.255.255.0
- can't quite remember if gateway or dns were screwed up also.

I have seen this several times on 2 different scenearios:
- when i was using my internet connection as normal,
- when i was connected via VPN to my work network.

Has anyone else seen this issue? The only way i can fix it is to do a factory reset and force it to get back basic settings (ie the mask) that will allow it to see IP addresses within my subnet. Very annoying.

Also, i have quite a few (atleast 3) other networks that i can see within my house which is wierd because i am in an old brick house, but whatever! I do think an improvement for the device though would be that you specify it to only connect to your particular SSID and to save that setting and that's it unless you specifically change it. I get the feeling that sometimes depending on wireless connections etc, it is getting confused and looking for settings on other networks.
Comment 1 Kevin Pearsall 2005-12-01 09:55:48 UTC
What model router are you using?  Are you using encryption?
Comment 2 Brett Stark 2005-12-01 11:09:17 UTC
i have a linksys wrt54gs router, am not using turbo mode, am using wpa
Comment 3 Blackketter Dean 2006-02-15 12:49:24 UTC
Brett:  what are the values that you are seeing change on your squeezebox?  What should they be?  More details would be most helpful.
Comment 4 Tyler 2006-03-20 07:37:55 UTC
I am experiencing the same exact problem as Brett.  I connect via a Microsoft MN-700 g-router to my office network via VPN, but all other wireless devices connect to my home workgroup are not having problems.  I replaced the SB3 that wouldn't connect with a second one that I ordered and it appears to be working fine.  How do I reset it so that it does a firmware search and gets back to the basic settings that will allow it to see IP addresses within my subnet?  I tried the factory reset procedure of plugging it in while holding Add (+), but that didn't wipe out the funky IP addresses.  This is extremely frustrating! 
Comment 5 Blackketter Dean 2006-03-20 08:01:46 UTC
Brett/Tyler: What IP addresses are you seeing?

Note:  to get back to the player setup, press and hold the LEFT arrow button for 5 seconds...
Comment 6 Tyler 2006-03-20 11:27:05 UTC
(In reply to comment #5)
> Brett/Tyler: What IP addresses are you seeing?
> Note:  to get back to the player setup, press and hold the LEFT arrow button
> for 5 seconds...

Here's what I'm seeing:
Connect via: wireless
Obtain IP address: Automatic (DHCP)
IP address: 0.0.0.0
Subnet mask: 255.255.255.0
Gateway: 0.0.0.0
DNS Server: 0.0.0.0
SSID: <name of my wireless network>
Wireless signal strenth: fluctuates every few seconds between 0-38-41-0-58-43-0-18-etc.
Wireless encryption: 128 bit
Bridge?: no
MAC address: ff f2 ff 00 00 03
Automatic upgrade: On
Firmware: 28

My other unit is able to get an IP address and connect to my server PC.  It also automatically updated to firmware v.35.  Signal strength is steady between 55-65%, which is not great, but it works. 

I turned off the Window XP software firewall and disabled worm protection on Norton just in case, but the working unit was able to connect even with these features enabled.
Comment 7 Richard Titmuss 2006-04-05 13:18:20 UTC
This sounds like a problem with the dhcp auto-ip address assignment. I have a fix that should appear in firmware 37.  Will update this bug when it's available for download.
Comment 8 Richard Titmuss 2006-04-06 06:05:24 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.