HowTo connect dhcpd and dhcp-client
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 # (which should correlate to your name server configuration) option domain-name "beer"; # this assumes that your dhcp server is also the router for the subnet option routers 192.168.0.1; # clients shall use this host as nameserver, too option domain-name-servers 192.168.0.1; # this can explicitely be specified option broadcast-address 192.168.0.255; # a minimal /etc/dhcpd.conf example # at first, edit /etc/sysconfig/dhcpd to configure all network interfaces # that the server should listen on (DHCPD_INTERFACE) # if you don't use dynamical DNS updates: # # this statement is needed by dhcpd-3 needs at least this statement. # you have to delete it for dhcpd-2, because it does not know it. # # if you want to use dynamical DNS updates, you should first read # read /usr/share/doc/packages/dhcp-server/DDNS-howto.txt ddns-update-style none; ddns-updates off; # this subnet is served by us authoritative ; # declare the lease times (the time after which a client needs to renew # its lease) # for production use you'll probably use lease times of several days or # even longer # (depending on whether hosts move in/out often (notebook note) or not. # for # example, you could assign long leases to your printers by class ids) default-lease-time 259200; # 3 days max-lease-time 604800; # 1 week # these 10 addresses will be given out dynamically subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.11 192.168.0.20; } --------------------------------------------------------
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.
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable... Check /var/log/{messages,warn} (client & server) * install dhcp-tools on client & server, it contains dhcpdump & dhcping * This little script will reduce typing: ----8<----8<--[dhcp-dump]--8<----8<----8<----8<---- #! /bin/bash DEV=${1:-eth0} tcpdump -i $DEV -lenx -s 1500 port bootps or port bootpc | dhcpdump ----8<----8<--[dhcp-dump]--8<----8<----8<----8<---- chmod +x dhcp-dump * on both client & server, run 'dhcp-dump eth0' or 'dhcp-dump eth0' * then on the client, on another console, do 'ifdown eth0', followed by 'ifup eth0' * on the client's dhcp-dump output, you'll see what is sent (& recieved) * on the servers's dhcp-dump putput, you should see what the client is sending. If you want to post the dhcp-dump output, try to cut it down by showing only the 1st of repeating packets. Cheers, Leen
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. 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 To keep things simple, and consistent with eth1, perhaps this is better: subnet 192.168.100.0 netmask 255.255.255.0 { range 192.168.100.11 192.168.100.20; } Cheers, Leen
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.
To keep things simple, and consistent with eth1, perhaps this is better:
subnet 192.168.100.0 netmask 255.255.255.0 { range 192.168.100.11 192.168.100.20; }
I have: subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.11 192.168.0.20; } But I think this should be correct now, right? So I better try your script first on both machines in order to see what the 'interfaces are talking'. Cheers, Ulrich
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
I just read this remark above. What does this mean? I am using a usual network cable which i usually use to connect to a DSL modem or network hub. In this case I connect both computers directly via the eth interfaces. DO I need a different cable? Cheers, Ulrich
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
On Friday 04 June 2004 09:52, Ulrich Leopold wrote:
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
I just read this remark above. What does this mean? I am using a usual network cable which i usually use to connect to a DSL modem or network hub.
In this case I connect both computers directly via the eth interfaces. DO I need a different cable?
That means: If you connect 2 pc's directly, i.e. with 1 cable, to eachother, you need a 'crosslink cable'. If you connect 1 pc to several other pc's using a hub (or switch?), then the cable from the server to the hub usually is a 'crosslink cable'. Some hubs do not need a crosslink cable, because the server connector is 'crosslinked in the hub itself'. IOW: RTFM, read the hub's (or switch's!) manual. Cheers, Leen
On Sat, 05 Jun, 2004 at 00:38:21 +0200, Leendert Meyer wrote:
On Friday 04 June 2004 09:52, Ulrich Leopold wrote:
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
I just read this remark above. What does this mean? I am using a usual network cable which i usually use to connect to a DSL modem or network hub.
In this case I connect both computers directly via the eth interfaces. DO I need a different cable?
That means:
If you connect 2 pc's directly, i.e. with 1 cable, to eachother, you need a 'crosslink cable'.
Unless one of the adapters is 'autosensing' (which I doubt) When you connect the PCs, do the LEDs on the adapters light up? If they don't, then you need to: a: Use a crosslink cable or b: Put a hub/switch in between the two HTH /Jon -- Whatever rocks your boat!
On Fri, 2004-06-04 at 01:11, Leendert Meyer wrote:
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.
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
If you want to post the dhcp-dump output, try to cut it down by showing only the 1st of repeating packets.
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client. Here is my dchp-dump output from the server for eth1. The client gets ip# 192.168.0.20 and netmask 255.255.255.0. The server shows the following for eth1: ----------------------------------------------------------- uleopold@iceland:~> head -n52 dhcp-dump.output TIME: 13:02:10.654738 IP: IPv4, (00:0b:db:14:dd:0c) > 590 (>) OP: 0 (wrong specified) HTYPE: 0 (wrong specified) HLEN: 0 HOPS: 0 XID: 00000000 SECS: 0 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . --------------------------------------------------------------------------- TIME: 13:02:10.654738 IP: IPv4, (00:0b:db:14:dd:0c) > 590 (>) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 00000000 SECS: 0 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . --------------------------------------------------------------------------- TIME: 13:02:10.654738 IP: IPv4, (00:0b:db:14:dd:0c) > 590 (>) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 0f7a9e40 SECS: 10 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . ----8<-----8<-----8<---------8<-------------8<--------------------- TIME: 13:02:10.677114 IP: IPv4, (52:54:05:fe:c2:d7) > 342 (>) OP: 2 (BOOTPREPLY) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 0f7a9e40 SECS: 10 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 192.168.0.20 SIADDR: 192.168.0.1 GIADDR: 0.0.0.0 CHADDR: 00:0b:db:14:dd:0c:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 192.168.0.1 OPTION: 51 ( 4) IP address leasetime 604800 (7d) OPTION: 1 ( 4) Subnet mask 255.255.255.0 OPTION: 3 ( 4) Routers 192.168.0.1 OPTION: 6 ( 4) DNS server 192.168.0.1 OPTION: 15 ( 5) Domainname beer OPTION: 28 ( 4) Broadcast address 192.168.0.255 --------------------------------------------------------------------------- TIME: 13:02:10.677114 IP: IPv4, (52:54:05:fe:c2:d7) > 342 (>) OP: 2 (BOOTPREPLY) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 0f7a9e40 SECS: 10 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 192.168.0.20 SIADDR: 192.168.0.1 GIADDR: 0.0.0.0 CHADDR: 00:0b:db:14:dd:0c:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 192.168.0.1 OPTION: 51 ( 4) IP address leasetime 604800 (7d) OPTION: 1 ( 4) Subnet mask 255.255.255.0 OPTION: 3 ( 4) Routers 192.168.0.1 OPTION: 6 ( 4) DNS server 192.168.0.1 OPTION: 15 ( 5) Domainname beer OPTION: 28 ( 4) Broadcast address 192.168.0.255 --------------------------------------------------------------------------- Cheers, Ulrich
On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1.
The client gets ip# 192.168.0.20 and netmask 255.255.255.0. No, ;) the dhcp server sends a reply with those data. The question is if that package is received by the client. dhcp-dump on the client would reveil that.
BTW, can you setup a static ip# on the client? This is the easiest, and it is just handy to know that there is a good connection possible between client and server (and the internet). Just fill in an ip# and a netmask in YaST (those above would be good). If your connection with a static ip# works, move on to a dynamic ip# with dhcp. Cheers, Leen
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1.
The client gets ip# 192.168.0.20 and netmask 255.255.255.0. No, ;) the dhcp server sends a reply with those data. The question is if that package is received by the client. dhcp-dump on the client would reveil that. The dhcp-dump for the client never showed anything.
BTW, can you setup a static ip# on the client? This is the easiest, and it is just handy to know that there is a good connection possible between client and server (and the internet). Just fill in an ip# and a netmask in YaST (those above would be good). If your connection with a static ip# works, move on to a dynamic ip# with dhcp. When I log in from the client on the server via ssh it works with a static ip#. But nothing else. Do I have to configure the firewalls on both machines differently for dhcp?
On the server it does IP forwarding and masquerading and allows ssh and rsync only. Do have to enable something there for the internal network?? Maybe an additional port? If yes, which one? On the client I use the setings I always use to get internet connections. It's a laptop and has been connected to various networks with this configuration. So I guess I still make a mistake on the server, right? I also had a look to the /var/log/[messages/warn] but could not reveal anything on the server nor on the client. So what can I do next to get an internet connection for this client? Cheers, Ulrich
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1.
The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
No, ;) the dhcp server sends a reply with those data. The question is if that package is received by the client. dhcp-dump on the client would reveil that.
The dhcp-dump for the client never showed anything.
Sorry, my question was stupid. dhcp-dump does not run when the network is down. ;)
BTW, can you setup a static ip# on the client?
When I log in from the client on the server via ssh it works with a static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host?
Do I have to configure the firewalls on both machines differently for dhcp?
Perhaps turn the firewalls of during testing. If all works well, you can turn them on. If consequently something breaks, you know it's the firewall. ;) You probably need the firewall later to reach the WWW, because of its masquerading/NATting.
On the server it does IP forwarding and masquerading and allows ssh and
As your dhcp server also serves as a router, you have to turn on IP forwarding in /etc/sysconfig/sysctl: IP_FORWARD="yes" cat /proc/sys/net/ipv4/ip_forward should output a single '1'. If not, set it manually with: echo '1' > /proc/sys/net/ipv4/ip_forward If you have put the firewall down on the host, then check this.
On the client I use the setings I always use to get internet connections. It's a laptop and has been connected to various networks with this configuration. So I guess I still make a mistake on the server, right?
AFAICS: Right. Well, that is, unless you hand out your ip# conditionally, in which case the client has to fullfill a certain condition (e.g. send a client-id). But you hand them out unconditionally, so no worries about that. BTW, no need to CC me, I'm on the list. ;) Cheers, Leen
On Mon, 2004-06-07 at 09:59, Leendert Meyer wrote:
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1.
The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
No, ;) the dhcp server sends a reply with those data. The question is if that package is received by the client. dhcp-dump on the client would reveil that.
The dhcp-dump for the client never showed anything.
Sorry, my question was stupid. dhcp-dump does not run when the network is down. ;)
BTW, can you setup a static ip# on the client?
When I log in from the client on the server via ssh it works with a static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host?
ping works in both ways.
Do I have to configure the firewalls on both machines differently for dhcp?
Perhaps turn the firewalls of during testing. If all works well, you can turn them on. If consequently something breaks, you know it's the firewall. ;) You probably need the firewall later to reach the WWW, because of its masquerading/NATting. nothing changes with firewall off. Pinging works but (of course ?) no internet connection because of ip forwarding. But also without ip forwarding it oes not work.
On the server it does IP forwarding and masquerading and allows ssh and
As your dhcp server also serves as a router, you have to turn on IP forwarding in /etc/sysconfig/sysctl: IP_FORWARD="yes" is turned on
cat /proc/sys/net/ipv4/ip_forward should output a single '1'. If not, set it manually with:
returns '1'
echo '1' > /proc/sys/net/ipv4/ip_forward
If you have put the firewall down on the host, then check this.
On the client I use the setings I always use to get internet connections. It's a laptop and has been connected to various networks with this configuration. So I guess I still make a mistake on the server, right?
AFAICS: Right.
Well, that is, unless you hand out your ip# conditionally, in which case the client has to fullfill a certain condition (e.g. send a client-id). But you hand them out unconditionally, so no worries about that. Now I do not know what is wrong?
Ping works with static address and dynamic address. ssh works also with both. Internet connection does not work. Do I have to configure tcp/ip transfer on the dhcp-server in a special way? Maybe the router configuration is wrong? If I turn off firewall what else should I turn off? IP forwarding on router? So basically the internet connection is not working.
BTW, no need to CC me, I'm on the list. ;) sorry, was too sleepy this morning. Realised too late when I had hit the send already. ;-).
Cheers, Ulrich
On Mon, 2004-06-07 at 09:59, Leendert Meyer wrote:
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
On Sunday 06 June 2004 15:37, Ulrich Leopold wrote:
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1.
The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
No, ;) the dhcp server sends a reply with those data. The question is if that package is received by the client. dhcp-dump on the client would reveil that.
The dhcp-dump for the client never showed anything.
Sorry, my question was stupid. dhcp-dump does not run when the network is down. ;)
BTW, can you setup a static ip# on the client?
When I log in from the client on the server via ssh it works with a static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host?
Do I have to configure the firewalls on both machines differently for dhcp?
Perhaps turn the firewalls of during testing. If all works well, you can turn them on. If consequently something breaks, you know it's the firewall. ;) You probably need the firewall later to reach the WWW, because of its masquerading/NATting.
On the server it does IP forwarding and masquerading and allows ssh and
As your dhcp server also serves as a router, you have to turn on IP forwarding in /etc/sysconfig/sysctl:
IP_FORWARD="yes"
cat /proc/sys/net/ipv4/ip_forward should output a single '1'. If not, set it manually with:
echo '1' > /proc/sys/net/ipv4/ip_forward
If you have put the firewall down on the host, then check this.
On the client I use the setings I always use to get internet connections. It's a laptop and has been connected to various networks with this configuration. So I guess I still make a mistake on the server, right?
AFAICS: Right.
Well, that is, unless you hand out your ip# conditionally, in which case the client has to fullfill a certain condition (e.g. send a client-id). But you hand them out unconditionally, so no worries about that.
Some other thought. How should my dhcp-server match the ip# and netmask of my internet connection at eth0? eth0 has ip# xxx.xxx.22.104 netmask 255.255.255.128. eth1 is configured with ip# 192.168.0.1 netmask 255.255.255.0 router just has ip forwarding router option is currently 192.168.0.1 (maybe rather eth0 ip#)? Cheers, Ulrich
On Sun, Jun 06, 2004 at 03:37:57PM +0200, Ulrich Leopold wrote:
On Fri, 2004-06-04 at 01:11, Leendert Meyer wrote:
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.
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
If you want to post the dhcp-dump output, try to cut it down by showing only the 1st of repeating packets.
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1. The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
The server shows the following for eth1: ----------------------------------------------------------- uleopold@iceland:~> head -n52 dhcp-dump.output TIME: 13:02:10.654738 IP: IPv4, (00:0b:db:14:dd:0c) > 590 (>) OP: 0 (wrong specified) HTYPE: 0 (wrong specified)
Please note that dhcpdump does not work with the tcpdump version that shipped with 9.1. You can find a fixed version here: ftp://ftp.suse.com/pub/people/poeml/dhcp-tools/ Peter
On Mon, 2004-06-07 at 11:57, poeml@cmdline.net wrote:
On Sun, Jun 06, 2004 at 03:37:57PM +0200, Ulrich Leopold wrote:
On Fri, 2004-06-04 at 01:11, Leendert Meyer wrote:
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.
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
If you want to post the dhcp-dump output, try to cut it down by showing only the 1st of repeating packets.
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
Here is my dchp-dump output from the server for eth1. The client gets ip# 192.168.0.20 and netmask 255.255.255.0.
The server shows the following for eth1: ----------------------------------------------------------- uleopold@iceland:~> head -n52 dhcp-dump.output TIME: 13:02:10.654738 IP: IPv4, (00:0b:db:14:dd:0c) > 590 (>) OP: 0 (wrong specified) HTYPE: 0 (wrong specified)
Please note that dhcpdump does not work with the tcpdump version that shipped with 9.1. You can find a fixed version here: ftp://ftp.suse.com/pub/people/poeml/dhcp-tools/
Peter
OK. Thanks. This is my new dhcp-dump output. Maybe it reveals some misconfiguration? Am not quite sure. ------------------------------------------------------------------------------- TIME: 12:09:42.289915 IP: 0.0.0.0.68 (00:0b:db:14:dd:0c) > 255.255.255.255.67 (ff:ff:ff:ff:ff:ff) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: c89cc37c SECS: 10 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:0b:db:14:dd:0c:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST) OPTION: 57 ( 2) Maximum DHCP message size 548 OPTION: 50 ( 4) Request IP address 192.168.0.20 OPTION: 51 ( 4) IP address leasetime -1 () OPTION: 55 ( 18) Parameter Request List 1 (Subnet mask) 3 (Routers) 6 (DNS server) 12 (Host name) 15 (Domainname) 17 (Root path) 23 (Default IP TTL) 28 (Broadcast address) 29 (Perform mask discovery) 31 (Perform router discovery) 33 (Static route) 40 (NIS domain) 41 (NIS servers) 42 (NTP servers) 9 (LPR server) 7 (Log server) 200 (???) 44 (NetBIOS name server) OPTION: 12 ( 10) Host name snowdonia OPTION: 60 ( 29) Vendor class identifier Linux 2.4.21-202-default i686 OPTION: 61 ( 7) Client-identifier 01:00:0b:db:14:dd:0c --------------------------------------------------------------------------- TIME: 12:09:42.955750 IP: 192.168.0.1.67 (52:54:05:fe:c2:d7) > 255.255.255.255.68 (ff:ff:ff:ff:ff:ff) OP: 2 (BOOTPREPLY) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: c89cc37c SECS: 10 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 192.168.0.20 SIADDR: 192.168.0.1 GIADDR: 0.0.0.0 CHADDR: 00:0b:db:14:dd:0c:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 192.168.0.1 OPTION: 51 ( 4) IP address leasetime 604800 (7d) OPTION: 1 ( 4) Subnet mask 255.255.255.0 OPTION: 3 ( 4) Routers 192.168.0.1 OPTION: 6 ( 4) DNS server 192.168.0.1 OPTION: 15 ( 5) Domainname beer OPTION: 28 ( 4) Broadcast address 192.168.0.255 --------------------------------------------------------------------------- Cheers, Ulrich
On Mon, Jun 07, 2004 at 12:19:26PM +0200, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 11:57, poeml@cmdline.net wrote:
On Sun, Jun 06, 2004 at 03:37:57PM +0200, Ulrich Leopold wrote:
On Fri, 2004-06-04 at 01:11, Leendert Meyer wrote:
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.
How do you connect your laptop to the server? via 1 cable or via a hub/switch? Mind the crosslink cable...
If you want to post the dhcp-dump output, try to cut it down by showing only the 1st of repeating packets.
I managed to get a connection between dhcp-server and dhcp-client. But I do not manage to get an internet connection for the client. eth1 is the dhcp-server where as eth0 gets the internet connection from the ISP as dhcp-client.
OK. Thanks. This is my new dhcp-dump output. Maybe it reveals some misconfiguration? Am not quite sure.
I don't think so. Check that your default route is correct (192.168.0.1), that you can ping the router (192.168.0.1), and then continue with debugging the firewall on the router. Use tcpdump to confirm that packages are forwarded across the interfaces. 'iptables -nvL -t nat' should show a masquarading rule, etc. Peter
On Monday 07 June 2004 11:26, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 09:59, Leendert Meyer wrote:
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
BTW, can you setup a static ip# on the client?
When I log in from the client on the server via ssh it works with a static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host? ... Now I do not know what is wrong?
Ping works with static address and dynamic address. ssh works also with both.
Huh? :)) So the dhcp setup works already?! Great. Then we can move on to the firewall. Use YaST -> Security -> Firewall. I included some variables from /etc/sysconfig/SuSEfirewall2, but YaST should set them up allright. They are in case of trouble to compare against. The following variables matter for SuSEfirewall2 *** For the server: FW_DEV_EXT="eth-id-xx:xx:xx:xx:xx:xx" FW_DEV_INT="eth-id-yy:yy:yy:yy:yy:yy" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_NETS="0/0" FW_PROTECT_FROM_INTERNAL="no" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_AUTODETECT="yes": means the firewall should detect some services, e.g. dhcp server, and enable them automatically. Start YaST -> Security -> Firewall: *) select the external and internal interfaces ifconfig shows the mac address (hw addr) that is used to distinguish eth devices *) perhaps enable/disable some services (does not matter) *) Firewall features: [x] Forward traffic and do masquerading [ ] Protect from internal network I believe these do not matter ATM: [x] Protect all running services [x] Allow traceroute [ ] Treat IPsec traffic as internal *) Logging options: Your choice. Default is good. *** For the client: basic settings should be *fine*. Perhaps only set the external interface FW_DEV_EXT="eth-id-zz:zz:zz:zz:zz:zz" That should get you on the net. Cheers, Leen
On Mon, 2004-06-07 at 15:25, Leendert Meyer wrote:
On Monday 07 June 2004 11:26, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 09:59, Leendert Meyer wrote:
On Monday 07 June 2004 08:29, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 03:03, Leendert Meyer wrote:
BTW, can you setup a static ip# on the client?
When I log in from the client on the server via ssh it works with a static ip#. But nothing else.
Not even ping? Ping host -> client, ping client -> host? ... Now I do not know what is wrong?
Ping works with static address and dynamic address. ssh works also with both.
Huh? :)) So the dhcp setup works already?! Great.
Then we can move on to the firewall. Use YaST -> Security -> Firewall. I included some variables from /etc/sysconfig/SuSEfirewall2, but YaST should set them up allright. They are in case of trouble to compare against.
The following variables matter for SuSEfirewall2
*** For the server:
FW_DEV_EXT="eth-id-xx:xx:xx:xx:xx:xx" FW_DEV_INT="eth-id-yy:yy:yy:yy:yy:yy" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_NETS="0/0" FW_PROTECT_FROM_INTERNAL="no" FW_SERVICE_AUTODETECT="yes"
FW_SERVICE_AUTODETECT="yes": means the firewall should detect some services, e.g. dhcp server, and enable them automatically.
Start YaST -> Security -> Firewall:
*) select the external and internal interfaces ifconfig shows the mac address (hw addr) that is used to distinguish eth devices
*) perhaps enable/disable some services (does not matter)
*) Firewall features: [x] Forward traffic and do masquerading [ ] Protect from internal network I believe these do not matter ATM: [x] Protect all running services [x] Allow traceroute [ ] Treat IPsec traffic as internal
*) Logging options: Your choice. Default is good.
*** For the client:
basic settings should be *fine*. Perhaps only set the external interface
FW_DEV_EXT="eth-id-zz:zz:zz:zz:zz:zz"
That should get you on the net.
Ok. I have all these options checked. It should work now. But it does not. I have the feeling that the problem is in the transmission on teh server of input from eth1 (dhcpd-server, internal device) to eth0 (dhcp-client to the internet, external device). Maybe the router configuration doe snot match? I configured this as default=192.168.01 and IP forwarding. In addition when I boot now the computer I get martian sources from my ISP somewhere which "blocks" the internet. Is this due to running and detecting a dhcpd-server? I am getting a bit lost I must say. I have been configuring and trying so much that I might have screwed something up now (?). Anyway, I woudl be gratful for further suggestions how to detect the flow from eth1 to eth0. Cheers, Ulrich
On Monday 07 June 2004 17:02, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 15:25, Leendert Meyer wrote:
Ok. I have all these options checked. It should work now. But it does not.
I have the feeling that the problem is in the transmission on teh server of input from eth1 (dhcpd-server, internal device) to eth0 (dhcp-client to the internet, external device).
Yes.
Maybe the router configuration doe snot match? I configured this as default=192.168.01 and IP forwarding.
In addition when I boot now the computer I get martian sources from my ISP somewhere which "blocks" the internet. Is this due to running and detecting a dhcpd-server?
Yes, you can turn that off with: FW_KERNEL_SECURITY="no" in /etc/sysconfig/SuSEfirewall2 (read its comment there).
I am getting a bit lost I must say. I have been configuring and trying so much that I might have screwed something up now (?).
That is a possibility. ;) I had some difficulties too with the first time. What is the output of: - diff -U 0 /etc/sysconfig/SuSEfirewall2 /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.sysconfig - ifconfig eth0 - ifconfig eth1 - route Leen
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
On Monday 07 June 2004 17:02, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 15:25, Leendert Meyer wrote:
Ok. I have all these options checked. It should work now. But it does not.
I have the feeling that the problem is in the transmission on teh server of input from eth1 (dhcpd-server, internal device) to eth0 (dhcp-client to the internet, external device).
Yes.
Maybe the router configuration doe snot match? I configured this as default=192.168.01 and IP forwarding.
In addition when I boot now the computer I get martian sources from my ISP somewhere which "blocks" the internet. Is this due to running and detecting a dhcpd-server?
Yes, you can turn that off with: FW_KERNEL_SECURITY="no" in /etc/sysconfig/SuSEfirewall2 (read its comment there).
I am getting a bit lost I must say. I have been configuring and trying so much that I might have screwed something up now (?).
That is a possibility. ;) I had some difficulties too with the first time.
What is the output of: - diff -U 0 /etc/sysconfig/SuSEfirewall2 /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.sysconfig - ifconfig eth0 - ifconfig eth1 - route
Ok. I attached three different files diff-firewall, ifconfig and route. So far I have not turned off FW_KERNEL_SECURITY="no" I changed some of the ip# numbers and subnet numbers as well in order to try to match them between eth0 and eth1 and route. But I am not quite there where I thought I could be ;-) But thanks a lot to you Leen and Peter so far. Cheers, Ulrich eth0 Link encap:Ethernet HWaddr 00:00:B4:BB:CA:DB inet addr:62.194.22.104 Bcast:255.255.255.255 Mask:255.255.255.128 inet6 addr: fe80::200:b4ff:febb:cadb/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:25586 errors:0 dropped:0 overruns:0 frame:0 TX packets:2642 errors:0 dropped:0 overruns:0 carrier:0 collisions:5 txqueuelen:1000 RX bytes:3422205 (3.2 Mb) TX bytes:360476 (352.0 Kb) Interrupt:5 Base address:0xbc00 eth1 Link encap:Ethernet HWaddr 52:54:05:FE:C2:D7 inet addr:192.168.0.1 Bcast:192.168.0.127 Mask:255.255.255.128 inet6 addr: fe80::5054:5ff:fefe:c2d7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:81 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9466 (9.2 Kb) TX bytes:4418 (4.3 Kb) Interrupt:9 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1223 errors:0 dropped:0 overruns:0 frame:0 TX packets:1223 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:237604 (232.0 Kb) TX bytes:237604 (232.0 Kb)
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
On Monday 07 June 2004 17:02, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 15:25, Leendert Meyer wrote:
Ok. I have all these options checked. It should work now. But it does not.
I have the feeling that the problem is in the transmission on teh server of input from eth1 (dhcpd-server, internal device) to eth0 (dhcp-client to the internet, external device).
Yes.
Maybe the router configuration doe snot match? I configured this as default=192.168.01 and IP forwarding.
In addition when I boot now the computer I get martian sources from my ISP somewhere which "blocks" the internet. Is this due to running and detecting a dhcpd-server?
Yes, you can turn that off with: FW_KERNEL_SECURITY="no" in /etc/sysconfig/SuSEfirewall2 (read its comment there).
I am getting a bit lost I must say. I have been configuring and trying so much that I might have screwed something up now (?).
That is a possibility. ;) I had some difficulties too with the first time.
What is the output of: - diff -U 0 /etc/sysconfig/SuSEfirewall2 /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.sysconfig - ifconfig eth0 - ifconfig eth1 - route
Ok. I attached three different files diff-firewall, ifconfig and route. So far I have not turned off FW_KERNEL_SECURITY="no" I changed some of the ip# numbers and subnet numbers as well in order to try to match them between eth0 and eth1 and route. But I am not quite there where I thought I could be ;-) But thanks a lot to you Leen and Peter so far. Cheers, Ulrich eth0 Link encap:Ethernet HWaddr 00:00:B4:BB:CA:DB inet addr:62.194.22.104 Bcast:255.255.255.255 Mask:255.255.255.128 inet6 addr: fe80::200:b4ff:febb:cadb/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:25586 errors:0 dropped:0 overruns:0 frame:0 TX packets:2642 errors:0 dropped:0 overruns:0 carrier:0 collisions:5 txqueuelen:1000 RX bytes:3422205 (3.2 Mb) TX bytes:360476 (352.0 Kb) Interrupt:5 Base address:0xbc00 eth1 Link encap:Ethernet HWaddr 52:54:05:FE:C2:D7 inet addr:192.168.0.1 Bcast:192.168.0.127 Mask:255.255.255.128 inet6 addr: fe80::5054:5ff:fefe:c2d7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:81 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9466 (9.2 Kb) TX bytes:4418 (4.3 Kb) Interrupt:9 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1223 errors:0 dropped:0 overruns:0 frame:0 TX packets:1223 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:237604 (232.0 Kb) TX bytes:237604 (232.0 Kb)
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
On Monday 07 June 2004 17:02, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 15:25, Leendert Meyer wrote:
Ok. I have all these options checked. It should work now. But it does not.
I have the feeling that the problem is in the transmission on teh server of input from eth1 (dhcpd-server, internal device) to eth0 (dhcp-client to the internet, external device).
Yes.
Maybe the router configuration doe snot match? I configured this as default=192.168.01 and IP forwarding.
In addition when I boot now the computer I get martian sources from my ISP somewhere which "blocks" the internet. Is this due to running and detecting a dhcpd-server?
Yes, you can turn that off with: FW_KERNEL_SECURITY="no" in /etc/sysconfig/SuSEfirewall2 (read its comment there).
I am getting a bit lost I must say. I have been configuring and trying so much that I might have screwed something up now (?).
That is a possibility. ;) I had some difficulties too with the first time.
What is the output of: - diff -U 0 /etc/sysconfig/SuSEfirewall2 /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.sysconfig - ifconfig eth0 - ifconfig eth1 - route
Ok. I attached three different files diff-firewall, ifconfig and route.
So far I have not turned off
FW_KERNEL_SECURITY="no"
I changed some of the ip# numbers and subnet
numbers as well in order to try to match them between eth0 and eth1 and route. But I am not
quite there where I thought I could be ;-) But thanks a lot to you Leen and Peter so far.
Cheers, Ulrich
diff-firewall
--- /etc/sysconfig/SuSEfirewall2 2004-06-07 17:38:14.260400832 +0200
+++ /usr/share/doc/packages/SuSEfirewall2/SuSEfirewall2.sysconfig 2004-04-06 03:24:40.000000000 +0200
@@ -1,0 +2 @@
+# Copyright (c) 2003,2004 SuSE Linux AG Nuernberg, Germany. All rights reserved.
@@ -3,2 +4 @@
-# Author: Marc Heuse
On Monday 07 June 2004 22:02, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
Ok. I attached three different files diff-firewall, ifconfig and route.
You did attach ifconfig and route, but no diff-firewall. Cheers, Leen
On Monday 07 June 2004 22:14, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
I changed some of the ip# numbers and subnet numbers as well in order to try to match them between eth0 and eth1 and route. But I am not quite there where I thought I could be ;-) But thanks a lot to you Leen and Peter so far.
Your firewall seems ok. Setting the external interface to 'auto' is an option. The broadcast/netmask on eth1 seems a bit strange to me, but it is not wrong persé. Did you deliberately set the eth1 netmask to match it with the eth0's? The route table seems ok. About the pinging from the client to the WWW: Try to ping by ip# instead of hostname. E.g. 'ping 195.135.220.3' to ping www.suse.de If that works, you only need to set the nameservers right in your dhcpd.conf! Use the same nameservers as on the host (your provider's). Cheers, Leen
On Mon, 2004-06-07 at 22:53, Leendert Meyer wrote:
On Monday 07 June 2004 22:14, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 18:46, Leendert Meyer wrote:
I changed some of the ip# numbers and subnet numbers as well in order to try to match them between eth0 and eth1 and route. But I am not quite there where I thought I could be ;-) But thanks a lot to you Leen and Peter so far.
Your firewall seems ok. Setting the external interface to 'auto' is an option.
The broadcast/netmask on eth1 seems a bit strange to me, but it is not wrong persé. Did you deliberately set the eth1 netmask to match it with the eth0's?
The route table seems ok.
About the pinging from the client to the WWW:
Try to ping by ip# instead of hostname.
E.g. 'ping 195.135.220.3' to ping www.suse.de
If that works, you only need to set the nameservers right in your dhcpd.conf! Use the same nameservers as on the host (your provider's).
Today I had more time to do some work on it. And it works!!! :) It was indeed only the name server which was not correctly configured. I put the first ip# of my ISP's name server. One further question: How can I put the second ip# of my ISP' name server in the dhcpd.conf? Just by sperating with commas or a space? Or do I have to write a complete new line. Thanks a lot Leen!! Best regards, Ulrich
On Wednesday 09 June 2004 19:37, Ulrich Leopold wrote:
On Mon, 2004-06-07 at 22:53, Leendert Meyer wrote:
Try to ping by ip# instead of hostname.
Today I had more time to do some work on it. And it works!!! :)
Great! :))
It was indeed only the name server which was not correctly configured. I put the first ip# of my ISP's name server.
One further question: How can I put the second ip# of my ISP' name server in the dhcpd.conf? Just by sperating with commas or a space? Or do I have to write a complete new line.
option domain-name-servers 10.0.0.1, 10.0.0.2; man dhcpd.conf, then press '/' to search, enter 'domain-name-servers' and press enter ;P Cheers, Leen
participants (4)
-
Jon Clausen -
Leendert Meyer -
poeml＠cmdline.net -
Ulrich Leopold