FS#25552 - [Netcfg] breaks dhcp on wireless with "carrier lost" message
Attached to Project:
Arch Linux
Opened by pedram (multiphrenic) - Saturday, 13 August 2011, 13:36 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Sunday, 14 August 2011, 16:06 GMT
Opened by pedram (multiphrenic) - Saturday, 13 August 2011, 13:36 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Sunday, 14 August 2011, 16:06 GMT
|
Details
Description:
I'm using the brcmsmac module in 3.0 and have been able to connect to the wireless network fine using wpa_supplicant. I then installed netcfg through pacman, configured it to run with my wireless network, added netcfg and removed network from my daemons, configured rc.conf to use the correct profile and rebooted. Upon reboot, I notice I do not have an ip address. I ran iwconfig and saw that I am connected to the wireless network properly and a link has been established. When I look in the logs, I notice dhcpcd is no longer able to maintain an ip address (though it does acquire one, which confirms that I am connected to the wireless network). Upon disabling netcfg and rerunning wpa_supplicant, I am able to run dhcp manually and it works fine. I have searched the forums and it was suggested to run dhcp --nohooks mtu but that did not change anything. I looked at my router's DHCP logs and the only two lines there showed that it had send an ACK to my computer and that a request was sent for an IP from my computer immediately after that. Additional info: Running: netcfg-2.6.7-1 /etc/network.d/wireless CONNECTION='wireless' DESCRIPTION='A simple WPA encrypted wireless connection' INTERFACE='wlan0' SECURITY='wpa' ESSID='biteynet' KEY='myawesomepassword'' IP='dhcp' # Uncomment this if your ssid is hidden #HIDDEN=yes DCHP log files ------------- Aug 12 20:17:24 localhost dhcpcd[810]: version 5.2.12 starting Aug 12 20:17:24 localhost dhcpcd[810]: wlan0: rebinding lease of 192.168.1.104 Aug 12 20:17:24 localhost dhcpcd[810]: wlan0: acknowledged 192.168.1.104 from 192.168.1.1 Aug 12 20:17:24 localhost dhcpcd[810]: wlan0: checking for 192.168.1.104 Aug 12 20:17:29 localhost dhcpcd[810]: wlan0: leased 192.168.1.104 for 86400 seconds Aug 12 20:17:29 localhost dhcpcd[810]: forked to background, child pid 833 Aug 12 20:17:42 localhost dhcpcd[833]: wlan0: carrier lost Aug 12 20:17:42 localhost kernel: [ 59.064218] cfg80211: Calling CRDA for country: US Aug 12 20:17:43 localhost dhcpcd[833]: wlan0: carrier acquired Aug 12 20:17:43 localhost dhcpcd[833]: wlan0: rebinding lease of 192.168.1.104 Aug 12 20:17:53 localhost dhcpcd[833]: wlan0: broadcasting for a lease Aug 12 20:17:53 localhost dhcpcd[833]: wlan0: carrier lost Aug 12 20:17:53 localhost kernel: [ 70.164055] cfg80211: Calling CRDA to update world regulatory domain Aug 12 20:17:54 localhost dhcpcd[833]: wlan0: carrier acquired Aug 12 20:17:54 localhost dhcpcd[833]: wlan0: rebinding lease of 192.168.1.104 Aug 12 20:18:04 localhost dhcpcd[833]: wlan0: broadcasting for a lease Aug 12 20:18:04 localhost dhcpcd[833]: wlan0: carrier lost Aug 12 20:18:04 localhost kernel: [ 81.303433] cfg80211: Calling CRDA to update world regulatory domain Router messages Fri, 12 Aug 2011 20:15:41 received REQUEST from 88:9F:FA:3B:0C:BC Fri, 12 Aug 2011 20:15:41 sending ACK to 192.168.1.104 Fri, 12 Aug 2011 20:16:52 received REQUEST from 88:9F:FA:3B:0C:BC Fri, 12 Aug 2011 20:16:52 sending ACK to 192.168.1.104 Steps to reproduce: * Install netcfg * Configure /etc/network.d/wireless and /etc/rc.conf as stated * Reboot |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Sunday, 14 August 2011, 16:06 GMT
Reason for closing: Works for me
Additional comments about closing: User could not reproduce.
Sunday, 14 August 2011, 16:06 GMT
Reason for closing: Works for me
Additional comments about closing: User could not reproduce.
Comment by
Rémy Oudompheng (remyoudompheng) -
Saturday, 13 August 2011, 22:35 GMT
The only job of netcfg is to set up the wireless connection and
launch dhcpcd. What happens if you start netcfg as usual, kill
dhcpcd and launch your own dhcpcd by hand? And if you launch
dhcpcd with the same options netcfg is using "dhcpcd -L -t 10" ?
Comment by pedram (multiphrenic) -
Saturday, 13 August 2011, 23:35 GMT
I am not sure what happened, but when I added net-profiles back to
rc.conf to test I had a new problem -- I couldn't even
authenticate to the router. I rebooted and the problem went away
and the IP renewed successfully (which is strange because I've
rebooted many times before.) I rebooted a few more times to make
sure it was not a fluke and it does seem to be resolved. Thank
you.