LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 12-12-2008, 02:28 AM   #16
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15

Update:
Really strange... If I set "wext", not ndiswrapper in wicd (so in wpa-supplicant), while I'm using ndiswrapper driver, it can authenticate with the router, however it can't get an ip, from dhcp . Using Broadcom's wl driver (and wext), it connects, authenticates, and gets az ip from dhcp, with no delay.
When using ndiswrapper driver, with ndiswrapper setting in wicd/wpa-supplicant, it cannot get through the authentication...
 
Old 12-12-2008, 07:30 AM   #17
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
If I set "wext", not ndiswrapper in wicd (so in wpa-supplicant), while I'm using ndiswrapper driver, it can authenticate with the router, however it can't get an ip, from dhcp . Using Broadcom's wl driver (and wext), it connects, authenticates, and gets az ip from dhcp, with no delay.
I suspect that the wpa_supplicant devs haven't been developing the ndiswrapper driver since wext should do whatever the ndiswrapper driver does. However, that doesn't explain why it doesn't get an IP address when using ndiswrapper and wext.

I can honestly say, you're having the strangest wireless problems I've seen in a long time. I wish I had some answers as to why!
 
Old 12-12-2008, 10:47 AM   #18
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15
Well...
I tried again, and sometimes (perhaps once / 5 try), it gets an ip via dhcp. So sometimes ndiswrapper works...
 
Old 02-04-2009, 08:19 AM   #19
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15
Since kernel 2.6.28, there is a new regulatory domain setting solution, crda. If I set iw set reg EU or HU, the card only sees 11 channel, however it should see 13. I have also set "cfg80211 ieee80211_regdom=EU" in /etc/modprobe.d/options, but still no luck. Is there any other way, setting the regdom value?
 
Old 02-04-2009, 11:59 AM   #20
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
I suggest you start another thread on that, I have absolutely no experience in setting regdom values, so all I could do would be to Google, which you've probably done already.
 
Old 02-04-2009, 04:36 PM   #21
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15
I've started a new topic because of the regdom problem:
http://www.linuxquestions.org/questi...module-702336/
 
Old 03-31-2009, 07:55 AM   #22
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15
JosipBroz: the ssid is not hidden, since under Vista I can see it, and also connect to it.
Update: the router seems to be an X-Micro XWL-11GRIX. I haven't found any linux-specific issues with it.
 
Old 04-26-2009, 02:13 AM   #23
muczy
Member
 
Registered: Nov 2003
Location: Üllés, Hungary
Distribution: Debian Linux amd64
Posts: 54

Original Poster
Rep: Reputation: 15
"Solved":
I have bought an Intel 4965 card, and it can see, and also connect to the AP.
The problem was, that the AP uses Channel 13 (b/g), but the broadcom wl driver simply can't change regulatory domains, so it can only operate in Channels 1-11 (b/g).
I really hate Broadcom...

With ndiswrapper, iwlist reported 14 channels, but it seems like hardware coded, or whatever. However in Vista, it can use channels 1-13...
 
Old 04-26-2009, 07:01 AM   #24
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
The problem was, that the AP uses Channel 13 (b/g), but the broadcom wl driver simply can't change regulatory domains, so it can only operate in Channels 1-11 (b/g).
I really hate Broadcom...

Wow. That is a new one. Yeah, nobody lives outside of the US, so why should their drivers support non-US standards. Thanks for posting this, you will definitely help others.
 
  


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
No scan results anymore with Broadcom BCM4312 LordFrancis Linux - Wireless Networking 8 10-04-2008 10:15 AM
help bcm4312 and b43 driver darkangel29 Linux - Wireless Networking 3 10-04-2008 03:09 AM
Crazy!! BCM4312 wireless still canNOT work... HELP ME! chopin1998@gmail.com Linux - Wireless Networking 3 08-22-2008 08:43 PM
BCM4312 and Slackware 12.1 RC1 andrew.46 Slackware 12 04-01-2008 08:02 PM
BCM4312 desperate redbook Linux - Wireless Networking 5 01-17-2008 01:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 04:00 PM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration