Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

[My problem is similar to Kubuntu 13.10 Wifi doesn't work - DHCP timeout but seems more tenacious.]

I have two wireless routers I can easily test:

  • a router installed by my service provider telenet.be
  • a DLink di-524up (which is connected via wired network to the first router)

After upgrading from ubuntu 13.04 to 13.11, I can connect smoothly to the internet via my DLink wireless router (surprisingly, since on 13.04 this was the slowest router) However, the two wireless networks provided by the telenet.be router (one password-protected and one open) fail. It seems that getting an IP address times out:

janr@guzumi:~$ lspci | grep -i wireless
12:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)

janr@guzumi:~$ sudo lshw -C network
  *-network               
       description: Wireless interface
       product: BCM4313 802.11bgn Wireless Network Adapter
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:12:00.0
       logical name: eth1
       version: 01
       serial: c0:cb:38:81:85:f8
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=6.30.223.141 (r415941) ip=192.168.24.101 latency=0 multicast=yes wireless=IEEE 802.11abg
       resources: irq:17 memory:fbb00000-fbb03fff
  *-network DISABLED
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:13:00.0
       logical name: eth0
       version: 03
       serial: f0:4d:a2:b5:50:b0
       size: 10Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:44 ioport:e000(size=256) memory:d0b04000-d0b04fff memory:d0b00000-d0b03fff memory:fba00000-fba1ffff

