rt73 & rutilt -- failing DHCP on reboot

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4563

bobmctoot

15-01-2008 15:06:21

Hi,

I wonder if anybody can give me any guidance?

First, I am a complete novice with Linux so if I've done something stupid or not given enough detail/used the wrong terminology please be gentle.

Until recently I'd been running a system with Oracle Enterprise Linux 5 (2.6.18 kernel) and was using the rt73 drivers and rutilt just fine to connect to a wireless network using a Sweex Wireless Lan USB 2.0 adapter. I had a profile saved in rutilt and called

ifconfig wlan0 up
/usr/local/sbin/rutilt wlan0 -d -e -p <profile>

in the /etc/rc.d/rc.local script. This worked a treat, reconnecting on reboots and staying connected consistently.

I've now rebuilt my system using Oracle Enterprise Linux 5, Update 1 (2.6.18-53). I've (I think) gone through the same process to install rt73 and rutilt. I've added the same to the rc.local script and can either use rutilt (through the gui) or call the rc.local script manually once the system is up and it connects fine.

However, when I reboot I no longer connect automatically (though rutilt continues to run in the background). Also, once I manually connect to the wireless network it drops the connection intermittently (sometimes within an hour, sometimes after a day or two).

The following is in /var/log/messages from startup

[code3khoshe5]Jan 14 22:53:34 oel51 kernel: rt73: Interface up for first time, activating permanent MAC
Jan 14 22:53:34 oel51 kernel: rt73: Active MAC is: 00:16:0a:0b:18:92.
Jan 14 22:53:34 oel51 kernel: rt73: Local MAC = 00:16:0a:0b:18:92
Jan 14 22:53:34 oel51 dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
Jan 14 22:53:34 oel51 dhclient: Copyright 2004-2006 Internet Systems Consortium.
Jan 14 22:53:34 oel51 dhclient: All rights reserved.
Jan 14 22:53:34 oel51 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jan 14 22:53:34 oel51 dhclient:
Jan 14 22:53:34 oel51 dhclient: Listening on LPF/wlan0/00:16:0a:0b:18:92
Jan 14 22:53:34 oel51 dhclient: Sending on LPF/wlan0/00:16:0a:0b:18:92
Jan 14 22:53:34 oel51 dhclient: Sending on Socket/fallback
Jan 14 22:53:34 oel51 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jan 14 22:53:35 oel51 avahi-daemon[3522]: New relevant interface wlan0.IPv6 for mDNS.
Jan 14 22:53:35 oel51 avahi-daemon[3522]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::216:aff:fe0b:1892.
Jan 14 22:53:35 oel51 avahi-daemon[3522]: Registering new address record for fe80::216:aff:fe0b:1892 on wlan0.
Jan 14 22:53:39 oel51 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jan 14 22:53:50 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jan 14 22:53:53 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jan 14 22:53:59 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jan 14 22:54:13 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jan 14 22:54:34 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jan 14 22:54:46 oel51 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jan 14 22:54:51 oel51 dhclient: No DHCPOFFERS received.
Jan 14 22:54:51 oel51 dhclient: Trying recorded lease 192.168.1.67
Jan 14 22:54:51 oel51 avahi-daemon[3522]: New relevant interface wlan0.IPv4 for mDNS.
Jan 14 22:54:51 oel51 avahi-daemon[3522]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.67.
Jan 14 22:54:51 oel51 avahi-daemon[3522]: Registering new address record for 192.168.1.67 on wlan0.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Withdrawing address record for 192.168.1.67 on wlan0.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.67.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.67.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Interface wlan0.IPv6 no longer relevant for mDNS.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::216:aff:fe0b:1892.
Jan 14 22:54:54 oel51 avahi-daemon[3522]: Withdrawing address record for fe80::216:aff:fe0b:1892 on wlan0.
Jan 14 22:54:54 oel51 dhclient: No working leases in persistent database - sleeping.
Jan 14 22:54:54 oel51 NET[3761]: /sbin/dhclient-script : updated /etc/resolv.conf
Jan 14 22:54:54 oel51 dhclient: receive_packet failed on wlan0: Network is down
[/code3khoshe5]

Like I say - I'm new to all this, so although I can see that I'm not getting any DHCP offers from my router I really don't know why. If it were my router, wouldn't the same happen when I try to manually connect? This happens [u3khoshe5]every time[/u3khoshe5] I reboot and [u3khoshe5]never[/u3khoshe5] when I connect manually.

Any pointers would be most welcome. I'll try (again - new to this) to get the debug information this evening if necessary.

Thanks

bobmctoot

15-01-2008 15:26:28

Sorry - may have found the answer to my question here[/urli78v5713] (though I swear I did search before posting oops ).

It refers to inserting

[codei78v5713]sleep 30[/codei78v5713]

after comments in /usr/local/share/rutilt/set_ip.sh - I presume to avoid the DHCP client start too quickly.

I'm going to give this a go this evening and will get debug if it doesn't help.