IPv6 discussions

bert64 · Jun 17, 2025

probablye said:
i have access to Singtel Business Broadband. very low-end basic 350 Mbps plan.

last year, i tried enabling IPv6, only the 6rd worked, which i didn't want to use.

i configured the router to native IPv6, which didn't work, but i just left it at that configuration.

i don't log in to the router admin page much except for when i need to update the firmware, which was a few months ago. but yesterday when i logged in, to my surprise, there was a native IPv6 /56 connection active!

i put in an IPv6 DNS server and it worked immediately.

i didn't request for it, it just happened on its own. looks like Singtel is really slowly rolling out native IPv6 across their network.

Supposedly if you're on a business plan you should be able to request a static /48 for free, but you have to call the business support line for that. It won't delegate it via DHCPv6.

If you got an automatic /56 it looks like they've rolled out the same DHCPv6 setup they have on the consumer side.

bert64 · Jun 17, 2025

Mach3.2 said:
Don't let VQ be your only WAN connection though, the uptime can be flaky.

I'm using VQ's /56 for my subnets, then NPTv6 from the VQ prefix to my secondary connection's /64 for dual WAN load balancing.

The gold standard for multi line load balancing is BGP, and with v6 you can get yourself your own provider independent /48 and an AS# for less than $200/year which is more than affordable for a small business or hobbyist.

Sadly most ISPs are still thinking in the legacy mindset where anyone who has enough address space for BGP has already invested thousands and won't blink at a few more thousand for the actual links.

There are several VPS providers who will let you run BGP (even on a virtual server costing $5/month), but then you'd have to tunnel your address space to wherever the VPS provider is which is going to add some latency.

overratedplot · Jun 19, 2025

woshiitcy said:
Just sharing my experience, has dual-stacked my home previously except for Wireguard until now
Below are some of the backstories and what are the problems faces and the steps to overcome it. Solution might be janky, but it works for me now.

Nice! If you don't want to assign your entire precious /64 to Wireguard, you can probably change the wireguard prefix length to something like /112. That way you can still use SLAAC on your local network, since it's a bit unlikely it will clash with your static wireguard IPs (which should be something like fdxx:xxxx:xxxx:0:0:0:0:xxxx)

woshiitcy · Jun 19, 2025

overratedplot said:
Nice! If you don't want to assign your entire precious /64 to Wireguard, you can probably change the wireguard prefix length to something like /112. That way you can still use SLAAC on your local network, since it's a bit unlikely it will clash with your static wireguard IPs (which should be something like fdxx:xxxx:xxxx:0:0:0:0:xxxx)

Hmmm, but wireguard config has to be static, then once my Starhub gives me a new prefix then it wouldn't work anymore.

bert64 · Jun 20, 2025

I have written a simple web application which maintains a database of ISPs and their level of IPv6 support:

https://ispdb.ev6.net/

I will populate it with more data in the coming days, if anyone else wishes to contribute i can create accounts, or if you send me up to date information i will add it.

bert64 · Jun 20, 2025

woshiitcy said:
Hmmm, but wireguard config has to be static, then once my Starhub gives me a new prefix then it wouldn't work anymore.

Yes that's one of the limitations of wireguard, and one of the hassles of having a dynamic prefix.
Also since starhub only give you a single /64, you can't set aside a separate /64 for the VPN clients.

You'd be stuck using ULA space and NAT66 in this situation, which is far from ideal but no worse than what you'd be doing for legacy ip.

hoision · Jun 22, 2025

bert64 said:
I have written a simple web application which maintains a database of ISPs and their level of IPv6 support:

I will populate it with more data in the coming days, if anyone else wishes to contribute i can create accounts, or if you send me up to date information i will add it.

Would like to find out on how to contribute

bert64 · Jun 22, 2025

hoision said:
Would like to find out on how to contribute

DM me, i can create you an account on it, or if you supply information i can add it to the db.

hoision · Jun 23, 2025

bert64 said:
DM me, i can create you an account on it, or if you supply information i can add it to the db.

I do not have the DM function opened yet..

xiaofan · Jul 17, 2025

For those who are using Singtel ONR, no matter bridged or unbridged, just wondering if you can get native IPv6 to work or not.