/var/syslog says:

Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) starting connection 'telenet-EE09A'
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1/wireless): access point 'telenet-EE09A' has security, but secrets are required.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1/wireless): connection 'telenet-EE09A' has security, and secrets exist.  No new secrets needed.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: added 'ssid' value 'telenet-EE09A'
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: added 'scan_ssid' value '1'
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: added 'key_mgmt' value 'WPA-PSK'
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: added 'auth_alg' value 'OPEN'
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: added 'psk' value ''
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Oct 24 09:01:13 guzumi NetworkManager[1008]:  Config: set interface ap_scan to 1
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: disconnected -> scanning
Oct 24 09:01:13 guzumi wpa_supplicant[1030]: eth1: Trying to associate with 5c:35:3b:5e:e0:9f (SSID='telenet-EE09A' freq=2417 MHz)
Oct 24 09:01:13 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: scanning -> associating
Oct 24 09:01:13 guzumi wpa_supplicant[1030]: eth1: CTRL-EVENT-ASSOC-REJECT status_code=16
Oct 24 09:01:23 guzumi wpa_supplicant[1030]: eth1: Authentication with 5c:35:3b:5e:e0:9f timed out.
Oct 24 09:01:23 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: associating -> disconnected
Oct 24 09:01:24 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: disconnected -> scanning
Oct 24 09:01:25 guzumi wpa_supplicant[1030]: eth1: Trying to associate with 5c:35:3b:5e:e0:9f (SSID='telenet-EE09A' freq=2417 MHz)
Oct 24 09:01:25 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: scanning -> associating
Oct 24 09:01:25 guzumi wpa_supplicant[1030]: eth1: Associated with 5c:35:3b:5e:e0:9f
Oct 24 09:01:25 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: associating -> 4-way handshake
Oct 24 09:01:25 guzumi wpa_supplicant[1030]: eth1: WPA: Key negotiation completed with 5c:35:3b:5e:e0:9f [PTK=CCMP GTK=TKIP]
Oct 24 09:01:25 guzumi wpa_supplicant[1030]: eth1: CTRL-EVENT-CONNECTED - Connection to 5c:35:3b:5e:e0:9f completed (reauth) [id=0 id_str=]
Oct 24 09:01:25 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: 4-way handshake -> completed
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'telenet-EE09A'.
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Oct 24 09:01:25 guzumi NetworkManager[1008]:  (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 24 09:01:25 guzumi NetworkManager[1008]:  dhclient started with pid 4812
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1) Beginning IP6 addrconf.
Oct 24 09:01:25 guzumi avahi-daemon[986]: Withdrawing address record for fe80::c2cb:38ff:fe81:85f8 on eth1.
Oct 24 09:01:25 guzumi avahi-daemon[986]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::c2cb:38ff:fe81:85f8.
Oct 24 09:01:25 guzumi avahi-daemon[986]: Interface eth1.IPv6 no longer relevant for mDNS.
Oct 24 09:01:25 guzumi NetworkManager[1008]:  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Oct 24 09:01:25 guzumi dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct 24 09:01:25 guzumi dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct 24 09:01:25 guzumi dhclient: All rights reserved.
Oct 24 09:01:25 guzumi dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct 24 09:01:25 guzumi dhclient: 
Oct 24 09:01:25 guzumi NetworkManager[1008]:  (eth1): DHCPv4 state changed nbi -> preinit
Oct 24 09:01:25 guzumi dhclient: Listening on LPF/eth1/c0:cb:38:81:85:f8
Oct 24 09:01:25 guzumi dhclient: Sending on   LPF/eth1/c0:cb:38:81:85:f8
Oct 24 09:01:25 guzumi dhclient: Sending on   Socket/fallback
Oct 24 09:01:25 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0x1efe537b)
Oct 24 09:01:27 guzumi avahi-daemon[986]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::c2cb:38ff:fe81:85f8.
Oct 24 09:01:27 guzumi avahi-daemon[986]: New relevant interface eth1.IPv6 for mDNS.
Oct 24 09:01:27 guzumi avahi-daemon[986]: Registering new address record for fe80::c2cb:38ff:fe81:85f8 on eth1.*.
Oct 24 09:01:28 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 (xid=0x1efe537b)
Oct 24 09:01:33 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 (xid=0x1efe537b)
Oct 24 09:01:38 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 (xid=0x1efe537b)
Oct 24 09:01:45 guzumi NetworkManager[1008]:  (eth1): IP6 addrconf timed out or failed.
Oct 24 09:01:45 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Oct 24 09:01:45 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) started...
Oct 24 09:01:45 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Oct 24 09:01:46 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 (xid=0x1efe537b)
Oct 24 09:01:56 guzumi dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 (xid=0x1efe537b)
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): DHCPv4 request timed out.
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): canceled DHCP transaction, DHCP client pid 4812
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv4 Configure Timeout) started...
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Activation (eth1) failed for connection 'telenet-EE09A'
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Activation (eth1) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): deactivating device (reason 'none') [0]
Oct 24 09:02:10 guzumi avahi-daemon[986]: Withdrawing address record for fe80::c2cb:38ff:fe81:85f8 on eth1.
Oct 24 09:02:10 guzumi avahi-daemon[986]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::c2cb:38ff:fe81:85f8.
Oct 24 09:02:10 guzumi avahi-daemon[986]: Interface eth1.IPv6 no longer relevant for mDNS.
Oct 24 09:02:10 guzumi NetworkManager[1008]:  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 24 09:02:10 guzumi wpa_supplicant[1030]: eth1: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
Oct 24 09:02:10 guzumi NetworkManager[1008]:  (eth1): supplicant interface state: completed -> disconnected
Oct 24 09:02:10 guzumi kernel: [ 1509.067650] cfg80211: Calling CRDA to update world regulatory domain
Oct 24 09:02:10 guzumi kernel: [ 1509.075711] cfg80211: World regulatory domain updated:
Oct 24 09:02:10 guzumi kernel: [ 1509.075721] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 24 09:02:10 guzumi kernel: [ 1509.075729] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 24 09:02:10 guzumi kernel: [ 1509.075736] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 24 09:02:10 guzumi kernel: [ 1509.075742] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct 24 09:02:10 guzumi kernel: [ 1509.075748] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 24 09:02:10 guzumi kernel: [ 1509.075755] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

I followed the suggestions to

  • ensure all packages are up-to-date
  • reboot
  • deleting the networkmanager "telenet-EE09A" network record and connecting again. However, this failed.

At the same time, other machines (my dual boot windows and my ipad) can still join the wireless telenet-EE09A network easily.

So there seems to be a mismatch between my new ubuntu 13.10 and the specifics to this particular router or wireless network type(s). Does anyone have an idea?

Jan

share|improve this question
    
Did you get it sorted? –  matcheek Dec 26 '13 at 21:06

1 Answer 1

For the benefit of people landing on this page

There is a bug raised on launchpad

In the comment #29 there is a solution provided that is to reload the wl module:

modprobe -r wl && modprobe wl
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.