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: dhcp relay (Patrick Trapp)
2. Re: Failover Peer Issue with Polycom SoundStation IP 6000
Phone (willieb)
3. Re: Failover Peer Issue with Polycom SoundStation IP 6000
Phone (Bruce Hudson)
----------------------------------------------------------------------
Message: 1
Date: Tue, 1 Dec 2020 14:11:43 +0000
From: Patrick Trapp <ptr...@nex-tech.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dhcp relay
Message-ID:
<dm6pr12mb3577cf40bf50c4ab646683e8e6...@dm6pr12mb3577.namprd12.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Ah, we are not. Strictly IPv4 here. I have no insight to share on that topic,
I'm afraid.
________________________________
From: dhcp-users <dhcp-users-boun...@lists.isc.org> on behalf of Alan Batie
<a...@peak.org>
Sent: Monday, November 30, 2020 8:32 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/30/20 12:55 PM, Patrick Trapp wrote:
> 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,
Are you doing IPv6? Apparently dhcpd6 doesn't support class definitions
(or something else I tried to do either, but I've forgotten what that
was ;-) ). It seems to be unloved...
_______________________________________________
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/20201201/bd60c574/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 1 Dec 2020 10:16:05 -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: <1606839365318-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii
Thanks Glenn,
That is great news! I won't try to add the allow statement then. But
unfortunately it's not working. The ACK still shows the identifier of the
secondary server and not the primary for the SSIP class match. I verified
this with a wireshark capture. Here's the syntax I've tried (separately) and
it makes no difference for the identifier used in the ACK:
class "SSIP" {
match if substring (hardware,2,4) = aa:bb:cc:34;
server-identifier x.x.14.34;
}
class "SSIP" {
match if substring (hardware,1,5) = 1:aa:bb:cc:34;
server-identifier x.x.14.34;
}
class "SSIP" {
match if substring (hardware,2,4) = aa:bb:cc:34;
option dhcp-server-identifier x.x.14.34;
}
class "SSIP" {
match if substring (hardware,1,5) = 1:aa:bb:cc:34;
option dhcp-server-identifier x.x.14.34;
}
class "SSIP" {
match if substring (hardware,2,4) = aa:bb:cc:34;
server-identifier x.x.14.34;
option dhcp-server-identifier x.x.14.34;
}
class "SSIP" {
match if substring (hardware,1,5) = 1:aa:bb:cc:34;
server-identifier x.x.14.34;
option dhcp-server-identifier x.x.14.34;
}
Edit: Glenn, I didn't mean to send those first 2 replies directly to your
email lol...
glenn.satchell wrote
> Hi Will,
>
> Looks like a simple syntax error of some sort in the config. If you run
> that ExecStart command yourself I'm sure it will give better info.
>
> However, the good news is that you don't need to 'allow members of
> "SSIP"' in the pool(s). All the work is done in the class statement, in
> that if it matches the class then all the settings in the class are
> applied to that request. IP address and other allocation will be done in
> whatever pools it subsequently uses. You could check this with a packet
> trace using tcpdump for example.
>
> regards,
> Glenn
>
> --snip--
Quoted from:
http://isc-dhcp-users.2343191.n4.nabble.com/Failover-Peer-Issue-with-Polycom-SoundStation-IP-6000-Phone-tp3609p3650.html
--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/
------------------------------
Message: 3
Date: Tue, 1 Dec 2020 16:49:24 -0400
From: Bruce Hudson <bruce.hud...@dal.ca>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Failover Peer Issue with Polycom SoundStation IP 6000
Phone
Message-ID: <20201201204924.ga19...@kil-bah-1.its.dal.ca>
Content-Type: text/plain; charset=us-ascii
On Tue, Dec 01, 2020 at 10:16:05AM -0600, willieb wrote:
> class "SSIP" {
> match if substring (hardware,2,4) = aa:bb:cc:34;
> server-identifier x.x.14.34;
> }
String offsets begin at zero. Try
> class "SSIP" {
> match if substring (hardware,1,4) = aa:bb:cc:34;
> server-identifier x.x.14.34;
> }
--
Bruce A. Hudson | bruce.hud...@dal.ca
ITS, Networks and Systems |
Dalhousie University |
Halifax, Nova Scotia, Canada | (902) 494-3405
------------------------------
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 146, Issue 2
******************************************
