On 18:47, Thu 25 Feb 10, Lars Nooden wrote:
> DHCPd on current serves up leases with no default route. It's been like
> that for a long while now and I've not been able to find anything about
> a solution.
Once you reread the configuration snippet from your mail it will be
clear. If not, read the end of my reply.
>
>
> I notice in particular when connecting with clients from the various
> debian-based distros' install CDs. Old CDs (e.g. Ubuntu 5.10, 8.10)
> which had previously gotten complete network information don't get a
> route from either subnet configuration below:
>
> subnet 192.168.100.0 netmask 255.255.255.196 {
> option routers 192.168.100.1;
> range 192.168.101.9 192.168.101.14;
> option domain-name-servers 192.168.101.1;
> }
>
> subnet 192.168.101.0 netmask 255.255.255.196 {
> #option routers 192.168.101.1;
> range 192.168.101.9 192.168.101.14;
> option domain-name-servers 192.168.101.1;
> }
>
> OpenBSD clients work fine. What needs changing in the configuration?
>
> Fully installed debian and debian-based distros' dhclient give and error
> "SIOCSIFNETMASK: Invalid argument" but otherwise seem to function:
The invalid argument is because the netmask is invalid. Try 192 instead
of 196.
>
> wmaster0: unknown hardware address type 801
> wmaster0: unknown hardware address type 801
> Listening on LPF/eth0/00:bb:bb:bb:bb:bb
> Sending on LPF/eth0/00:bb:bb:bb:bb:bb
> Sending on Socket/fallback
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPACK from 192.168.101.1
> SIOCSIFNETMASK: Invalid argument
> bound to 192.168.101.9 -- renewal in 19062 seconds.
As you can see, it picks an ip from the 101.X subnet.
There, you clearly commented out the 'option routers' entry.
Not _that_ weird dhcpd does not provide a default gateway now is it ?
--
Michiel van Baak
[email protected]
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD
"Why is it drug addicts and computer aficionados are both called users?"
