rc.inet1 wireless problem

mcnalu · 11-16-2008, 03:56 PM

I've got my rt2860 wireless working on my new asus 1000h running slackware 12.1. With static IP it works without a problem, but if I use dhcp then it fails - no ip gets assigned to it.

Here's the output with LOGGER messages:

Code:

bash-3.1# ./rc.inet1 start
./rc.inet1: /sbin/ifconfig ra0 up
./rc.inet1:  ra0 information: 'Any ESSID'
./rc.inet1:  /sbin/iwconfig ra0 nick mynick
./rc.inet1:  /sbin/iwconfig ra0 essid "myessid"
./rc.inet1:  '/sbin/iwpriv ra0 set AuthMode=WPAPSK'
./rc.inet1:  '/sbin/iwpriv ra0 set EncrypType=TKIP'
./rc.inet1:  '/sbin/iwpriv ra0 set WPAPSK=myhexkey'
./rc.inet1:  /sbin/iwconfig ra0 essid "myessid"
Polling for DHCP server on interface ra0:
/etc/rc.d/rc.inet1:  /sbin/dhcpcd -d -t 30 -h myhostname ra0
dhcpcd: MAC address = 00:22:43:43:63:7f
/etc/rc.d/rc.inet1:  eth5 interface does not exist (yet)
/etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.1.1 metric 1
SIOCADDRT: No such process

All the config is in rc.inet1.conf, here's the relevant stuff:

Code:

IFNAME[4]="ra0"
#IPADDR[4]="192.168.1.104"
#NETMASK[4]="255.255.255.0"
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="myhostname"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""

WLAN_ESSID[4]=myessid
WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set 
WPAPSK=myhexkey"

After looking at rc.inet1 and rc.wireless and the log messages above, I created this script:

Code:

#!/bin/bash
ifconfig ra0 up
sleep 3
iwconfig ra0 nick mynick
iwconfig ra0 essid "myessid"
iwpriv ra0 set AuthMode=WPAPSK
iwpriv ra0 set EncrypType=TKIP
iwpriv ra0 set WPAPSK=myhexkey
iwconfig ra0 essid "myessid"
dhcpcd -d -t 5 -h myhostname ra0

This works, but I can't see why rc.inet1 is failing.

Any ideas?
Edit: it seems to be related to the ifconfig up then down in rc.inet1.conf which tests for a connection when DHCP_TIMEOUT isn't set.

Ilgar · 11-16-2008, 04:15 PM

Yes, this DHCP_TIMEOUT issue came up in several other cases too (you can search for the threads). Set a timeout in inet1.conf, that will probably solve the problem.

mcnalu · 11-16-2008, 04:57 PM

Thanks Ilgar - didn't spot those posts.

I don't think it's the timeout that's the problem, but the code that tests the connection and decides the timeout.

Here's the relevant bit of rc.inet1:

Code:

        if [ "${DHCP_TIMEOUT[$i]}" = "" ]; then
          ifconfig ${1} up && sleep 1
          CONNSTATUS="$(cat /sys/class/net/${1}/carrier 2> /dev/
null)" 
          ifconfig ${1} down
          if [ "$CONNSTATUS" = "0" ]; then
            # The kernel has just told us the cable isn't even p
lugged in, but we will
            # give any DHCP server a short chance to reply anywa
y:
            echo "No carrier detected on ${1}.  Reducing DHCP ti
meout to 10 seconds."
            DHCP_TIMEOUT[$i]=10
          fi
        fi

If DHCP_TIMEOUT isn't set then this code is executed and the problem occurs. If DHCP_TIMEOUT is set to anything then it won't be executed and so the problem doesn't occur.

Ilgar · 11-17-2008, 05:26 AM

Your post brings back some memories

:

http://www.linuxquestions.org/questi...ml#post3135298

mcnalu · 11-18-2008, 03:26 PM

Nice to know I'm not alone

I think this problem is caused by dhcpcd failing to bring the interface up after the "is the cable connected" ifconfig up/down test.