I tend to think Singtel has fully deployed native IPv6 but I am not so sure if ONR users have IPv6 enabled by default now or still not enabled by default. If it is still not enabled by default, then it is probably troublesome to get IPv6 as you have to request through Singtel.

ONR without bridging (most of users should be in this case) -- test IPv6 and see if you get IPv6.
https://test-ipv6.com/

ONR with bridging, configure native IPv6 on your own router using DHCPv6 Prefix Delegation (DHCPv6-PD). Then carry out IPv6 test using the above website.

xiaofan · Jul 17, 2025

Pretty decent test results with native Singtel IPv6 and IPv4, to Cloudflare DNS server, Google DNS server and s.taobao.com.

Singtel 5Gbps, bridged ONR.

IPv4 address --> 42.60.xxx.xxx
IPv6 address --> 2400:d802:0dxx:xx00.xxxx.xxxx.xxxx.xxxx

Bash:

root@OpenWrt:~# ping -4 -c 4 dns.cloudflare.com
PING dns.cloudflare.com (162.159.61.8): 56 data bytes
64 bytes from 162.159.61.8: seq=0 ttl=55 time=2.555 ms
64 bytes from 162.159.61.8: seq=1 ttl=55 time=2.926 ms
64 bytes from 162.159.61.8: seq=2 ttl=55 time=3.092 ms
64 bytes from 162.159.61.8: seq=3 ttl=55 time=2.748 ms

--- dns.cloudflare.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.555/2.830/3.092 ms

root@OpenWrt:~# ping -6 -c 4 dns.cloudflare.com
PING dns.cloudflare.com (2a06:98c1:52::8): 56 data bytes
64 bytes from 2a06:98c1:52::8: seq=0 ttl=55 time=2.400 ms
64 bytes from 2a06:98c1:52::8: seq=1 ttl=55 time=2.775 ms
64 bytes from 2a06:98c1:52::8: seq=2 ttl=55 time=2.118 ms
64 bytes from 2a06:98c1:52::8: seq=3 ttl=55 time=2.553 ms

--- dns.cloudflare.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.118/2.461/2.775 ms

