Hi Jim,
Would the following imply that /etc/dhcpd.conf should include
'192.168.0.2' rather 192.168.0.1' in the 'next-server- entry ?
Adam Bogacki,
[EMAIL PROTECTED]
> ep 21 20:45:02 tux CRON[9489]: (pam_unix) session closed for user root
> Sep 21 20:45:45 tux dhcpd: DHCPDISCOVER from 00:0b:2b:03:d2:57 via eth1
> Sep 21 20:45:45 tux dhcpd: DHCPOFFER on 192.168.0.2 to
> 00:0b:2b:03:d2:57 via eth1
> Sep 21 20:48:24 tux dhcpd: DHCPDISCOVER from 00:0b:2b:03:d2:57 via eth1
> Sep 21 20:48:24 tux dhcpd: DHCPOFFER on 192.168.0.2 to
> 00:0b:2b:03:d2:57 via eth1
Current /etc/dhcpd.conf
> option domain-name-servers 203.96.152.4, 203.96.152.12;
> next-server 192.168.0.1;
> option routers 192.168.0.1;
> #next-server 192.168.0.1;
> option subnet-mask 255.255.255.0;
> default-lease-time 21600;
> max-lease-time 21600;
> #next-server 192.168.0.1;
>
> option root-path "192.168.0.1:/opt/ltsp/i386";
> filename "/tftpboot/lts/2.4.26-ltsp-2/pxelinux.0";
> option log-servers 192.168.0.1;
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.3 192.168.0.10;
> }
>
>
"Anyone who believes that exponential growth can go on /forever/ in a
finite world is either a madman or an economist." --- Kenneth E.
Boulding
0x4E553910.asc
Description: application/pgp-keys
