Hi everyone!
I just got IPv6 all setup on my EdgeRouter Lite running v1.10.0. Everything seems to be working pretty well, but Stateless DHCPv6 isn't consistently providing DNS servers to my clients.
Here's how I have dhcpv6-server configured:
ubnt@ubnt# show service dhcpv6-server
shared-network-name LANv6 {
name-server 2001:4860:4860::8888
name-server 2001:4860:4860::8844
subnet fe80::46d9:e7ff:fe9e:3682/128 {
}
}
shared-network-name WLANv6 {
name-server 2001:4860:4860::8888
name-server 2001:4860:4860::8844
subnet fe80::46d9:e7ff:fe9e:3683/128 {
}
}
[edit]
When a Windows client connects via my LAN interface, this is what I see. MAC Addresses and Client/Server Identifiers appear to be consistent. If the reply that contains the DNS server addresses is sent/recieved first, all is well. If it is received last, the DNS server addresses are not configured as expected.
Frame 1: 102 bytes on wire (816 bits), 102 bytes captured (816 bits)
Ethernet II, Src: Ubiquiti_9e:36:82 (44:d9:e7:9e:36:82), Dst: Microsof_01:6e:b0 (00:15:5d:01:6e:b0)
Internet Protocol Version 6, Src: fe80::46d9:e7ff:fe9e:3682, Dst: fe80::2502:a82:4ce7:486c
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Reply (7)
Transaction ID: 0x21d76b
Client Identifier
Option: Client Identifier (1)
Length: 14
Value: 00010001223f557900155d016eb0
DUID: 00010001223f557900155d016eb0
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 16, 2018 23:26:33.000000000 Central Daylight Time
Link-layer address: 00:15:5d:01:6e:b0
Server Identifier
Option: Server Identifier (2)
Length: 14
Value: 00010001224015dd44d9e79e3682
DUID: 00010001224015dd44d9e79e3682
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 17, 2018 13:07:25.000000000 Central Daylight Time
Link-layer address: 44:d9:e7:9e:36:82
Frame 2: 138 bytes on wire (1104 bits), 138 bytes captured (1104 bits)
Ethernet II, Src: Ubiquiti_9e:36:82 (44:d9:e7:9e:36:82), Dst: Microsof_01:6e:b0 (00:15:5d:01:6e:b0)
Internet Protocol Version 6, Src: fe80::46d9:e7ff:fe9e:3682, Dst: fe80::2502:a82:4ce7:486c
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Reply (7)
Transaction ID: 0x21d76b
Client Identifier
Option: Client Identifier (1)
Length: 14
Value: 00010001223f557900155d016eb0
DUID: 00010001223f557900155d016eb0
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 16, 2018 23:26:33.000000000 Central Daylight Time
Link-layer address: 00:15:5d:01:6e:b0
Server Identifier
Option: Server Identifier (2)
Length: 14
Value: 00010001223e067e44d9e79e3682
DUID: 00010001223e067e44d9e79e3682
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 15, 2018 23:37:18.000000000 Central Daylight Time
Link-layer address: 44:d9:e7:9e:36:82
DNS recursive name server
Option: DNS recursive name server (23)
Length: 32
Value: 200148604860000000000000000088882001486048600000...
1 DNS server address: 2001:4860:4860::8888
2 DNS server address: 2001:4860:4860::8844
When a Windows client connects via my WLAN interface, this is what I see. MAC Addresses and Client/Server Identifiers appear to be inconsistent. If the reply that contains the DNS server addresses is sent/recieved first, all is well. If it is received last, the DNS server addresses are not configured as expected.
Frame 1: 102 bytes on wire (816 bits), 102 bytes captured (816 bits)
Ethernet II, Src: Ubiquiti_9e:36:83 (44:d9:e7:9e:36:83), Dst: Microsof_1c:2b:1b (c4:9d:ed:1c:2b:1b)
Internet Protocol Version 6, Src: fe80::46d9:e7ff:fe9e:3683, Dst: fe80::fdc2:401e:22d9:2949
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Reply (7)
Transaction ID: 0xbb0393
Client Identifier
Option: Client Identifier (1)
Length: 14
Value: 000100012228f373c49ded1c2b1b
DUID: 000100012228f373c49ded1c2b1b
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Feb 27, 2018 22:58:27.000000000 Central Standard Time
Link-layer address: c4:9d:ed:1c:2b:1b
Server Identifier
Option: Server Identifier (2)
Length: 14
Value: 00010001224015df44d9e79e3683
DUID: 00010001224015df44d9e79e3683
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 17, 2018 13:07:27.000000000 Central Daylight Time
Link-layer address: 44:d9:e7:9e:36:83
Frame 2: 138 bytes on wire (1104 bits), 138 bytes captured (1104 bits)
Ethernet II, Src: Ubiquiti_9e:36:83 (44:d9:e7:9e:36:83), Dst: Microsof_1c:2b:1b (c4:9d:ed:1c:2b:1b)
Internet Protocol Version 6, Src: fe80::46d9:e7ff:fe9e:3683, Dst: fe80::fdc2:401e:22d9:2949
User Datagram Protocol, Src Port: 547, Dst Port: 546
DHCPv6
Message type: Reply (7)
Transaction ID: 0xbb0393
Client Identifier
Option: Client Identifier (1)
Length: 14
Value: 000100012228f373c49ded1c2b1b
DUID: 000100012228f373c49ded1c2b1b
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Feb 27, 2018 22:58:27.000000000 Central Standard Time
Link-layer address: c4:9d:ed:1c:2b:1b
Server Identifier
Option: Server Identifier (2)
Length: 14
Value: 00010001223e067e44d9e79e3682 [Why isn't this 44d9e79e3683?]
DUID: 00010001223e067e44d9e79e3682 [Why isn't this 44d9e79e3683?]
DUID Type: link-layer address plus time (1)
Hardware type: Ethernet (1)
DUID Time: Mar 15, 2018 23:37:18.000000000 Central Daylight Time
Link-layer address: 44:d9:e7:9e:36:82 [Why isn't this 44:d9:e7:9e:36:83?]
DNS recursive name server
Option: DNS recursive name server (23)
Length: 32
Value: 200148604860000000000000000088882001486048600000...
1 DNS server address: 2001:4860:4860::8888
2 DNS server address: 2001:4860:4860::8844
Anybody have any idea what's going on or how to correct this?
Thanks!