[solved] No DHCPOFFER with IPW3945 at Home

somebody · 2006-11-02 20:16:36

Hello,

I've installed networkmanager and knetworkmanager.
I'm in the right groups to use knetworkmanager:

dbus network audio storage scanner camera users nik

I added the dhcdbd and networkmanager to DAEMONS in rc.conf:

DAEMONS=(syslog-ng @acpid ipw3945d !network @crond dbus hal dhcdbd networkmanager)

I configure my network with DHCP (rc.conf):

lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo !eth0 !eth1)

Of course, the router is configured for dhcp(d).

eth0 is my normal network device (Driver: e1000).
eth1 is my wlan network device (Driver: ipw3945, ipw3945d is running).

If I configure the devices manually (ifconfig, iwconfig, route) it works all fine.
Using networkmanager only eth0 works fine, eth1 not.

So If I SWITCH TO ONLINE MODE (eth0)
I get (log):

Nov  2 20:11:25 alinux NetworkManager: <information>    Waking up from sleep.
Nov  2 20:11:25 alinux NetworkManager: <information>    Deactivating device eth0.
Nov  2 20:11:25 alinux NetworkManager: <information>    Deactivating device eth1.
Nov  2 20:11:25 alinux NetworkManager: <information>    eth0: Device is fully-supported using driver 'e1000'.
Nov  2 20:11:25 alinux NetworkManager: <information>    nm_device_init(): waiting for device's worker thread to start
Nov  2 20:11:25 alinux NetworkManager: <information>    nm_device_init(): device's worker thread started, continuing.
Nov  2 20:11:25 alinux NetworkManager: <information>    Now managing wired Ethernet (802.3) device 'eth0'.
Nov  2 20:11:25 alinux NetworkManager: <information>    Deactivating device eth0.
Nov  2 20:11:25 alinux NetworkManager: <information>    eth1: Device is fully-supported using driver 'ipw3945'.
Nov  2 20:11:25 alinux NetworkManager: <information>    nm_device_init(): waiting for device's worker thread to start
Nov  2 20:11:25 alinux NetworkManager: <information>    nm_device_init(): device's worker thread started, continuing.
Nov  2 20:11:25 alinux NetworkManager: <information>    Now managing wireless (802.11) device 'eth1'.
Nov  2 20:11:25 alinux NetworkManager: <information>    Deactivating device eth1.
Nov  2 20:11:25 alinux NetworkManager: <information>    Will activate wired connection 'eth0' because it now has a link.
Nov  2 20:11:25 alinux NetworkManager: <information>    SWITCH: no current connection, found better connection 'eth0'.
Nov  2 20:11:25 alinux NetworkManager: <information>    Will activate connection 'eth0'.
Nov  2 20:11:25 alinux NetworkManager: <information>    Device eth0 activation scheduled...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) started...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Nov  2 20:11:25 alinux NetworkManager: <information>    Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Nov  2 20:11:27 alinux NetworkManager: <information>    Activation (eth0) Beginning DHCP transaction.
Nov  2 20:11:27 alinux NetworkManager: <information>    Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Nov  2 20:11:27 alinux NetworkManager: <information>    DHCP daemon state is now 12 (successfully started) for interface eth0
Nov  2 20:11:27 alinux NetworkManager: <information>    DHCP daemon state is now 1 (starting) for interface eth0
Nov  2 20:11:30 alinux dhclient: Trying medium "-link0 -link1 -link2" 1
Nov  2 20:11:30 alinux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Nov  2 20:11:30 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:11:30 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth0
Nov  2 20:11:30 alinux dhclient: DHCPOFFER from 192.168.0.1
Nov  2 20:11:35 alinux dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Nov  2 20:11:35 alinux dhclient: DHCPACK from 192.168.0.1
Nov  2 20:11:35 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:11:35 alinux NetworkManager: <information>    DHCP daemon state is now 2 (bound) for interface eth0
Nov  2 20:11:35 alinux NetworkManager: <information>    Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Nov  2 20:11:35 alinux NetworkManager: <information>    Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Nov  2 20:11:35 alinux dhclient: bound to 192.168.0.7 -- renewal in 1544 seconds.
Nov  2 20:11:35 alinux dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Nov  2 20:11:35 alinux dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Nov  2 20:11:35 alinux dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Nov  2 20:11:35 alinux NetworkManager: <information>    Retrieved the following IP4 configuration from the DHCP daemon:
Nov  2 20:11:35 alinux NetworkManager: <information>      address 192.168.0.7
Nov  2 20:11:35 alinux NetworkManager: <information>      netmask 255.255.255.0
Nov  2 20:11:35 alinux NetworkManager: <information>      broadcast 192.168.0.255
Nov  2 20:11:35 alinux NetworkManager: <information>      gateway 192.168.0.1
Nov  2 20:11:35 alinux NetworkManager: <information>      nameserver 127.0.0.1
Nov  2 20:11:35 alinux NetworkManager: <information>      nameserver 192.168.0.1
Nov  2 20:11:35 alinux NetworkManager: <information>      domain name 'chaos.lan'
Nov  2 20:11:35 alinux NetworkManager: <information>    Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov  2 20:11:35 alinux NetworkManager: <information>    Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Nov  2 20:11:35 alinux NetworkManager: <information>    Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Nov  2 20:11:36 alinux NetworkManager: <information>    Activation (eth0) Finish handler scheduled.
Nov  2 20:11:36 alinux NetworkManager: <information>    Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Nov  2 20:11:36 alinux NetworkManager: <information>    Activation (eth0) successful, device activated.

