Johan skrev:
Please post the appropriate configuration and log files, at least /etc/dhcpd*.

        Joachim


dhcpd seems to work ok, verified this by using the sis0 interface on the same computer:
# dhcpd -d sis0
DHCPDISCOVER from 00:0c:6e:7e:9e:4f via sis0
DHCPOFFER on 172.16.90.32 to 00:0c:6e:7e:9e:4f via sis0
DHCPREQUEST for 172.16.90.32 from 00:0c:6e:7e:9e:4f via sis0
DHCPACK on 172.16.90.32 to 00:0c:6e:7e:9e:4f via sis0

no messages at all in /var/log/messages or dmesg concerning dhcpd

/etc/dhcpd.conf:
option  domain-name "linner.biz";
option  domain-name-servers 195.67.199.9, 195.67.199.10, 195.67.199.11;

subnet 172.16.90.0 netmask 255.255.255.0 {
        option routers 172.16.90.1;

        range 172.16.90.32 172.16.90.127;
}

/var/db/dhcpd.leases (first entry is ral0, second sis0, yeah the ral0 lease is there but don't reaches the client):
lease 172.16.90.33 {
        starts 4 2005/11/10 00:57:28;
        ends 4 2005/11/10 00:57:32;
        hardware ethernet 00:13:46:7a:63:01;
        uid 01:00:13:46:7a:63:01;
        client-hostname "deefault";
}
lease 172.16.90.32 {
        starts 6 2005/11/12 19:02:02;
        ends 0 2005/11/13 07:02:02;
        hardware ethernet 00:0c:6e:7e:9e:4f;
        uid 01:00:0c:6e:7e:9e:4f;
        client-hostname "deefault";
}

/etc/dhcpd.interfaces:
sis0
ral0

/Johan


Ok, I have narrowed the problem down.
If I don't use a wep key (ifconfig ral0 -nwkey) then dhcpd works and the client gets the ip. So it seems like some kind of problem with hostap/ral/nwkey together with dhcpd...

/Johan

Reply via email to