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. spawning classes bug? (Troy Ayers)
2. Re: spawning classes bug? (Philippe Maechler)
3. Raw IP interface support under Linux (Loic Poulain)
4. Re: Raw IP interface support under Linux (Bj?rn Mork)
----------------------------------------------------------------------
Message: 1
Date: Fri, 30 Oct 2020 14:32:46 +0000
From: Troy Ayers <tr...@wcta.net>
To: "dhcp-users@lists.isc.org" <dhcp-users@lists.isc.org>
Subject: spawning classes bug?
Message-ID: <1604068366997.80...@wcta.net>
Content-Type: text/plain; charset="iso-8859-1"
We limit each customer, which is uniquely identified with a combination of
circuit ID, and remote id, to two IP addresses. Like so:
class "customer" {spawn with concat(option agent.remote-id," interface
",binary-to-ascii(10,8,".",substring(option agent.circuit-id,0,2)));
lease limit 2;}
This is reproducible with dhcp 442. There are no other spawn classes. Lease
times are 24 hours.
Customer has router A, using one IP with mac 11:11:11:11:11:11
Router A gets disconnected and replaced with Router B.
Router B gets an IP. This is the 2nd IP with mac 22:22:22:22:22:22
Router B updates firmware, and reboots.
Then we get this over and over...?
DHCPDISCOVER from 22:22:22:22:22:22 via 10.x.x.x: no available billing: lease
limit reached in all matching classes (last: 'customer')
?
The clients MAC did not change.
The clients billing sub-class (concatenated remote id, circuit id) did not
change.
I've examined the leases file while this is occurring. There is:
billing subclass "customer" "ShelfXYZ interface 0.0";
One for Router A's MAC and one for Router B's MAC address.
When we run into this, we have to allow their billing subclass to have a lease
limit of 3, temporarily.
Re-examining the leases file after allowing a "3rd IP", shows that the client
gets the same 2nd IP on the Router B, and the leases file shows the same two
billing sub-classes & same MAC addresses.
I've tried ignore-client-uids, to no effect.
What can I do to allow this Router B, without temporarily allowing a lease
limit of "3" ?
Also, this behavior is not always reproducible, this is what is especially
baffling to me.
-Troy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20201030/5f103029/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 30 Oct 2020 16:15:06 +0100
From: Philippe Maechler <plcmaech...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: spawning classes bug?
Message-ID:
<caphukgyyxgqjck_hgfpa04f5zgeuokwzz8-xwyeruh04cfw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Troy
I can't help you here, but we use a similar approach and that works pretty
well for us:
class "CUSTOMER001_CPE_DHCP" {
match if ( substring ( option agent.circuit-id, 0, 30 ) = "someAwesome
String 2 m-a-t-c-h" );
spawn with option agent.circuit-id; lease limit 1;
}
And I never saw nor see the issue you are describing. This setup is working
fine, although router changes may bite us, because they are not so easy
doable
But our lease time is set to 1h
This is currently on dhcp-4.3.6-P1 and we have that setup since 4.2 (maybe
4.1, can't remember). the standby machine runs 4.4.1 (no failover involved
here)
/BR
Philippe
On Fri, 30 Oct 2020 at 15:33, Troy Ayers <tr...@wcta.net> wrote:
> We limit each customer, which is uniquely identified with a combination of
> circuit ID, and remote id, to two IP addresses. Like so:
>
> class "customer" {spawn with concat(option agent.remote-id," interface
> ",binary-to-ascii(10,8,".",substring(option agent.circuit-id,0,2)));
> lease limit 2;}
>
>
> This is reproducible with dhcp 442. There are no other spawn classes.
> Lease times are 24 hours.
>
>
> Customer has router A, using one IP with mac 11:11:11:11:11:11
>
> Router A gets disconnected and replaced with Router B.
>
> Router B gets an IP. This is the 2nd IP with mac 22:22:22:22:22:22
>
> Router B updates firmware, and reboots.
>
> Then we get this over and over...?
> DHCPDISCOVER from 22:22:22:22:22:22 via 10.x.x.x: no available billing:
> lease limit reached in all matching classes (last: 'customer')
>
> ?
>
> The clients MAC did not change.
>
> The clients billing sub-class (concatenated remote id, circuit id) did not
> change.
>
>
> I've examined the leases file while this is occurring. There is:
>
> billing subclass "customer" "ShelfXYZ interface 0.0";
>
> One for Router A's MAC and one for Router B's MAC address.
>
>
> When we run into this, we have to allow their billing subclass to have a
> lease limit of 3, temporarily.
>
>
> Re-examining the leases file after allowing a "3rd IP", shows that
> the client gets the same 2nd IP on the Router B, and the leases file shows
> the same two billing sub-classes & same MAC addresses.
>
>
> I've tried ignore-client-uids, to no effect.
>
>
> What can I do to allow this Router B, without temporarily allowing a lease
> limit of "3" ?
>
>
> Also, this behavior is not always reproducible, this is what is especially
> baffling to me.
>
>
> -Troy
> _______________________________________________
> 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/20201030/39b645dc/attachment-0001.htm>
------------------------------
Message: 3
Date: Fri, 30 Oct 2020 18:47:30 +0100
From: Loic Poulain <loic.poul...@linaro.org>
To: dhcp-users@lists.isc.org
Subject: Raw IP interface support under Linux
Message-ID:
<CAMZdPi8d0U+PpPssoL2W7tTegJ31T8+Hn1z=vvuia+yqjhz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi folks,
Currently, network interfaces with ARPHRD_RAWIP sa_family type are not
supported by dhclient (contrary to e.g. udhcpc):
dhclient: can't create /var/db/dhclient.leases: No such file or directory
dhclient: Unsupported device type 519 for "rmnet_data1"
Is there any plan to add such support? Or any known limitation to not add this?
Regards,
Loic
------------------------------
Message: 4
Date: Fri, 30 Oct 2020 19:46:55 +0100
From: Bj?rn Mork <bj...@mork.no>
To: Loic Poulain <loic.poul...@linaro.org>
Cc: dhcp-users@lists.isc.org
Subject: Re: Raw IP interface support under Linux
Message-ID: <87imark0v4....@miraculix.mork.no>
Content-Type: text/plain; charset=utf-8
Loic Poulain <loic.poul...@linaro.org> writes:
> Currently, network interfaces with ARPHRD_RAWIP sa_family type are not
> supported by dhclient (contrary to e.g. udhcpc):
>
> dhclient: can't create /var/db/dhclient.leases: No such file or directory
> dhclient: Unsupported device type 519 for "rmnet_data1"
>
> Is there any plan to add such support? Or any known limitation to not add
> this?
I don't think there are any such plans. But it's not difficult to
fix. I made a proof-of-concept patch 5 years ago:
https://mail.gnome.org/archives/networkmanager-list/2015-December/msg00044.html
This is Linux only, but I guess those raw-ip network drivers are too ;-)
Bj?rn
------------------------------
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 144, Issue 20
*******************************************
