You are not logged in.
I've recently started to use netcfg2 in order to connect to either an ethernet interface, or wireless.
After a recent update, I find I have to consistently issue the command twice before a connection is made, and I have no idea why.
For example, I'll type
sudo netcfg uw-wireless
where /etc/network.d/uw-wireless is
CONNECTION="wireless"
INTERFACE=ath0
ESSID=uw-wireless
IP="dhcp"
TIMEOUT=20
DHCLIENT=no
(note that I added the DHCLIENT=no thing in an attempt to fix this problem).
and after a pause, get a DHCPCD timeout error. The second time I issue the command, it will connect almost instantly.
The same happens for my ethernet profile.
Is this a bug in netcfg, or am I making a stupid mistake?
Offline
Try using some of the quirk modes. http://wiki.archlinux.org/index.php/Net … d_later.29
I would try predown and/or postsleep
Offline
post the EXACT COMPLETE output of netcfg
Offline
If you are running the .27 kernel, you can try this, it worked for me with the same problem: Set SCAN="no". You can leave the rest of the profile settings to default, like dhcp. I was using WPA on my Intel 4965 AGN.
Zack
Last edited by Sjoden (2008-10-27 01:26:48)
Offline
[jesse@tuvok ~]$ sudo netcfg ethernet
:: ethernet up - DHCP IP lease attempt failed [FAIL]
[jesse@tuvok ~]$ sudo netcfg ethernet
:: ethernet up [DONE]
EDIT: Sjoden: Thanks for the tip. I'm going to wait to hear from iphitus before I try anything.
EDIT2: Here's the ethernet profile.
CONNECTION="ethernet"
DESCRIPTION="Basic ethernet profile, using dhcp"
INTERFACE=eth0
IP="dhcp"
DHCP_TIMEOUT=10
DHCLIENT=no
Last edited by Jessehk (2008-10-27 03:08:24)
Offline
Bizarre. I've never seen a basic dhcp fail on the plain ethernet profile.
And this is for both your ethernet and wireless profiles? Even more bizarre.
This is a guess, but see if the workaround listed here helps: http://bbs.archlinux.org/viewtopic.php? … 41#p440841
Offline