FS#25611 - dhcpcd continually disconnects and reconnects

Attached to Project: Arch Linux
Opened by Gavin Costello (gavcos) - Tuesday, 16 August 2011, 18:33 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 14 November 2011, 11:51 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: dhcpcd continually disconnects and reconnects (every 10 minutes or so) when using netcfg and wireless (wpa_supplicant)


Additional info:
* dhcpcd 5.2.12-1 (base)
* /etc/dhcpcd.conf:

# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
#clientid

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
#option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll

/etc/conf.d/dhcpcd:
DHCPCD_ARGS="-L -t 10 -q -S 192.168.0.100"


Steps to reproduce:
Configure rc.conf with wireless profile (DAEMONS array contains network and net-profiles) as per wiki
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 14 November 2011, 11:51 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Adding nolink option to dhcpcd.conf fixes this issue.
Comment by Ronald van Haren (pressh) - Wednesday, 17 August 2011, 12:03 GMT
Any logs?
Comment by Gavin Costello (gavcos) - Wednesday, 17 August 2011, 17:31 GMT
Sorry, here's an example from /var/log/messages:

Aug 17 19:17:20 thinkpad dhcpcd[1726]: version 5.2.12 starting
Aug 17 19:17:20 thinkpad dhcpcd[1726]: wlan0: rebinding lease of 192.168.0.100
Aug 17 19:17:20 thinkpad dhcpcd[1726]: wlan0: acknowledged 192.168.0.100 from 192.168.0.254
Aug 17 19:17:20 thinkpad dhcpcd[1726]: wlan0: checking for 192.168.0.100
Aug 17 19:17:23 thinkpad acpid: client connected from 1718[1000:100]
Aug 17 19:17:23 thinkpad acpid: 1 client rule loaded
Aug 17 19:17:26 thinkpad dhcpcd[1726]: wlan0: leased 192.168.0.100 for 864000 seconds
Aug 17 19:17:26 thinkpad dhcpcd[1726]: forked to background, child pid 1757
Aug 17 19:24:54 thinkpad kernel: [ 157.810215] chromium-sandbo (4126): /proc/4124/oom_adj is deprecated, plea
se use /proc/4124/oom_score_adj instead.
Aug 17 19:27:21 thinkpad dhcpcd[1757]: wlan0: carrier lost
Aug 17 19:27:21 thinkpad kernel: [ 304.027590] cfg80211: Calling CRDA to update world regulatory domain
Aug 17 19:27:25 thinkpad dhcpcd[1757]: wlan0: carrier acquired
Aug 17 19:27:25 thinkpad dhcpcd[1757]: wlan0: rebinding lease of 192.168.0.100
Aug 17 19:27:25 thinkpad dhcpcd[1757]: wlan0: acknowledged 192.168.0.100 from 192.168.0.254
Aug 17 19:27:25 thinkpad dhcpcd[1757]: wlan0: checking for 192.168.0.100
Aug 17 19:27:30 thinkpad dhcpcd[1757]: wlan0: leased 192.168.0.100 for 864000 seconds
Comment by Leonid Isaev (lisaev) - Monday, 22 August 2011, 18:08 GMT
This is not a problem with dhcpcd, but with you wireless nic/driver/AP. Those lines "carrier lost" and subsequent kernel: messages indicate that wpa_supplicant reconnects to the AP, and dhcp just follows this.

Please attach the output of iwconfig wlan0, or similar using iw...
Comment by Gavin Costello (gavcos) - Monday, 22 August 2011, 18:38 GMT
iwconfig wlan0
wlan0 IEEE 802.11abg ESSID:"freecos"
Mode:Managed Frequency:2.412 GHz Access Point: AA:23:61:45:4B:2C
Bit Rate=2 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-33 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:54 Missed beacon:0
Comment by Gavin Costello (gavcos) - Monday, 22 August 2011, 19:13 GMT
The problem only occurs when running dhcpcd, if I issue killall dhcpcd && dhclient wlan0 the connection persists.
Comment by Leonid Isaev (lisaev) - Friday, 26 August 2011, 19:23 GMT
dhcpcd supports link status detection, while (please correct me if I'm wrong here) dhclient does not. So you simply do not see the log messages. If you would like to disable them in dhcpcd, look at man 5 dhcpcd.conf and search for "nolink". You can also consult dhcpcd website and debian bug 594672 for dhcpcd features.

For the record, I encountered those 4 sec "blackouts" quite frequently with linksys and actiontec routers, even on a wired connection with the latter. OTOH, our newest buffalo gateway works OK. The wireless nic is intel 5100agn.

EDIT: By link, I meant "link carrier"...
Comment by Gavin Costello (gavcos) - Thursday, 10 November 2011, 21:08 GMT
Sorry for the late reply: thanks Leonid, adding nolink option did the trick :-)

Loading...