Note that the DHCPDISCOVER is answered.
I'm online, I can ping the router and any internet sites.

ifconfig, iwconfig and route output is just fine.

Now I'm SWITCHING TO MY WLAN AP with eth1:

Nov  2 20:18:54 alinux NetworkManager: <information>    User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / wlango
Nov  2 20:18:54 alinux NetworkManager: <information>    Deactivating device eth1.
Nov  2 20:18:54 alinux dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Nov  2 20:18:54 alinux NetworkManager: <information>    Device eth1 activation scheduled...
Nov  2 20:18:54 alinux NetworkManager: <information>    Deactivating device eth0.
Nov  2 20:18:54 alinux dhclient: There is already a pid file /var/run/dhclient-eth0.pid with pid 3482
Nov  2 20:18:54 alinux dhclient: killed old client process, removed PID file
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) started...
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1/wireless): access point 'wlango' is encrypted, but NO valid key exists.  New key needed.
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) New wireless user key requested for network 'wlango'.
Nov  2 20:18:55 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) New wireless user key for network 'wlango' received.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1/wireless): access point 'wlango' is encrypted, and a key exists.  No new key needed.
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'INTERFACE_ADD eth1                wext   /var/run/wpa_supplicant  '
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'AP_SCAN 1'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'ADD_NETWORK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was '0'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'SET_NETWORK 0 ssid 776c616e676f'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: sending command 'ENABLE_NETWORK 0'
Nov  2 20:19:02 alinux NetworkManager: <information>    SUP: response was 'OK'
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'wlango'.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Nov  2 20:19:02 alinux NetworkManager: <information>    Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Nov  2 20:19:03 alinux NetworkManager: <information>    Activation (eth1) Beginning DHCP transaction.
Nov  2 20:19:03 alinux NetworkManager: <information>    Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Nov  2 20:19:03 alinux NetworkManager: <information>    DHCP daemon state is now 12 (successfully started) for interface eth1
Nov  2 20:19:03 alinux NetworkManager: <information>    DHCP daemon state is now 1 (starting) for interface eth1
Nov  2 20:19:07 alinux dhclient: Trying medium "-link0 -link1 -link2" 1
Nov  2 20:19:07 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Nov  2 20:19:07 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:07 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:11 alinux dhclient: Trying medium "link0 link1" 0
Nov  2 20:19:11 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Nov  2 20:19:11 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:11 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:15 alinux dhclient: Trying medium "-link0 -link1 -link2" 1
Nov  2 20:19:15 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:15 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
Nov  2 20:19:15 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:24 alinux dhclient: Trying medium "link0 link1" 0
Nov  2 20:19:24 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
Nov  2 20:19:24 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:24 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:33 alinux dhclient: Trying medium "-link0 -link1 -link2" 1
Nov  2 20:19:33 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
Nov  2 20:19:33 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:33 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:46 alinux dhclient: Trying medium "link0 link1" 0
Nov  2 20:19:46 alinux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
Nov  2 20:19:46 alinux dhcdbd: dhco_parse_option_settings: no new option definition for medium
Nov  2 20:19:46 alinux NetworkManager: <information>    DHCP daemon state is now 7 (unknown) for interface eth1
Nov  2 20:19:48 alinux NetworkManager: <information>    Device 'eth1' DHCP transaction took too long (>45s), stopping it.
Nov  2 20:19:48 alinux dhclient: There is already a pid file /var/run/dhclient-eth1.pid with pid 3527
Nov  2 20:19:48 alinux dhclient: killed old client process, removed PID file
Nov  2 20:19:49 alinux NetworkManager: <information>    Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled...
Nov  2 20:19:49 alinux NetworkManager: <information>    DHCP daemon state is now 14 (normal exit) for interface eth1
Nov  2 20:19:49 alinux NetworkManager: <information>    DHCP daemon state is now 14 (normal exit) for interface eth1
Nov  2 20:19:49 alinux NetworkManager: <information>    Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started...
Nov  2 20:19:49 alinux NetworkManager: <information>    Activation (eth1) New wireless user key requested for network 'wlango'.
Nov  2 20:19:49 alinux NetworkManager: <information>    Activation (eth1) Stage 4 of 5 (IP Configure Timeout) complete.
Nov  2 20:19:53 alinux NetworkManager: <WARNING>         nm_dbus_get_user_key_for_network_cb (): nm_dbus_get_user_key_for_network_cb(): dbus returned an error.   (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKeyError
Nov  2 20:19:53 alinux NetworkManager: <information>    Deactivating device eth1.
Nov  2 20:19:53 alinux NetworkManager: <information>    Activation (eth1): cancelling...
Nov  2 20:19:53 alinux NetworkManager: <information>    Activation (eth1) cancellation handler scheduled...
Nov  2 20:19:53 alinux NetworkManager: <information>    Activation (eth1): waiting for device to cancel activation.
Nov  2 20:19:53 alinux NetworkManager: <information>    Activation (eth1) cancellation handled.
Nov  2 20:19:53 alinux NetworkManager: <information>    Activation (eth1): cancelled.

I'm asked for the WEP key, I enter the WEP key, hit OK.
Note that there is no DHCPOFFER from router...

Doing a:

eth1="eth1 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
gateway="default gw 192.168.0.1"
ROUTES=(gateway)

in rc.conf I can't also access the internet. Eveything (ifconfig, iwconfig, route) looks fine. But I can't ping the router (Destination Host Unreachable).

Like I said before, configuring eth1 with static ip address manually (and in rc.conf) whereas DHCPD in router is off, it work all fine. Is DHCPD on, and I start dhcpd..I wait and wait...

So: DHCP do not work with IPW3945 here at home.
But: In university it works fine (eth1="dhcp").

Any hint?
Really strange to me...

shen · 2006-11-02 21:27:42

One thing I did notice was you have a ! infront of network in your daemons line in rc.conf. As far as I know you need to load that before loading the ipw3945 daemon. At least that is what I had to do to get it to work right. Also you don't need to laod the dhcpcd daemon via rc.conf

somebody · 2006-11-02 21:48:42

I use "!network" because I think the networkmanager do all related network stuff. ipw3945d before network works fine (in university...).

But I changed it to

DAEMONS=(syslog-ng @acpid network ipw3945d @crond dbus hal dhcdbd networkmanager)

It's the same.

Concerning dhcpd:

After that you need to add dhcdbd and networkmanager to the daemons array in /etc/rc.conf and restart your system.

from http://wiki.archlinux.org/index.php/Networkmanager

somebody · 2006-11-30 11:30:51

Finally I found out why I wasn't able to connect via knetworkmanager.

All the time I entered the hex key as passphrase, not as hex key. (You can choose this in the knetworkmanager dialog)

Of course, that's also the reason there was no dhcpd answer...

Sometimes you have to read the dialogs

Edit: Seems to me that I did it right in university, just not at home...

Arch Linux

#1 2006-11-02 20:16:36

[solved] No DHCPOFFER with IPW3945 at Home

#2 2006-11-02 21:27:42

Re: [solved] No DHCPOFFER with IPW3945 at Home

#3 2006-11-02 21:48:42

Re: [solved] No DHCPOFFER with IPW3945 at Home

#4 2006-11-30 11:30:51

Re: [solved] No DHCPOFFER with IPW3945 at Home

Board footer