Hi, I got a new accesspoint. Unfortunately, my OS 13.2 laptop can't connect to it. With older accesspoints I don't have problems. Is there any way to debug this ? I'm using Network-manager. Other computers can connect without problems. lspci on my laptop gives this : 45:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Please ask if other info is needed. TIA, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 31-10-16 om 15:14 schreef James Knott:
On 10/31/2016 09:56 AM, Koenraad Lelong wrote:
Please ask if other info is needed.
Well, a description of what happens might help.
well, In Networkmanager I click on the SSID. The passphrase is asked. After a while Network-manager gives up and reconnects to my old accesspoint. Actually, I just solved my problem, I hope. I let the accesspoint choose its channel ( -> 6) although I know there is interference in the middle of the 2.4GHz band. Since other computers could connect I suspected my laptop (and a raspberry pi). I just changed the channel to channel 1, now I can connect. Strange, because my phone and two other laptops have no problems connecting to the accesspoint. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/31/2016 07:33 AM, Koenraad Lelong wrote:
Op 31-10-16 om 15:14 schreef James Knott:
On 10/31/2016 09:56 AM, Koenraad Lelong wrote:
Please ask if other info is needed.
Well, a description of what happens might help.
well,
In Networkmanager I click on the SSID. The passphrase is asked. After a while Network-manager gives up and reconnects to my old accesspoint.
Actually, I just solved my problem, I hope. I let the accesspoint choose its channel ( -> 6) although I know there is interference in the middle of the 2.4GHz band. Since other computers could connect I suspected my laptop (and a raspberry pi). I just changed the channel to channel 1, now I can connect. Strange, because my phone and two other laptops have no problems connecting to the accesspoint.
Koenraad.
I wonder if it has more to do with the mode the access point is running in than the channel? In many APs even one 801.11G connection forces the whole operation to G, and N goes out the window. Depending on the vintage of your laptop, it may, or may not have 5ghz as well as 2.4ghz, or only 2.4ghz bands. This while still advertising itself as a BCM4313. Given yours is rev 1 I suspect you have only 2.4ghz. If your new AP has both bands, that doesn't mean they work equally well, nor does it mean that the AP is set up to use both bands. Most 5ghz capable devices will preferentially connect using that band and fall back to 2.4. Some early drivers did not properly fall back, and some early APs would improperly respond on 5ghz to 2.4ghz connection attempts. When was the last time you installed the firmware for your laptop's BCM4313? Does the new AP have newer firmware on the manufacturer's site? I doubt you've solved this problem, I suspect you just got lucky, and I predict it will be back to haunt you. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/31/2016 01:46 PM, John Andersen wrote:
In many APs even one 801.11G connection forces the whole operation to G, and N goes out the window.
A client should connect, no matter whether it's g or n. Also, any AP that slows down entirely to g is in violation of the spec. When there is a g device nearby, the header is transmitted at g, but the rest of the frame can still go at n. This is so that the g devices know how long the channel will be used for the transmission. Beyond the slower header there should be no difference. This contrasts with when there's a b device present, in which case the g or n device has to send a b frame to reserve the channel long enough to send the g/n frame. This is necessary, as b uses a completely different modulation method than g & n and can't receive the headers. That is also why having a b device nearby hurts g/n performance so much. However, it's best to configure an AP to whatever you expect to connect. These days, it could be n only or g & n, if you have older gear. Anything that runs b only should be tossed. In fact, if you have an AP that's configured to support b, it can't use n, as the spec requires n to use WPA2, which b doesn't support at all. My home AP is configured for n only, as all the devices I use support it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
James Knott -
John Andersen -
Koenraad Lelong