En 1.10 dibbler-client ne fonctionne plus chez moi, il ne récupère plus le prefixe.
Par contre tout fonctionne si on connait son prefixe
fttmeh as tu l'ipv6 dans la beta3 ?
log de dibbler-client run
2018.02.01 21:48:09 Client Notice Parsing /etc/dibbler/client.conf config file...
2018.02.01 21:48:09 Client Debug PD: Following interfaces marked as downlink: none
2018.02.01 21:48:09 Client Debug Prefix delegation option (no parameters) found.
2018.02.01 21:48:09 Client Debug Will send option 16 (hex data, len11)
2018.02.01 21:48:09 Client Debug Will send option 15 (hex data, len45)
2018.02.01 21:48:09 Client Debug Will send option 11 (hex data, len22)
2018.02.01 21:48:09 Client Debug Will send option 11 (hex data, len22)
2018.02.01 21:48:09 Client Debug Parsing /etc/dibbler/client.conf done, result=0(success)
2018.02.01 21:48:09 Client Debug 1 interface(s) specified in /etc/dibbler/client.conf
2018.02.01 21:48:09 Client Info Interface eth1.832/12 configuration has been loaded.
2018.02.01 21:48:09 Client Debug DUID's value = 000:01:00:01:22:06:31:xx:xx:xx:xx:xx:xx:xx was loaded from client-duid file.
2018.02.01 21:48:09 Client Info My DUID is 00:01:00:01:22:06:31:xx:xx:xx:xx:xx:xx:xx.
2018.02.01 21:48:09 Client Info Loading old address database (client-AddrMgr.xml), using built-in routines.
2018.02.01 21:48:09 Client Info DB timestamp:1517518156, now()=1517518605, db is 449 second(s) old.
2018.02.01 21:48:09 Client Debug Auth: Replay detection value loaded 0
2018.02.01 21:48:09 Client Info All client's 00:01:00:01:22:06:31:xx:xx:xx:xx:xx:xx:xx leases are not valid.
2018.02.01 21:48:09 Client Debug Bind reuse enabled (multiple instances allowed).
2018.02.01 21:48:09 Client Notice Creating control (
socket on the lo/1 interface.
2018.02.01 21:48:09 Client Notice Creating socket (addr=fe80::822a:a8ff:fe4c:375d) on eth1.832/12 interface.
2018.02.01 21:48:09 Client Debug Initialising link-state detection for interfaces: eth1.832/12
2018.02.01 21:48:09 Client Notice CONFIRM support compiled in.
2018.02.01 21:48:09 Client Info Creating SOLICIT message with 0 IA(s), no TA and 1 PD(s) on eth1.832/12 interface.
2018.02.01 21:48:09 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:09 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:09 Client Debug Sleeping for 1 second(s).
2018.02.01 21:48:10 Client Info Processing msg (SOLICIT,transID=0xf9544b,opts: 1 25 8 16 15 11 11 6)
2018.02.01 21:48:10 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:10 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:10 Client Debug Sleeping for 2 second(s).
2018.02.01 21:48:12 Client Info Processing msg (SOLICIT,transID=0xf9544b,opts: 1 25 8 16 15 11 11 6)
2018.02.01 21:48:12 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:12 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:12 Client Debug Sleeping for 4 second(s).
2018.02.01 21:48:16 Client Info Processing msg (SOLICIT,transID=0xf9544b,opts: 1 25 8 16 15 11 11 6)
2018.02.01 21:48:16 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:16 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:16 Client Debug Sleeping for 8 second(s).
2018.02.01 21:48:24 Client Info Processing msg (SOLICIT,transID=0xf9544b,opts: 1 25 8 16 15 11 11 6)
2018.02.01 21:48:24 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:24 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:24 Client Debug Sleeping for 16 second(s).
2018.02.01 21:48:40 Client Info Processing msg (SOLICIT,transID=0xf9544b,opts: 1 25 8 16 15 11 11 6)
2018.02.01 21:48:40 Client Error AUTH: protocol 11320104 not supported yet.
2018.02.01 21:48:40 Client Debug Sending SOLICIT(opts:1 25 8 16 15 11 11 6 ) on eth1.832/12 to multicast.
2018.02.01 21:48:40 Client Debug Sleeping for 33 second(s).