Shared Network Question
inetadmin at ruraltel.net
Tue Aug 7 13:08:27 UTC 2007
Glenn Satchell wrote:
>> Date: Mon, 06 Aug 2007 10:29:54 -0500
>> From: Clayton Keller <inetadmin at ruraltel.net>
>> To: dhcp-users at isc.org
>> Subject: Shared Network Question
>> I have a setup in which a DHCP request is coming in from a Relay Agent
>> IP address of 192.168.121.2, however, I'd like to assign it an address
>>from a 10.10.45.0 subnet.
>> My understanding was I could use a shared-network to handle this type of
>> situation. We are also looking at using some Option 82 info as well.
>> Here is my configuration for the shared network:
>> shared-network Lab
>> subnet 192.168.121.0 netmask 255.255.255.128
>> class "Test"
>> match if option agent.circuit-id = "XXXX";
>> subnet 10.1.45.0 netmask 255.255.255.0
>> default-lease-time 1800;
>> max-lease-time 3600;
>> option routers 10.1.45.1;
>> option broadcast-address 10.1.45.255;
>> failover peer "failover";
>> deny dynamic bootp clients;
>> allow members of "XXXX";
>> range 10.1.45.10 10.1.45.254;
>> When I have this config loaded on both dhcpd servers, the following
>> response is seen from the logs when the discover packet is received.
>> dhcpd: DHCPDISCOVER from xx:xx:xx:xx:xx:xx via 192.168.121.2: peer holds
>> all free leases
>> I'm not sure if I'm not setting this up properly, or if this is a viable
>> option to the setup we are working with regarding the incoming traffic.
> The class is called "Test" but you're allowing members of "XXXX". You
> should allow members of "Test". All others are implicitly denied,
> including your Test class.
> Also classes are usually defined in the global scope, but I don't think
> that is the immediate problem.
> Glenn Satchell mailto:glenn.satchell at uniq.com.au | Some days we are
> Uniq Advances Pty Ltd http://www.uniq.com.au | the flies; some
> PO Box 70 Paddington NSW Australia 2021 | days we are the
> tel:0409-458-580 tel:02-9380-6360 fax:02-9380-6416 | windscreens...
Thank you for the input. My immediate issue was that of a non-matching
Option 82 value. Once corrected, all was functioning as expected.
More information about the dhcp-users