dhcp on p-t-p interface

[Blake Hudson]

Start DHCPD with '-q venet0:0' or similar or put in 79.99.1.114 as a 
dummy unauthoritative subnet that does not have any pools.

--Blake

-------- Original Message  --------
Subject: dhcp on p-t-p interface
From: Anders Rosendal <anders at rosendal.nu>
To: dhcp-users at isc.org
Date: Friday, September 19, 2008 3:41:35 PM
>
> Hi
> I'm having one server at local LAN that I'm serving with IP's. I'm now 
> trying out a a virtual server from a hosting provider, and aiming to 
> use that as a redundant dhcp-server. When installing dhcpd on it I ran 
> into problems. The public network interface of the server is a p-t-p 
> one, with a broadcast set to 0.0.0.0.
> I guess that the hosting supplier is using XEN or similar to provide 
> the service.
> This is what I've got:
>
> A Ubuntu 8.04 LTS server with isc-dhcpd-V3.0.6.
>
> rosendal at hera:~$ cat /etc/network/interfaces
> # This configuration file is auto-generated.
> # WARNING: Do not edit this file, otherwise your changes will be lost.
> # Please edit template /etc/network/interfaces.template instead.
>
>
> # Auto generated interfaces
> auto lo
> iface lo inet loopback
>
> auto venet0
> iface venet0 inet static
>         address 127.0.0.1
>         netmask 255.255.255.255
>         broadcast 0.0.0.0
>         up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
>         up route add default gw 192.0.2.1
>
> iface venet0 inet6 static
>         address ::1
>         netmask 128
>
> auto venet0:0
> iface venet0:0 inet static
>         address 79.99.1.114
>         netmask 255.255.255.255
>         broadcast 0.0.0.0
>
> rosendal at hera:~$ ifconfig -a
> 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:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> venet0    Link encap:UNSPEC  HWaddr 
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
>           inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  
> Mask:255.255.255.255
>           inet6 addr: ::1/128 Scope:Host
>           UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:452 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:339 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:49704 (48.5 KB)  TX bytes:56924 (55.5 KB)
>
> venet0:0  Link encap:UNSPEC  HWaddr 
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
>           inet addr:79.99.1.114  P-t-P:79.99.1.114  Bcast:0.0.0.0  
> Mask:255.255.255.255
>           UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
>
> rosendal at hera:~$
>
> The dhcpd.conf file is copied from the working server and I have added:
>
> subnet 79.99.1.114 netmask 255.255.255.255 {
> }
>
>
> but when restarting dhcpd I get the following message in dhcpd I get 
> the following message:
>
> Sep 19 22:30:04 hera dhcpd: No subnet declaration for venet0:0 (0.0.0.0).
> Sep 19 22:30:04 hera dhcpd: ** Ignoring requests on venet0:0.  If this 
> is not what
> Sep 19 22:30:04 hera dhcpd:    you want, please write a subnet declaration
> Sep 19 22:30:04 hera dhcpd:    in your dhcpd.conf file for the network 
> segment
> Sep 19 22:30:04 hera dhcpd:    to which interface venet0:0 is attached. **
> Sep 19 22:30:04 hera dhcpd:
> Sep 19 22:30:04 hera dhcpd:
> Sep 19 22:30:04 hera dhcpd: Not configured to listen on any interfaces!
>
>
>
> Does anyone has suggestion how I should configure to get the server to 
> listen to the venet0:0 interface?
> The router on my main network is configured to forward dhcp-requests 
> to my "redundant" server, so this is not a problem.
>
>
> Thanks in advance.
>
> Regards Anders R
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/> at
> mars.rosendal.nu, and is believed to be clean. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20080919/95d97979/attachment.html>