LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 02-07-2007, 01:42 PM   #1
aw_wolfe
Member
 
Registered: Apr 2005
Posts: 50

Rep: Reputation: 15
Unhappy upgrade from fc4 to fc6 and now broadcomm 4306 not working


I had a broadcom 4306 wireless card working fine in fedora core 4 using ndiswrapper. Recently I upgraded to fc 6 (using anaconda updater) and then the wireless card would recieve error when I tried to activate using gui...unable to obtain ip...

what I've done so far....
installed latest version of ndiswrapper
blacklisted bcm43xx

ndiswrapper -l tells me driver installed and present

wlan0 still listed in network gui with all previous settings
Verified alias wlan0 ndiswrapper in both etc/*.conf files

dmesg lists card working fine.

iwconfig report ok, except AP: Invalid (using essid non-broadcast, so do not remember if this is normal)

AP and card do work, using them now to write this on windows boot.

Any suggestions? Anything else different to occur when upgraded to FC6

Thanks,

Tony
 
Old 02-09-2007, 06:58 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
using essid non-broadcast, so do not remember if this is normal
I would broadcast the SSID simply because it sometimes makes a difference and the security "boost" you get from not broadcasting it is a joke.

Quote:
iwconfig report ok, except AP: Invalid
No, that's not OK. If it isn't finding the AP, then it is possible that the config is not correct. It would be helpful if you can post the output of iwconfig.

Also, check to make sure bcm43xx is NOT loaded (run lsmod and see if it is there). If the blacklist is failing for some reason, that might cause this problem.

Finally, when you installed ndiswrapper, did you do it from source or did you grab the latest RPM?
 
Old 02-10-2007, 09:43 AM   #3
aw_wolfe
Member
 
Registered: Apr 2005
Posts: 50

Original Poster
Rep: Reputation: 15
Thanks for the help. Not sure why, but finally got it working. Think that it had to do with the blacklist not reloading until I rebooted. Once that seemed to work, I was able to re-install ndiswrapper without too much difficulty and now everything seems to be working well.

Is there a specific reason why not broadcasting ESSID isn't that good of an idea? Is it still easy to scan for networks that are not broadcasting essid?

Thanks,

Tony
 
Old 02-10-2007, 10:51 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,785
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by aw_wolfe
Thanks for the help. Not sure why, but finally got it working. Think that it had to do with the blacklist not reloading until I rebooted. Once that seemed to work, I was able to re-install ndiswrapper without too much difficulty and now everything seems to be working well.
Yeah, unless you manually removed the module with modprobe, it isn't going to unload until a reboot. Just adding a module to the blacklist doesn't do anything by itself.

Quote:
Originally Posted by aw_wolfe
Is there a specific reason why not broadcasting ESSID isn't that good of an idea? Is it still easy to scan for networks that are not broadcasting essid?

Thanks,

Tony
People seem to think that if they don't broadcast their SSID that their access point can't be found. That may be true for some of the trivial wireless scanning tools out there, but for the stuff that you have to worry about (like aircrack or kismet) not broadcasting your SSID does absolutely nothing. They can find you anyway. Instead you need to implement WPA encryption. If for some reason you can only use WEP, that is better than nothing and will keep the casual snooper out.
 
Old 02-10-2007, 10:54 AM   #5
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
Some configurations have difficulty connecting when the SSID broadcast is disabled - WPA configs in particular.

Even with the SID broadcast off, you're still broadcasting. The AP or router simply transmits a null instead of a name field. Any wireless tool worth a damn will still see your network. The SSID will show up eventually, or can be forced to reveal itself with a probe request.

Anyone fooled by SSID broadcast disable was no threat to your network.

edit: Hangdog beat me. I need more coffee.

Last edited by 2Gnu; 02-10-2007 at 10:55 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel issues after upgrading FC4 to FC6 rodrigo_tomita Fedora 4 09-13-2007 04:27 PM
upgrade FC5->FC6? Not working at here! GL1800 Fedora 6 12-12-2006 08:52 AM
FC4 vrs FC6 - performance Jose Rivas Fedora 1 11-15-2006 06:40 PM
FC6 beta3 upgrade to Final FC6 thyraios Fedora 1 09-18-2006 07:55 PM
Samba stopped working after FC3 to FC4 upgrade HomeBrewer Linux - Networking 18 08-29-2006 02:13 AM


All times are GMT -5. The time now is 07:14 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration