No more ipv6 in Singtel home 1G fibre broadband?

Mach3.2

Mach3.2

Great Supremacy Member
HWZ Insider
Joined
Apr 8, 2011
Messages
72,404
Reaction score
2,461
xiaofan said:
Supposedly it is automatically done by enabling DHCP-PD.

If I do not enable DHCP-PD, then I can set up LAN Prefix Length to be between /56 to /64. However, then it asks me to set a valid LAN IPv6 Address which I can not do (dynamic IPv6 address).

Asus IPv6 settings are a bit limited.
https://www.asus.com/support/FAQ/113990

So far I find out OpenWRT to have the most comprehensive IPv6 settings, beating pfSense. But still I feel none of them have very good IPv6 documentations.
https://openwrt.org/docs/guide-user/network/ipv6/configuration
https://docs.netgate.com/pfsense/en/latest/interfaces/configure-ipv6.html

mFMP1Cl.png
Click to expand...

It might be under stateful configuration.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Mach3.2 said:
Not sure if this option is available in your Asus router settings, if you route a prefix shorter than /64 (e.g. /63 for 2 /64 subnets) to the upstream LAN, you can route additional /64 subnet(s) to your downstream router.

See DHCPv6 Prefix Delegation.
https://docs.netgate.com/pfsense/en/latest/services/dhcp/ipv6.html
Click to expand...

The best what I can achieve now is using OpenWRT.
OpenWRT main router + OpenWRT secondary router (Double NAT for IPv4).

Main router IPv6: WAN /56; LAN /60
Secondary router IPv6: WAN: /62, LAN /64

1) Main router (Open WRT 23.05 VM under PVE8.0, Intel N100 mini PC)
Hw1uEM4.png



2) Secondary router, OpenWRT 22.03.5, Linksys WRT1900AC v1.

c4LlzjU.png



3) Wireless client of WRT1900AC V1 -- Acer Windows 11 laptop.

Code: 
PS C:\work> tracert ipv6.google.com

Tracing route to ipv6.l.google.com [2404:6800:4003:c00::71]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  2400:d802:xxxx:xx04::1 (Linksys WRT1900AC OpenWRT)
  2     3 ms     2 ms     2 ms  2400:d802:xxxx:xx00::1 (Intel N100 OpenWRT VM)
  3     7 ms     5 ms     5 ms  2400:d802:1:606:: (Singtel IPv6 gateway)
  4    41 ms    36 ms    36 ms  2001:c20:3c00::6
  5     5 ms     3 ms     3 ms  2001:c20:3c00::7
  6    17 ms     4 ms     4 ms  2001:c20:0:3::35
  7     4 ms     4 ms     4 ms  2001:c20:0:3::a
  8     6 ms     4 ms     4 ms  2001:c10:80:2::a21
  9     6 ms     8 ms     4 ms  2001:c10:80:2::915
 10    22 ms    10 ms    67 ms  2001:c10:80:1::a75
 11     6 ms     5 ms     5 ms  2001:4860:1:1:0:1d31:0:20
 12    14 ms     4 ms     5 ms  2001:4860:0:f90::9
 13    25 ms     4 ms     4 ms  2001:4860::c:4003:1c92
 14    33 ms     6 ms     5 ms  2001:4860::cc:4000:fa62
 15     8 ms     6 ms     6 ms  2001:4860:0:1::1201
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25    46 ms     6 ms     4 ms  sa-in-x71.1e100.net [2404:6800:4003:c00::71]

Trace complete.
 
Mach3.2

Mach3.2

Great Supremacy Member
HWZ Insider
Joined
Apr 8, 2011
Messages
72,404
Reaction score
2,461
xiaofan said:
The best what I can achieve now is using OpenWRT.
OpenWRT main router + OpenWRT secondary router (Double NAT for IPv4).

Main router IPv6: WAN /56; LAN /60
Secondary router IPv6: WAN: /62, LAN /64

1) Main router (Open WRT 23.05 VM under PVE8.0, Intel N100 mini PC)
Hw1uEM4.png



2) Secondary router, OpenWRT 22.03.5, Linksys WRT1900AC v1.

