netcfg2

vbtricks · 2008-05-09 15:55:47

Salut,

since I encountered some problems (not concerning wireless) using 2007.08-2, I installed 2008.03. While setting up the wireless card worked in 2007.08-2 without any problems, I do not manage to persuade the new netcfg2 to connect to my wireless network.

I set up the wireless card using ndiswrapper and are able to list up all available networks using iwlist. Then I tried to create a profile by copying the wpa.example file and modifying the relevant settings (ESSID, KEY):

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="mynetwork"
KEY="SomePasskey"
IP="dhcp"
TIMEOUT=20

Starting

netcfg2 profilename

results in a "profile up - Wireless association failed. [FAIL]".

I checked the WPA-Key several times, it's correct. Any chance to get my wireless back to work or switch back to the old (working) netcfg?

Thanks in advance,

Stefan

PS: Some detailed progress information might be a good feature for the future of netcfg2.

Last edited by vbtricks (2008-05-09 15:56:36)

lexiw · 2008-05-09 16:07:43

What's the output of iwconfig?

vbtricks · 2008-05-09 16:17:24

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:10 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lexiw · 2008-05-09 16:30:07

vbtricks wrote:

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:10 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

That's after "netcfg2 profilename" right?
What's the name of the device and the corresponding drivers?

vbtricks · 2008-05-09 16:35:39

That's right, it's after "netcfg2 profilename".

The device is a DWL G650+ (Revision B) with the Windows XP drivers (Version 2.02). Exactly the same as were working with the 2007.08-2 installation.

vbtricks · 2008-05-09 16:40:37

Well, before "netcfgs2 profilename" it looks exactly the same.

lexiw · 2008-05-09 16:57:36

vbtricks wrote:

Well, before "netcfgs2 profilename" it looks exactly the same.

Try changing the TIMEOUT value and check if wpa_supplicant is correctly installed.

vbtricks · 2008-05-09 17:04:06

Well, I increased both TIMEOUT and DHCP_TIMEOUT, wpa_supplicant seems to be correctly installed as well (when renaming the KEY value in the profile it states that the length of the key must be between 8 and 6?).

Any chance to get back the old netcfg script? It's a bit frustrating...

lexiw · 2008-05-09 17:14:11

After the switch to netcfg2 i never had the need to modify any wpa_supplicant related stuff, i just modified the wpa.example to fit my needs.
It may be a netcfg2 problem but you can't be sure untill you try to setup your network manually (iwconfig/wpa_supplicant).
Try setting it manually and if does works, file a bug against netcfg2.

vbtricks · 2008-05-09 17:44:38

Setting it up manually worked out fine. Though this is no practical solution for a laptop. Seems I have to send a bug report.

iphitus · 2008-05-09 23:36:56

Alternatively read the wiki:
http://wiki.archlinux.org/index.php/Net … ion_failed

If you set it up manually, what commands did you use?

vbtricks · 2008-05-10 09:49:34

Well, the wiki is not really helpful on this.

What I did:

wpa_passphrase MYSSID MYPASSPHRASE >> /etc/wpa_supplicant.conf

modifying the /etc/wpa_supplicant.conf

network={
        ssid="foobard"
        scan_ssid=1
        psk="it's a secret to everybody"
        key_mgmt=WPA-PSK
        proto=WPA
        pairwise=TKIP
        group=TKIP
        priority=9
}

and then the trouble shooting advice from http://wiki.archlinux.org/index.php/Wpa_supplicant

iwconfig wlan0 mode managed essid foobard channel 6
ifconfig wlan0 up
wpa_supplicant -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dddd
dhcpd wlan0

Currently I'm using that for a bash-script.

Stefan

iphitus · 2008-05-11 13:22:24

Salut

those are the same commands netcfg2 uses... except for your typo on dhcpcd.

This puzzles me... but I've seen it before. There is a funny bug in netcfg2 somewhere. It's terrible to track down, because half the time wireless problems are user error. I suspect it's something that only occurs with some drivers/configs too.

Does it work for you if you....
- Don't issue that iwconfig command at all?
- Don't have the channel bit on that iwconfig command?
- Issue ifconfig wlan0 up before the iwconfig command?

Important... what driver?

As for the progress information, I'll add it to the list for netcfg3.

Last edited by iphitus (2008-05-11 13:47:32)

vbtricks · 2008-05-11 15:40:57

Salut,

iphitus wrote:

- Don't issue that iwconfig command at all?

fails

iphitus wrote:

- Don't have the channel bit on that iwconfig command?

fails

iphitus wrote:

- Issue ifconfig wlan0 up before the iwconfig command?

works
(restarted each time, so always the same conditions)

iphitus wrote:

Important... what driver?

As stated above, ndiswrapper 1.52-1 with version 2.02 of the Windows XP driver (Revision B of the device).

Stefan

iphitus · 2008-05-12 06:41:25

Ahah!

So to confirm...

This works:

iwconfig wlan0 mode managed essid foobard channel 6
ifconfig wlan0 up
wpa_supplicant -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dddd
dhcpd wlan0

And this doesnt (see missing channel option):

iwconfig wlan0 mode managed essid foobard 
ifconfig wlan0 up
wpa_supplicant -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dddd
dhcpd wlan0

Which is slightly odd. Usually you don't need to specify the channel to connect. Might be a bug in ndiswrapper, so you could report that to them.

If that's right... I'll have to make a small change to netcfg2, to allow you to specify channel for a WPA connection (you can use WEP_OPTS for wep).

This profile should work:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="mynetwork"
KEY="SomePasskey"
IP="dhcp"
TIMEOUT=20
PRE_UP="iwconfig wlan0 channel 6"

if that doesnt work, try the full:

