Re: Not automatically connecting to a previously configed wifi connection
Ken,
The WAP54G is HW version 2
You are not logged in. Please login or register.
Welcome
Not automatically connecting to a previously configed wifi connection (Page 2 of 3)
chumbysphere forum → Chumby, the Device → Not automatically connecting to a previously configed wifi connection
Posts: 26 to 50 of 73
Re: Not automatically connecting to a previously configed wifi connection
Any progress? Any other info I can send?
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Nothing else for now - we need to try to reproduce your situation with the hardware we have.
I see some indication of some other Linux distributions having exactly the same problem, so we're reviewing if it's the same issue, and if so, how it was addressed. It's possible this is a wifi driver bug specifically associated with this chipset.
Re: Not automatically connecting to a previously configed wifi connection
Thanks for the update. It is a bit of showstopper for us, hopefully it will end up being an easy and quick fix.
Re: Not automatically connecting to a previously configed wifi connection
Duane,
Just checking in to see if there is any progress?
Thanks
-Sam
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Not so far - this is a tough thing for us to reproduce.
Re: Not automatically connecting to a previously configed wifi connection
Duane,
Have you guys got it reproduced at least once? Would it help to send you our access point to help reproduce this? We have about 15 Chumbys we are sitting on waiting for this to get resolved.
Also you mentioned that another Linux distribution had a similar problem do you know which distribution that is?
Let me know how we can help
-Sam
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
I found references to the exact same problem in Debian and Ubuntu, circa 2007. That would be consistent with the general age of the driver we're using.
No, we haven't been able to reproduce the problem so far.
Re: Not automatically connecting to a previously configed wifi connection
Is there a newer driver? Could we build it and test it out here on our setup?
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Unfortunately, it's not that easy - there are newer drivers for this part, however, they require newer kernels.
Re: Not automatically connecting to a previously configed wifi connection
We can test a new kernel/driver should not be an issue. We can pull a different SVN tree and build on our side if that helps.
Re: Not automatically connecting to a previously configed wifi connection
I have the same issue with wifi connections. I've only ever connected to one wifi source, so it's the only one on my list. But frequently I get the "do you want to connect to an existing source or a new one?" dialog when I power up my Chumby. I thought this might be related to the way my router is set up (it hides the wireless signal when it's not in use so my wireless devices have to specifically seek it out).
- PaperClippy
Blue Buddy- Offline
Re: Not automatically connecting to a previously configed wifi connection
Actually that's a good point!
In addition to my AP running encryption it is also non-broadcasting.
When I get the "select an AP" screen from memory it does show me both my AP and my pesky neighbour's AP as well
Re: Not automatically connecting to a previously configed wifi connection
PaperClippy wrote:
Actually that's a good point!
In addition to my AP running encryption it is also non-broadcasting.
When I get the "select an AP" screen from memory it does show me both my AP and my pesky neighbour's AP as well
Getting the same problem with my Chumby too and came here to see if there was a fix. Apparently, this is a pesky bug to track down and hasn't been squashed yet.
I've had to delete my AP config from the Chumby and reconfig it to get it to connect. Hopefully that won't be every time I power this guy on as my WPA shared key is LONG.
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Yours won't connect even when selected an existing configuration and you have to reenter everything again? If so, that's not the same issue as the rest of this thread, which seems to revolve around two issues:
1) Devices not connecting on boot to the current configuration
2) Devices attempting to connect to the *wrong* access point, despite the configuration
In these two cases, devices are able to connect after boot by selecting the configuration. What you appear to be describing is new behavior, which is that a saved configuration doesn't work at all. Is this correct?
Re: Not automatically connecting to a previously configed wifi connection
I think it was #2 Devices attempting to connect to the *wrong* access point, despite the configuration.
As a quick test I deleted my network config, rebooted and it connected fine to my access point. Weird. So in short, I guess I need to do some more testing to get it to fail on repeatable set of steps. I'll come back and post that when I get them together.
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
If you suspect that it's attempting to associate with the wrong AP, please confirm that by taking the same steps that samkwitty has taken to collect information using a dongle. In particular the output of the iwconfig command will confirm this.
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
samkwitty - you said in an earlier thread that you were able to reproduce this behavior at home. Could you please collect the same information on *that* network - that would be helpful to us to try to reproduce this.
Unfortunately, updating the kernel is a multi-man-month project - it's often easier to backport. Until we are able to reproduce the issue, it's all speculative since we can't know we've actually solved anything.
Re: Not automatically connecting to a previously configed wifi connection
Duane,
My setup is slightly diffrent. My access point "Radio" does not brodcast its SSID.
My access point is Linksys WAP54G (I have sent you the full info before)
Here is the data you asked for:
chumby:/mnt/usb/bug# cat ifconfig.txt
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:117 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12630 (12.3 KiB) TX bytes:12630 (12.3 KiB)
rausb0 Link encap:Ethernet HWaddr 00:1D:0F:B2:1D:F1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6983 (6.8 KiB) TX bytes:4716 (4.6 KiB)
------------------------------
chumby:/mnt/usb/bug# cat iwconfig.txt
rausb0 RT73 WLAN ESSID:"Radio"
Mode:Managed Frequency=2.412 GHz Access Point: 00:12:17:6F:86:7E
Bit Rate=9 Mb/s
RTS thr:off Fragment thr:off
Encryption key:4F25-46A8-25
Link Quality=49/100 Signal level:-70 dBm Noise level:-107 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
------------------------------
chumby:/mnt/usb/bug# cat iwlist.txt
rausb0 Peers/Access-Points in range:
00:12:17:6F:86:7E : Quality:75/100 Signal level:-64 dBm Noise level:-107 dBm
------------------------------
chumby:/mnt/usb/bug# cat network_status.txt
<network>
<interface if="rausb0" up="true" link="true" gateway="">
<stats rx_bytes="6983" rx_packets="90" rx_errs="0" rx_drop="0" rx_fifo="0" rx_frame="0" rx_compressed="0" rx_multicast="0" tx_bytes="4716" tx_packets="28" tx_errs="0" tx_drop="0" tx_fifo="0" tx_colls="0" tx_carrier="0" tx_compressed="0" wifi_link="49." wifi_level="186" wifi_noise="149" />
<error>failed to obtain IP address</error>
<error>chumby.com is unreachable</error>
</interface>
<configuration gateway="" ip="" nameserver1="" encryption="WEP" key="[MY WEP KEY]" hwaddr="00:12:17:6F:86:7E" nameserver2="" auth="WEPAUTO" netmask="" type="wlan" ssid="Radio" allocation="dhcp" encoding="hex" />
</network>
------------------------------
chumby:/mnt/usb/bug# cat iwlist_scan.txt
rausb0 Scan completed :
Cell 01 - Address: 00:12:17:6F:86:7E
ESSID:"Radio"
Mode:Managed
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 54 Mb/s
Quality:75/100 Signal level:-64 dBm Noise level:-107 dBm
Cell 02 - Address: 00:18:39:96:A2:FE
ESSID:"CHAMBERLAIN"
Mode:Managed
Channel:7
Encryption key:on
Bit Rates:1 Mb/s; 6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s; 2 Mb/s
5.5 Mb/s; 11 Mb/s
Quality:67/100 Signal level:-72 dBm Noise level:-107 dBm
------------------------------
chumby:/mnt/usb/bug# cat ap_scan.txt
<aps>
<ap mode="Managed" encryption="WEP" channel="1" hwaddr="00:12:17:6F:86:7E" auth="WEPAUTO" linkquality="-64" signalstrength="75" ssid="Radio" noiselevel="-107" />
<ap mode="Managed" encryption="TKIP" channel="7" hwaddr="00:18:39:96:A2:FE" auth="WPAPSK" linkquality="-72" signalstrength="67" ssid="CHAMBERLAIN" noiselevel="-107" />
</aps>
------------------------------
chumby:/mnt/usb/bug# cat link-status.txt
1: STATUS=0 NETWORK=INFRA SSID=<Radio> AUTH=UNKNOWN ENCRYPT=WEP KEY=wep64[<MY WEP KEY>]
------------------------------
chumby:/mnt/usb/bug# cat mlme-aux.txt
BssType=2 Bssid=[00:12:17:6f:86:7e] Ssid=<> AutoReconnectSsid=<Radio>
Alg=1 ScanType=18 Channel=0 Aid=2 CapInfo=0x11
BeaconPeriod=100 BssIdx=0 RoamIdx=0 CurrReqIsFromNdis=0Re: Not automatically connecting to a previously configed wifi connection
Duane -- Any luck tracking this down?
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Sorry, no. We have another device that we *thought* was doing the same thing, but it turns out it wasn't.
Re: Not automatically connecting to a previously configed wifi connection
Duane,
Can you give me a sense if this is something that will get fix in the near future or not at all?
Thanks
-Sam
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
Unfortunately, there's no way to know - if we can't reproduce it, we can't diagnose it, and therefore can't fix it.
I've even got a setup at home that's not too different from yours - an old 802.11b-only AP and a couple of faster 802.11g APs, with three chumbys, and they're not failing for me.
So, we're stumped at the moment, but this problem does have our attention.
We had a bug related to a time drift that was also a head-scratcher - it affected only a very small number of people and was very tough to reproduce. Eventually, the planets aligned and we were able to see it on a single unit in the office, and it was fixed within a day or so. Hopefully that will happen here.
Re: Not automatically connecting to a previously configed wifi connection
Duane,
I am happy to send you are access point and one of our Chumby's that is doing this consistently.
-Sam
- Duane
- Blue Octy
- Offline
Re: Not automatically connecting to a previously configed wifi connection
I'll talk with Customer Support to see if that works. Please send me an email from the forum.
Posts: 26 to 50 of 73
chumbysphere forum → Chumby, the Device → Not automatically connecting to a previously configed wifi connection
Powered by PunBB, supported by Informer Technologies, Inc.