c4LlzjU.png



3) Wireless client of WRT1900AC V1 -- Acer Windows 11 laptop.

Code: 
PS C:\work> tracert ipv6.google.com

Tracing route to ipv6.l.google.com [2404:6800:4003:c00::71]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  2400:d802:xxxx:xx04::1 (Linksys WRT1900AC OpenWRT)
  2     3 ms     2 ms     2 ms  2400:d802:xxxx:xx00::1 (Intel N100 OpenWRT VM)
  3     7 ms     5 ms     5 ms  2400:d802:1:606:: (Singtel IPv6 gateway)
  4    41 ms    36 ms    36 ms  2001:c20:3c00::6
  5     5 ms     3 ms     3 ms  2001:c20:3c00::7
  6    17 ms     4 ms     4 ms  2001:c20:0:3::35
  7     4 ms     4 ms     4 ms  2001:c20:0:3::a
  8     6 ms     4 ms     4 ms  2001:c10:80:2::a21
  9     6 ms     8 ms     4 ms  2001:c10:80:2::915
 10    22 ms    10 ms    67 ms  2001:c10:80:1::a75
 11     6 ms     5 ms     5 ms  2001:4860:1:1:0:1d31:0:20
 12    14 ms     4 ms     5 ms  2001:4860:0:f90::9
 13    25 ms     4 ms     4 ms  2001:4860::c:4003:1c92
 14    33 ms     6 ms     5 ms  2001:4860::cc:4000:fa62
 15     8 ms     6 ms     6 ms  2001:4860:0:1::1201
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25    46 ms     6 ms     4 ms  sa-in-x71.1e100.net [2404:6800:4003:c00::71]

Trace complete.
Click to expand...
Nice.

That's also a lot of hops before the traffic finally leaves their network :spin:

Bash: 
tracert -4 sc-in-f94.1e100.net