root@OpenWrt:~# ping -4 -c 4 dns.google.com
PING dns.google.com (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=115 time=2.055 ms
64 bytes from 8.8.8.8: seq=1 ttl=115 time=2.627 ms
64 bytes from 8.8.8.8: seq=2 ttl=115 time=2.330 ms
64 bytes from 8.8.8.8: seq=3 ttl=115 time=2.623 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.055/2.408/2.627 ms

root@OpenWrt:~# ping -6 -c 4 dns.google.com
PING dns.google.com (2001:4860:4860::8844): 56 data bytes
64 bytes from 2001:4860:4860::8844: seq=0 ttl=115 time=1.999 ms
64 bytes from 2001:4860:4860::8844: seq=1 ttl=115 time=2.319 ms
64 bytes from 2001:4860:4860::8844: seq=2 ttl=115 time=2.346 ms
64 bytes from 2001:4860:4860::8844: seq=3 ttl=115 time=2.385 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.999/2.262/2.385 ms

root@OpenWrt:~# ping -4 -c 4 s.taobao.com
PING s.taobao.com (59.82.121.163): 56 data bytes
64 bytes from 59.82.121.163: seq=0 ttl=82 time=116.585 ms
64 bytes from 59.82.121.163: seq=1 ttl=82 time=114.239 ms
64 bytes from 59.82.121.163: seq=2 ttl=82 time=111.611 ms
64 bytes from 59.82.121.163: seq=3 ttl=82 time=129.574 ms

--- s.taobao.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 111.611/118.002/129.574 ms

root@OpenWrt:~# ping -6 -c 4 s.taobao.com
PING s.taobao.com (2408:4001:f00::412): 56 data bytes
64 bytes from 2408:4001:f00::412: seq=0 ttl=85 time=109.252 ms
64 bytes from 2408:4001:f00::412: seq=1 ttl=85 time=109.085 ms
64 bytes from 2408:4001:f00::412: seq=2 ttl=85 time=102.665 ms
64 bytes from 2408:4001:f00::412: seq=3 ttl=85 time=108.812 ms

--- s.taobao.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 102.665/107.453/109.252 ms

xiaofan · Jul 17, 2025

IPv6 ping to M1 SpeedTest server is much better than last time but still worse than IPv4.

But IPv4 is already not good as it goes through Hong Kong.

Bash:

root@OpenWrt:~# ping -4 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (103.1.138.214): 56 data bytes
64 bytes from 103.1.138.214: seq=0 ttl=53 time=38.677 ms
64 bytes from 103.1.138.214: seq=1 ttl=53 time=43.056 ms
64 bytes from 103.1.138.214: seq=2 ttl=53 time=40.334 ms
64 bytes from 103.1.138.214: seq=3 ttl=53 time=39.737 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 38.677/40.451/43.056 ms

root@OpenWrt:~# ping -6 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (2401:7400:8888:13::2): 56 data bytes
64 bytes from 2401:7400:8888:13::2: seq=0 ttl=51 time=74.539 ms
64 bytes from 2401:7400:8888:13::2: seq=1 ttl=51 time=74.246 ms
64 bytes from 2401:7400:8888:13::2: seq=2 ttl=51 time=74.319 ms
64 bytes from 2401:7400:8888:13::2: seq=3 ttl=51 time=74.449 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 74.246/74.388/74.539 ms

root@OpenWrt:~# mtr -4 m1speedtest1.m1net.com.sg
                                                 My traceroute  [v0.95]
OpenWrt (42.60.xxx.xxx) -> m1speedtest1.m1net.com.sg (103.1.138.214)                             2025-07-17T21:22:37+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. bb42-60-xx-254.singnet.com.sg                                             0.0%    65    1.4   1.6   1.1   7.1   0.9
 2. 165.21.193.22                                                             0.0%    65    3.1   3.8   2.6  13.4   2.1
 3. 165.21.193.21                                                             0.0%    65    2.1   4.6   1.9  44.6   8.6
 4. 165.21.138.245                                                            0.0%    65    2.2   3.5   1.8  26.2   4.4
 5. SN-SINQT1-BO403-ae1.singnet.com.sg                                        0.0%    65    2.1   1.9   1.5   2.2   0.2
 6. 203.208.177.213                                                           0.0%    65    2.2   2.5   1.7  10.8   1.5
 7. xn-lhrcl1-bo706.ix.singtel.com                                            0.0%    65    2.4   3.8   2.2  27.6   4.1
 8. 203.208.158.9                                                             0.0%    65    3.0   3.1   2.5   8.5   1.0
 9. 203.208.158.206                                                          74.6%    64    2.9   9.5   2.8  62.9  15.9
10. 203.208.151.122                                                           0.0%    64   38.3  38.3  37.2  56.8   2.5
11. 203.208.151.93                                                            0.0%    64   37.5  37.3  36.9  38.9   0.4
12. 203.208.178.17                                                            0.0%    64   38.7  39.3  38.3  79.1   5.1
13. ix-be-5.ecore1.hk2-hongkong.as6453.net                                    1.6%    64   38.6  38.5  38.0  39.2   0.2
14. if-bundle-9-2.qcore2.hk2-hongkong.as6453.net                             69.8%    64   73.7  74.2  73.6  74.9   0.3
15. if-bundle-32-2.qcore2.svw-singapore.as6453.net                           92.1%    64   72.7  72.4  72.2  72.7   0.2
16. if-bundle-19-2.qcore1.esin4-singapore.as6453.net                         87.3%    64   72.0  71.7  71.2  72.1   0.3
17. if-be-20-2.ecore1.svq-singapore.as6453.net                                1.6%    64   70.9  75.9  69.8 313.4  31.1
18. if-ae-40-2.thar1.svq-singapore.as6453.net                                 0.0%    64   75.5  74.6  73.9  86.7   1.7
19. 120.29.215.162                                                            0.0%    64   37.9  38.6  37.5  48.6   2.0
20. 220.246.65.202.unknown.m1.com.sg                                          0.0%    64   38.4  38.7  38.0  47.4   1.3
21. 214.138.1.103.unknown.m1.com.sg                                           0.0%    64   38.5  38.8  38.2  42.5   0.8

root@OpenWrt:~# mtr -6 m1speedtest1.m1net.com.sg
                                                 My traceroute  [v0.95]
OpenWrt (2400:d802:0dxx::xx:xxxx) -> m1speedtest1.m1net.com.sg (2401:7400:8888:13::2)             2025-07-17T21:20:18+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2400:d801:4001:611::                                                      0.0%    91    1.5   1.5   1.1   2.4   0.2
 2. 2001:c20:3c00::6                                                          0.0%    91    3.3   4.3   2.8  22.0   2.9
 3. 2001:c20:3c00::7                                                          0.0%    91    2.5   4.0   1.9  38.3   5.3
 4. 2001:c20:0:3::35                                                          0.0%    91    2.1   7.5   1.8  81.1  14.9
 5. 2001:c20:0:3::a                                                           0.0%    91    2.3   2.1   1.7   2.5   0.2
 6. 2001:c10:80:2::a21                                                        0.0%    91    2.4   3.4   1.8  42.0   4.9
 7. 2001:c10:80:2::915                                                        0.0%    91    3.0   5.3   2.1  67.4   8.3
 8. 2001:c10:80:1::ee5                                                        0.0%    91   41.6  43.4  41.5  75.1   4.9
 9. (waiting for reply)
10. (waiting for reply)
11. (waiting for reply)
12. (waiting for reply)
13. 2401:7400:0:2::                                                           0.0%    90   72.0  73.2  71.9  85.7   2.3
14. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    90   74.1  74.3  73.9  74.8   0.2

joeltng · Jul 31, 2025

Just wanted to chime in. Recently saw that there were reports of Starhub IPv6 being fixed a while back and decided to give it a try.

So while most issues I had seen fixed, unfortunately the responsiveness leaves alot to be desired. Everything takes just that little extra to load with some apps just completely bugging out and not able to send GIFs etc. sad. Gonna bring the network down again. Guess I'll try again in 6 months or so

xiaofan · Aug 1, 2025

xiaofan said:
Pretty decent test results with native Singtel IPv6 and IPv4, to Cloudflare DNS server, Google DNS server and s.taobao.com.

Singtel 5Gbps, bridged ONR.

IPv4 address --> 42.60.xxx.xxx
IPv6 address --> 2400:d802:0dxx:xx00.xxxx.xxxx.xxxx.xxxx

Another IPv4 address segment and the results to Cloudflare DNS is quite different this time.

IPv4 ping to Cloudflare DNS is very bad today but IPv6 is fine.
ping to "s.taobao.com" is very good, for both IPv4 and IPv6.

Singtel 5Gbps, bridged ONR, native Singtel IPv6.

IPv4 address --> 115.66.xxx.xxx
IPv6 address --> 2400:d802:0dxx:xx00.xxxx.xxxx.xxxx.xxxx

Bash:

root@OpenWrt:~# ping -4 -c 4 cloudflare-dns.com
PING cloudflare-dns.com (104.16.248.249): 56 data bytes
64 bytes from 104.16.248.249: seq=0 ttl=39 time=153.164 ms
64 bytes from 104.16.248.249: seq=1 ttl=39 time=150.790 ms
64 bytes from 104.16.248.249: seq=2 ttl=39 time=151.118 ms
64 bytes from 104.16.248.249: seq=3 ttl=39 time=151.244 ms

--- cloudflare-dns.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 150.790/151.579/153.164 ms

root@OpenWrt:~# ping -6 -c 4 cloudflare-dns.com
PING cloudflare-dns.com (2606:4700::6810:f9f9): 56 data bytes
64 bytes from 2606:4700::6810:f9f9: seq=0 ttl=54 time=2.914 ms
64 bytes from 2606:4700::6810:f9f9: seq=1 ttl=54 time=3.141 ms
64 bytes from 2606:4700::6810:f9f9: seq=2 ttl=54 time=3.019 ms
64 bytes from 2606:4700::6810:f9f9: seq=3 ttl=54 time=3.328 ms

--- cloudflare-dns.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.914/3.100/3.328 ms

root@OpenWrt:~# ping -4 -c 4 dns.google
PING dns.google (8.8.4.4): 56 data bytes
64 bytes from 8.8.4.4: seq=0 ttl=117 time=2.402 ms
64 bytes from 8.8.4.4: seq=1 ttl=117 time=2.297 ms
64 bytes from 8.8.4.4: seq=2 ttl=117 time=1.878 ms
64 bytes from 8.8.4.4: seq=3 ttl=117 time=2.315 ms

--- dns.google ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.878/2.223/2.402 ms

root@OpenWrt:~# ping -6 -c 4 dns.google
PING dns.google (2001:4860:4860::8888): 56 data bytes
64 bytes from 2001:4860:4860::8888: seq=0 ttl=115 time=1.852 ms
64 bytes from 2001:4860:4860::8888: seq=1 ttl=115 time=1.917 ms
64 bytes from 2001:4860:4860::8888: seq=2 ttl=115 time=2.563 ms
64 bytes from 2001:4860:4860::8888: seq=3 ttl=115 time=2.036 ms

--- dns.google ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.852/2.092/2.563 ms

root@OpenWrt:~# ping -4 -c 4 s.taobao.com
PING s.taobao.com (59.82.120.242): 56 data bytes
64 bytes from 59.82.120.242: seq=0 ttl=83 time=97.016 ms
64 bytes from 59.82.120.242: seq=1 ttl=83 time=83.563 ms
64 bytes from 59.82.120.242: seq=2 ttl=83 time=82.881 ms
64 bytes from 59.82.120.242: seq=3 ttl=83 time=82.600 ms

--- s.taobao.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 82.600/86.515/97.016 ms

root@OpenWrt:~# ping -6 -c 4 s.taobao.com
PING s.taobao.com (2408:4001:f10::d3): 56 data bytes
64 bytes from 2408:4001:f10::d3: seq=0 ttl=85 time=87.690 ms
64 bytes from 2408:4001:f10::d3: seq=1 ttl=85 time=86.633 ms
64 bytes from 2408:4001:f10::d3: seq=2 ttl=85 time=86.161 ms
64 bytes from 2408:4001:f10::d3: seq=3 ttl=85 time=84.917 ms

--- s.taobao.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 84.917/86.350/87.690 ms

IPv4 to M1 SpeedTest server is back to normal. IPv6 to M1 SpeedTest server is still not as good as IPv4.

Bash:

root@OpenWrt:~# ping -4 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (103.1.138.214): 56 data bytes
64 bytes from 103.1.138.214: seq=0 ttl=53 time=3.583 ms
64 bytes from 103.1.138.214: seq=1 ttl=53 time=3.846 ms
64 bytes from 103.1.138.214: seq=2 ttl=53 time=3.868 ms
64 bytes from 103.1.138.214: seq=3 ttl=53 time=3.577 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.577/3.718/3.868 ms

root@OpenWrt:~# ping -6 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (2401:7400:8888:13::2): 56 data bytes
64 bytes from 2401:7400:8888:13::2: seq=0 ttl=51 time=35.991 ms
64 bytes from 2401:7400:8888:13::2: seq=1 ttl=51 time=36.320 ms
64 bytes from 2401:7400:8888:13::2: seq=2 ttl=51 time=36.016 ms
64 bytes from 2401:7400:8888:13::2: seq=3 ttl=51 time=36.420 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 35.991/36.186/36.420 ms

xiaofan · Aug 1, 2025

Singtel 5Gbps, bridged ONR, native Singtel IPv6.

IPv4 address --> 115.66.xxx.xxx
IPv6 address --> 2400:d802:0dxx:xx00.xxxx.xxxx.xxxx.xxxx

IPv6 to Quad 9 DNS is very bad. IPv4 is okay.

Bash:

root@OpenWrt:~# ping -4 -c 4 dns.quad9.net
PING dns.quad9.net (149.112.112.112): 56 data bytes
64 bytes from 149.112.112.112: seq=0 ttl=55 time=2.569 ms
64 bytes from 149.112.112.112: seq=1 ttl=55 time=2.328 ms
64 bytes from 149.112.112.112: seq=2 ttl=55 time=2.153 ms
64 bytes from 149.112.112.112: seq=3 ttl=55 time=2.475 ms

--- dns.quad9.net ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.153/2.381/2.569 ms

root@OpenWrt:~# ping -6 -c 4 dns.quad9.net
PING dns.quad9.net (2620:fe::9): 56 data bytes
64 bytes from 2620:fe::9: seq=0 ttl=50 time=183.346 ms
64 bytes from 2620:fe::9: seq=1 ttl=50 time=183.178 ms
64 bytes from 2620:fe::9: seq=2 ttl=50 time=183.162 ms
64 bytes from 2620:fe::9: seq=3 ttl=50 time=182.995 ms

--- dns.quad9.net ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 182.995/183.170/183.346 ms

xiaofan · Aug 1, 2025

Singtel 5Gbps, bridged ONR, native Singtel IPv6.

IPv4 address --> 115.66.xxx.xxx
IPv6 address --> 2400:d802:0dxx:xx00.xxxx.xxxx.xxxx.xxxx

IPv6 to ControlD DNS is not as good as IPv4.

Bash:

root@OpenWrt:~# ping -4 -c 4 dns.controld.com
PING dns.controld.com (76.76.2.22): 56 data bytes
64 bytes from 76.76.2.22: seq=0 ttl=51 time=2.761 ms
64 bytes from 76.76.2.22: seq=1 ttl=51 time=2.575 ms
64 bytes from 76.76.2.22: seq=2 ttl=51 time=2.748 ms
64 bytes from 76.76.2.22: seq=3 ttl=51 time=2.933 ms

--- dns.controld.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss

round-trip min/avg/max = 2.575/2.754/2.933 ms

root@OpenWrt:~# ping -6 -c 4 dns.controld.com
PING dns.controld.com (2606:1a40::22): 56 data bytes
64 bytes from 2606:1a40::22: seq=0 ttl=51 time=33.878 ms
64 bytes from 2606:1a40::22: seq=1 ttl=51 time=34.263 ms
64 bytes from 2606:1a40::22: seq=2 ttl=51 time=33.974 ms
64 bytes from 2606:1a40::22: seq=3 ttl=51 time=34.292 ms

--- dns.controld.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 33.878/34.101/34.292 ms

Qubicfactor · Aug 4, 2025

Dear ViewQwest Customers,

As part of our commitment to delivering innovative and future-ready connectivity solutions, we are excited to announce that IPv6 address space is now available for our customers! This upgrade aligns with our vision to provide safer, better, and faster internet to power your digital way of life.

To enable IPv6 for your connection, simply send a request to our team by emailing residential.support@viewqwest.com. Our dedicated support team will work promptly to activate IPv6 via DHCP for your account.

We are proud to bring you this advanced connectivity option, ensuring your home network is ready for the future of the internet.

Above info from VQ internal forums, just announced yesterday apparently. IPv6 support for VQ now officially launched rather than the previous soft launch. But still need to manually request.

Jirachi · Aug 6, 2025

How important is it to have IPv6 in today's context? I am with MyRepublic and is well known that they do not have it.

ieatcable · Aug 6, 2025

xiaofan said:

IPv6 ping to M1 SpeedTest server is much better than last time but still worse than IPv4.

But IPv4 is already not good as it goes through Hong Kong.

Bash:

root@OpenWrt:~# ping -4 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (103.1.138.214): 56 data bytes
64 bytes from 103.1.138.214: seq=0 ttl=53 time=38.677 ms
64 bytes from 103.1.138.214: seq=1 ttl=53 time=43.056 ms
64 bytes from 103.1.138.214: seq=2 ttl=53 time=40.334 ms
64 bytes from 103.1.138.214: seq=3 ttl=53 time=39.737 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 38.677/40.451/43.056 ms

root@OpenWrt:~# ping -6 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (2401:7400:8888:13::2): 56 data bytes
64 bytes from 2401:7400:8888:13::2: seq=0 ttl=51 time=74.539 ms
64 bytes from 2401:7400:8888:13::2: seq=1 ttl=51 time=74.246 ms
64 bytes from 2401:7400:8888:13::2: seq=2 ttl=51 time=74.319 ms
64 bytes from 2401:7400:8888:13::2: seq=3 ttl=51 time=74.449 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 74.246/74.388/74.539 ms

root@OpenWrt:~# mtr -4 m1speedtest1.m1net.com.sg
                                                 My traceroute  [v0.95]
OpenWrt (42.60.xxx.xxx) -> m1speedtest1.m1net.com.sg (103.1.138.214)                             2025-07-17T21:22:37+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. bb42-60-xx-254.singnet.com.sg                                             0.0%    65    1.4   1.6   1.1   7.1   0.9
 2. 165.21.193.22                                                             0.0%    65    3.1   3.8   2.6  13.4   2.1
 3. 165.21.193.21                                                             0.0%    65    2.1   4.6   1.9  44.6   8.6
 4. 165.21.138.245                                                            0.0%    65    2.2   3.5   1.8  26.2   4.4
 5. SN-SINQT1-BO403-ae1.singnet.com.sg                                        0.0%    65    2.1   1.9   1.5   2.2   0.2
 6. 203.208.177.213                                                           0.0%    65    2.2   2.5   1.7  10.8   1.5
 7. xn-lhrcl1-bo706.ix.singtel.com                                            0.0%    65    2.4   3.8   2.2  27.6   4.1
 8. 203.208.158.9                                                             0.0%    65    3.0   3.1   2.5   8.5   1.0
 9. 203.208.158.206                                                          74.6%    64    2.9   9.5   2.8  62.9  15.9
10. 203.208.151.122                                                           0.0%    64   38.3  38.3  37.2  56.8   2.5
11. 203.208.151.93                                                            0.0%    64   37.5  37.3  36.9  38.9   0.4
12. 203.208.178.17                                                            0.0%    64   38.7  39.3  38.3  79.1   5.1
13. ix-be-5.ecore1.hk2-hongkong.as6453.net                                    1.6%    64   38.6  38.5  38.0  39.2   0.2
14. if-bundle-9-2.qcore2.hk2-hongkong.as6453.net                             69.8%    64   73.7  74.2  73.6  74.9   0.3
15. if-bundle-32-2.qcore2.svw-singapore.as6453.net                           92.1%    64   72.7  72.4  72.2  72.7   0.2
16. if-bundle-19-2.qcore1.esin4-singapore.as6453.net                         87.3%    64   72.0  71.7  71.2  72.1   0.3
17. if-be-20-2.ecore1.svq-singapore.as6453.net                                1.6%    64   70.9  75.9  69.8 313.4  31.1
18. if-ae-40-2.thar1.svq-singapore.as6453.net                                 0.0%    64   75.5  74.6  73.9  86.7   1.7
19. 120.29.215.162                                                            0.0%    64   37.9  38.6  37.5  48.6   2.0
20. 220.246.65.202.unknown.m1.com.sg                                          0.0%    64   38.4  38.7  38.0  47.4   1.3
21. 214.138.1.103.unknown.m1.com.sg                                           0.0%    64   38.5  38.8  38.2  42.5   0.8

root@OpenWrt:~# mtr -6 m1speedtest1.m1net.com.sg
                                                 My traceroute  [v0.95]
OpenWrt (2400:d802:0dxx::xx:xxxx) -> m1speedtest1.m1net.com.sg (2401:7400:8888:13::2)             2025-07-17T21:20:18+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2400:d801:4001:611::                                                      0.0%    91    1.5   1.5   1.1   2.4   0.2
 2. 2001:c20:3c00::6                                                          0.0%    91    3.3   4.3   2.8  22.0   2.9
 3. 2001:c20:3c00::7                                                          0.0%    91    2.5   4.0   1.9  38.3   5.3
 4. 2001:c20:0:3::35                                                          0.0%    91    2.1   7.5   1.8  81.1  14.9
 5. 2001:c20:0:3::a                                                           0.0%    91    2.3   2.1   1.7   2.5   0.2
 6. 2001:c10:80:2::a21                                                        0.0%    91    2.4   3.4   1.8  42.0   4.9
 7. 2001:c10:80:2::915                                                        0.0%    91    3.0   5.3   2.1  67.4   8.3
 8. 2001:c10:80:1::ee5                                                        0.0%    91   41.6  43.4  41.5  75.1   4.9
 9. (waiting for reply)
10. (waiting for reply)
11. (waiting for reply)
12. (waiting for reply)
13. 2401:7400:0:2::                                                           0.0%    90   72.0  73.2  71.9  85.7   2.3
14. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    90   74.1  74.3  73.9  74.8   0.2

xiaofan said:

IPv4 to M1 SpeedTest server is back to normal. IPv6 to M1 SpeedTest server is still not as good as IPv4.

Bash:

root@OpenWrt:~# ping -4 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (103.1.138.214): 56 data bytes
64 bytes from 103.1.138.214: seq=0 ttl=53 time=3.583 ms
64 bytes from 103.1.138.214: seq=1 ttl=53 time=3.846 ms
64 bytes from 103.1.138.214: seq=2 ttl=53 time=3.868 ms
64 bytes from 103.1.138.214: seq=3 ttl=53 time=3.577 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.577/3.718/3.868 ms

root@OpenWrt:~# ping -6 -c 4 m1speedtest1.m1net.com.sg
PING m1speedtest1.m1net.com.sg (2401:7400:8888:13::2): 56 data bytes
64 bytes from 2401:7400:8888:13::2: seq=0 ttl=51 time=35.991 ms
64 bytes from 2401:7400:8888:13::2: seq=1 ttl=51 time=36.320 ms
64 bytes from 2401:7400:8888:13::2: seq=2 ttl=51 time=36.016 ms
64 bytes from 2401:7400:8888:13::2: seq=3 ttl=51 time=36.420 ms

--- m1speedtest1.m1net.com.sg ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 35.991/36.186/36.420 ms

I know I am going offtopic in IPv6 thread but since you mention ST to M1 ping I just want to supplement it with my uptime kuma monitor from M1 to ST IPv4 :lick:

History:
From 2023 up till Jan 2025, M1 was a customer of ST (AS7473)'s IP transit services, meaning M1 can connect with ST directly and vice versa.

After Jan 2025, M1 cut off from ST. M1 <-> ST was routing via HK so latency was 60-70ms.
A moment after that, M1 rerouted ST bound traffic via SH IP transit which could connect to ST directly. However, ST still stubbornly routed M1 bound traffic via HK. This made the latency 35-45ms.

On 1 Aug 2025, ST finally routes the traffic locally to RETN, reaching M1 more directly.

Code:

2 192.168.1.254 0.976ms 0.721ms 0.713ms 
3 115.66.107.254 2.73ms 2.756ms 2.652ms 
4 * 165.21.193.234 3.074ms * 
5 165.21.193.233 2.493ms 2.448ms 2.825ms 
6 165.21.139.169 3.27ms 3.747ms 2.593ms 
7 165.21.139.134 2.776ms 2.792ms 2.144ms 
8 203.208.143.129 2.705ms 2.522ms 2.789ms 
9 203.208.158.205 12.674ms 14.077ms 5.444ms 
10 ae7-1747.rt.eqx.sin.sg.retn.net (87.245.230.9) 3.596ms 3.741ms 3.865ms 
11 * * * 
12 138.245.65.202.unknown.m1.com.sg (202.65.245.138) 4.403ms 4.075ms 4.179ms 
13 202.246.65.202.unknown.m1.com.sg (202.65.246.202) 5.798ms 4.985ms 4.975ms 
14 138.75.x.x 3.747ms 4.331ms 4.233ms

bert64 · Aug 8, 2025

Jirachi said:
How important is it to have IPv6 in today's context? I am with MyRepublic and is well known that they do not have it.

There are hundreds of thousands of IPv6-only sites and other resources online, you won't be able to reach them:
https://www.ev6.net/v6sites.php

What's worse is you will get a generic error, so unless you look into it and have appropriate knowledge you will not realise *why* a site failed to load. You may have hit upon v6-only sites already and falsely assumed they were down, or that they were being censored.

Many networks are IPv6-first, including Microsoft, Google, Facebook etc - legacy ip is retained for backwards compatibility, but is second class and not their main focus:
https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/
https://www.internetsociety.org/res...book-moving-to-an-ipv6-only-internal-network/

Several governments including USA, China, India etc are heavily pushing the move to IPv6, and to drop legacy IP.

A lot of ISPS, including MR/VQ and all mobile operators are now using CGNAT, and in some countries there is little alternative to it. Many users in China and Thailand for instance are only able to self-host or participate in p2p networks over v6. You can see a lot of home NAS appliances in such countries which are online v6-only.

Even in SG, if you want to properly use p2p or self-host on a consumer mobile data service, you have to use v6.

Many hosting providers charge extra for legacy IP including major ones like AWS, if you are renting servers for your own use and you need to access them from a legacy network you will be paying extra.

IPv6 discussions

Senior Member

Senior Member

Junior Member

Member

Senior Member

Senior Member

Junior Member

Senior Member

Junior Member

High Supremacy Member

High Supremacy Member

High Supremacy Member

Member

High Supremacy Member

High Supremacy Member

High Supremacy Member

Supremacy Member

Great Supremacy Member

Junior Member

Senior Member