In a simple setup I would like to demonstrate (to my students) IPv6-Prefix-Delegation using RB951G as the router and an ISC-DHCP-SERVER running on a Linux-Box in -6 mode. That used to work perfectly with ROS 6.15.
Now on recently purchased RB951G with ROS 6.34 the routers says the following:
interface=ether2-master status=bound duid="0x000300016c3b6b24f761" dhcp-server-v6=fe80::92e2:baff:fe26:77d1 request=address,prefix add-default-route=no
use-peer-dns=yes pool-name="schwimmbad" pool-prefix-length=64 prefix-hint=::/0
isc-dhcp-server is telling me:
Reply PD: address 2001:db8:caff::/48 to client with duid 00:03:00:01:6c:3b:6b:24:f7:61 iaid = 3 valid for 600 seconds
BUT the pool is empty:
/ipv6 dhcp-client> .. pool print
Flags: D - dynamic
NAME PREFIX PREFIX-LENGTH EXPIRES-AFTER
Where is the prefix? Why is it not showing up in the pool?
On a router with OS 6.15 and exactly the same config the prefix is immediately showing up in the pool.
Router advertisement with a manually populated pool works fine.
Exports:
/ipv6 dhcp-client
add interface=ether2-master pool-name=schwimmbad request=address,prefix
I checked with the option request=prefix, too. I also tried a hAP ac (RB962UiGS-5HacT2HnT) : no prefix in pool.
An upgrade to ROS 6.41 does not solve the problem. The log (see below) shows the message "not ready for packet" What does that mean?
Any help is appreciated.
Best regards,
Michael
01:09:11 dhcp,debug resending..
01:09:11 dhcp,debug,packet send ether2-master -> ff02::1:2%11
01:09:11 dhcp,debug,packet type: solicit
01:09:11 dhcp,debug,packet transaction-id: a1e478
01:09:11 dhcp,debug,packet -> clientid: 00030001 64d15423 7037
01:09:11 dhcp,debug,packet -> ia_na:
01:09:11 dhcp,debug,packet t1: 1800
01:09:11 dhcp,debug,packet t2: 2880
01:09:11 dhcp,debug,packet id: 0x2
01:09:11 dhcp,debug,packet -> oro: 23
01:09:11 dhcp,debug,packet -> elapsed_time: 1
01:09:11 dhcp,debug,packet -> rapid_commit:
01:09:11 dhcp,debug,packet -> ia_pd:
01:09:11 dhcp,debug,packet t1: 1800
01:09:11 dhcp,debug,packet t2: 2880
01:09:11 dhcp,debug,packet id: 0x2
01:09:11 dhcp,debug,packet recv : fe80::92e2:baff:fe26:77d1 -> fe80::66d1:54ff:fe23:7038
01:09:11 dhcp,debug,packet type: advertise
01:09:11 dhcp,debug,packet transaction-id: a1e478
01:09:11 dhcp,debug,packet -> clientid: 00030001 64d15423 7037
01:09:11 dhcp,debug,packet -> serverid: 00010001 2201d9d9 90e2ba26 77d1
01:09:11 dhcp,debug,packet -> ia_na:
01:09:11 dhcp,debug,packet t1: 0
01:09:11 dhcp,debug,packet t2: 0
01:09:11 dhcp,debug,packet id: 0x2
01:09:11 dhcp,debug,packet -> ia_addr:
01:09:11 dhcp,debug,packet address: 2001:db8:0:1::98
01:09:11 dhcp,debug,packet valid time: 600
01:09:11 dhcp,debug,packet pref. time: 375
01:09:11 dhcp,debug,packet -> ia_pd:
01:09:11 dhcp,debug,packet t1: 0
01:09:11 dhcp,debug,packet t2: 0
01:09:11 dhcp,debug,packet id: 0x2
01:09:11 dhcp,debug,packet -> ia_prefix:
01:09:11 dhcp,debug,packet prefix: 2001:db8:caff::/60
01:09:11 dhcp,debug,packet valid time: 600
01:09:11 dhcp,debug,packet pref. time: 375
01:09:11 dhcp,debug client not ready for packet!