Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: Failover Peer Issue with Polycom SoundStation IP 6000
Phone (willieb)
2. Re: dhcp relay (Alan Batie)
3. Re: dhcp relay (Patrick Trapp)
----------------------------------------------------------------------
Message: 1
Date: Mon, 30 Nov 2020 09:44:28 -0600 (CST)
From: willieb <will.bash...@btctelcom.net>
To: dhcp-users@lists.isc.org
Subject: Re: Failover Peer Issue with Polycom SoundStation IP 6000
Phone
Message-ID: <1606751068746-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii
Thanks for the reply. I'm back working on this since Thanksgiving is over. I
was able to create a class with the text below:
class "SSIP" {
match if substring (hardware,2,4) = aa:bb:cc:34;
server-identifier x.x.14.34;
}
But when I add:
allow members of "SSIP";
to the shared-network then I get the errors at the end of this reply.
Also, if I add the allow members statement, doesn't that deny other clients?
My goal is to allow all clients normally, but clients that have the hardware
address beginning with aa:bb:cc:34 I want them to get the server-identifier
of x.x.14.34. I hope that makes sense. Thanks for your help guys.
-Will
? dhcpd.service - DHCPv4 Server Daemon
Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-11-30 10:39:20 EST; 4s
ago
Docs: man:dhcpd(8)
man:dhcpd.conf(5)
Process: 27298 ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user
dhcpd -group dhcpd --no-pid (code=exited, status=1/FAILURE)
Main PID: 27298 (code=exited, status=1/FAILURE)
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]:
^
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]: Configuration file
errors encountered -- exiting
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]:
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]: This version of ISC DHCP
is based on the release available
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]: on ftp.isc.org.
Features have been added and other changes
Nov 30 10:39:20 localhost.localdomain dhcpd[27298]: have been made to the
base software release in order to make
Nov 30 10:39:20 localhost.localdomain systemd[1]: dhcpd.service: main
process exited, code=exited, status=1/FAILURE
Nov 30 10:39:20 localhost.localdomain systemd[1]: Failed to start DHCPv4
Server Daemon.
Nov 30 10:39:20 localhost.localdomain systemd[1]: Unit dhcpd.service entered
failed state.
Nov 30 10:39:20 localhost.localdomain systemd[1]: dhcpd.service failed.
--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/
------------------------------
Message: 2
Date: Mon, 30 Nov 2020 11:56:42 -0800
From: Alan Batie <a...@peak.org>
To: dhcp-users@lists.isc.org
Subject: Re: dhcp relay
Message-ID: <10128a19-1ac2-5173-64ed-1d382f68a...@peak.org>
Content-Type: text/plain; charset=windows-1252
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...
------------------------------
Message: 3
Date: Mon, 30 Nov 2020 20:55:14 +0000
From: Patrick Trapp <ptr...@nex-tech.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dhcp relay
Message-ID:
<dm6pr12mb3577c16f5e546208e4fcd3e4e6...@dm6pr12mb3577.namprd12.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
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-boun...@lists.isc.org> on behalf of Alan Batie
<a...@peak.org>
Sent: Monday, November 30, 2020 1:56 PM
To: dhcp-users@lists.isc.org <dhcp-users@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@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.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
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@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 145, Issue 22
*******************************************