PRE_UP="iwconfig wlan0 mode managed essid mynetwork channel 6"

Good luck! Thanks for your debugging work.

James

vbtricks · 2008-05-12 09:31:53

Salut,

nope. Unfortunately no luck with both solutions. This is my profile

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="mynetwork"
KEY="mykey"
IP="dhcp"
TIMEOUT=30
DHCP_TIMEOUT=20
PRE_UP="iwconfig wlan0 mode managed essid mynetwork channel 6"

Key is correct, checked it again (copying the successful used one below the line in the profile above in the text-editor ).

Well, problem is less important to me as I got a working solution by now. If you want me to test a version with more debug output or something else, don't hesitate to reply.

Otherwise I'd regard this thread as solved,

Stefan

iphitus · 2008-05-15 08:30:22

I missed something else. You said you modified the generated wpa_supplicant.conf.

Try using the above profile, but set SECURITY="wpa-config" and use the /etc/wpa_supplicant.conf you made yourself.

Thanks!

vbtricks · 2008-05-15 08:50:08

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa-config"
ESSID="mynetwork"
KEY="mykey"
IP="dhcp"
TIMEOUT=30
DHCP_TIMEOUT=20
PRE_UP="iwconfig wlan0 mode managed essid mynetwork channel 6"
WPA_CONF=/etc/wpa_supplicant.conf

No, unfortunately this results in a "fail" as well

iphitus · 2008-05-15 10:10:59

Darn. I'll get back to you on this, I'd like to sort this one out.

I've seen this bug before but never really had someone willing to debug it properly.

unregistered · 2008-05-15 16:05:00

using 2008, i have had wireless association problems too but with open and wep secured networks so far ive only been able to connect to the wep secured network once or twice and none for the open network even though someone said in the thread i started that my configuration was correct so I don't really know what's the problem, Admittedly, my signal strength is pretty low but when using the network manager in fedora livecd, i get drastically better results meaning that it connects almost all the time hence my dilemma.

HydroDiOxide · 2008-07-30 08:39:17

Having troubles connecting to a wpa secured network using netcfg2 as well. Error:

mynetwork up  - Wireless association failed.                     [FAIL]

I was able to succesfully connect to the network using networkmanager.

My profile in /etc/network.d:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="MyESSIDinMixedCase"
KEY="mykeyinlowercase"
IP="dhcp"
TIMEOUT=30
PRE_UP="iwconfig wlan0 mode managed essid MyESSIDinMixedCase channel 6"

I did not do or change anything in my wpa_supplicant config files.

Any suggestions?

iphitus · 2008-07-30 09:55:26

Ok, few suggestions:

For a start, give netcfg from [testing] a try.
Then
- Instead of the PRE_UP line, use ([testing] netcfg only)

IWCONFIG="mode managed essid MyESSIDinMixedCase channel 6"

- If it doesnt work, try adding and using a combination of different quirks as listed on this page:
http://wiki.archlinux.org/index.php/Net … evelopment

HydroDiOxide · 2008-07-30 12:36:24

None of the suggested sollutions worked.

I tried installing the b43 drivers as well (with networkmanager I used ndiswrapper because my BCM4310 is not officially supported by the b43 driver) but to no avail. So I banged out the b43 module inde modules array (!b43) and tried the netcfg from testing with ndiswrapper, but that didn't work either. I still get the failed to associate error.

Any other suggestions?

Update: I managed to connect just once. First I ran iwlist scan and then I used netcfg2 profile (instead of netcfg profile). That resulted in an association, but I was not able to use Internet.

Last edited by HydroDiOxide (2008-07-31 09:30:31)

iphitus · 2008-07-31 09:35:03

ok, ensure you're using netcfg2 from [testing] and try your profile with many different combinations of the options for the QUIRKS=() variable. For a start, prescan might be useful.

There's more details on the wiki I linked before.

And just double, triple check your wireless config -- check the channel is correct, and your key is case perfect.

Last edited by iphitus (2008-07-31 09:35:55)

HydroDiOxide · 2008-07-31 11:58:04

Still no succes. Is there any info I can post that can be of any help to pinpoint the problem?

Arch Linux

#1 2008-05-09 15:55:47

netcfg2

#2 2008-05-09 16:07:43

Re: netcfg2

#3 2008-05-09 16:17:24

Re: netcfg2

#4 2008-05-09 16:30:07

Re: netcfg2

#5 2008-05-09 16:35:39

Re: netcfg2

#6 2008-05-09 16:40:37

Re: netcfg2

#7 2008-05-09 16:57:36

Re: netcfg2

#8 2008-05-09 17:04:06

Re: netcfg2

#9 2008-05-09 17:14:11

Re: netcfg2

#10 2008-05-09 17:44:38

Re: netcfg2

#11 2008-05-09 23:36:56

Re: netcfg2

#12 2008-05-10 09:49:34

Re: netcfg2

#13 2008-05-11 13:22:24

Re: netcfg2

#14 2008-05-11 15:40:57

Re: netcfg2

#15 2008-05-12 06:41:25

Re: netcfg2

#16 2008-05-12 09:31:53

Re: netcfg2

#17 2008-05-15 08:30:22

Re: netcfg2

#18 2008-05-15 08:50:08

Re: netcfg2

#19 2008-05-15 10:10:59

Re: netcfg2

#20 2008-05-15 16:05:00

Re: netcfg2

#21 2008-07-30 08:39:17

Re: netcfg2

#22 2008-07-30 09:55:26

Re: netcfg2

#23 2008-07-30 12:36:24

Re: netcfg2

#24 2008-07-31 09:35:03

Re: netcfg2

#25 2008-07-31 11:58:04

Re: netcfg2

Board footer