aquire an dhcp-address ALL network devs fails?! [Solved]

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

aquire an dhcp-address ALL network devs fails?! [Solved]

Postby st » Sun Jul 29, 2007 20:17

i am having a weird network issue on my dell precision m65 laptop. dhcp was working fine on 3.4a_x64 yesterday but now after an update it suddenly stopped working. I can see my accespoint, it connects and negotiates with the accespoint but it won't get an ip-adress with dhcp. If I configure the ip-adress manually all is fine. Even when I run /etc/init.d/net.wlan0 i get an dhcp address from the router (but no dns server). it is just with Knetworkmanager that all fails.

UPDATE: today i tried connecting through my wired eth0 device, this also fails to aquire a dhcp address through Knetworkmanager. The problem seems to be confined to Knetworkmanager because a /etc/init.d/net.eth0 worked fine again, apart from the DNS settings. This really sucks because i connect to three different networks and would like to have them automatically set.

emerge.log:

Code: Select all
1185664909:  >>> AUTOCLEAN: net-misc/dhcpcd
1185664909: === Unmerging... (net-misc/dhcpcd-3.0.17)
1185664910:  >>> unmerge success: net-misc/dhcpcd-3.0.17
1185664910:  === (76 of 588) Post-Build Cleaning (net-misc/dhcpcd-3.1.1::/usr/portage/net-misc/dhcpcd/dhcpcd-3.1.1.ebuild)
1185664910:  ::: completed emerge (76 of 588) net-misc/dhcpcd-3.1.1 to /


messages:
Code: Select all
Jul 29 21:16:45 homerus NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'XXX'.
Jul 29 21:16:45 homerus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 29 21:16:45 homerus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 29 21:16:47 homerus NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Jul 29 21:16:47 homerus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 29 21:16:47 homerus NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 29 21:16:47 homerus dhclient: wmaster0: unknown hardware address type 801
Jul 29 21:16:47 homerus dhclient: wmaster0: unknown hardware address type 801
Jul 29 21:16:47 homerus dhcdbd: dhco_parse_option_settings: bad option setting: old_server_name =
Jul 29 21:16:47 homerus NetworkManager: <info>  DHCP daemon state is now 6 (unknown) for interface wlan0
Jul 29 21:16:47 homerus dhcdbd: Unrequested down ?:3
Jul 29 21:16:47 homerus NetworkManager: <info>  DHCP daemon state is now 14 (normal exit) for interface wlan0
Jul 29 21:16:47 homerus NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Jul 29 21:17:32 homerus NetworkManager: <info>  Device 'wlan0' DHCP transaction took too long (>45s), stopping it.
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) failure scheduled...
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) failed for access point (XXX)
Jul 29 21:17:32 homerus NetworkManager: <info>  Activation (wlan0) failed.
Jul 29 21:17:32 homerus NetworkManager: <info>  Deactivating device wlan0.
Jul 29 21:17:32 homerus [  500.828986] wlan0: deauthenticate(reason=3)
Jul 29 21:17:32 homerus [  498.899608] wlan0: RX deauthentication from XXX (reason=1)
Jul 29 21:17:32 homerus [  498.899617] wlan0: deauthenticated
Jul 29 21:17:44 homerus [  505.524573] iwl3945: REPLY_ADD_STA failed


manual:
Code: Select all
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: dhcpcd 3.1.1 starting
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: hardware address = XXX
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: DUID = XXX
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: broadcasting for a lease
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: offered 192.168.1.33 from 192.168.1.254 `X'
Jul 29 21:17:50 homerus dhcpcd[14279]: wlan0: checking 192.168.1.33 is available on attached networks
Jul 29 21:17:51 homerus dhcpcd[14279]: wlan0: leased 192.168.1.33 for 28800 seconds
Jul 29 21:17:51 homerus dhcpcd[14279]: wlan0: adding IP address 192.168.1.33/24
Jul 29 21:17:51 homerus dhcpcd[14279]: wlan0: adding route to 192.168.1.0 (255.255.255.0) via 0.0.0.0 metric 2000
Jul 29 21:17:51 homerus dhcpcd[14279]: wlan0: removing route to 192.168.1.0 (255.255.255.0) via 0.0.0.0 metric 0
Jul 29 21:17:51 homerus dhcpcd[14279]: wlan0: adding default route via 192.168.1.254 metric 2000
Jul 29 19:17:51 homerus avahi-daemon[8107]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.99.
Jul 29 19:17:51 homerus avahi-daemon[8107]: New relevant interface wlan0.IPv4 for mDNS.
Jul 29 19:17:51 homerus avahi-daemon[8107]: Registering new address record for 192.168.1.99 on wlan0.IPv4.


can anyone help me out here? could it be the dhcp update or is it something else? I also noted that after the update starting wireless stated (for the first time?) that /etc/conf.d/wireless was deprecated and the settings should be placed in /etc/conf.d/net. I did fix this but it didn't help and i didn't notice this before.

thanks,
stefan
st
Baby Hen
 
Posts: 13
Joined: Sun Apr 08, 2007 19:01
Location: Netherlands

Postby wolfden » Sun Aug 05, 2007 3:55

User avatar
wolfden
Sharecropper
 
Posts: 8824
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA


Return to Networking and Wireless

Who is online

Users browsing this forum: No registered users and 1 guest