Bonjour
Après avoir lu pas mal de messages sur ce forum et en particulier sur ce thread, j'ai effectué quelques tests sur une connexion Orange ADSL avec un modem perso (donc sans Livebox) et j'ai obtenu des résultats intéressants.
Premièrement, j'ai changé la configuration de mon modem, je suis passé d'un bridge RFC2684 sur ATM VPI/VCI 8.35 vers 8.32.
Ensuite, j'ai utilisé une configuration similaire à ce qu'il se fait sur des connexions fibre derrière un ONT (DHCP avec option 90, etc...).
En IPv4, je constate qu'il y a bien un équipement qui répond à mes requêtes DHCP Discover:
Frame 1: 372 bytes on wire (2976 bits), 372 bytes captured (2976 bits) on interface 0
Ethernet II, Src: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0, Dst: 255.255.255.255
User Datagram Protocol, Src Port: 68, Dst Port: 67
Bootstrap Protocol (Discover)
Message type: Boot Request (1)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0xda10e530
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
0... .... .... .... = Broadcast flag: Unicast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0
Your (client) IP address: 0.0.0.0
Next server IP address: 0.0.0.0
Relay agent IP address: 0.0.0.0
Client MAC address: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (Discover)
Length: 1
DHCP: Discover (1)
Option: (55) Parameter Request List
Length: 7
Parameter Request List Item: (1) Subnet Mask
Parameter Request List Item: (28) Broadcast Address
Parameter Request List Item: (2) Time Offset
Parameter Request List Item: (3) Router
Parameter Request List Item: (15) Domain Name
Parameter Request List Item: (6) Domain Name Server
Parameter Request List Item: (12) Host Name
Option: (90) Authentication
Length: 22
Protocol: configuration token (0)
Algorithm: 0
Replay Detection Method: Monotonically-increasing counter (0)
RDM Replay Detection Value: 0x0000000000000000
Authentication Information: fti/xxxxxxx
Option: (60) Vendor class identifier
Length: 5
Vendor class identifier: sagem
Option: (77) User Class Information
Length: 44
Instance of User Class: [0]
User Class Length: 43
User Class Data: 46535644534c5f6c697665626f782e496e7465726e65742e...
Option: (255) End
Option End: 255
Frame 2: 346 bytes on wire (2768 bits), 346 bytes captured (2768 bits) on interface 0
Ethernet II, Src: Nokia_xx:xx:xx (00:d0:f6:xx:xx:xx), Dst: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Internet Protocol Version 4, Src: 172.16.0.1, Dst: 172.16.134.24
User Datagram Protocol, Src Port: 67, Dst Port: 68
Bootstrap Protocol (Offer)
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0xda10e530
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
0... .... .... .... = Broadcast flag: Unicast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0
Your (client) IP address: 172.16.134.24
Next server IP address: xx.xx.xxx.xxx
Relay agent IP address: xx.xx.xxx.xxx
Client MAC address: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (Offer)
Length: 1
DHCP: Offer (2)
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: xx.xx.xxx.xxx
Option: (51) IP Address Lease Time
Length: 4
IP Address Lease Time: (7200s) 2 hours
Option: (125) V-I Vendor-specific Information
Length: 17
Enterprise: France Telecom (1368)
Length: 12
Option 125 Suboption: 1
Option: (90) Authentication
Length: 27
Protocol: configuration token (0)
Algorithm: 0
Replay Detection Method: Monotonically-increasing counter (0)
RDM Replay Detection Value: 0x0000000000000000
Authentication Information: dhcpliveboxfr250
Option: (255) End
Option End: 255
Frame 3: 384 bytes on wire (3072 bits), 384 bytes captured (3072 bits) on interface 0
Ethernet II, Src: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 0.0.0.0, Dst: 255.255.255.255
User Datagram Protocol, Src Port: 68, Dst Port: 67
Bootstrap Protocol (Request)
Message type: Boot Request (1)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0xda10e530
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
0... .... .... .... = Broadcast flag: Unicast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0
Your (client) IP address: 0.0.0.0
Next server IP address: 0.0.0.0
Relay agent IP address: 0.0.0.0
Client MAC address: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (Request)
Length: 1
DHCP: Request (3)
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: xx.xx.xxx.xxx
Option: (50) Requested IP Address
Length: 4
Requested IP Address: 172.16.134.24
Option: (55) Parameter Request List
Length: 7
Parameter Request List Item: (1) Subnet Mask
Parameter Request List Item: (28) Broadcast Address
Parameter Request List Item: (2) Time Offset
Parameter Request List Item: (3) Router
Parameter Request List Item: (15) Domain Name
Parameter Request List Item: (6) Domain Name Server
Parameter Request List Item: (12) Host Name
Option: (90) Authentication
Length: 22
Protocol: configuration token (0)
Algorithm: 0
Replay Detection Method: Monotonically-increasing counter (0)
RDM Replay Detection Value: 0x0000000000000000
Authentication Information: fti/xxxxxxx
Option: (60) Vendor class identifier
Length: 5
Vendor class identifier: sagem
Option: (77) User Class Information
Length: 44
Instance of User Class: [0]
User Class Length: 43
User Class Data: 46535644534c5f6c697665626f782e496e7465726e65742e...
Option: (255) End
Option End: 255
Mais ça part mal, on voit que le serveur DHCP essaie de m'affecter une IP RFC1918: 172.16.134.24.
De plus, le serveur ne répond pas aux DHCP Request et la négociation DHCP ne se finit pas.
En IPv6, les choses sont différentes:
Frame 1: 200 bytes on wire (1600 bits), 200 bytes captured (1600 bits) on interface 0
Ethernet II, Src: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx), Dst: IPv6mcast_01:00:02 (33:33:00:01:00:02)
Internet Protocol Version 6, Src: fe80::xxx:xxff:fexx:xxxx, Dst: ff02::1:2
User Datagram Protocol, Src Port: 546, Dst Port: 547
DHCPv6
Message type: Solicit (1)
Transaction ID: 0x3373c3
Client Identifier
Option: Client Identifier (1)
Length: 10
Value: xxxxxxxxxxxxxxxxxxxx
DUID: xxxxxxxxxxxxxxxxxxxx
DUID Type: link-layer address (3)
Hardware type: Ethernet (1)
Link-layer address: xx:xx:xx:xx:xx:xx
Option Request
Option: Option Request (6)
Length: 4
Value: 00170018
Requested Option code: DNS recursive name server (23)
Requested Option code: Domain Search List (24)
Elapsed time
Option: Elapsed time (8)
Length: 2
Value: 0000
Elapsed time: 0 ms
Authentication
Option: Authentication (11)
Length: 22
Value: 0000000000000000000000xxxxxxxxxxxxxxxxxxxxxx
Protocol: 0
Algorithm: 0
RDM: 0
Replay Detection: 0000000000000000
Authentication Information: xxxxxxxxxxxxxxxxxxxxxx
User Class
Option: User Class (15)
Length: 45
Value: 002b46535644534c5f6c697665626f782e496e7465726e65...
Vendor Class
Option: Vendor Class (16)
Length: 11
Value: 0000040e0005736167656d
Enterprise ID: SAGEMCOM SAS (1038)
vendor-class-data: sagem
Identity Association for Prefix Delegation
Option: Identity Association for Prefix Delegation (25)
Length: 12
Value: xxxxxxxxxxxxxxxxxxxxxxxx
IAID: xxxxxxxx
T1: 3600
T2: 5400
Frame 2: 185 bytes on wire (1480 bits), 185 bytes captured (1480 bits) on interface 0
Ethernet II, Src: Nokia_xx:xx:xx (00:d0:f6:xx:xx:xx), Dst: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Internet Protocol Version 6, Src: fe80::ba0:bab, Dst: fe80::xxx:xxff:fexx:xxxx
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Advertise (2)
Transaction ID: 0x3373c3
Identity Association for Prefix Delegation
Option: Identity Association for Prefix Delegation (25)
Length: 41
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
IAID: xxxxxxxx
T1: 43200
T2: 69120
IA Prefix
Option: IA Prefix (26)
Length: 25
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
Preferred lifetime: 86400
Valid lifetime: 86400
Prefix length: 56
Prefix address: 2a01:cbxx:xxxx:xx00::
Server Identifier
Option: Server Identifier (2)
Length: 20
Value: 0002000005584445534841594553535544524f54
DUID: 0002000005584445534841594553535544524f54
DUID Type: assigned by vendor based on Enterprise number (2)
Enterprise ID: France Telecom (1368)
Identifier: 4445534841594553535544524f54
Client Identifier
Option: Client Identifier (1)
Length: 10
Value: xxxxxxxxxxxxxxxxxxxx
DUID: xxxxxxxxxxxxxxxxxxxx
DUID Type: link-layer address (3)
Hardware type: Ethernet (1)
Link-layer address: xx:xx:xx:xx:xx:xx
Authentication
Option: Authentication (11)
Length: 27
Value: 0000000000000000000000646863706c697665626f786672...
Protocol: 0
Algorithm: 0
RDM: 0
Replay Detection: 0000000000000000
Authentication Information: 646863706c697665626f786672323530
Preference
Option: Preference (7)
Length: 1
Value: ff
Pref-value: 255
Frame 3: 253 bytes on wire (2024 bits), 253 bytes captured (2024 bits) on interface 0
Ethernet II, Src: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx), Dst: IPv6mcast_01:00:02 (33:33:00:01:00:02)
Internet Protocol Version 6, Src: fe80::xxx:xxff:fexx:xxxx, Dst: ff02::1:2
User Datagram Protocol, Src Port: 546, Dst Port: 547
DHCPv6
Message type: Request (3)
Transaction ID: 0xdf1070
Client Identifier
Option: Client Identifier (1)
Length: 10
Value: xxxxxxxxxxxxxxxxxxxx
DUID: xxxxxxxxxxxxxxxxxxxx
DUID Type: link-layer address (3)
Hardware type: Ethernet (1)
Link-layer address: xx:xx:xx:xx:xx:xx
Server Identifier
Option: Server Identifier (2)
Length: 20
Value: 0002000005584445534841594553535544524f54
DUID: 0002000005584445534841594553535544524f54
DUID Type: assigned by vendor based on Enterprise number (2)
Enterprise ID: France Telecom (1368)
Identifier: 4445534841594553535544524f54
Option Request
Option: Option Request (6)
Length: 4
Value: 00170018
Requested Option code: DNS recursive name server (23)
Requested Option code: Domain Search List (24)
Elapsed time
Option: Elapsed time (8)
Length: 2
Value: 0000
Elapsed time: 0 ms
Authentication
Option: Authentication (11)
Length: 22
Value: 0000000000000000000000xxxxxxxxxxxxxxxxxxxxxx
Protocol: 0
Algorithm: 0
RDM: 0
Replay Detection: 0000000000000000
Authentication Information: xxxxxxxxxxxxxxxxxxxxxx
User Class
Option: User Class (15)
Length: 45
Value: 002b46535644534c5f6c697665626f782e496e7465726e65...
Vendor Class
Option: Vendor Class (16)
Length: 11
Value: 0000040e0005736167656d
Enterprise ID: SAGEMCOM SAS (1038)
vendor-class-data: sagem
Identity Association for Prefix Delegation
Option: Identity Association for Prefix Delegation (25)
Length: 41
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
IAID: xxxxxxxx
T1: 3600
T2: 5400
IA Prefix
Option: IA Prefix (26)
Length: 25
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
Preferred lifetime: 7200
Valid lifetime: 7500
Prefix length: 56
Prefix address: 2a01:cbxx:xxxx:xx00::
Frame 4: 180 bytes on wire (1440 bits), 180 bytes captured (1440 bits) on interface 0
Ethernet II, Src: Nokia_xx:xx:xx (00:d0:f6:xx:xx:xx), Dst: xx:xx:xx:xx:xx:xx (xx:xx:xx:xx:xx:xx)
Internet Protocol Version 6, Src: fe80::ba0:bab, Dst: fe80::xxx:xxff:fexx:xxxx
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Reply (7)
Transaction ID: 0xdf1070
Identity Association for Prefix Delegation
Option: Identity Association for Prefix Delegation (25)
Length: 41
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
IAID: xxxxxxxx
T1: 43200
T2: 69120
IA Prefix
Option: IA Prefix (26)
Length: 25
Value: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...
Preferred lifetime: 86400
Valid lifetime: 86400
Prefix length: 56
Prefix address: 2a01:cbxx:xxxx:xx00::
Server Identifier
Option: Server Identifier (2)
Length: 20
Value: 0002000005584445534841594553535544524f54
DUID: 0002000005584445534841594553535544524f54
DUID Type: assigned by vendor based on Enterprise number (2)
Enterprise ID: France Telecom (1368)
Identifier: 4445534841594553535544524f54
Client Identifier
Option: Client Identifier (1)
Length: 10
Value: xxxxxxxxxxxxxxxxxxxx
DUID: xxxxxxxxxxxxxxxxxxxx
DUID Type: link-layer address (3)
Hardware type: Ethernet (1)
Link-layer address: xx:xx:xx:xx:xx:xx
Authentication
Option: Authentication (11)
Length: 27
Value: 0000000000000000000000646863706c697665626f786672...
Protocol: 0
Algorithm: 0
RDM: 0
Replay Detection: 0000000000000000
Authentication Information: 646863706c697665626f786672323530
J'obtiens une réponse de la fameuse IPv6 fe80::ba0:bab qui m'affecte un préfixe /56 et la négociation DHCPv6-PD va jusqu'au bout cette fois ici.
Un simple ping vers une IPv6 montre que les paquets sont bien routés:
# ping6 -n 2a01:e00::1
PING 2a01:e00::1(2a01:e00::1) 56 data bytes
64 bytes from 2a01:e00::1: icmp_seq=1 ttl=57 time=24.9 ms
64 bytes from 2a01:e00::1: icmp_seq=2 ttl=57 time=25.2 ms
64 bytes from 2a01:e00::1: icmp_seq=3 ttl=57 time=24.5 ms
64 bytes from 2a01:e00::1: icmp_seq=4 ttl=57 time=24.7 ms
64 bytes from 2a01:e00::1: icmp_seq=5 ttl=57 time=24.5 ms
^C
--- 2a01:e00::1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 24.551/24.821/25.279/0.270 ms
Voilà, je fais de l'IPv6 natif sur une connexion Orange ADSL
À ce stade, je me retrouve avec une IPv6 (enfin un préfixe) mais pas d'IPv4.
Une connexion IPv6 c'est bien, mais une connexion IPv6-only ce n'est pas (encore) très utilisable au quotidien.
J'ai donc voulu voir si je pouvais établir une connexion PPPoE pour IPv4 en plus du DHCPv6-PD.
En ADSL, le flux PPPoE se trouve sur un autre circuit ATM, heureusement mon modem me permet d'utiliser plusieurs circuits ATM en simultané et de "mapper" les bridges RFC2684 dans des VLAN sur son interface Ethernet.
J'ai donc configuré mon modem de la sorte:
ATM VPI/VCI 8.35 <-> Ethernet VLAN 835
ATM VPI/VCI 8.32 <-> Ethernet VLAN 832
L'avantage de cette configuration est que du point de vue du routeur qui est derrière, le modem ressemble beaucoup à un ONT sur la fibre (même VLANs).
Ceci m'a permis de faire un quasi copié-collé depuis les configurations full DHCP et PPPoE de mon autre routeur chez moi qui est sur une connexion Orange Fibre.
Sur mon routeur, je lance le client DHCPv6 sur l'interface eth0.832 et le client PPPoE sur eth0.835, et... ça marche !
La connexion PPP est établie, le serveur DHCPv6-PD répond, je peux échanger des paquets IPv4 sur l'interface PPP et IPv6 sur eth0.832.
Au final je me retrouve avec ce setup un peu bizarre mais qui fonctionne:
eth0.832 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
adr inet6: 2a01:cbxx:xxxx:xx00::1/128 Scope:Global
adr inet6: fe80::xx:xxx:xxxx:xxxx/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29446 errors:0 dropped:0 overruns:0 frame:0
TX packets:23948 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:18902912 (18.0 MiB) TX bytes:4243406 (4.0 MiB)
eth0.835 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:535591 errors:0 dropped:0 overruns:0 frame:0
TX packets:341575 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:695665787 (663.4 MiB) TX bytes:36650786 (34.9 MiB)
ppp0 Link encap:Protocole Point-à-Point
inet adr:xx.xxx.x.xx P-t-P:193.253.160.3 Masque:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:533207 errors:0 dropped:0 overruns:0 frame:0
TX packets:339192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:3
RX bytes:691290216 (659.2 MiB) TX bytes:29117027 (27.7 MiB)
Voilà, je pense (j'espère
) que cette configuration n'est que temporaire et que le DHCPv4 va finir par fonctionner, mais en attendant, ça confirme bien que le DHCPv6-PD arrive sur l'ADSL !