You are not logged in.
Pages: 1
We started using WPA2 in our office and netcfg2 generally can't connect to it.. Manually trying via the command
sudo netcfg2 parkyeri
sometimes connects but generally not... Is this problem netcfg2 related or something wrong on the router etc ?
Quis custodiet ipsos custodiet?
Offline
You might get more help if you post in this thread: http://bbs.archlinux.org/viewtopic.php?id=39505
Offline
"doesnt work" tells me nothing whatsoever.
http://wiki.archlinux.org/index.php/Net … nt_work.3F
I'm guessing... it's dhcp not getting an IP?
Last edited by iphitus (2008-03-09 10:11:48)
Offline
I use netcfg2 and WPA2 without any problems. (ipw2200)
Offline
I'm guessing... it's dhcp not getting an IP?
Do you (or anyone) happen to have any background on this? I have that very same problem both with my linux/ndiswrapper laptop and with my boss's lenovo XP laptop on the university's WPA2 WLAN. The connection seems to be established but both systems never get an IP addy.
Offline
Well; I think it doesn't get an IP address... NetworkManager seems to work for now so I switched back to it but you never know when it's gonna get broke.. :S
Quis custodiet ipsos custodiet?
Offline
This is odd. All of a sudden, in the last fortnight to a month, netcfg2 has suddenly failed getting an IP via dhcp for a whole tonne of people...
It's either one of these things:
dhcpcd update 3.2.0 -> 3.2.1
netcfg update v2.0.4 -> 2.0.6
some funny kernel change
ipw3945, a few people who have this issue use it. Not sure about everyone though.
If you get a chance, could you try dhcpcd 3.2.0. If that still fails, try the last netcfg2 version or two.
In the meantime, you can try this workaround which should work for sure, "pacman -S dhclient" and set DHCLIENT="yes" in your profiles. (makes netcfg use dhclient instead of dhcpcd)
James
Last edited by iphitus (2008-03-09 21:52:35)
Offline
I've tried both ipw3945 and iwlwifi and I generally had that problem that I couldn't get an IP address and have to try more than twice to get it.. By the way, what is the advantage of using dhcpcd instead of dhclient ? Which ways is it better ?
Quis custodiet ipsos custodiet?
Offline
I've tried both ipw3945 and iwlwifi and I generally had that problem that I couldn't get an IP address and have to try more than twice to get it.. By the way, what is the advantage of using dhcpcd instead of dhclient ? Which ways is it better ?
None really, just easier to work with from a developer's perspective. I was going to move to dhclient at some stage, but something got in the way -- I left it there as an option anyway.
Let me know how you go with the older dhcpcd version and older netcfg versions, I'd like to pin down what's causing this.
Offline
Dhclient wird der Standard in der nächsten Version
(dhclient will be the default in the next version)
Last edited by iphitus (2008-04-01 08:33:18)
Offline
Could any of you look at ifconfig when dhcp fails? In the line where it says "UP", there should be a keyword "RUNNING" as well. If that is missing, this might be a bug in dhcpcd (I had this problem with dhclient and just fixed it a few days ago).
Offline
For Intel 5100 it works with QUIRKS=(wpaessid) for me!
Offline
Pages: 1