DHCPD on eth0:0 ?
Hello, Did anyone ever set up a DHCP server on a virtual interface (e.g. eth0:0)? I've searched the archives on the web but nothing came out of this. I've succeeded may times to set DHCPD on boxes with 2 NIC's, but this one's too hard for me. When invoking dhcpd on net device eth0:0, it complains about not being configured to listen on any interface, among other things: Jan 20 17:30:14 patagonia dhcpd: Wrote 0 leases to leases file. Jan 20 17:30:14 patagonia dhcpd: Jan 20 17:30:14 patagonia dhcpd: No subnet declaration for eth0:0 (0.0.0.0). Jan 20 17:30:14 patagonia dhcpd: Ignoring requests on eth0:0. Jan 20 17:30:14 patagonia dhcpd: If this is not what you want, please write Jan 20 17:30:14 patagonia dhcpd: a subnet declaration in your dhcpd.conf file for Jan 20 17:30:14 patagonia dhcpd: the network segment to which interface eth0:0 is att ached. Jan 20 17:30:14 patagonia dhcpd: Jan 20 17:30:14 patagonia dhcpd: Not configured to listen on any interfaces! This is the case with SuSE's rpm, and with the latest DHCPD version from tarball found on ISC's ftp. This box runs SuSE 6.2 with Kernel 2.4.0. Somebody to help me? If so, what should I have in the network section of /etc/rc.config? TIA /NB ________________ Nicolas Beaulieu Teamwork is essential: it allows you to blame someone else. _________________
Nicolas Beaulieu wrote:
Hello,
Did anyone ever set up a DHCP server on a virtual interface (e.g. eth0:0)? I've searched the archives on the web but nothing came out of this.
I've succeeded may times to set DHCPD on boxes with 2 NIC's, but this one's too hard for me. When invoking dhcpd on net device eth0:0, it complains about not being configured to listen on any interface, among other things:
Jan 20 17:30:14 patagonia dhcpd: Wrote 0 leases to leases file. Jan 20 17:30:14 patagonia dhcpd: Jan 20 17:30:14 patagonia dhcpd: No subnet declaration for eth0:0 (0.0.0.0). Jan 20 17:30:14 patagonia dhcpd: Ignoring requests on eth0:0. Jan 20 17:30:14 patagonia dhcpd: If this is not what you want, please write Jan 20 17:30:14 patagonia dhcpd: a subnet declaration in your dhcpd.conf file for Jan 20 17:30:14 patagonia dhcpd: the network segment to which interface eth0:0 is attached. Jan 20 17:30:14 patagonia dhcpd: Not configured to listen on any interfaces!
This is the case with SuSE's rpm, and with the latest DHCPD version from tarball found on ISC's ftp.
This box runs SuSE 6.2 with Kernel 2.4.0.
Somebody to help me? If so, what should I have in the network section of /etc/rc.config?
Have you checked your /etc/dhcpd.conf file to see if there is a subnet... section for the subnet that eth0:0 is on? That's pretty much what the error messages imply. The subnet part of my dhcpd.conf looks like: subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.64 192.168.0.127; option broadcast-address 192.168.0.255; } Here, eth0 is on the 192.168.0.0 network. Let me know if you still can't quite nail the problem, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Sun, 21 Jan 2001, Chris Reeves wrote: <*]Date: Sun, 21 Jan 2001 17:01:55 +0000 <*]From: Chris Reeves <chris.reeves@iname.com> <*]To: Nicolas Beaulieu <gulliver@patagonia.dyndns.org>, <*] SuSE Mailing List <suse-linux-e@suse.com> <*]Subject: Re: [SLE] DHCPD on eth0:0 ? [...] <*] <*]Have you checked your /etc/dhcpd.conf file to see if there is a <*]subnet... section for the subnet that eth0:0 is on? That's pretty much <*]what the error messages imply. The subnet part of my dhcpd.conf looks <*]like: <*]subnet 192.168.0.0 netmask 255.255.255.0 { <*] range 192.168.0.64 192.168.0.127; <*] option broadcast-address 192.168.0.255; <*]} <*]Here, eth0 is on the 192.168.0.0 network. <*] <*]Let me know if you still can't quite nail the problem, <*] Chris Chris, Yes, the error message implies that "there is no subnet declaration" for this specific net device, which is the virtual eth0:0... But there is a subnet declaration for this device in dhcpd.conf: -> From ifconfig: eth0:0 Link encap:Ethernet HWaddr 00:E0:29:39:E7:F6 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING PROMISC MTU:1500 Metric:1 Interrupt:9 Base address:0xe800 -> From dhcpd.conf subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.10 192.168.1.16; option routers 192.168.1.1; option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option domain-name-servers a.b.c.d, a.b.c.e; [...] } Moreover, DHCPD version 3.0 &+ complains about missing subnet declaration for each net device, but ignores them all but the net device on which the DHCPD runs. So the issue here is not the subnet declaration for eth0:0 that's missing (I think), but how to bind eth0:0 with DHCPD config. The archives on the web about this specific problem are not clear. Nobody seems to have an answer to my question. The other solution would be: get rid of the old ISA modem and get an ISA NIC as eth1 (which is very easy to configure with DHCPD). Anyway, thanks for your help... /NB ________________ Nicolas Beaulieu Teamwork is essential: it allows you to blame someone else. _________________
participants (2)
-
Chris Reeves -
Nicolas Beaulieu