Re: HEADSUP: OpenBSD dhclient incoming

On Mon, Jun 06, 2005 at 09:57:45PM -0700, Brooks Davis wrote:
> 
> In theory we're all clear.  I'll start some buildworlds to verify that.
> If you experience any issues, please post here and I'll try to figure
> them out.  I deleted a lot of code from the rc scripts, so unexpected,
> subtle changes are no unlikely.

I haven't read through the new man pages yet, so it's entirely likely
that enough of dhclient.conf's syntax has changed to make mine
incorrect. However, dhclient now dumps core when trying to process my
media statements from dhclient.conf. From dmesg -a:

...

Setting hostname: x40.teardrop.org.
em0: no link ...  giving up
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPNAK from 192.168.1.1
 Trying medium "ssid NET1 channel 5 wepmode on wepkey 0xWEPKEY" 1
 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
 Segmentation fault
em0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        ether 00:0a:e4:2d:8b:0f
        media: Ethernet autoselect
        status: no carrier
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::20e:9bff:fe6e:60fc%ath0 prefixlen 64 scopeid 0x2 
        ether 00:0e:9b:6e:60:fc
        media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps)
        status: no carrier
        ssid NET1 channel 5
        authmode OPEN privacy ON deftxkey UNDEF
        wepkey 1:104-bit <WEPKEY>
        txpowmax 51 protmode CTS bintval 100
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 
Additional routing options:
.
Starting devd.
hw.acpi.cpu.cx_lowest: 
C1 -> C1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPREQUEST on ath0 to 255.255.255.255 port 67
Trying medium "ssid NET1 channel 5 wepmode on wepkey 0xWEPKEY" 1
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
Trying medium "ssid NET2 channel 11 wepmode on wepkey 0xWEPKEY" 0
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPNAK from 192.168.0.1
Trying medium "ssid NET1 channel 5 wepmode on wepkey 0xWEPKEY" 1
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
Segmentation fault
dhclient ath0: already running?
Mounting NFS file systems:

...

If I comment the following lines out of /etc/dhclient.conf and manually
setup the SSID and WEP keys for the ath0 interface, it works fine:

interface "ath0" {
       media 
       # NET1
       "ssid NET1 channel 5 wepmode on wepkey 0xWEPKEY", 

       # NET2
       "ssid NET2 channel 11 wepmode on wepkey 0xWEPKEY",

       # NET3
       "ssid NET3 channel 8 wepmode on wepkey 0xWEPKEY",

       # NET4
       "ssid NET4 channel 4 wepmode on wepkey 0xWEPKEY",

       # NET5
       "ssid NET5 channel 1 wepmode off";
}

x40# /etc/rc.d/dhclient start ath0
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.103 -- renewal in 43200 seconds.
x40#

I will recompile my dhclient with debugging flags so the core dump is
actually useful. I'll also go through the new man pages to see if I've
missed something, but I figured that even if I am doing something wrong,
dhclient shouldn't dump core.

Please excuse me if I'm doing something dumb; I haven't had any coffee
yet.


-Snow