dhcp relay
Patrick Trapp
ptrapp at nex-tech.com
Mon Nov 30 20:55:14 UTC 2020
We do, also. I was trying to avoid dropping a lot of unnecessary info on you. We use class definitions based on the parameters our network guys give me. For example,
WARNING: This has not been tested, it's a production config obfuscated, so I may have dropped some punctuation accidently - but hopefully you will see something in the structure that will aid you.
-----------------------------------------------------------------
class "Endpoint-devices"
{ match if
(substring (option agent.circult_id, 0, 4) = "TOWN")
and not
(suffix (option agent.circuit-id,5) = "vlan7")
}
class "Gateway-devices"
{ match if
(substring (option agent.circult_id, 0, 4) = "TOWN")
and
(suffix (option agent.circuit-id,5) = "vlan7")
}
-----------------------------------------------------------------
shared-network TOWN_A_Endpoints {
# 192.168.1.0/24 Town Network Infrastructure
subnet 192.168.1.0 netmask 255.255.255.0 {}
# 10.10.100.0/22 Town Endpoints Network
subnet 10.10.100.0 netmask 255.255.252.0 {
option routers 10.10.100.1;
option broadcast-address 10.10.103.255;
pool { # Production endpoints
failover peer "failover";
deny dynamic bootp clients;
allow members of "Endpoint-devices";
range 10.10.100.30 10.10.103.254;
} # Close production endpoints pool
pool { # Test endpoints hanging directly off E7
failover peer "failover";
deny dynamic bootp clients;
deny members of "Endpoint-devices";
deny members of "Gateway-devices";
range 10.10.100.10 10.10.100.29;
default-lease-time 21600;
min-lease-time 21600;
max-lease-time 43200;
} #Close test endpoints pool
} # Close endpoints subnet
# 172.16.1.1/23 Town Residential Gateways
subnet 172.16.1.0 netmask 255.255.254.0 {
option broadcast-address 172.16.1.255;
pool { # Gateway-devices pool
failover peer "failover";
deny dynamic bootp clients;
allow members of "Gateway-devices";
range 172.16.1.10 172.16.1.254;
} # Close Gateway-devices pool
} # Close gateways subnet
} # Close shared-network
-----------------------------------------------------------------
Cheers!
________________________________
From: dhcp-users <dhcp-users-bounces at lists.isc.org> on behalf of Alan Batie <alan at peak.org>
Sent: Monday, November 30, 2020 1:56 PM
To: dhcp-users at lists.isc.org <dhcp-users at lists.isc.org>
Subject: Re: dhcp relay
CAUTION: This email originated from outside of the company. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 11/27/20 6:59 AM, Patrick Trapp wrote:
> Hello, Alan. I am using a similar configuration here, including E7
> devices. We use shared networks to identify the subnet that network
> devices that the end devices are attached to occupy.
We're setup for a vlan/slot so I need to be able to distinguish between
the two vlans; it looks like I'm going to have to use the option82 info
somehow to do this...
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20201130/8529dd01/attachment-0001.htm>
More information about the dhcp-users
mailing list