SV: Listening IP

[Anders Rosendal]

Have you tried setting:
 
option dhcp-server-identifier 192.168.31.10;
 
/Anders Rosendal

________________________________

Från: dhcp-users-bounce at isc.org genom Frank Bulk - iNAME
Skickat: sö 2008-07-06 05:19
Till: dhcp-users at isc.org
Ämne: RE: Listening IP



Why not load DHCP to bind to the second Ethernet port?  You can also use
iptables to manipulate just the DHCP response packets (that's what our DHCP
appliance does).

Frank

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
Of Dean, Barry
Sent: Wednesday, July 02, 2008 8:26 AM
To: dhcp-users at isc.org
Subject: Listening IP

Hi, I have four DHCP servers, ISC DHCP 4.0.0 running on Solaris 10 x86 on
Sun X4200 hardware.

These machines have 4 network cards. The one I am using has id e1000g3.

On this card there are two IPs, an example:

e1000g3:        192.168.31.100  primary-name
e1000g3:1       192.168.31.10   dhcp

My config file says to listen on the 31 subnet thus:

subnet 192.168.31.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0 ;
  option routers 192.168.31.1 ;
  option domain-name-servers 192.168.120.100, 192.168.120.101 ;
}

Problem is clients report that the DHCP server that gave them an IP was
192.168.31.100, the primary-name.

I would like them to think it was the 192.168.31.10 IP, the dhcp name
instead.

With other daemons, like DNS, RADIUS, I am used to binding the service to an
IP, with DHCP it looks like you bind to an entire subnet, can this be
changed? I would only like the servers to listen on the "dhcp" interface and
only reply from it.

Thanks.

---------------
Barry Dean
Networks Team
Computing Services Department
Browlow Hill/Crown Street
Liverpool
Email: B.Dean_at_liverpool.ac.uk





--
This message has been scanned for viruses and
dangerous content by MailScanner on mars.rosendal.nu,
and is believed to be clean.




-- 
This message has been scanned for viruses and
dangerous content by MailScanner on 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/20080706/88600729/attachment.html>