wireless requires network restart

Sun Apr 23 19:47:54 UTC 2006

I've recently switched to using a wireless connection with a broadband router.
When I boot my machine (daily) the wireless initially doesn't work.  I have to
do 'sudo /etc/init.d/networking restart' to get it to function.  Here is what
deamon.log shows today after booting:

Apr 23 16:03:20 localhost NetworkManager: <information>^Istarting...
Apr 23 16:03:21 localhost NetworkManager: <information>^Ieth0: Driver support
level for 'e100' is fully-supported
Apr 23 16:03:21 localhost NetworkManager: <information>^Inm_device_new():
waiting for device's worker thread to start
Apr 23 16:03:21 localhost NetworkManager: <information>^Inm_device_new():
device's worker thread started, continuing.
Apr 23 16:03:21 localhost NetworkManager: <information>^INow managing wired
device 'eth0'.
Apr 23 16:03:21 localhost NetworkManager: <information>^IDeactivating device eth0.
Apr 23 16:03:21 localhost NetworkManager: <information>^Ira0: Driver support
level for 'rt2500' is fully-supported
Apr 23 16:03:21 localhost NetworkManager: <information>^Inm_device_new():
waiting for device's worker thread to start
Apr 23 16:03:22 localhost NetworkManager: <information>^Inm_device_new():
device's worker thread started, continuing.
Apr 23 16:03:22 localhost NetworkManager: <information>^INow managing wireless
device 'ra0'.
Apr 23 16:03:22 localhost NetworkManager: <information>^IDeactivating device ra0.
Apr 23 16:03:24 localhost NetworkManager: <information>^Inamed started with pid 7681
Apr 23 16:03:25 localhost named[7681]: starting BIND 9.3.1 -f -u bind -c
/var/lib/NetworkManager/NetworkManager-named.conf
Apr 23 16:03:25 localhost named[7681]: found 1 CPU, using 1 worker thread
Apr 23 16:03:25 localhost named[7681]: loading configuration from
'/var/lib/NetworkManager/NetworkManager-named.conf'
Apr 23 16:03:25 localhost named[7681]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 23 16:03:25 localhost named[7681]:
/var/lib/NetworkManager/NetworkManager-named.conf:7: no forwarders seen;
disabling forwarding
Apr 23 16:03:25 localhost named[7681]:
/var/lib/NetworkManager/NetworkManager-named.conf:7: no forwarders seen;
disabling forwarding
Apr 23 16:03:26 localhost named[7681]: running
Apr 23 16:03:28 localhost named[7995]: starting BIND 9.3.1 -u bind
Apr 23 16:03:28 localhost named[7995]: found 1 CPU, using 1 worker thread
Apr 23 16:03:28 localhost named[7995]: loading configuration from
'/etc/bind/named.conf'
Apr 23 16:03:28 localhost named[7995]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 23 16:03:28 localhost named[7995]: binding TCP socket: address in use
Apr 23 16:03:28 localhost named[7995]: command channel listening on 127.0.0.1#953
Apr 23 16:03:28 localhost named[7995]: command channel listening on ::1#953
Apr 23 16:03:28 localhost named[7995]: zone 0.in-addr.arpa/IN: loaded serial 1
Apr 23 16:03:28 localhost named[7995]: zone 127.in-addr.arpa/IN: loaded serial 1
Apr 23 16:03:28 localhost named[7995]: zone 255.in-addr.arpa/IN: loaded serial 1
Apr 23 16:03:28 localhost named[7995]: zone localhost/IN: loaded serial 1
Apr 23 16:03:28 localhost named[7995]: running

and here is what it has after the restart:

Apr 23 16:24:04 localhost dhclient: There is already a pid file
/var/run/dhclient.ra0.pid with pid 7040
Apr 23 16:24:04 localhost dhclient: killed old client process, removed PID file
Apr 23 16:24:04 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.2
Apr 23 16:24:04 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Apr 23 16:24:04 localhost dhclient: All rights reserved.
Apr 23 16:24:04 localhost dhclient: For info, please visit
http://www.isc.org/products/DHCP
Apr 23 16:24:04 localhost dhclient:
Apr 23 16:24:04 localhost dhclient: sit0: unknown hardware address type 776
Apr 23 16:24:04 localhost dhclient: sit0: unknown hardware address type 776
Apr 23 16:24:04 localhost dhclient: Listening on LPF/ra0/00:0e:2e:51:c6:f6
Apr 23 16:24:04 localhost dhclient: Sending on   LPF/ra0/00:0e:2e:51:c6:f6
Apr 23 16:24:04 localhost dhclient: Sending on   Socket/fallback
Apr 23 16:24:04 localhost dhclient: DHCPRELEASE on ra0 to 192.168.1.1 port 67
Apr 23 16:24:04 localhost dhclient: send_packet: Network is unreachable
Apr 23 16:24:04 localhost dhclient: send_packet: please consult README file
regarding broadcast address.
Apr 23 16:24:05 localhost dhclient: There is already a pid file
/var/run/dhclient.ra0.pid with pid 1
Apr 23 16:24:05 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.2
Apr 23 16:24:05 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Apr 23 16:24:05 localhost dhclient: All rights reserved.
Apr 23 16:24:05 localhost dhclient: For info, please visit
http://www.isc.org/products/DHCP
Apr 23 16:24:05 localhost dhclient:
Apr 23 16:24:05 localhost dhclient: sit0: unknown hardware address type 776
Apr 23 16:24:05 localhost dhclient: sit0: unknown hardware address type 776
Apr 23 16:24:05 localhost dhclient: Listening on LPF/ra0/00:0e:2e:51:c6:f6
Apr 23 16:24:05 localhost dhclient: Sending on   LPF/ra0/00:0e:2e:51:c6:f6
Apr 23 16:24:05 localhost dhclient: Sending on   Socket/fallback
Apr 23 16:24:09 localhost dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port
67 interval 3
Apr 23 16:24:12 localhost dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port
67 interval 5
Apr 23 16:24:17 localhost dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port
67 interval 7
Apr 23 16:24:18 localhost dhclient: DHCPOFFER from 192.168.1.1
Apr 23 16:24:18 localhost dhclient: DHCPREQUEST on ra0 to 255.255.255.255 port 67
Apr 23 16:24:18 localhost dhclient: DHCPACK from 192.168.1.1
Apr 23 16:24:18 localhost dhclient: bound to 192.168.1.101 -- renewal in 34193
seconds.
Apr 23 17:03:28 localhost named[7995]: listening on IPv4 interface ra0,
192.168.1.101#53

and here is my /etc/network/interfaces file:

===
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
   script grep
   map eth0

#iface eth0 inet dhcp
#auto eth0

iface ra0 inet dhcp
wireless-essid *****
wireless-key *****
#wireless-mode Managed

auto ra0
===

any ideas what is causing this problem?

Toby