my singtel 6rd ipv6 is not working this morning.
who has same problem please share here.
root@OpenWrt:~# ping -c 4 ipv6.google.com
PING ipv6.google.com(sh-in-f113.1e100.net (2404:6800:4003:c1c::71)) 56 data bytes
64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=1 ttl=109 time=4.19 ms
64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=2 ttl=109 time=4.04 ms
64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=3 ttl=109 time=3.87 ms
64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=4 ttl=109 time=4.14 ms
--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 3.873/4.059/4.186/0.119 ms
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 'dda5:edda:cf50::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.38.1'
option netmask '255.255.255.0'
option delegate '0'
option ip6assign '64'
list ip6class 'wan6'
config interface 'wan'
option device 'eth0'
option proto 'dhcp'
config interface 'wan6'
option proto '6rd'
option peeraddr '202.166.127.6'
option ip6prefix '2400:d803::'
option ip6prefixlen '32'
No issue here with Singtel 6rd with a virtual OpenWRT router.
Bash:root@OpenWrt:~# ping -c 4 ipv6.google.com PING ipv6.google.com(sh-in-f113.1e100.net (2404:6800:4003:c1c::71)) 56 data bytes 64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=1 ttl=109 time=4.19 ms 64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=2 ttl=109 time=4.04 ms 64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=3 ttl=109 time=3.87 ms 64 bytes from sh-in-f113.1e100.net (2404:6800:4003:c1c::71): icmp_seq=4 ttl=109 time=4.14 ms --- ipv6.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 3.873/4.059/4.186/0.119 ms 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 'dda5:edda:cf50::/48' config device option name 'br-lan' option type 'bridge' list ports 'eth1' config interface 'lan' option device 'br-lan' option proto 'static' option ipaddr '192.168.38.1' option netmask '255.255.255.0' option delegate '0' option ip6assign '64' list ip6class 'wan6' config interface 'wan' option device 'eth0' option proto 'dhcp' config interface 'wan6' option proto '6rd' option peeraddr '202.166.127.6' option ip6prefix '2400:d803::' option ip6prefixlen '32'
My singtel 6rd ipv6 doesn't work again now:
root@OpenWrt:~# ping -c 4 ipv6.google.com
PING ipv6.google.com(sd-in-f138.1e100.net (2404:6800:4003:c0f::8a)) 56 data bytes
--- ipv6.google.com ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3142ms
root@OpenWrt:~# ping -c 4 ipv6.google.com
PING ipv6.google.com(sb-in-x71.1e100.net (2404:6800:4003:c01::71)) 56 data bytes
64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=1 ttl=108 time=4.20 ms
64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=2 ttl=108 time=4.09 ms
64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=3 ttl=108 time=3.74 ms
64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=4 ttl=108 time=3.94 ms
--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 3.737/3.991/4.200/0.173 ms
Hmm, this time I can reproduce your issue.
Bash:root@OpenWrt:~# ping -c 4 ipv6.google.com PING ipv6.google.com(sd-in-f138.1e100.net (2404:6800:4003:c0f::8a)) 56 data bytes --- ipv6.google.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3142ms
Edit to add --> reboot the virtual OpenWRT and it works again.
Bash:root@OpenWrt:~# ping -c 4 ipv6.google.com PING ipv6.google.com(sb-in-x71.1e100.net (2404:6800:4003:c01::71)) 56 data bytes 64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=1 ttl=108 time=4.20 ms 64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=2 ttl=108 time=4.09 ms 64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=3 ttl=108 time=3.74 ms 64 bytes from sb-in-f113.1e100.net (2404:6800:4003:c01::71): icmp_seq=4 ttl=108 time=3.94 ms --- ipv6.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 3.737/3.991/4.200/0.173 ms
why not? lolrebooting router is not good solution..
rebooting router is not good solution..
Is native ipv6 always working?
why not? lol
Yes, Singtel native IPv6 is always working in my case. I am using XGS-PON ONR so I had to request through Singtel to enable native IPv6. But as per the reports, Singtel may have not finished the deployment yet (strange that it takes so long as I got native IPv6 working with my ONT connection back in Nov 2023).
You should really try native IPv6 if it is available in your area, it is way better than 6rd.
rebooting router is not good solution..
Is native ipv6 always working?
You should really try native IPv6 if it is available in your area, it is way better than 6rd.
The reboot is doing something to restore service over the 6rd connection. If you can figure out what that something is then you can do just that, without a reboot. Probably with an automated script of some kind.My 6rd also not working, disabled it on boot.
The reboot is doing something to restore service over the 6rd connection. If you can figure out what that something is then you can do just that, without a reboot. Probably with an automated script of some kind.
In addition to native IPv6 (if available) Hurricane Electric's Tunnel Broker is an option. You can even "dual path" Singtel 6rd and HE Tunnel Broker so that if one IPv6 path is down the other will be used, and vice versa. Just be aware that streaming services such as Netflix may geoblock IPv6 traffic that Hurricane Electric routes.
You could do that. Another potentially simpler option is to insert a delay early in your router's boot process. Typically that's a matter of changing a parameter/configuration setting.If ONT and router reboot at same time, 6rd IPv6 will not work.
If ONT reboots first, router reboots 5 mins later, 6rd IPv6 will work properly.
This problem never occurs before.
Now I am using single timer power socket for both ONT and router auto-rebooting so I can see this problem.
I will use different timer power sockets for ONT and router auto-rebooting.
It's not the router that needs an address, it needs a prefix delegation that you can apply to your inside interfaces.Now I change back to Singtel Mesh Router.
The strange thing is:
When I set ipv6 as 6RD, router can't ipv6 address;
When I set ipv6 as Dual Stack, it can get native ipv6 address:
Internet
Status: Connected
IPv4 Address: 42.60.134.xx
IPv6 Address: 2400:d802:321a:f24e::41
But ipv6 has no internet access.
Then I call 1688 and they say that they need 2-4 days to do ipv6 troubleshooting.
It's not the router that needs an address, it needs a prefix delegation that you can apply to your inside interfaces.
The router technically does not need a WAN address in a native setup (it can use the link-local), and the WAN address (if assigned) does not need to be routable.
What matters if that the router receives a prefix delegation (singtel give you a /56 on native), and then the router needs to split off a /64 from that /56 for each VLAN you want to create.
Check your prefix delegation settings.
6rd works differently...When I set 6RD ipv6 in router, I'm using default setting:
IPv6 Protocol IPv6 - 6rd
6rd Tunnel Type Manual Configuration
Prefix 2400: D803
Prefix Length 32
Border Relay 6rd.singnet.com.sg
IPv4 Address Mask 0
client PC can get 6rd ipv6 address as below, but it doesn't have internet access:
IPv6 Address 2400:d803:2a3c:8684:359a:bd22:d7b
Temporary IPv6 Address 2400:d803:2a3c:8684:59fef186f740
Link-ocal IPv6 Address fe80:fb8d:509f:5:6053%.9
IPv6 Default Gateway fe80:aaa2:37ffe35:ce94%9
IPv6 DNS Servers 2400:d800::1
2400:d800::2