Tracing route to sc-in-f94.1e100.net [74.125.68.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.80.30.1
  2     2 ms     2 ms     2 ms  1.64.156.175.unknown.m1.com.sg [175.156.64.1]
  3     3 ms     2 ms     2 ms  204.246.65.202.unknown.m1.com.sg [202.65.246.204]
  4     2 ms     3 ms     2 ms  205.246.65.202.unknown.m1.com.sg [202.65.246.205]
  5     3 ms     3 ms     3 ms  159.245.65.202.unknown.m1.com.sg [202.65.245.159] < Final M1 router
  6     4 ms     3 ms     3 ms  72.14.222.186 < Google's network
  7     4 ms     4 ms     4 ms  108.170.240.225
  8     3 ms     3 ms     3 ms  108.170.240.241
  9     5 ms     5 ms     5 ms  209.85.255.43
 10    21 ms    10 ms     5 ms  216.239.56.38
 11     4 ms     5 ms     4 ms  216.239.35.145
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     4 ms     4 ms     4 ms  sc-in-f94.1e100.net [74.125.68.94]

Trace complete.

Bash: 
tracert -6 sc-in-f94.1e100.net

Tracing route to sc-in-f94.1e100.net [2404:6800:4003:c02::5e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  0.0.4.7.1.0.4.2.ip6.arpa [2401:7400:c80b:xxxx:xxxx:xxxx:xxxx:xxxx]
  2     *        *        *     Request timed out.
  3     3 ms     3 ms     2 ms  0.0.4.7.1.0.4.2.ip6.arpa [2401:7400:800:2a::]
  4     4 ms     3 ms     3 ms  0.0.4.7.1.0.4.2.ip6.arpa [2401:7400:800:2a::1]
  5     4 ms     4 ms     4 ms  2401:7400:0:8::1 < Final M1 router
  6     4 ms     4 ms     4 ms  2001:4860:1:1::1a4c < Google's network
  7     4 ms     4 ms     4 ms  2404:6800:8341:40::1
  8     5 ms     4 ms     4 ms  2001:4860:0:1::77ba
  9     5 ms     5 ms     5 ms  2001:4860:0:f90::9
 10    36 ms     8 ms     4 ms  2001:4860::c:4003:1c92
 11     4 ms     5 ms     4 ms  2001:4860::cc:4000:fa62
 12     6 ms     5 ms     5 ms  2001:4860:0:1::1201
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     5 ms     4 ms     4 ms  sc-in-x5e.1e100.net [2404:6800:4003:c02::5e]

Trace complete.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Main OpenWRT router configuration.
Code: 
root@OpenWrt:~# cat /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd50:64a0:e3e0::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.28.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        list ip6class 'wan6'
        list dns '1.1.1.3'
        list dns '1.0.0.3'
        list dns '9.9.9.9'
        list dns '9.9.9.10'

config interface 'wan'
        option device 'eth1'
        option proto 'dhcp'
        option peerdns '0'
        list dns '1.1.1.3'
        list dns '1.0.0.3'
        list dns '9.9.9.9'
        list dns '9.9.9.10'

config interface 'wan6'
        option device 'eth1'
        option proto 'dhcpv6'
        option reqaddress 'try'
        option reqprefix '56'
        option peerdns '0'
        list dns '2606:4700:4700::1113'
        list dns '2606:4700:4700::1003'
        list dns '2620:fe::fe'
        list dns '2620:fe::10'
        list dns '1.1.1.3'
        list dns '1.0.0.3'
        list dns '9.9.9.9'
        list dns '9.9.9.10'
        
    root@OpenWrt:~# cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option localservice '1'
        option ednspacket_max '1232'
        list server '/mask.icloud.com/'
        list server '/mask-h2.icloud.com/'
        list server '/use-application-dns.net/'
        option serversfile '/var/run/adblock-fast/dnsmasq.servers'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Secondary router OpenWRT 22.03.5 configuration -- Linksys WRT1900 AC V1

Code: 
root@OpenWrt:~# cat /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd99:c359:f0c9::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config device
        option name 'lan1'
        option macaddr 'xx:xx:xx:xx:xx:xx'

config device
        option name 'lan2'
        option macaddr 'xx:xx:xx:xx:xx:xx'

config device
        option name 'lan3'
        option macaddr 'xx:xx:xx:xx:xx:xx'

config device
        option name 'lan4'
        option macaddr 'xx:xx:xx:xx:xx:xx'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '64'
        list ip6class 'wan6'

config device
        option name 'wan'
         option macaddr 'xx:xx:xx:xx:xx:xx'

config interface 'wan'
        option device 'wan'
        option proto 'dhcp'

config interface 'wan6'
        option device 'wan'
        option proto 'dhcpv6'
        option reqaddress 'try'
        option reqprefix 'auto'

root@OpenWrt:~# cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option ra 'server'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'
        option dhcpv6 'server'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config dhcp 'wan6'
        option interface 'wan6'
        option ignore '1'
        option master '1'
        option ra 'relay'
        option dhcpv6 'relay'
        option ndp 'relay'
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Mach3.2 said:
Not sure if this option is available in your Asus router settings, if you route a prefix shorter than /64 (e.g. /63 for 2 /64 subnets) to the upstream LAN, you can route additional /64 subnet(s) to your downstream router.

See DHCPv6 Prefix Delegation.
https://docs.netgate.com/pfsense/en/latest/services/dhcp/ipv6.html
Click to expand...

It turns out Merlin FW (official Merlin FW or gnuton fork) has that setting.

This is from my Asus RT-AX82U running gnuton fork of merlin. It is behind the OpenWRT 23.05 virtual router.

9T1vV6Z.png


Just for fun, the following is with triple-NAT for IPv6 (typo, should be IPv4).

Main OpenWRT 23.05 VM router -- Asus RT-AX82U gnuton Merlin FW -- OpenWRT 22.03.5 Linksys WRT1900AC -- Acer Windows 11 laptop wireless client

Code: 
PS C:\work> tracert ipv6.google.com

Tracing route to ipv6.l.google.com [2404:6800:4003:c00::65]
over a maximum of 30 hops:

  1    29 ms    18 ms    17 ms  2400:d802:xxxx:xx08:xxxx:xxxx:xxxx:xxxx (Linksys WRT1900AC v1)
  2    30 ms    17 ms    17 ms  RT-AX82U-83E0 [2400:d802:xxxx:xx08::1] (RT=AX82U gnuton Merlin)
  3    26 ms    16 ms    37 ms  2400:d802:xxxx:xx00::1 (OpenWRT 23.05 VM)
  4    35 ms    37 ms    17 ms  2400:d802:1:606:: (Singtel gateway)
  5    33 ms    16 ms    16 ms  2001:c20:3c00::6
  6    19 ms    18 ms    15 ms  2001:c20:3c00::7
  7    26 ms    17 ms    16 ms  2001:c20:0:3::35
  8    32 ms    57 ms    16 ms  2001:c20:0:3::a
  9    26 ms    17 ms    17 ms  2001:c10:80:2::a21
 10    19 ms    77 ms    16 ms  2001:c10:80:2::915
 11    58 ms    57 ms    16 ms  2001:c10:80:1::a75
 12    33 ms    38 ms    57 ms  2001:4860:1:1:0:1d31:0:20
 13    53 ms    16 ms    17 ms  2001:4860:0:1008::10
 14    23 ms    33 ms    18 ms  2001:4860::c:4003:1c93
 15    67 ms    17 ms    36 ms  2001:4860::cc:4000:fa63
 16    62 ms    37 ms    77 ms  2001:4860:0:1::d9
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     6 ms     4 ms     5 ms  sa-in-f101.1e100.net [2404:6800:4003:c00::65]

Trace complete.
 
Last edited:
B

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,027
Reaction score
538
xiaofan said:
Just for fun, the following is with triple-NAT for IPv6.
Click to expand...

No NAT at all, just pure routing. With a /56 you can create up to 256 VLANs, so you could theoretically make a chain of 200+ devices if you wanted, or setup a pretty complex network.
Everything is directly addressable, and reachable subject to your firewall rules allowing it.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
bert64 said:
No NAT at all, just pure routing. With a /56 you can create up to 256 VLANs, so you could theoretically make a chain of 200+ devices if you wanted, or setup a pretty complex network.
Everything is directly addressable, and reachable subject to your firewall rules allowing it.
Click to expand...

Sorry for the typo.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
xiaofan said:
It turns out Merlin FW (official Merlin FW or gnuton fork) has that setting.

This is from my Asus RT-AX82U running gnuton fork of merlin. It is behind the OpenWRT 23.05 virtual router.

9T1vV6Z.png
Click to expand...

It turns out this is not useful.

I have installed Merlin FW for my Asus RT-AX86U and it still only gives /64 to the router connects to the LAN port.
 
B

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,027
Reaction score
538
xiaofan said:
It turns out this is not useful.

I have installed Merlin FW for my Asus RT-AX86U and it still only gives /64 to the router connects to the LAN port.
Click to expand...
Pfsense/Opnsense can do downstream delegation for sure.
You can also turn off state tracking so your traffic will pass through unfiltered (higher throughput and lower cpu/mem usage). You can leave any filtering to the downstream devices.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
bert64 said:
Pfsense/Opnsense can do downstream delegation for sure.
You can also turn off state tracking so your traffic will pass through unfiltered (higher throughput and lower cpu/mem usage). You can leave any filtering to the downstream devices.
Click to expand...

So far I have only got consistent results using OpenWRT and Asus router to get Singtel native IPv6 to work. And only OpenWRT is able to carry out proper downstream delegation.

I have only got pfSense to work once (posted before in this thread) and never got success after that (not able to get IPv6 address). I have never got OPNsense to work at all (not able to get IPv6 address).

I wil try later this week.
 
Mach3.2

Mach3.2

Great Supremacy Member
HWZ Insider
Joined
Apr 8, 2011
Messages
72,404
Reaction score
2,461
xiaofan said:
I have only got pfSense to work once (posted before in this thread) and never got success after that (not able to get IPv6 address). I have never got OPNsense to work at all (not able to get IPv6 address).
Click to expand...
Perhaps can check the DUID type is set to DUID-LL. It might be set to DUID-LLT by default, and bert64 mentioned having some difficulties with M1 when it's set to DUID-LLT.

System > Advanced > Networking > DHCP Options > DHCP6 DUID
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Mach3.2 said:
Perhaps can check the DUID type is set to DUID-LL. It might be set to DUID-LLT by default, and bert64 mentioned having some difficulties with M1 when it's set to DUID-LLT.

System > Advanced > Networking > DHCP Options > DHCP6 DUID
Click to expand...

Unfortunately it does not work.

Then I go back to use 6rd and then it works again.

4iWsIT3.png


6RD Prefix: 2400:d803::/32
6RD Border relay: 202.166.127.6
6RD IPv4 Prefix length: 0

For the LAN interface, IPv4 DHCP is enabled. IPv6 DHCP is disabled (edit: actually disable/enable are both okay) but Router Advertisement needs to be set as Unmanged.
 
Last edited:
Mach3.2

Mach3.2

Great Supremacy Member
HWZ Insider
Joined
Apr 8, 2011
Messages
72,404
Reaction score
2,461
xiaofan said:
Unfortunately it does not work.

Then I go back to use 6rd and then it works again.

4iWsIT3.png


6RD Prefix: 2400:d803::/32
6RD Border relay: 202.166.127.6
6RD IPv4 Prefix length: 0

For the LAN interface, IPv4 DHCP is enabled. IPv6 DHCP is disabled but Router Advertisement needs to be set as Unmanged.
Click to expand...
I'll also try cloning the DUID and MAC address of your openwrt router, maybe Singtel's DHCPv6 server have some sort of restriction on multiple devices requesting for delegated prefixes.

Setting the DHCP6 client into debug mode should also generate more verbose log that might shed some light on what's going on.

System > Advanced > Networking > DHCP Options > DHCP6 Debug
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Mach3.2 said:
I'll also try cloning the DUID and MAC address of your openwrt router, maybe Singtel's DHCPv6 server have some sort of restriction on multiple devices requesting for delegated prefixes.

Setting the DHCP6 client into debug mode should also generate more verbose log that might shed some light on what's going on.

System > Advanced > Networking > DHCP Options > DHCP6 Debug
Click to expand...

I am using the same WAN MAC address for OpenWRT and pfSense (as well as OPNsense) on my Intel J4105 mini PC running PVE 7.4. This is to prevent Singtel IPv4 change problem (up to 3 times).

I will try to debug this later. So much for today.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
xiaofan said:
I am using the same WAN MAC address for OpenWRT and pfSense (as well as OPNsense) on my Intel J4105 mini PC running PVE 7.4. This is to prevent Singtel IPv4 change problem (up to 3 times).

I will try to debug this later. So much for today.
Click to expand...

Not much from the log info.

Code: 
Nov 21 21:08:44 pfSense dhcp6c[12398]: Sending Request
Nov 21 21:08:44 pfSense dhcp6c[12398]: set client ID (len 10)
Nov 21 21:08:44 pfSense dhcp6c[12398]: set server ID (len 14)
Nov 21 21:08:44 pfSense dhcp6c[12398]: set IA address
Nov 21 21:08:44 pfSense dhcp6c[12398]: set status code
Nov 21 21:08:44 pfSense dhcp6c[12398]: set identity association
Nov 21 21:08:44 pfSense dhcp6c[12398]: set elapsed time (len 2)
Nov 21 21:08:44 pfSense dhcp6c[12398]: set option request (len 4)
Nov 21 21:08:44 pfSense dhcp6c[12398]: set IA_PD prefix
Nov 21 21:08:44 pfSense dhcp6c[12398]: set status code
Nov 21 21:08:44 pfSense dhcp6c[12398]: set IA_PD
Nov 21 21:08:44 pfSense dhcp6c[12398]: send request to ff02::1:2%vtnet0
Nov 21 21:08:44 pfSense dhcp6c[12398]: reset a timer on vtnet0, state=REQUEST, timeo=9, retrans=30180
Nov 21 21:09:14 pfSense dhcp6c[12398]: no responses were received
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
Reboot and it seems that pfSense tried three times and then gave up.

Code: 
Nov 21 21:33:38 pfSense dhcp6c[14154]: Sending Request
Nov 21 21:33:38 pfSense dhcp6c[14154]: set client ID (len 10)
Nov 21 21:33:38 pfSense dhcp6c[14154]: set server ID (len 14)
Nov 21 21:33:38 pfSense dhcp6c[14154]: set IA address
Nov 21 21:33:38 pfSense dhcp6c[14154]: set status code
Nov 21 21:33:38 pfSense dhcp6c[14154]: set identity association
Nov 21 21:33:38 pfSense dhcp6c[14154]: set elapsed time (len 2)
Nov 21 21:33:38 pfSense dhcp6c[14154]: set option request (len 4)
Nov 21 21:33:38 pfSense dhcp6c[14154]: set IA_PD prefix
Nov 21 21:33:38 pfSense dhcp6c[14154]: set status code
Nov 21 21:33:38 pfSense dhcp6c[14154]: set IA_PD
Nov 21 21:33:38 pfSense dhcp6c[14154]: send request to ff02::1:2%vtnet0
Nov 21 21:33:38 pfSense dhcp6c[14154]: reset a timer on vtnet0, state=REQUEST, timeo=6, retrans=28152
Nov 21 21:34:06 pfSense dhcp6c[14154]: Sending Request
Nov 21 21:34:06 pfSense dhcp6c[14154]: set client ID (len 10)
Nov 21 21:34:06 pfSense dhcp6c[14154]: set server ID (len 14)
Nov 21 21:34:06 pfSense dhcp6c[14154]: set IA address
Nov 21 21:34:06 pfSense dhcp6c[14154]: set status code
Nov 21 21:34:06 pfSense dhcp6c[14154]: set identity association
Nov 21 21:34:06 pfSense dhcp6c[14154]: set elapsed time (len 2)
Nov 21 21:34:06 pfSense dhcp6c[14154]: set option request (len 4)
Nov 21 21:34:06 pfSense dhcp6c[14154]: set IA_PD prefix
Nov 21 21:34:06 pfSense dhcp6c[14154]: set status code
Nov 21 21:34:06 pfSense dhcp6c[14154]: set IA_PD
Nov 21 21:34:06 pfSense dhcp6c[14154]: send request to ff02::1:2%vtnet0
Nov 21 21:34:06 pfSense dhcp6c[14154]: reset a timer on vtnet0, state=REQUEST, timeo=7, retrans=30834
Nov 21 21:34:37 pfSense dhcp6c[14154]: Sending Request
Nov 21 21:34:37 pfSense dhcp6c[14154]: set client ID (len 10)
Nov 21 21:34:37 pfSense dhcp6c[14154]: set server ID (len 14)
Nov 21 21:34:37 pfSense dhcp6c[14154]: set IA address
Nov 21 21:34:37 pfSense dhcp6c[14154]: set status code
Nov 21 21:34:37 pfSense dhcp6c[14154]: set identity association
Nov 21 21:34:37 pfSense dhcp6c[14154]: set elapsed time (len 2)
Nov 21 21:34:37 pfSense dhcp6c[14154]: set option request (len 4)
Nov 21 21:34:37 pfSense dhcp6c[14154]: set IA_PD prefix
Nov 21 21:34:37 pfSense dhcp6c[14154]: set status code
Nov 21 21:34:37 pfSense dhcp6c[14154]: set IA_PD
Nov 21 21:34:37 pfSense dhcp6c[14154]: send request to ff02::1:2%vtnet0
Nov 21 21:34:37 pfSense dhcp6c[14154]: reset a timer on vtnet0, state=REQUEST, timeo=8, retrans=27750
Nov 21 21:35:05 pfSense dhcp6c[14154]: Sending Request
Nov 21 21:35:05 pfSense dhcp6c[14154]: set client ID (len 10)
Nov 21 21:35:05 pfSense dhcp6c[14154]: set server ID (len 14)
Nov 21 21:35:05 pfSense dhcp6c[14154]: set IA address
Nov 21 21:35:05 pfSense dhcp6c[14154]: set status code
Nov 21 21:35:05 pfSense dhcp6c[14154]: set identity association
Nov 21 21:35:05 pfSense dhcp6c[14154]: set elapsed time (len 2)
Nov 21 21:35:05 pfSense dhcp6c[14154]: set option request (len 4)
Nov 21 21:35:05 pfSense dhcp6c[14154]: set IA_PD prefix
Nov 21 21:35:05 pfSense dhcp6c[14154]: set status code
Nov 21 21:35:05 pfSense dhcp6c[14154]: set IA_PD
Nov 21 21:35:05 pfSense dhcp6c[14154]: send request to ff02::1:2%vtnet0
Nov 21 21:35:05 pfSense dhcp6c[14154]: reset a timer on vtnet0, state=REQUEST, timeo=9, retrans=30180
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
xiaofan said:
Reboot and it seems that pfSense tried three times and then gave up.
Click to expand...

More complete dhcp6c log. Looks like it has some initial success and get /56. But somehow it failed later. I am not so sure if it is a pfSense problem or Singtel problem. However, since Asus and OpenWRT work fine, I tend to think it is a pfSense problem. I am running pfSense CE 2.7 release version.

Code: 
Nov 21 22:37:03 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=INIT, timeo=0, retrans=891
Nov 21 22:37:04 pfSense dhcp6c[14400]: Sending Solicit
Nov 21 22:37:04 pfSense dhcp6c[14400]: a new XID (2833bf) is generated
Nov 21 22:37:04 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:04 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:04 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:04 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:04 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:04 pfSense dhcp6c[14400]: transmit failed: Can't assign requested address
Nov 21 22:37:04 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=SOLICIT, timeo=0, retrans=1091
Nov 21 22:37:06 pfSense dhcp6c[14400]: Sending Solicit
Nov 21 22:37:06 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:06 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:06 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:06 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:06 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:06 pfSense dhcp6c[14400]: send solicit to ff02::1:2%vtnet0
Nov 21 22:37:06 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=SOLICIT, timeo=1, retrans=2083
Nov 21 22:37:06 pfSense dhcp6c[14400]: receive advertise from fe80::ae85:3dff:fe93:66f6%vtnet0 on vtnet0
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option client ID, len 10
Nov 21 22:37:06 pfSense dhcp6c[14400]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option server ID, len 14
Nov 21 22:37:06 pfSense dhcp6c[14400]:   DUID: 00:01:00:01:28:ef:71:0d:00:0c:29:cc:c5:b3
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option preference, len 1
Nov 21 22:37:06 pfSense dhcp6c[14400]:   preference: 0
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option identity association, len 53
Nov 21 22:37:06 pfSense dhcp6c[14400]:   IA_NA: ID=0, T1=43200, T2=75600
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option IA address, len 24
Nov 21 22:37:06 pfSense dhcp6c[14400]:   IA_NA address: 2400:d802:1c18::1:6ce7 pltime=86400 vltime=86400
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option status code, len 9
Nov 21 22:37:06 pfSense dhcp6c[14400]:   status code: success
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option IA_PD, len 54
Nov 21 22:37:06 pfSense dhcp6c[14400]:   IA_PD: ID=0, T1=43200, T2=75600
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option IA_PD prefix, len 25
Nov 21 22:37:06 pfSense dhcp6c[14400]:   IA_PD prefix: 2400:d802:1cec:c500::/56 pltime=86400 vltime=450839087813841280
Nov 21 22:37:06 pfSense dhcp6c[14400]: get DHCP option status code, len 9
Nov 21 22:37:06 pfSense dhcp6c[14400]:   status code: success
Nov 21 22:37:06 pfSense dhcp6c[14400]: server ID: 00:01:00:01:28:ef:71:0d:00:0c:29:cc:c5:b3, pref=0
Nov 21 22:37:06 pfSense dhcp6c[14400]: reset timer for vtnet0 to 0.983112
Nov 21 22:37:07 pfSense dhcp6c[14400]: picked a server (ID: 00:01:00:01:28:ef:71:0d:00:0c:29:cc:c5:b3)
Nov 21 22:37:07 pfSense dhcp6c[14400]: Sending Request
Nov 21 22:37:07 pfSense dhcp6c[14400]: a new XID (1210b3) is generated
Nov 21 22:37:07 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set server ID (len 14)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA address
Nov 21 22:37:07 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:07 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:07 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA_PD prefix
Nov 21 22:37:07 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:07 pfSense dhcp6c[14400]: send request to ff02::1:2%vtnet0
Nov 21 22:37:07 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=REQUEST, timeo=0, retrans=911
Nov 21 22:37:07 pfSense dhcp6c[14400]: Sending Request
Nov 21 22:37:07 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set server ID (len 14)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA address
Nov 21 22:37:07 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:07 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:07 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA_PD prefix
Nov 21 22:37:07 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:07 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:07 pfSense dhcp6c[14400]: send request to ff02::1:2%vtnet0
Nov 21 22:37:07 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=REQUEST, timeo=1, retrans=1845
Nov 21 22:37:09 pfSense dhcp6c[14400]: Sending Request
Nov 21 22:37:09 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:09 pfSense dhcp6c[14400]: set server ID (len 14)
Nov 21 22:37:09 pfSense dhcp6c[14400]: set IA address
Nov 21 22:37:09 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:09 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:09 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:09 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:09 pfSense dhcp6c[14400]: set IA_PD prefix
Nov 21 22:37:09 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:09 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:09 pfSense dhcp6c[14400]: send request to ff02::1:2%vtnet0
Nov 21 22:37:09 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=REQUEST, timeo=2, retrans=3735
Nov 21 22:37:13 pfSense dhcp6c[14400]: Sending Request
Nov 21 22:37:13 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:13 pfSense dhcp6c[14400]: set server ID (len 14)
Nov 21 22:37:13 pfSense dhcp6c[14400]: set IA address
Nov 21 22:37:13 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:13 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:13 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:13 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:13 pfSense dhcp6c[14400]: set IA_PD prefix
Nov 21 22:37:13 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:13 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:13 pfSense dhcp6c[14400]: send request to ff02::1:2%vtnet0
Nov 21 22:37:13 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=REQUEST, timeo=3, retrans=7304
Nov 21 22:37:20 pfSense dhcp6c[14400]: Sending Request
Nov 21 22:37:20 pfSense dhcp6c[14400]: set client ID (len 10)
Nov 21 22:37:20 pfSense dhcp6c[14400]: set server ID (len 14)
Nov 21 22:37:20 pfSense dhcp6c[14400]: set IA address
Nov 21 22:37:20 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:20 pfSense dhcp6c[14400]: set identity association
Nov 21 22:37:20 pfSense dhcp6c[14400]: set elapsed time (len 2)
Nov 21 22:37:20 pfSense dhcp6c[14400]: set option request (len 4)
Nov 21 22:37:20 pfSense dhcp6c[14400]: set IA_PD prefix
Nov 21 22:37:20 pfSense dhcp6c[14400]: set status code
Nov 21 22:37:20 pfSense dhcp6c[14400]: set IA_PD
Nov 21 22:37:20 pfSense dhcp6c[14400]: send request to ff02::1:2%vtnet0
Nov 21 22:37:20 pfSense dhcp6c[14400]: reset a timer on vtnet0, state=REQUEST, timeo=4, retrans=14748
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
30,842
Reaction score
8,570
This request failed for the WAN interface -- send request to ff02::1:2%vtnet0.

The request is to get DHCPv6 server as per the following IPv6 cheat sheet.
https://github.com/onemarcfifty/cheat-sheets/blob/main/networking/ipv6.md

The following IPv6 multicast addresses may be used in in the link-local scope:

RangePurpose
ff02::1All Nodes within the network segment
ff02::2All Routers within the network segment
ff02::fbmDNSv6
ff02::1:2All DHCP Servers and Agents
ff02::101All NTP Servers
 
You must log in or register to reply here.
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Community Guidelines and Standards, Terms of Service and Member T&Cs for more information.
Top