Bugzilla – Bug 12933
Can't connect to wireless except with AES encryption
Last modified: 2009-09-08 09:32:01 UTC
As of a few days ago, the Baby will not connect to a wireless network unless it uses AES encryption only. I need TKIP for compatibility with other devices on my network. I was working with Baby before. Seems to have broken around the 15-16th. I have a Buffalo router running Tomato firmware, but there are other reports in the forum of this problem with Netgear routers.
Sue do you remember which firmware version was on baby when you saw this?
I don't remember the firmware version, but I'm pretty sure the last day I used it was Thursday the 16th, so it was probably whatever firmware came out after that.
A change I made to support hidden ssids broke all APs using 'TKIP' or 'TKIP and AES'. Only 'AES' only was still ok. This should be fixed in r6674 onwards. Could you please retest when newer firmware is available and report back to this bug? Thanks Felix
Please reopen if you still see issues with newer firmware, thanks.
Sorry, due to a file not being deleted on the build machine the fix didn't make it for the revision stated earlier. It should be fixed in r6711 onwards though. Felix
I reproduced that 6633 cannot connect to TKIP but can connect to AES, waiting for bug 12970 to be fixed so I can verify the fix.
Verified baby now connects TKIP with r6729. Sue, yours working now too?
Will let you know when I get that version.
With r6758 I can't connect to wireless with any combination of WPA/WPA2/TKIP/AES. Even AES only that was working before is not working now. Note I just went through network setup without factory reset. If need be, I will try it from factory reset when I have more time.
Scary! Sue please do factory reset and let us know how that goes.
got it! Factory reset did the trick.
I am unable to connect with 6758, even after factory reset. PIN, push button, and password methods all fail. (although push button, according to my router's control panel, it's connected..) Network Name (SSID) : Burlesque Wireless Security : Configured Network Authentication : WPA+PSK Data Encryption : TKIP
Hello Fred Thank you for the feedback. - What router model, firmware are you using? - What wireless channel uses your router? - Could you power cycle your router and see if that helps? - Did Baby (with earlier firmware) ever connect to that router? - Have you tried (temporarily) to disable security on your router? Thanks Felix
Reset priority before triage.
(In reply to comment #13) > Hello Fred > > Thank you for the feedback. > > - What router model, firmware are you using? > - What wireless channel uses your router? > - Could you power cycle your router and see if that helps? > - Did Baby (with earlier firmware) ever connect to that router? > - Have you tried (temporarily) to disable security on your router? > > Thanks > Felix I'm using Belkin F5D8236-4v1(01) Channel 11. I have restarted my router and had no luck. I've never had Baby connect wirelessly to this router before, but I did have it connected to my netgear for a while with AES. Interestingly, now (as of this firmware, but not before) I can connect with AES. I just tested the pushbutton method with these settings: Network Name (SSID) : Burlesque Wireless Security : Configured Network Authentication : WPA2+PSK Data Encryption : AES AES Currently working. Still no luck with TKIP.
(In reply to comment #15) > (In reply to comment #13) > > Hello Fred > > > > Thank you for the feedback. > > > > - What router model, firmware are you using? > > - What wireless channel uses your router? > > - Could you power cycle your router and see if that helps? > > - Did Baby (with earlier firmware) ever connect to that router? > > - Have you tried (temporarily) to disable security on your router? > > > > Thanks > > Felix > > I'm using Belkin F5D8236-4v1(01) > Channel 11. > I have restarted my router and had no luck. > I've never had Baby connect wirelessly to this router before, but I did have it > connected to my netgear for a while with AES. Interestingly, now (as of this > firmware, but not before) I can connect with AES. > > I just tested the pushbutton method with these settings: > Network Name (SSID) : Burlesque > Wireless Security : Configured > Network Authentication : WPA2+PSK > Data Encryption : AES > > AES Currently working. Still no luck with TKIP. Sorry I was a little vague, to clarify, I'm able now, but not before this firmware, to connect to the belkin with AES, not TKIP.
QA to reproduce with this router.
I'm not able to reproduce this with the WPS Belkin I have here (F5D8231-4) I'll pick up the exact model you have and try it. Fred, have you tried connecting baby without using the push button method? Factory reset baby and try connecting to your SSID, you'll see 3 options push button, PIN, and enter password. Try the 3rd option and let me know if that connects.
Also, when you did the factory reset did you see the 'Factory reset' screen and then are back at the language selection screen (i.e. begin of setup)? I am specifically asking this again, because a bad configuration file needs to be replaced and that only happens when a factory reset really takes place. BTW: A factory reset can be done either by pressing and holding button More (+) on the front panel while plugging in power or by going to Settings - Advanced - Factory Reset - Continue. Thanks
I'm pretty certain I did a factory reset before trying each of the three methods. I will try again tonight and report back.
I have just tested and confirmed: I cannot connect to: Network Name (SSID) : Burlesque Wireless Security : Configured Network Authentication : WPA+PSK Data Encryption : TKIP Even after a factory reset between. I also tested another router: Belkin: Firmware Version 4.05.03 Boot Version 2.01.09 Hardware F5D7231-4 It has multiple options: WPA-PSK - AES, and WPA-PSK TKIP, it does not support WPA2. I cannot connect with either setting. I can connect to the F5D8236-4v1 with WPA2-AES.
I'm not able to reproduce any AES related connection issues at this time. It appears Fred may have identified a particular older Belkin router we have issues connecting to. I've opened a bug for that specific bug and I'm going to close this bug as it appears to be resolved. Bug 13223 is the F5D7231-4 specific bug.
(In reply to comment #22) > I'm not able to reproduce any AES related connection issues at this time. It > appears Fred may have identified a particular older Belkin router we have > issues connecting to. I've opened a bug for that specific bug and I'm going to > close this bug as it appears to be resolved. > > Bug 13223 is the F5D7231-4 specific bug. I'd like to clarify that I'm having issues with two different models (I've tested them seperately). -F5D8236 WPA TKIP does not connect -F5D7231 WPA TKIP does not connect -F5D7231 WPA AES does not connect I'll post this on the other bug report