Bugzilla – Bug 9264
SB3 wireless disconnect issues with Billion router (WPA2)
Last modified: 2009-06-17 09:35:36 UTC
Customer has a Billion BiPAC 7401vgp-m Router. I have been working with this customer to help him get his SB3 connected to it wirelessly but it will only connect with encryption turned off. With WPA2 turned on the SB3 will not connect.
James to help me acquire, maybe this: http://www.lhdigital.co.uk/product_info.php?language=en¤cy=USD&products_id=10459 Anoop to follow up if router is up to date with firmware.
Looks like this ADSL Modem is ONLY available in the UK. We are unable to acquire one here for testing or evaluation. Maybe Richard will have better luck in getting one for evaluation.
SB3 initially connects to the Billion router with WPA2, but after a short time continually loses and re-establishes connection with it.
see RN ticket# 080807-001665
Info from Customer Ticket: -------------------------- System ------- * PC running ubuntu gutsy * Billion 7401VGPM access point, with WPA2 encryption, not broadcasting SSID * Squeezebox v3 with firmware 101 * Squeezecenter 7.1, installed from repo. Things I've tried ----------------- * stopping apparmor and restarting SC (bug 7580, bug 8046) * restarting router * power cycling SB * used wired ethernet connection instead of wireless. * pinging SB ------------ Connecting the SB via an ethernet cable does fix the problem I've been seeing. During testing I didn't see any regular disconnections from squeezecenter. Things I noticed: 1. Every time a new track is played the player IP stays the same but the port number changes. Is that expected? I then updated the firmware of my Billion Bipac7401vgpm router to the latest version to see if that fixed the problem I've been seeing when using wireless connection. Results: 1, SB connected to the network fine. 2. At first use the SB seemed to operate OK, with no blank screens and re-connection. However the was the occasional lag in responsiveness when pressing buttons on the remote. 3. After rebooting my PC the blank screens and re-connection problem started again. The time between disconnections doesn't seem to be regular like before. Also the time taken to reconnect varies too. It happens even if none of the buttons are being pressed on the remote. Could the player be having trouble going into screensaver mode? ---------------- As far as I know there is no firewall software running on my machine. I'm running a standard (up-to-date) ubuntu 7.10 OS. I have never explicitly installed any firewall software. Further testing results ----------------------- Router setup: -broadcasting SSID for wlan -using routers DHCP server 1. Re-connected the SB3 via ethernet cable to the router, PC connect via wireless (WPA2) to router. Factory reset the SB3 and. Experienced no connection failures after using for approx 20m. 2. Disabled the security on wlan (no encryption), connected PC via wireless, factory reset the SB3, connected the SB3 via wireless. Experienced no connection failures after approx 10m of testing. 3. Enabled WPA encryption on wlan, restarted router, connected PC via wireless, factory reset the SB3, connected SB3 via wireless. SB3 initially connected to the network fine, but I experienced many irregular connection failures to squeezecenter. During operation the SB3 reports that connection timed out, screen then blank and displays "connecting to squeezecenter" when a remote button is pressed. Pinging the SB3 during these disconnections results in lost packets. SB3 is unusable in this state. 4. Enabled WPA2 encryption on wlan, restarted router, connected PC via wireless, factory reset the SB3, connected SB3 via wireless. Same results as test 3 Notes: -using lastest router firmware. -server.log file only shows some dns (name resolution) errors when first started, probably because the PCs wireless network is still authenticating when squeezecenter starts. -problems I'm seeing sound very similar to several forum posts http://forums.slimdevices.com/showthread.php?t=50517 and a duet connection problem that i can't find at the moment. What now? I don't want to run and insecure network, just to get SB3 to work. SB3 is supposed to work with WPA2. ------------- Below is a link to another forum thread that I think describes a problem that is similar to mine. Difference being that I have a SB3. http://forums.slimdevices.com/showthread.php?t=45031&page=26 ------------- When I turn encryption off, the connection issues go away. Also, when encryption is turned on, and SB3 is connected to squeezenetwork, the connection issues also go away (seams to only be an issue with SC) -------------
Investigating the possibility of getting a router from one of these sources: http://www.shopbot.com.au/p-36502-487138.html
Thanks James for your help. I put a request in with bectechnologies.net, I will update this bug as soon as I can.
(In reply to comment #5) > Also, when encryption is turned on, and SB3 is connected to squeezenetwork, the > connection issues also go away (seams to only be an issue with SC) Anoop / Dan please check in on this. If this is the case, this is not a router bug... It sounds as though the customer might actually just be having a SqueezeCenter issue. We do have issues with AppArmor but workarounds are documented in the forums. Suggest the customer run SqueezeCenter on another PC if it is an option.
Ping support. I believe I have one of these units on the way soon, however this may only be to confirm my hypothesis in comment #8.
Ross: wrote customer back asking if he installs SC on another PC if he is able to connect. WIll keep bug updated with the results.
I already asked the customer this, but he has gotten rid of the Billion router... "I have replaced my billion router with a netgear router using wpa (doesn't support wpa2) and PC and SB work flawlessly. This would suggest it's not a problem with the squeezecenter server running on my PC..."
Dan / Anoop: Given that the customer has now upgraded his router, I will be marking this bug as "monitor", then stopping all active support until we are able to get the appropriate router. Ross: Please add the appropriate notes in the Router Wiki.
I haven't got rid of my billion router, I'm just borrowing the netgear router and plan use the billion when I get confirmation that there is nothing wrong with it. The billion is meant to be a more powerful unit than the netgear and there are a lot of user here in Australia, so it would be useful to do some testing on it.
(In reply to comment #13) > I haven't got rid of my billion router, I'm just borrowing the netgear router > and plan use the billion when I get confirmation that there is nothing wrong > with it. The billion is meant to be a more powerful unit than the netgear and > there are a lot of user here in Australia, so it would be useful to do some > testing on it. > It will probably be at least a week or two, perhaps longer until I have some Billion hardware to test here in the office. As I've mentioned a couple times now, I suspect there is more to the problem you're experiencing than a wireless router issue. Please work with Anoop I think you should start by trying to track down a potential SqueezeCenter issue. Is SqueezeCenter running? Firewall? Do you have any other PCs you can run SqueezeCenter on temporarily just to diagnose this issue?
I've just received word from another of our Australian users which clearly indicates that we have some sort of wireless encryption connectivity problem with the Billion 7401-vgp-m. Thank you Cameron. Ross to acquire and test.
Karl how frequently do you experience disconnect issues with your Billion? I finally got a hold of BiPAC 7401VGPR3 and I can't reproduce any problems. I've been streaming to an SB3 for about 4 hours without any issue.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
I'm still not able to easily reproduce this with Duet or SB3. Karl could you please offer me any other tips? Roughly how long do you have to wait until you see a problem on average? Also please note this is an SB3 bug, not specific to Controller or SqueezeOS.
Fixed in 7.3.3 - r5225. If you've experienced this bug please update to latest nightly 7.3.3 build. Install the new version of SqueezeCenter, update your Duet firmware, factory reset both Controller and Receiver and setup one more time. Please post here in the bug with your findings. 7.3.3 nightly download here: http://downloads.slimdevices.com/nightly/?ver=7.3
Correcting target milestone to 7.3.3.
Sorry should have marked this as fixed with other busybox / mini_fo related issues.
Verified fixed in r5497.
This bug has been fixed in the 7.3.3 release version of SqueezeCenter! If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.