IPv6 discussions

[bert64]

my ping to cloud flare still 30-40ms. With no real solid evidence (just my own ep, It feels like Singtel has different routing for each of their different public IPs for whatever reason. Own (admitedly not scientific or controlled) exp was that I used to have lower ms pings to cloud flare, but ever since I got a new IP its mbeen 30-40ms and routing to certian Local game server (namely Apex Legends SG server) has been severely affected. (talking about 200ms ping or ping spikes randomly up to 200ms)

All of their public addresses are announced via the same AS#, but because the legacy BGP table is so bloated and messy you can get corner cases where routing is different - especially if the announced prefixes are different sizes. Some of the peers may filter smaller prefixes, or drop excess numbers of prefixes etc - which will then cause the traffic to take a different route.

Also take a look at the prefixes section of https://bgp.he.net/AS9506:
https://bgp.he.net/AS9506

You'll see they have multiple overlapping announcements, where some of the more specific announcements have low visibility. Also a lot of their v6 announcements have invalid RPKI. All of this will cause some peers (but not all) to reject the invalid routes, causing traffic to those destinations to reroute via peers that don't reject it - which may be slower. You may find you have an address which falls into one of these low visibility routes.
Or it could be the other way round where the low visibility routes are intentional to enable peering with specific destinations.

For v6 there is an overall /30 route which covers everything, so peers can aggregate to just this and ignore all the others.

 

[xiaofan]

From here.
https://forums.hardwarezone.com.sg/threads/singtel-1-gbps-fibre.5930834/page-237#post-152925115

https://stats.labs.apnic.net/ipv6/AS9506?c=SG&p=1&v=1&w=30&x=1

If we look at AS9506's IPv6 deployment stats, IPv6 capable and preferred percentage is still very low, which is highly unlikely if the deployment is almost done.

I'd expect at least 40-50% if there's some form of widespread deployment.

It is quite interesting to see low IPv6 adoption from NUS and NTU. NTU is at 0%...

 

[hwzlite]

In the case of high latency like this, the happy eyeballs algorithm would automatically downgrade to legacy ip.

Happy Eyeballs algorithm is another interesting topic.
Great insight on IPv6, the DNS and Happy Eyeballs and video from the same author :

 

[yjwong]

I just signed SingTel 5 Gbps Enhanced plan recently. The sales person checked in with their superiors on whether IPv6 was available, and the answer was yes and needs to be enabled on an account-by-account basis.

Fast forward, now that everything's gotten installed, I made a request to enable IPv6. The CSOs did understand my request on first try, and they sent someone down to my house, who also seemed to understand IPv6 but was curious as to why I needed it. Unfortunately, the field technician didn't succeed at enabling it after a few phone calls to their backend team.

I had initially placed the ONR in bridged mode, which the technician suspected to be the issue. But I'm quite sure it wasn't, since it's the same router that I used for M1, which had native IPv6 since quite a while back). After a couple of back and forth, we decided to revert the ONR back to default configuration, but IPv6 also didn't work.

The technician promised to file an internal ticket and I was then asked to check back in 2 weeks' time. Will see how things go...

Seems like it's still quite early days for SingTel IPv6.

 

[xiaofan]

I just signed SingTel 5 Gbps Enhanced plan recently. The sales person checked in with their superiors on whether IPv6 was available, and the answer was yes and needs to be enabled on an account-by-account basis.
Fast forward, now that everything's gotten installed, I made a request to enable IPv6. The CSOs did understand my request on first try, and they sent someone down to my house, who also seemed to understand IPv6 but was curious as to why I needed it. Unfortunately, the field technician didn't succeed at enabling it after a few phone calls to their backend team.
I had initially placed the ONR in bridged mode, which the technician suspected to be the issue. But I'm quite sure it wasn't, since it's the same router that I used for M1, which had native IPv6 since quite a while back). After a couple of back and forth, we decided to revert the ONR back to default configuration, but IPv6 also didn't work.
The technician promised to file an internal ticket and I was then asked to check back in 2 weeks' time. Will see how things go...
Seems like it's still quite early days for SingTel IPv6.

Thanks a lot for the updates.

Now we know why the IPv6 adoption rate of SingTel is still so low, since it is not enabled by default, at least for the ONR users.

Moreover, from the reports in the SingTel 1Gbps thread, the native IPv6 deployment project does not seem to be completed yet.

 

[tuapuikia]

I been using singtel 6rd for a months now. So far the peering network performed better than 3 year ago. I'm using openwrt with GUA in local LAN. No plan to go back to Nat era with NAT66.

Sites is loaded faster for Google services and YouTube. Will update here if Singtel block my peering IP again.

 

[xiaofan]

I been using singtel 6rd for a months now. So far the peering network performed better than 3 year ago. I'm using openwrt with GUA in local LAN. No plan to go back to Nat era with NAT66.

Sites is loaded faster for Google services and YouTube. Will update here if Singtel block my peering IP again.

Have you tried native IPv6 (DHCPv6) to see if that work for you? Thanks.

 

[tuapuikia]

Have you tried native IPv6 (DHCPv6) to see if that work for you? Thanks.

I tried, the port is not receiving IP from dhcpv6. Maybe I needs to call CS to enable it.

 

[tuapuikia]

I'm quite impressed with the Singtel 6rd tunnel. It has really improved a lot compared to a few years ago when I tested it. This is an iperf3 test against the OVH server with a 1Gbps link, with SQM capped at 880Mbps to prevent bufferbloat.


ipv4 upload

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 117 MBytes 97.8 Mbits/sec 8 sender
[ 5] 0.00-10.03 sec 114 MBytes 95.6 Mbits/sec receiver
[ 7] 0.00-10.00 sec 104 MBytes 87.3 Mbits/sec 8 sender
[ 7] 0.00-10.03 sec 102 MBytes 85.3 Mbits/sec receiver
[ 9] 0.00-10.00 sec 106 MBytes 88.7 Mbits/sec 7 sender
[ 9] 0.00-10.03 sec 104 MBytes 86.6 Mbits/sec receiver
[ 11] 0.00-10.00 sec 103 MBytes 86.4 Mbits/sec 7 sender
[ 11] 0.00-10.03 sec 101 MBytes 84.4 Mbits/sec receiver
[ 13] 0.00-10.00 sec 129 MBytes 108 Mbits/sec 8 sender
[ 13] 0.00-10.03 sec 126 MBytes 106 Mbits/sec receiver
[ 15] 0.00-10.00 sec 182 MBytes 153 Mbits/sec 17 sender
[ 15] 0.00-10.03 sec 180 MBytes 150 Mbits/sec receiver
[ 17] 0.00-10.00 sec 112 MBytes 94.1 Mbits/sec 8 sender
[ 17] 0.00-10.03 sec 110 MBytes 91.9 Mbits/sec receiver
[ 19] 0.00-10.00 sec 125 MBytes 105 Mbits/sec 7 sender
[ 19] 0.00-10.03 sec 122 MBytes 102 Mbits/sec receiver
[SUM] 0.00-10.00 sec 977 MBytes 820 Mbits/sec 70 sender
[SUM] 0.00-10.03 sec 960 MBytes 802 Mbits/sec receiver

iperf Done.
---
ipv4 download

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 139 MBytes 116 Mbits/sec 25 sender
[ 5] 0.00-10.00 sec 136 MBytes 114 Mbits/sec receiver
[ 7] 0.00-10.04 sec 124 MBytes 104 Mbits/sec 18 sender
[ 7] 0.00-10.00 sec 121 MBytes 102 Mbits/sec receiver
[ 9] 0.00-10.04 sec 106 MBytes 88.5 Mbits/sec 15 sender
[ 9] 0.00-10.00 sec 103 MBytes 86.7 Mbits/sec receiver
[ 11] 0.00-10.04 sec 109 MBytes 91.4 Mbits/sec 15 sender
[ 11] 0.00-10.00 sec 107 MBytes 89.5 Mbits/sec receiver
[ 13] 0.00-10.04 sec 112 MBytes 93.6 Mbits/sec 15 sender
[ 13] 0.00-10.00 sec 109 MBytes 91.8 Mbits/sec receiver
[ 15] 0.00-10.04 sec 125 MBytes 104 Mbits/sec 17 sender
[ 15] 0.00-10.00 sec 122 MBytes 103 Mbits/sec receiver
[ 17] 0.00-10.04 sec 121 MBytes 101 Mbits/sec 12 sender
[ 17] 0.00-10.00 sec 119 MBytes 99.7 Mbits/sec receiver
[ 19] 0.00-10.04 sec 125 MBytes 104 Mbits/sec 16 sender
[ 19] 0.00-10.00 sec 122 MBytes 103 Mbits/sec receiver
[SUM] 0.00-10.04 sec 962 MBytes 803 Mbits/sec 133 sender
[SUM] 0.00-10.00 sec 941 MBytes 789 Mbits/sec receiver

iperf Done.

---
ipv6 upload
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 86.4 MBytes 72.5 Mbits/sec 53 sender
[ 5] 0.00-10.08 sec 84.3 MBytes 70.2 Mbits/sec receiver
[ 7] 0.00-10.00 sec 56.0 MBytes 47.0 Mbits/sec 24 sender
[ 7] 0.00-10.08 sec 54.9 MBytes 45.7 Mbits/sec receiver
[ 9] 0.00-10.00 sec 40.1 MBytes 33.6 Mbits/sec 7 sender
[ 9] 0.00-10.08 sec 39.3 MBytes 32.7 Mbits/sec receiver
[ 11] 0.00-10.00 sec 59.6 MBytes 50.0 Mbits/sec 51 sender
[ 11] 0.00-10.08 sec 57.4 MBytes 47.8 Mbits/sec receiver
[ 13] 0.00-10.00 sec 64.1 MBytes 53.8 Mbits/sec 26 sender
[ 13] 0.00-10.08 sec 61.9 MBytes 51.5 Mbits/sec receiver
[ 15] 0.00-10.00 sec 67.8 MBytes 56.9 Mbits/sec 30 sender
[ 15] 0.00-10.08 sec 65.6 MBytes 54.6 Mbits/sec receiver
[ 17] 0.00-10.00 sec 66.1 MBytes 55.4 Mbits/sec 40 sender
[ 17] 0.00-10.08 sec 63.9 MBytes 53.2 Mbits/sec receiver
[ 19] 0.00-10.00 sec 80.1 MBytes 67.2 Mbits/sec 78 sender
[ 19] 0.00-10.08 sec 77.8 MBytes 64.7 Mbits/sec receiver
[SUM] 0.00-10.00 sec 520 MBytes 436 Mbits/sec 309 sender
[SUM] 0.00-10.08 sec 505 MBytes 420 Mbits/sec receiver

iperf Done.
---

ipv6 download
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 95.0 MBytes 79.4 Mbits/sec 50 sender
[ 5] 0.00-10.00 sec 92.4 MBytes 77.6 Mbits/sec receiver
[ 7] 0.00-10.04 sec 67.5 MBytes 56.4 Mbits/sec 31 sender
[ 7] 0.00-10.00 sec 65.0 MBytes 54.5 Mbits/sec receiver
[ 9] 0.00-10.04 sec 144 MBytes 120 Mbits/sec 56 sender
[ 9] 0.00-10.00 sec 141 MBytes 118 Mbits/sec receiver
[ 11] 0.00-10.04 sec 163 MBytes 137 Mbits/sec 72 sender
[ 11] 0.00-10.00 sec 161 MBytes 135 Mbits/sec receiver
[ 13] 0.00-10.04 sec 49.3 MBytes 41.2 Mbits/sec 54 sender
[ 13] 0.00-10.00 sec 47.4 MBytes 39.8 Mbits/sec receiver
[ 15] 0.00-10.04 sec 50.6 MBytes 42.3 Mbits/sec 28 sender
[ 15] 0.00-10.00 sec 48.7 MBytes 40.8 Mbits/sec receiver
[ 17] 0.00-10.04 sec 55.4 MBytes 46.3 Mbits/sec 37 sender
[ 17] 0.00-10.00 sec 53.6 MBytes 45.0 Mbits/sec receiver
[ 19] 0.00-10.04 sec 138 MBytes 116 Mbits/sec 44 sender
[ 19] 0.00-10.00 sec 136 MBytes 114 Mbits/sec receiver
[SUM] 0.00-10.04 sec 763 MBytes 638 Mbits/sec 372 sender
[SUM] 0.00-10.00 sec 745 MBytes 625 Mbits/sec receiver

iperf Done.


Upload
ipv4 - 802 Mbits/sec
ipv6 - 420 Mbits/sec (-52%)


Download
ipv4 - 789 Mbits/sec
ipv6 - 625 Mbits/sec (-21%)

 

[yjwong]

Fast forward, after a whole bunch of calls and 2 field engineer visits later, today SingTel finally enabled native IPv6 for my account.

However, it was quite short lived - while I was trying to enable port forwarding/DMZ, I forgot my password and had to reset the router. Upon reset, native IPv6 was gone.

This was quite interesting, because it suggests that it isn't just something at the account level, but something to do with the configuration on the F8648P itself. It might be some kind of configuration push to the ONR?

I'm not sure, will contact SingTel again and see how this goes.

That said, now that M1 has 2.5 Gbps, kind of regret signing up. M1 was much more hassle free in both having bridge mode + native IPv6.

 

[xiaofan]

Fast forward, after a whole bunch of calls and 2 field engineer visits later, today SingTel finally enabled native IPv6 for my account.

However, it was quite short lived - while I was trying to enable port forwarding/DMZ, I forgot my password and had to reset the router. Upon reset, native IPv6 was gone.

This was quite interesting, because it suggests that it isn't just something at the account level, but something to do with the configuration on the F8648P itself. It might be some kind of configuration push to the ONR?

I'm not sure, will contact SingTel again and see how this goes.

That said, now that M1 has 2.5 Gbps, kind of regret signing up. M1 was much more hassle free in both having bridge mode + native IPv6.

Thanks for the info.

Your experiences match the one from @probablye in the following thread. He is probably the first one to get ZTE F8648P to work with Singtel Native IPv6 and you are the second one.
https://forums.hardwarezone.com.sg/threads/singtel-5gbps-ipv6.7053976/

Apparently the backend needs to push some configuration to the ZTE F8648P ONR.

Unfortunately M1 announced 2.5Gbps too late and I took risk to go with Singtel 5Gbps and the installation was done yesterday. Anyway, I will take this as a challenge.

Right now I use Double NAT setup and configure my OpenWRT router (behind F8648P ONR) to use 6rd IPv6.

BTW, are you bridging the ONR or keep the ONR unbridged? Previously it was easy to bridge the ZTE F8648P ONR but now it seems to be problematic.
https://forums.hardwarezone.com.sg/...zte-f8648p-superadmin-password.6946718/page-6

 

[xiaofan]

Lost my access to Singtel native IPv6 after upgrading to Singtel 5Gbps plan -- now using Singtel issued ZTE F8648P XGS-PON ONR and then my Asus RT-AX86U router and virtual OpenWRT router behind the Singtel ONR (Double NAT).

Singtel 6rd IPv6 is still working though once I set it up on the virtual OpenWRT router.

BTW, Singtel connection to Cloudflare is still good now, either on IPv4 or 6rd IPv6.

PS C:\work\speedtest> ping 1.1.1.3

Pinging 1.1.1.3 with 32 bytes of data:
Reply from 1.1.1.3: bytes=32 time=5ms TTL=50
Reply from 1.1.1.3: bytes=32 time=6ms TTL=50
Reply from 1.1.1.3: bytes=32 time=7ms TTL=50
Reply from 1.1.1.3: bytes=32 time=7ms TTL=50

Ping statistics for 1.1.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 7ms, Average = 6ms
PS C:\work\speedtest> ping 2606:4700:4700::1113

Pinging 2606:4700:4700::1113 with 32 bytes of data:
Reply from 2606:4700:4700::1113: time=6ms
Reply from 2606:4700:4700::1113: time=8ms
Reply from 2606:4700:4700::1113: time=6ms
Reply from 2606:4700:4700::1113: time=5ms

Ping statistics for 2606:4700:4700::1113:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 8ms, Average = 6ms

 

[xiaofan]

Lost my access to Singtel native IPv6 after upgrading to Singtel 5Gbps plan -- now using Singtel issued ZTE F8648P XGS-PON ONR and then my Asus RT-AX86U router and virtual OpenWRT router behind the Singtel ONR (Double NAT).

Singtel 6rd IPv6 is still working though once I set it up on the virtual OpenWRT router.

BTW, Singtel connection to Cloudflare is still good now, either on IPv4 or 6rd IPv6.

But IPv6 is still bad when it comes to ControlD Family DNS. IPv4 is good.

PS C:\work\speedtest> ping family.freedns.controld.com

Pinging family.freedns.controld.com [2606:1a40::11] with 32 bytes of data:
Reply from 2606:1a40::11: time=195ms
Reply from 2606:1a40::11: time=202ms
Reply from 2606:1a40::11: time=180ms
Reply from 2606:1a40::11: time=192ms

Ping statistics for 2606:1a40::11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 180ms, Maximum = 202ms, Average = 192ms

PS C:\work\speedtest> ping -4 family.freedns.controld.com

Pinging family.freedns.controld.com [76.76.2.11] with 32 bytes of data:
Reply from 76.76.2.11: bytes=32 time=5ms TTL=49
Reply from 76.76.2.11: bytes=32 time=7ms TTL=49
Reply from 76.76.2.11: bytes=32 time=6ms TTL=49
Reply from 76.76.2.11: bytes=32 time=7ms TTL=49

Ping statistics for 76.76.2.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 7ms, Average = 6ms

 

[yjwong]

After re-bridging,

Thanks for the info.

Your experiences match the one from @probablye in the following thread. He is probably the first one to get ZTE F8648P to work with Singtel Native IPv6 and you are the second one.
https://forums.hardwarezone.com.sg/threads/singtel-5gbps-ipv6.7053976/

Apparently the backend needs to push some configuration to the ZTE F8648P ONR.

Unfortunately M1 announced 2.5Gbps too late and I took risk to go with Singtel 5Gbps and the installation was done yesterday. Anyway, I will take this as a challenge.

Right now I use Double NAT setup and configure my OpenWRT router (behind F8648P ONR) to use 6rd IPv6.

BTW, are you bridging the ONR or keep the ONR unbridged? Previously it was easy to bridge the ZTE F8648P ONR but now it seems to be problematic.
https://forums.hardwarezone.com.sg/...zte-f8648p-superadmin-password.6946718/page-6

I'm currently leaving it unbridged. However, I did try to bridge with OPNsense, no luck getting an address via DHCPv6 either (after the first time successfully getting it). So reverted to unbridged.

Am starting to think it could be some DHCPv6 params (DUID?) that SingTel is specifically looking for. In your previous configuration that worked, did you manage to figure anything special about the way they were sending DHCPv6 IA_PD/IA_NA messages?

 

[xiaofan]

After re-bridging,

I'm currently leaving it unbridged. However, I did try to bridge with OPNsense, no luck getting an address via DHCPv6 either (after the first time successfully getting it). So reverted to unbridged.

Am starting to think it could be some DHCPv6 params (DUID?) that SingTel is specifically looking for. In your previous configuration that worked, did you manage to figure anything special about the way they were sending DHCPv6 IA_PD/IA_NA messages?

No, nothing special when I was using ONT.

I was installing a new OpenWRT VM and found out Singtel native IPv6 worked initially. Then I could also get Asus RT-AX86U to work. But no matter what I did (including changing the DUID as per the advise from bert64), I could not get pfSense to work (okay, it sort of worked once).

However, later pfSense magically worked this year (since 31 May 2024) and it worked well. I tend to think Singtel fixed some IPv6 issues in the backend.

Now I am back to 6rd with the new ZTE F8648P ONR (unbridged as of now).

 

[xiaofan]

New findings: I can get multiple /64 IPv6 subnets if I use multiple virtual OpenWRT routers and configure 6rd on OpenWRT.

Now I use two virtual OpenWRT routers behind Singtel ZTE F8648P ONR (Double NAT) and I can get two /64 IPv6 subnets.

Edit: no, somehow the second one cannot access internet...

 

[xiaofan]

Please refer to the updates on VQ and SIMBA in Post #3 by @Mach3.2.
https://forums.hardwarezone.com.sg/threads/ipv6-discussions.6976522/#post-150380870

 

[xiaofan]

Interesting, now Singtel 6rd IPv6 and IPv4 both have its better point.

Using wireless and Double NAT so adding a few ms compared to running directly from OpenWRT (behind Singtel ZTE F8648P XGS-PON ONR).

Google DNS -- same
Cloudflare DNS -- Singtel 6rd IPv6 is better
ControldD DNS -- Singtel IPv6 is better.

PS C:\work\speedtest> ping -4 one.one.one.one

Pinging one.one.one.one [1.1.1.1] with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=37ms TTL=49
Reply from 1.1.1.1: bytes=32 time=39ms TTL=49
Reply from 1.1.1.1: bytes=32 time=40ms TTL=49
Reply from 1.1.1.1: bytes=32 time=39ms TTL=49

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 40ms, Average = 38ms
PS C:\work\speedtest> ping -6 one.one.one.one

Pinging one.one.one.one [2606:4700:4700::1111] with 32 bytes of data:
Reply from 2606:4700:4700::1111: time=9ms
Reply from 2606:4700:4700::1111: time=6ms
Reply from 2606:4700:4700::1111: time=6ms
Reply from 2606:4700:4700::1111: time=6ms

Ping statistics for 2606:4700:4700::1111:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 9ms, Average = 6ms
PS C:\work\speedtest> ping -4 dns.google.com

Pinging dns.google.com [8.8.4.4] with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=6ms TTL=112
Reply from 8.8.4.4: bytes=32 time=10ms TTL=112
Reply from 8.8.4.4: bytes=32 time=7ms TTL=112
Reply from 8.8.4.4: bytes=32 time=7ms TTL=112

Ping statistics for 8.8.4.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 10ms, Average = 7ms
PS C:\work\speedtest> ping -6 dns.google.com

Pinging dns.google.com [2001:4860:4860::8844] with 32 bytes of data:
Reply from 2001:4860:4860::8844: time=7ms
Reply from 2001:4860:4860::8844: time=8ms
Reply from 2001:4860:4860::8844: time=7ms
Reply from 2001:4860:4860::8844: time=8ms

Ping statistics for 2001:4860:4860::8844:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 8ms, Average = 7ms
PS C:\work\speedtest> ping -4 family.freedns.controld.com

Pinging family.freedns.controld.com [76.76.2.11] with 32 bytes of data:
Reply from 76.76.2.11: bytes=32 time=4ms TTL=48
Reply from 76.76.2.11: bytes=32 time=6ms TTL=48
Reply from 76.76.2.11: bytes=32 time=6ms TTL=48
Reply from 76.76.2.11: bytes=32 time=5ms TTL=48

Ping statistics for 76.76.2.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 6ms, Average = 5ms
PS C:\work\speedtest> ping -6 family.freedns.controld.com

Pinging family.freedns.controld.com [2606:1a40::11] with 32 bytes of data:
Reply from 2606:1a40::11: time=40ms
Reply from 2606:1a40::11: time=43ms
Reply from 2606:1a40::11: time=43ms
Reply from 2606:1a40::11: time=42ms

Ping statistics for 2606:1a40::11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 43ms, Average = 42ms
PS C:\work\speedtest> ping -4 family.freedns.controld.com

Pinging family.freedns.controld.com [76.76.2.11] with 32 bytes of data:
Reply from 76.76.2.11: bytes=32 time=5ms TTL=48
Reply from 76.76.2.11: bytes=32 time=7ms TTL=48
Reply from 76.76.2.11: bytes=32 time=8ms TTL=48
Reply from 76.76.2.11: bytes=32 time=7ms TTL=48

Ping statistics for 76.76.2.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 8ms, Average = 6ms

 

[xiaofan]

Singtel IPv6 routing issue to M1 still exists (high latency).

Using wireless, Xiaomi BE5000 AP, CH60, 160MHz channel bandwidth, Acer Windows 11 laptop 2021 model, Intel AX200 wireless adapter.

PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 7311

   Speedtest by Ookla

      Server: M1 Limited - Singapore (id: 7311)
         ISP: Singtel Fibre
Idle Latency:   214.67 ms   (jitter: 23.50ms, low: 212.74ms, high: 260.96ms)
    Download:   232.93 Mbps (data used: 286.2 MB)
                390.17 ms   (jitter: 83.77ms, low: 217.89ms, high: 1434.77ms)
      Upload:   184.30 Mbps (data used: 314.9 MB)
                344.99 ms   (jitter: 80.30ms, low: 216.92ms, high: 950.22ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/f5d00558-1b4e-484f-bce0-529a786a1283

PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 4235

   Speedtest by Ookla

      Server: StarHub Ltd - Singapore (id: 4235)
         ISP: Singtel Fibre
Idle Latency:     4.87 ms   (jitter: 0.34ms, low: 4.34ms, high: 4.95ms)
    Download:   608.38 Mbps (data used: 1.2 GB)
                 13.36 ms   (jitter: 17.14ms, low: 5.31ms, high: 253.45ms)
      Upload:  1006.74 Mbps (data used: 1.4 GB)
                104.14 ms   (jitter: 33.31ms, low: 4.84ms, high: 374.64ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/f95b5ef0-2df0-4ef8-9f64-5f399217cbc0

PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.77 ms   (jitter: 0.41ms, low: 3.63ms, high: 4.26ms)
    Download:  1098.35 Mbps (data used: 1.5 GB)
                 17.73 ms   (jitter: 17.98ms, low: 4.64ms, high: 103.81ms)
      Upload:   971.32 Mbps (data used: 1.7 GB)
                 32.72 ms   (jitter: 21.77ms, low: 4.90ms, high: 290.45ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/9a92c61a-8aa1-4f13-a4b6-1e6e9a9ba61c

 

[xiaofan]

First day with Singtel SIM Only new contract. cycle (with 12 months free 5G access, previous contract only first 3 months free 5G access)

SingTel 5G NSA/SA: CGNAT for IPv4

Looks can get IPv6 now.

Tested with my Xiaomi Poco X4 GT Android phone. With Chrome browser.

Updates:
1) 5G SA : consistent IPv6
2) 5G NSA : inconsistent IPv6
3) Cannot get IPv6 to work with Termux terminal simulator.