spawning class on ethernet

Eugene M. Zheganin eugene at zhegan.in
Mon Feb 9 13:22:09 UTC 2015


Hi.

I'm still getting these "Reclaiming abandoned addresses is not yet
supported.  Treating this as an out of space condition." messages in my
dhcpd6 log, and, in order to restrict clients to one ip address, I'm
trying to create spawning class, since classes are already supported in
ipv6. Unfortunately, all of the examples are for cable networks, and my
attepts to create a ethernet spawning class are unsuccessful, due to
lack of documentation all examples are for "spawn with option
agent.circuit-id;".

Can spawning class be created for ethernet ?

I created the following class and pool:

class "default" {
    spawn with hardware;
    lease limit 1;
}

subnet6 fd00::0300/120 {
    pool6 {
          range6 fd00::332 fd00::3fe;
          allow members of "default";
          option dhcp6.name-servers fd00::301;
    }
}

This is considered as a valid config, but when running I see the
following in logs:

Feb  9 18:10:49 taiga dhcpd: data: hardware: invalid hlen (122)
Feb  9 18:10:49 taiga dhcpd: Sending Reply to fe80::b423:fd45:b872:9e45
port 546
Feb  9 18:10:50 taiga dhcpd: Renew message from fe80::cab:44eb:7774:e2
port 546, transaction ID 0x488E3400
Feb  9 18:10:50 taiga dhcpd: data: hardware: invalid hlen (142)
Feb  9 18:10:50 taiga dhcpd: Sending Reply to fe80::cab:44eb:7774:e2
port 546
Feb  9 18:10:51 taiga dhcpd: Renew message from fe80::dc07:cc4:454c:bfb7
port 546, transaction ID 0x6919F500
Feb  9 18:10:51 taiga dhcpd: data: hardware: invalid hlen (25)

Thus I'm doing something terribly wrong.
Can someone point me to a right direction ?

Thanks.


More information about the dhcp-users mailing list