Broadcome wireless network spottly accesses my WPA-protected network
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Broadcome wireless network spottly accesses my WPA-protected network
Hello.
All through this (and others) forum I have read just so many threads about the WAP/Broadcom issues. Basically, the latter will not access, but my case is slightly different.
My system DOES connect the protected w-network via Gnome Network Manager, but only after several attempts (sometime at 1st-2nd attempt, sometime after tens of attempts I just grow tired and give up ...).
By means of WiCD (which, on its side never makes it) I have discovered that the problem is not on the security stage, but while receiving the IP address from the DHCP server.
(It also happen to drop connection relatively easily (compared to Win), but this I guess is a secondary problem)
I use Sabayon Linux on an HP Pavillion, with obvious Broadcom w-network (eth1). I use a w-bridge to extend the newtork availability from a Netgear router. No issue is reported with wireless when using Win.
I have the same kit. Broadcom 4312 in a HP laptop (HP Compaq 6715S) If you type in iwconfig wlan0 at any point while connected, you can see signal strength. If you're disconnected, iwlist wlan0 scan |less
does show it also.
Find out what level you disconnect at, and I'll try to duplicate here. You could have plenty of noise, or a competing wifi link on the same channel. It may be as simple as changing modem channel. You may do better to set up with iw-tools on bopotup, instead of using network manager - it is a royal PITA sometimes.
Ok. 2 wirweless sources? Are you going from one to the other?
I would check /etc/wpa_supplicant/wpa_supplicant.conf and make sure you have both cells and both keys in there, as well as all the protocols pask,tkip, ccmp
The best kept secret in this is wpa_passphrase. Run that (Man wpa_passphrase), and put the output in as your key.
No, it was a mess I must have made with Network Manager.
Due to frustration, I had made an attempt my manually setting my Wireless network ("Pian Family Wireless Network"); NM must have added it to the one already automatically recognized, so it actually is the same one doubled.
Well, I have checked it out... and /etc/wpa_supplicant/wpa_supplicant.conf does not even exist.
The only thing present into the above directory is a script: wpa_cli.sh
On wpa_supplicant.conf, Slcakware puts it in /etc, Fedora in /etc/wpa_supplicant. Your friend is
man wpa_supplicant.conf
But you are connected. The first rule in my business (hardware) is
"If it ain't broke, don't fix it!"
Thank you, I will inspect the man file as soon as I get back home.
Yes, I am connected, but as I mentioned above, my system takes several (frustrating) attempts before achieving that... last night, for instance, after 20 attempts it was still not able to get IP, so I grew fed up and went to sleep...
This is a sign that there must be a some systematic mistake in my settings, which makes my connection getting an IP correctly dependent on a random parameter that I cannot identify.
It is not possible that Win connects right away at start-up, and Linux shows these problems, on the same laptop!
1) I have found out why two wireless seem present : since I am using a wireless bridge as range extender due to house walls, my laptop now reports the presence of the same network twice. One is the bridge signal (stronger), and the other is the DSL router signal (weaker).
2) I have gone through the wpa_supplicant.conf example file and man, and this is the file I have composed then:
Make sure you have run your key through wpa_passhphrase
wpa_passphrase Your_Essid Your_Key
It willo give you a totally different string, abnd use that in the conf.
To use it,
ifconfig wlan0 up
iwlist wlan0 scan |less. Then pick out your essid, and run a mouse over the mac address of the access point
iwconfig essid Your_Essid ap <paste mac address> ap
Iwconfig wlan0 should now show you the magic word 'associated'. You are now on the router
dhcpcd (or dhclient) wlan0 should not get an ip for wlan0
It of course helps if Network Manager or dhcp are not already running, as they think they know better and may screw thiongs up automagically for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
...).
n
0
