On Friday 04 June 2004 09:48, Ulrich Leopold wrote:
On Fri, 2004-06-04 at 01:21, Leendert Meyer wrote:
Hi Ulrich,
I posted my previous mail too soon, read on...
On Thursday 03 June 2004 22:54, Ulrich Leopold wrote:
Hi,
I got the dhcpd server (SuSE 9.1) running with the configuration below. But I cannot assign an dynamic IP address to my laptop (SuSE 9.0) in the local network now. The laptop is configured as a dhcp client and usually to works fine with this configuration. So I guess there are still some things missing in the dhcpd configuration?
Can it be due to my firewall settings of the dhcpd server? I turned on ssh and rsync ports as well as forwarding and masquerading, protect all running services and trace route. Protect from internal network is disabled.
Regards, Ulrich
--------------------------------------------------------- # let's give the local domain a name
...
subnet 192.168.0.0 netmask 255.255.255.0 {
according to the netmask, the network is 192.168.0
range 192.168.0.11 192.168.0.20; }
What is the ip# of the interface on wich you are listening? It should be in the same subnet as the declaration above.
The ip# for eth1 is 192.168.0.1. The dhcpd server is listening to eth1 and is connected to the internet via eth0 and dhcp-client. So ip3 of eth1 and subnet should match, right?
In an earlier post, in another thread, that interface, eth1, had ip# 192.168.100.99. That is /not/ on the same subnet. Change the ip# to 192.168.0.x or change the netmask to 255.255.0.0
Yes, but I changed it to the above ip#. Sorry for the confusion.
Well done! :) I was afraid you would not have done this. ;) ...
But I think this should be correct now, right?
Yes, I think so.
So I better try your script first on both machines in order to see what the 'interfaces are talking'.
Yes, continue in the other thread. Cheers, Leen