Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

Unifi Official TM UniFi High Speed Broadband Thread V41, READ 1ST PAGE FOR RELEVANT WIFI INFO

views
     
kwss
post Nov 6 2023, 10:24 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
Anybody notice their ping during speedtest has also gotten an upgrade?
Before the upgrade announcement, I got 2-3ms, 4ms worst case.
Now it is like 8-9ms, 11ms worst case.
I am talking about the idle ping in speedtest.

Wondering if it is just my area or someone else is also seeing this
kwss
post Nov 6 2023, 10:27 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(jiaen0509 @ Nov 6 2023, 10:08 PM)
So right now still tiada ahli2 yang berhormat got upgrade from 800mbps right?
*
I had a friend who got upgraded by calling 100.

TM offered him:

Upgrade to 1Gbps for the same price.
-or-
2Gbps for the same price but he has to remove IPTV.

He picked 2Gbps. But he is also paying RM299 a month for 800Mbps + Ruby Pack.
kwss
post Nov 27 2023, 04:08 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 26 2023, 05:17 PM)
I guess some ISP is special?
Unsure, can be their tech setup it wrongly? hmm.gif
Based on this thread, UniFi
https://forum.lowyat.net/topic/5073652/+100

I think If you feel slow down, then try disable IPv6 la, but the issues is mostly caused by the throttling of UniFi on SG, like the rerouting of HK to SG CloudFlare now.... doh.gif  doh.gif
---
For your info, I performed testing on www.lazada.com.my with IPv4 and IPv6 of Google DNS and CloudFlare DNS.
Here is the result.

2606:4700:4700::1111, MY
2606:4700:4700::1001, MY
1.1.1.1, SG Akamai for IPv4/IPv6
1.0.0.1, SG Akamai for IPv4/IPv6

2001:4860:4860::8888, MY
2001:4860:4860::8844, MY
8.8.8.8, MY for both
8.8.4.4, MY for both

This is why I prefer Google DNS, lol.

For the extra, both IPv6 DNS got reaching issues for Public Bank's DNS server, lol.
https://www2.pbebank.com/

Yes, there is 10s timeout for public bank.(old is 30s)
This might be caused by the caching time TTL is 30s, but strange that if I check via Android network tools, it is fine.... hmm.gif
---
More testing on PBe, it works well also on DNS over HTTPS, both IPv4/IPv6, so... hmm.gif
Seem like only happen on DNS over UDP for IPv6 la.
*
You are misdiagnosing the issue. It has nothing to do with DNS or IPv6.

lowyat.net:
CODE

$ dig +short lowyat.net a lowyat.net aaaa @1.1.1.1
104.26.7.73
172.67.74.89
104.26.6.73
2606:4700:20::ac43:4a59
2606:4700:20::681a:749
2606:4700:20::681a:649

$ dig +short lowyat.net a lowyat.net aaaa @8.8.8.8
172.67.74.89
104.26.7.73
104.26.6.73
2606:4700:20::681a:649
2606:4700:20::681a:749
2606:4700:20::ac43:4a59


lazada.com.my:
CODE

$ dig +short lazada.com.my a lazada.com.my aaaa @1.1.1.1
47.246.167.7
47.246.165.39
47.246.165.72
47.246.165.182
47.246.165.115
47.246.167.210
47.246.167.252
47.246.167.254

$ dig +short lazada.com.my a lazada.com.my aaaa @8.8.8.8
47.246.167.7
47.246.165.39
47.246.165.72
47.246.165.182
47.246.165.115
47.246.167.210
47.246.167.252
47.246.167.254


As you can clearly see, both Cloudflare DNS and Google DNS return the same result. So changing what DNS server you use doesn't affect the result one bit.

For lowyat.net, all IPv4 go to HK directly. all IPv6 go to SG directly.
lowyat.net uses Cloudflare DNS as their authoritative DNS and also CDN.
Simply using IPv6 cut latency in half!
Trying a few other Cloudflare fronted domain, not all of them have this problem, which I suspect is how Cloudflare distribute traffic between HK and SG datacenter.

For lazada.com.my, all IPv4 go to HK > SG. No IPv6 support.
lazada.com.my uses Alibaba Cloud as their authoritative DNS.

To further diagnose this issue, TM need to provide public access to their BGP Looking Glass. Alternatively anyone who has peering with TM BGP + full internet routing table should be able to diagnose it properly.

pbebank.com:
CODE

$ dig +short pbebank.com a pbebank.com aaaa @1.1.1.1
203.115.208.218

$ dig +short pbebank.com a pbebank.com aaaa @8.8.8.8
43.241.40.218

$ dig +short www.pbebank.com a www.pbebank.com aaaa @1.1.1.1
203.115.208.218

$ dig +short www.pbebank.com a www.pbebank.com aaaa @8.8.8.8
203.115.208.218

$ dig +short www2.pbebank.com a www2.pbebank.com aaaa @1.1.1.1
43.241.40.253

$ dig +short www2.pbebank.com a www2.pbebank.com aaaa @8.8.8.8
43.241.40.253


Here we can see the apex domain return a different IP address: 203.115.208.218 (Cloudflare), 43.241.40.218 (Google)

43.241.40.218 and 43.241.40.253 (AS6453 TATA COMMUNICATIONS (AMERICA) INC) go to Singapore and come back to Kuala Lumpur.
203.115.208.218 (AS10204 Arcnet NTT MSC ISP) route directly via MyIX.

Let's flush the DNS resolver cache:
Google: https://dns.google/cache
Cloudflare: https://1.1.1.1/purge-cache/

CODE

$ dig +short pbebank.com a pbebank.com aaaa @8.8.8.8
43.241.40.218

$ dig +short pbebank.com a pbebank.com aaaa @1.1.1.1
58.26.83.218


You can see Cloudflare DNS now gets a new IP address while Google DNS gets the same IP address.
58.26.83.218 (AS4788 TM TECHNOLOGY SERVICES SDN. BHD.) is super fast since it is inside TM network and I am using TM.

Let's flush the cache for a second time:
CODE

$ dig +short pbebank.com a pbebank.com aaaa @8.8.8.8
43.241.40.218

$ dig +short pbebank.com a pbebank.com aaaa @1.1.1.1
203.115.208.218


Notice we are back to square one? This must be pbebank.com authoritative DNS problem.
CODE

$ dig +short ns pbebank.com
ns1.a1.impervasecuredns.net.
ns1.a0.impervasecuredns.net.
ns1.a2.impervasecuredns.net.


It might be Imperva problem, or more likely Public Bank configure Geo IP resolver incorrectly.



EDIT:
CODE

$ wget -O - -4 https://cloudflare.com/cdn-cgi/trace
--2023-11-27 04:42:50--  https://cloudflare.com/cdn-cgi/trace
Resolving cloudflare.com (cloudflare.com)... 104.16.132.229, 104.16.133.229
Connecting to cloudflare.com (cloudflare.com)|104.16.132.229|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘STDOUT’

-                            [<=>                                ]       0  --.-KB/s               fl=632f34
h=cloudflare.com
ip=115.134.178.XXX
ts=1701031371.005
visit_scheme=https
uag=Wget/1.21.3
colo=SIN
sliver=010-tier1
http=http/1.1
loc=MY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

$ wget -O - -6 https://cloudflare.com/cdn-cgi/trace
--2023-11-27 04:42:57--  https://cloudflare.com/cdn-cgi/trace
Resolving cloudflare.com (cloudflare.com)... 2606:4700::6810:84e5, 2606:4700::6810:85e5
Connecting to cloudflare.com (cloudflare.com)|2606:4700::6810:84e5|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘STDOUT’

-                            [<=>                                ]       0  --.-KB/s               fl=497f454
h=cloudflare.com
ip=2001:e68:5427:A:B:C:D:E
ts=1701031377.522
visit_scheme=https
uag=Wget/1.21.3
colo=SIN
sliver=010-tier1
http=http/1.1
loc=MY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519


Looks like Cloudflare is working properly over both IPv4 and IPv6. colo=SIN, loc=MY
A quick look into their community forum shows that this is an intended behavior for customer using Free and Pro plan. Fork out the money for Business or Enterprise plan and the problem will disappear.
Maybe lowyat.net should just pay more.

This post has been edited by kwss: Nov 27 2023, 04:48 AM
kwss
post Nov 27 2023, 09:49 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(OlgaC4 @ Nov 27 2023, 08:43 AM)
www.lowyat.net website take 2 second for  unfi to load when start.
Maxis load super fast. Please tell me why?
*
That's some very general statement, and I am sure you will see general reply:
1. TM routing problem
2. Your router problem

You must perform diagnostic during the problem to find out why.
Based on your wording, I am assuming when your WiFi has problem loading, you use your data which is Maxis and it load fast?
The thing is you have instantly changed a lot of variables. You are no longer using your WiFi, your router, TM fiber network, TM BNG, TM core network, TM peering and everything upstream.

Like are you even sure if you are connecting to the exact same IP address from the exact same data center on the exact same server?
Cloudflare uses Anycast BGP. One IP address can mean different datacenter, different load balancer, different physical server.

I am also not clear if lowyat.net will take you 2 seconds to load, every, single, time?
While Maxis load instantly, every, single, time?

Also if you are using a phone, network diagnostic is impossible.

QUOTE(nonamer @ Nov 27 2023, 08:45 AM)
it might be load balancing mechanism using dns...if the application can handle it then what is the problem?
*
You mean pbebank? One prefix is so much faster than the other.
I am sure many people don't mind as long as it works.
kwss
post Nov 27 2023, 10:30 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(OlgaC4 @ Nov 27 2023, 10:09 AM)
All are cat 6 cable connection.
lowyat take 2 seconds to load at the beginning only when using unfi.
It take maxis less then 1 sec to load. 

High end router Mikrotik RB5009

lowyat website respond faster when using maxis compared to unfi.
note that my maxis is using LTE.

Main reasons i downgrade from unfi 500mbps to maxis 300mbps paying the same price
*
After you open a new tab and before you type in lowyat.net, open Developer Tool, then load lowyat.net.
What do you see in Network > First load item > Timing?

user posted image
kwss
post Nov 27 2023, 11:17 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(OlgaC4 @ Nov 27 2023, 10:56 AM)
164ms
*
Can I have the screenshot of the whole thing? There are a few numbers inside.
Please only submit screenshot for the "slow loading".


QUOTE(nonamer @ Nov 27 2023, 10:56 AM)
what means by prefix? if they have 2 datacenter the slower server will be the one remotely accessing the shared database
*
This: https://bgp.he.net/net/43.241.40.0/24
I am talking about the network path going from Kuala Lumpur to Singapore and back to Kuala Lumpur. The other prefix route via MyIX or directly to TM. It has nothing to do with app, database, etc. It is all OSI Layer 3.
kwss
post Nov 28 2023, 05:01 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 27 2023, 09:33 PM)
You are saying me wrong, but supporting me with your proof lol.
And thanks for proofing me it is pbe's DNS server issues. thumbsup.gif
-----
Yes, it is TM issues to redirect customer wrongly to the server, or I should said, load-balancing or best-cost.

And nope, you are using wrong address.
I test on www.lazada.com.my la...

In browser, or any DNS eyes, lazada.com.my ≠ www.lazada.com.my, that's why you get your result wrong.
Same to lowyat.net ≠ forum.lowyat.net

Else, it is a big security that can harm for good, and yes I know a few gov website don't support jumping from lazada.com.my to www.lazada.com.my(as example), as browser just showing DNS not result error, lol. tongue.gif

So here u go~
Skip lowyat as same server, talk later.

PS: Somehow the A also need @, else it go to my router which is Google dns for A result, lol.
www.lazada.com.my:
CODE

dig +short www.lazada.com.my a @2001:4860:4860::8888 www.lazada.com.my aaaa @2001:4860:4860::8888
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
23.47.103.216
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
2001:e68:2:390::15a5
2001:e68:2:388::15a5

dig +short www.lazada.com.my a @8.8.8.8 www.lazada.com.my aaaa @8.8.8.8
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
23.14.199.55
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
2001:e68:2:388::15a5
2001:e68:2:390::15a5


CODE

dig +short www.lazada.com.my a @2606:4700:4700::1111 www.lazada.com.my aaaa @2606:4700:4700::1111
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
23.210.102.139
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
2600:1413:b000:38d::15a5
2600:1413:b000:382::15a5

dig +short www.lazada.com.my a @1.1.1.1 www.lazada.com.my aaaa @1.1.1.1
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
23.210.102.139
www.lazada-lazpay.edgekey.net.
e5541.dsca.akamaiedge.net.
2600:1413:b000:38d::15a5
2600:1413:b000:382::15a5

And yes, during the testing, I found out IPv6 1.1.1.1 get return Malaysia Akamai, while IPv4 1.1.1.1 return SG Akamai.
But more strange, only dig still showing SG Akamai, the "Best Track" is returning MY Akamai already... sweat.gif

So yes, even using different query tools get different result, lol.

If I set my Secure DNS on my phone as one.one.one.one, the result is SG Akamai, same as dig.
» Click to show Spoiler - click again to hide... «


Hei!
23.58.31.78???
lol, it is at India!!!

Much more fun to be play in the future!!! devil.gif  rclxms.gif
---
Back to lowyat.
CODE
dig +short forum.lowyat.net a forum.lowyat.net aaaa @2001:4860:4860::8888
172.67.74.89
104.26.6.73
104.26.7.73
2606:4700:20::ac43:4a59
2606:4700:20::681a:749
2606:4700:20::681a:649


http://[2606:4700:20::ac43:4a59]/cdn-cgi/trace
CODE
fl=35f716
h=[2606:4700:20::ac43:4a59]
ip=(hidden)
ts=1701088906.577
visit_scheme=http
uag=(hidden)
colo=SIN
sliver=010-sin02
http=http/1.1
loc=MY
tls=off
sni=off
warp=off
gateway=off
rbi=off
kex=none


Other 681a also SG, IPv4 for HK yes.

So you ask me, why you said it is Johor?
Well, I locked it based on lowyat IPv6 address that provided 1 years ago.

Sorry, hide it as I still using it for JHB lol, later UniFi found out they forget this IPv6 address, it will get kicked to SG or HK lol. laugh.gif
http://[2606:4700:Hidden:Hidden]/cdn-cgi/trace
CODE
fl=242f15
h=[2606:4700:Hidden:Hidden]
ip=(hidden)
ts=1701089177.025
visit_scheme=http
uag=(hidden)
colo=JHB
sliver=010-jhb01
http=http/1.1
loc=MY
tls=off
sni=off
warp=off
gateway=off
rbi=off
kex=none


So after admin team look at it, found out the performance not good, then kicked it to new IP address?
This is a unknown answer for me...
----
For pbe, you half-half agreed with me, but using wrong address, still works la, lol.
I means the return result time, not the routing issues la...

As Dig failed to showing the slowness part, and also different AAAA + A result, which means DIG don't = real-world performance.

PS: I reopen browser for each test, else it is default to DNS cache lol.
With browser, it is following the result from Best Trace, slowing 10s.
user posted image
But if you enabled DNS over HTTPS, result changed.

user posted image

For interesting part?
Yes, it need a reopen of browser to trigger it, flush DNS or flush idle connection on Chrome don't happen.

Second Strange part?
on Chrome showing stall, not DNS.

It can be the DNSSEC issues, which I then perform testing, yes, it is.

https://dnssec-analyzer.verisignlabs.com/www2.pbebank.com
CODE
All Queries to ns1.a1.impervasecuredns.net for www2.pbebank.com/DNSKEY timed out or failed

So the slowness is caused by not DNS, or DNS caching, but the pbe failed to host DNSKEY?

This, I need to use fiddler to capture Firefox, see did it query for DNSKEY, but I am hungry now, lol!!! laugh.gif
----
In the end, well, new stuff on the surface now.
1. DIG is not the real-world
2. Google DNS really can go crazy, giving India IPv4 as result, lol
3. Public bank lacking DNSKEY?

Now your turn, I wonder did DNS give different result based on requester's IP address.

For me, I am at Melaka, which is nearby SG, more easier to be taken as SG customer. wink.gif

Later post the CF's IP address that is public for KUL lol.
*
I will still say your statement on IPv6 and DNS were wrong. Specifically:
1. Telling user to change to ABC DNS server because it is better than XYZ DNS server. What happen in pbebank.com is strictly limited to pbebank.com authoritative DNS server (which is Imperva configured by Public Bank). There is no best DNS server for everyone.
2. Telling user to disable IPv6. There will always be some site that works better on IPv6 or IPv4. In the perfect world they should both work equally well but... We are not a perfect world.

It is not TM that redirect customer to different Cloudflare server.
Cloudflare did it themself and even wrote about it: https://blog.cloudflare.com/meet-traffic-manager/
Inside the blog post they specifically mention Free customer will be moved to the slowest free region first, followed by Pro, and Business plan. Enterprise plan will get top priority.
It might also happen when the data center is having problem. All hyperscaler do this, including Akamai.

There is no secret in network routing. It is how routers around the world know where to send your packet.
JHB POP:
2606:4700:3108::ac42:2b02
2606:4700:3108::ac42:28fe
172.66.40.254
172.66.43.2

DO NOT HARDCODE THE ABOVE TO YOUR HOST FILE. IT IS JUST FOR YOUR INFORMATION.
If Cloudflare change their JHB addresses, everyone in this forum that do what you suggested will have broken sites. NOT GOOD!

OK, I used lazada.com.my instead of www.lazada.com.my. I am going to make it up for you in this post.

I will address ns1.a1.impervasecuredns.net first.
Whenever you see message like that, it can mean a lot of things.

CODE

$ dig +short tm.com.my @ns1.a1.impervasecuredns.net
45.60.243.95
45.60.245.95


This works because TM also uses Imperva for as their authoritative DNS provider.
What does this means? It means the resolver is working from my connection.

It could very well just a transient network issue between:
AS30060 VeriSign Infrastructure & Operations
-and-
AS19551 Incapsula Inc

The best action from now on would be to find a Looking Glass in one of those AS and check where things break. But everything is up now.

A simple clarification for dig. It is not only real world. It is real time. It is reliable. It is battle tested. It is THE tool for DNS diagnostic. What you are facing is not the tool's fault. You are just misunderstanding how CDN works, and also DNSoTLS / DNSoHTTPS which is a separate layer.

So I would like to address traffic steering for CDN
I assume you have read and understand the Cloudflare post first.

You have an existing understanding on Cloudflare with their long list of IP addresses when you do your query (300 seconds TTL).
Akamai only return one or two IP address with a very short TTL of 20 seconds.

The strategy both CDN uses are different.
Cloudflare mostly depend on BGP prefix announcement to manipulate where user get served. They will use region specific data center IP address depending on the subscription plan, latency and traffic pattern. Cloudflare has specified 50ms latency worldwide. As far as I can tell they are still delivering their promise.

Akamai predominantly depends on publishing and withdrawing IP addresses using DNS to manipulate where user get served. The advantage is that Akamai do not need to wait for BGP announcement to propagate around the world. There is also zero chance of killing the Internet in the case of misconfiguration causing BGP Route Leak or BGP Poisoning. However, it does come with downside too and they documented it here:
https://techdocs.akamai.com/edge-ip-binding/docs
https://techdocs.akamai.com/client-access-control/docs

Again I would like to emphasize there is no single best way to do things in this world. When you use a tool, you first must understand the architecture behind it. In this case Cloudflare and Akamai.

If you really understand the above, then it should answer your question why it gone to India or why different DNS return different IP address but I will elaborate further for you.

Google has contract with TM to host their CDN right inside TM core network. Cloudflare does not.
Coincidentally Akamai also has contract with TM to host their CDN inside TM core network.

With Anycast routing, packet will go to the closest server, in this case, packet just traverse inside TM core network.

Obviously Cloudflare DNS do not have this privilege. Again this doesn't make one better than the other. It is case by case basis. If you predominantly use Akamai, then having TM as your provider and using Google DNS will be the best choice for you. But not for others.

Regarding why it goes to India, it is just a transient network condition. It happen all the time. That's why people use monitoring tools if network performance and uptime is important. Dig didn't show it and your app show it doesn't means one is wrong and the other is right. 20 seconds has passed (remember the TTL) and Akamai can return a different IP. You can try again every 20 seconds and see if it end up in India all the time and tell me about it.

Last I will address your "browser issue".
I will start by saying I do not have a metric how long it takes for first DNSoHTTPS connection is normal. It is like asking people what is the normal boot time for a computer. A laptop and a 2 socket x 128 core server have very different boot time.

What happen is this:
1. Browser query your OS resolver to resolve whatever DNSoHTTPS that's configured.
2. Browser will setup DNSoHTTPS (handshake, verify certificate, key exchange, final encrypted connection)
3. All DNS queries in browser will now be done using DNSoHTTPS

What I suspect is you have adblocker extension like uBO, Tracking Protection or others. They will block all connection before they finish starting up to prevent content from being leaked. So they too block DNSoHTTPS.

The question you must ask is how do you further diagnose this issue?
I will start by repeatedly do the following when I start the browser and the page loads:
CODE

$ ss -tanp; ss -uanp


It gives you a high level overview of what is being done network wise. If you are still not sure why it is taking so long, do a Wireshark capture and see if it is really network stalling. If yes, where does it stall. If not, then it is isolated in the browser code and nothing to do with network.

in Firefox about:networking, you can capture application log. That could be done to gather more information.

Conclusion:
First understand the architecture, understand the process.
Use the tool, understand the tool, understand the limitation.
Come out with hypothesis and further action plan.

Like I said, there is no secret in networking. There is no best way to do something.
Cheers
kwss
post Nov 28 2023, 10:47 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 10:06 AM)
Thanks for sharing me extra IP address, I get different CloudFlare Johor than yours, lol.
Also thanks not sharing the abuse IP address, as it is really abuse. :thumbsup:

I give up, I telling you 99% of times, google DNS give better result, which is Malaysia CDN, and yes, in case it is laggy because MY CDN(Any, Tencent or Akamai or Alibaba) back to SG/HK server caused by crappy TM backbone, then I will switch to one.one.one.one
1. I am not doing that, I just tell everyone, switch to DNS over HTTPS to solve this slowness issues.
Somehow browser need to obtain DNSKEY from the PBE website server, but DNS over HTTPS might already provide DNSKEY, so there is no 10s delay on opening PBE website for the first time.

5 years ago with that old Chrome it is much worse result, the DNSKEY don't cached and expired during browsing of PBE, I think Firefox and Chrome solved this issues, based on me need to relaunch browser to reproduce this issues.
Also yes, 5 years ago there is no DNS over HTTPS yet.

PS: Might not be the DNSKEY, but I lazy to discover, because the solution is switch to DNS over HTTPS. tongue.gif

2. I told them to use IPv6 instead of IPv4, all my result pointing to IPv6 provide better routing(cloudflare going to SG for lowyat)and better DNS result because the IPv6 is more precise on where are you(lazada going to MY or SG for any DNS).

I think you have been messed up with someone, I am fine with it lol.
Because I am same line with you, disable IPv6 and thinking it will solve everything?

Hei, how about Steam gamer?
Now Steam all using steamwork that depend on P2P!!!

IPv4 = Steam P2P Relays server
IPv6 = Steam Friend shared IPv6 and directly connected

Also CGNAT.

So, nope, I reject on disabling IPv6, because bad network is better than dead network.
It is just like telling everyone use 5GHz WiFi on IoT, but not thinking it is possible 100 meter passing multiple wall, which 2.4GHz perform better.
How about those get interference at 2.4GHz?
Go 5GHz with router put outdoor, problem solved!

Sadly, most people don't hand-craft like me, written the IP Address into host file as need, not saying Android phone need ROOT or VPN DNS apps to do that, and local VPN burn a lot battery life.
So yes, most of my method don't works well for regular user, which easy to be solved by burn money, going VPN, get new router and IoT supported 5GHz, lol.
Yup, like I said, I share it out, everyone did it, then the traffic to JHB too large, it will still get load-balanced to SG in the end, lol.

And same to the abuse, I think you might have idea about it now. devil.gif
If, DIG works as real world, how did I get different result from ping???

The screenshot on phone just for simple record, the real world is, I use ping on my computer, the result is same as the screenshot.
I use browser on my PC, result same.

Only DIG is different.
See?

DIG is good, but not when server treat differently to tools and real-world application.
Then you will be like, DIG IS FINE, customer FAULT!!!

So is my fault that DIG get different result from PING that request over DNS UDP, or BEST TRACE, or DNS over HTTPS, or DNS over TLS???
DIG fighting 4 different method to obtain the AAAA and A result, only DIG came out wrong result.

Your conclusion, this guys is fault, DIG is the only ANSWER because it is It is real time. It is reliable. It is battle tested!!!
Your Bowser is doing it wrong, as it get the different result than DIG!!!

Just like Google did to other browser, not chromium based?
Ban this feature!!!

Then you gonna tell all of them, change to Chrome, your own fault using Firefox and Safari!!!
Why use Safari on iOS! go to Chrome!
The fault is at DNS side, because same time I run all 4 tools, only DIG get different result, even after ttl, and others 4 changed/updated the result, that's what I observer.

Hmm, thanks for new knowledge, yes, it is trouble for keeping low latency, but not target high bandwidth lol.
So yes, promise is done, 50ms, but crappy because throttling by TM. laugh.gif

Sound funny it is 50ms, but getting throttling to like 1-10 MBPS, and it is enough for CloudFlare, lol.
Fun fact, you know why Google did this?

During the switching on IPv4 to IPv6 few years ago, TM has silently enabled IPv6 support for Streamyx customer, then for the first month, no throttling from Streamyx to Google own server.
Then after they was like DUDE, no more high QoS for normal Streamyx customer!!!

The speed is getting throttling sharp, again(why again? they already throttling to Streamyx user on IPv4), 480 KBPS.
Only method, is just what I did now.
Enforcing Johor CloudFlare server, let the CloudFlare bring the data from SG Server to Johor Server, so I can enjoy my internet.
But I guess you need sharp answer, so here it is.
During that time, IPv6 99% of time it is providing Google server instead of TM peer server, which you can fell the slowdown on Google, 480 KBPS.

Solution?
Hope your IPv4 DNS give you IPv4 result that end up as TM peer server, else, feel the pain of 480 KBPS watching YouTube.(Yes, throttling because YouTube mostly, but it also hurt Google as there are same to TM ISP, lol)
For YouTube that is real pain, because Google choose which very_long_hostname_that_choose_which_IP_you_should_connected.video.youtube.com, so I had to face 3-5 times of wrong result(Google server), then hoping it finally give me TM peer server.

That, forced me to start writing own host files until now, including Bilibili which was using Sina and other server as their free video server hoster during that time, and now, still crappy at HK server back to China Mainland, lol.
Yes, as above, I will switch as I need, if slowness detected, then jump in between one.one.one.one and google dns la.
Easy.

India is not the problem, because it is still 50ms without random jumping to 200ms and feel the slowness and jitter.
It works fine! As long as no one notify the slowness!

The problem is too heavy throttling on TM side!!!

Wrong, you are not point the error on DNSKEY, which might be the possible, but pointing it is USER PROBLEM again.
You are looking me too down, I am not that stupid, if this is caused by extension, why all website is fine, except PBE?

Remember?
I am firefox user, I know the regular method.
1. Hold shift, safe mode
2. if safe mode fine, then extension error
3. If safe mode failed, then browser or website issues
4. 2=True? Time to perform half-half solution, disable half of your extension, until problem solved, then seek those small range extension.

Anyways, if it end out to be extension, it, will be interesting bug, lol. tongue.gif
----
Tested, nope, not extension, safe mode same issues.
user posted image

Not a Public Bank customer, fine to me.
Let the Public Bank solve it, not me.

I am other bank's regular customer, lol. laugh.gif

But yes, I might try observe and learn how this happen, so to prevent it happen when I deploy my own la, lol.
Still

Conclusion, based on real world result, not DIG tools.

You don't try open Public Bank website on your own side, using Private/Incognito, first-time, uncached, with DNS UDP(not over HTTPS).
You don't try switching one.one.one.one which solved laggy issues during Guess It 2.0 Lazada live event, which solved laggy on livestream video.(by jumping to SG server instead of MY server)
you don't try switching to dot-jp.blahdns.com as private DNS on your Android, which enforce UC Webview engine to happy connect to far server that avoid laggy and deploy(yes, Taobao always forgot to deploy and causing event load failed issues on HK server, lol) issues on Taobao.
(And also using HK DNS server sometimes, or Ali DNS, because Ali DNS IPv4 on Malaysia, but IPv6 on China, lol.)

You, point it out, it is my fault, to doing all those step, to "workaround" TM bad routing issues, workaround Public Bank 10s timeout issues, workaround lazada SG and MY server issues, using host file to using Johor server for CloudFlare issues.

In the end, Yes, it is my fault la, lol. thumbup.gif
*
Now you said it, I am 99% sure your problem will be gone after you delete your host file and reboot.
kwss
post Nov 28 2023, 11:07 AM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 10:49 AM)
I also don't, but my neighbor and my housemate are both using laptop to perform P2P transfer, suck out all the WiFi Channel for their 24/7 uploading, yuck....

Come on!!!
P2P please use it on cable la!!! doh.gif
Fxxk you, no!
I tried, thanks!!!

You live in your own world la, no reply to you anymore, thanks, I hope you are happy living in your little world. thumbup.gif
*
Love your confidence. As if TM know you closed your browser and open it again. Throttle this guy whenever he open his browser and visit pbebank.com

Highly emotional.
kwss
post Nov 28 2023, 01:06 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 12:37 PM)
Hei, I done my part, it is 1%, happy?
Bye. rclxs0.gif
*
I am happy for you. The problem is still on your side.
Don't scream routing problem when it's actually your own hardware problem. None of your own advice works in this case. Your very own DNS problem doesn't means Public Bank get the blame either, or Cloudflare DNS, or Google DNS.

Does TM share the responsibility? Maybe, since they supply the hardware.

Use more logic instead of emotion next time.

About my long dig story, I don't do butt dyno. Measure it or it's just "feeling".

If I don't come and challenge you, you will still be blaming routing problem or other people's DNS problem instead of you.

Oh, you did learn my DNS diagnostic technique right? The Timing tool in Firefox. LMAO.

Anyway, proud of you. Fast learner.
kwss
post Nov 28 2023, 01:41 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 01:29 PM)
And for you, here is the gift.

https://zh.moegirl.org.cn/zh-hans/%E6%88%91...%89%9B%E8%82%89
https://www.bilibili.com/video/BV1vu4y1a72J/

蛮不讲理(Unreasonable), here is my tags for you. tongue.gif

Blaming others to win for your answer, saying your logic is better than my logic, lol!!!
----
It is just like, I drive 10 years old car, I do maintenance and checking car period, based on the car's manual.
Then, it crashed, the result is there is bug or stackoverflow happen on the car's break assistance Firmware, very hard to trigger, it taken a certain degree to press on the break on certain time, certain speed, certain force.

With a lot of effort, I finally found it out, proof it.
Then you are like: Hahahahaha, I told you it is your fault, you should not using this old and low end B40 car!!! laugh.gif
And drive your new car away, on the TM bad route.
*
You are welcome.
kwss
post Nov 28 2023, 01:49 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 01:42 PM)
Another nice troll by you, lol.

Are we at /k?
I am sure I am on "Networks and Broadband"

Here is your result, safe mode + profiling.
user posted image

It did nothing, but showing it is DNS error, again, as F12 - networking.

Based on bugzilla, they mention their profiling tools are greatly limited, lol.
Anyways, I am here to learn based on Truth, not TROLL!!
Fuck off if you do nothing to this thread!!!
*
You obviously still blame Public Bank. I double checked it and there is nothing wrong. Come papa teach you.

CODE

dig pbebank.com +trace


What you see is DNSSEC in action. In DNSSEC, all non-existance record must be signed, it's called NSEC3

Today papa good mood. Who is so kind to teach high ego people for free.

Regards,
Someone who don't know DNS
kwss
post Nov 28 2023, 02:12 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 02:07 PM)
More here

CODE
dig aaaa pbebank.com @1.1.1.1

; <<>> DiG 9.16.37 <<>> aaaa pbebank.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 7558
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 6 (DNSSEC Bogus): (proof of non-existence of pbebank.com. AAAA)
;; QUESTION SECTION:
;pbebank.com.                   IN      AAAA

;; Query time: 31 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Nov 28 14:01:49 Malay Peninsula Standard Time 2023
;; MSG SIZE  rcvd: 89

https://developers.cloudflare.com/1.1.1.1/i...ns-error-codes/

CODE
dig aaaa pbebank.com @8.8.8.8

; <<>> DiG 9.16.37 <<>> aaaa pbebank.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 36087
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
; EDE: 12 (NSEC Missing): (No NSEC or NSEC3 records to validate non-existence of pbebank.com/aaaa)
;; QUESTION SECTION:
;pbebank.com.                   IN      AAAA

;; Query time: 31 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 28 14:04:19 Malay Peninsula Standard Time 2023
;; MSG SIZE  rcvd: 116

https://developers.cloudflare.com/1.1.1.1/i...ns-error-codes/

Compare with others IPv4 only website, but supported AAAA.
CODE
dig aaaa v4.ipv6test.app @1.1.1.1

; <<>> DiG 9.16.37 <<>> aaaa v4.ipv6test.app @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35565
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;v4.ipv6test.app.               IN      AAAA

;; AUTHORITY SECTION:
ipv6test.app.           900     IN      SOA     ns-1656.awsdns-15.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 109 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Nov 28 14:03:23 Malay Peninsula Standard Time 2023
;; MSG SIZE  rcvd: 131


And you still change topic to another side, ignoring other's website AAAA record are FINE.
Blame on user error. sweat.gif
*
CODE

dig pbebank.com +trace
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> pbebank.com +trace
;; global options: +cmd
.                       15357   IN      NS      a.root-servers.net.
.                       15357   IN      NS      b.root-servers.net.
.                       15357   IN      NS      c.root-servers.net.
.                       15357   IN      NS      d.root-servers.net.
.                       15357   IN      NS      e.root-servers.net.
.                       15357   IN      NS      f.root-servers.net.
.                       15357   IN      NS      g.root-servers.net.
.                       15357   IN      NS      h.root-servers.net.
.                       15357   IN      NS      i.root-servers.net.
.                       15357   IN      NS      j.root-servers.net.
.                       15357   IN      NS      k.root-servers.net.
.                       15357   IN      NS      l.root-servers.net.
.                       15357   IN      NS      m.root-servers.net.
.                       15357   IN      RRSIG   NS 8 0 518400 20231210050000 20231127040000 46780
. qzfQhxgaypARZKV79AZ7ZrThuOiQfEsJawcaJEJchmHfyz4/Cud+wllI 244xxeJQofKSmglOiONsse3i/CfmxassYgKQgMrzqa2SSvCCTPFjfWUm jPPzQFhcjITcpLmev5c84nG4j+dwUWkfXOlsaO360Gm8iQXVopQbZXoQ sMTaFNBo+e6UjndTa9/3pLeyuE9gElrrdr0GhCjA32yRyTwEbdcCM0pw uUyn6LFa22mfSfKA6EQc1XA0Z3DWs0pdbA6bzwdjZSBZpOhxSBKy2FwS 62Oqt7seOMtRfYhlqvzEUGmNazUr2YgV0nlDutaWNeoVh9TVXE3j1dm4 M2oF3w==
;; Received 717 bytes from 127.0.0.1#53(127.0.0.1) in 40 ms
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    86400   IN      DS      30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.                    86400   IN      RRSIG   DS 8 1 86400 20231211050000 20231128040000 46780 . AB0wxGUe/6J/3O1b+gX65q2tRpB/pTK2q2SwPcTMM+PJcz8mnjk7MuAv h6fS/ulTrSVZ8CffF8CFQTZVIaIWC9CV/jOjJhdCOcggKbGZnKhjegHq uGvYCEV32TvoLMIkoMZXF1dLOZM389pPOJEjMzZyK2jaFBcBRceYPfBK MCEXVDQ1utI5MOzwXy4xAC3jKEGpOH1aVHxj205XejjYO3gPnPjCB6kd /eViI0qDRlBtI3CfUxJ6A/d6Fgun+EzyiqMZ2ZVqOH8LTdRczz+FOL86 /vh5ZzlgY2zRmbl9RYsPr/XDbkdQ2nrVPCaUDSMMhY/AcDSvxC6yOUFv
/TO1lg==
;; Received 1171 bytes from 192.58.128.30#53(j.root-servers.net) in 12 ms
pbebank.com.            172800  IN      NS      ns1.a1.impervasecuredns.net.
pbebank.com.            172800  IN      NS      ns1.a2.impervasecuredns.net.
pbebank.com.            172800  IN      NS      ns1.a0.impervasecuredns.net.
pbebank.com.            86400   IN      DS      34567 8 2 A552CD4F0FF3299CBC0698DACD65FE7AAB2A6EE735770CE0854813A4 BD9B3650
pbebank.com.            86400   IN      RRSIG   DS 8 2 86400 20231202054645 20231125043645 63246 com. QQ0j7nRZL+oKGOhWtIq4Avdv4sgXVF9DJdBpHfVJK4SGiG7JCUtGzbVy Oqza+p+wkp048p7WXNkcxME5zq9pz/UCAKg8BpB83jTMuaj/lhSJonBD rUF4YZ2dZks1RU50ELJZho9Mtc/OE1AKtzrPuhQB6XC1r/ipiKj+ePuR cXNunJriKKL1sBOfma17CW46AVBhJA8OLFku2zuozuN/9Q==
;; Received 366 bytes from 2001:502:8cc::30#53(h.gtld-servers.net) in 16 ms
pbebank.com.            30      IN      A       203.115.208.218
pbebank.com.            30      IN      RRSIG   A 8 2 30 20231202171229 20231125161229 52614 pbebank.com. AH3Ta4kcJtg6oXS9+zRGxzcciedLVh8g7ycPDdSSf9R0Vnu0Z2f4CCCV GvvpVTQza776eZ0+ate+7ehmB2Enl2EhwxWI/nMDQi64f6yBIg2ThnQg JMnjxkEgBoGVPzWVxXNOGh5Zs0EvYPpYzyIIUamn2t8DsggEifwj0E2U eC90vSjXtOq3foeh1+hTT0xF+z8kpeVLiCaM3GmxjDzAnHwFy945Xn/Y Uey0IeNod9mSREFoEpcL+apsFHJQIKOIXvr2K6zU5mOU//ZkRf68CoIN tfp33zfpdGWwdVWoAUmtA6mnOfTJzDdxfE9qJQ1kac8Uh/JUF+FudR8T UY634A==
;; Received 355 bytes from 192.230.123.1#53(ns1.a2.impervasecuredns.net) in 20 ms


You keep running dig with a router that chew up your packet.
DNS Analyzer and DNSViz said Public Bank is fine.

kwss
post Nov 28 2023, 02:24 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 02:15 PM)
Sure?
You are changing topic.

I run dig aaaa pbebank.com @8.8.8.8, you run dig aaaa pbebank.com +trace that showing no error.

You dare to post your result at
dig aaaa pbebank.com

And proof it is not "status: SERVFAIL"?

Also
dig aaaa pbebank.com @8.8.8.8 pls. nod.gif
*
Ah okay I get what you mean. LMAO.
Yes in this case Public Bank is non-compliant.
Don't la so emo... Jeez
kwss
post Nov 28 2023, 02:38 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
Tested other website with DNSSEC:
cloudflare.com
imi.gov.my

imi.gov.my don't have AAAA but it does return NSEC3
Want to try with your Netis and see if it works?
kwss
post Nov 28 2023, 02:50 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(BenYeeHua @ Nov 28 2023, 02:45 PM)
tongue.gif
Yes, it works, because it is "status: NOERROR"
The router's DNS relay only drop on "status: SERVFAIL". laugh.gif

CODE
dig aaaa imi.gov.my

; <<>> DiG 9.16.37 <<>> aaaa imi.gov.my
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63776
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;imi.gov.my.                    IN      AAAA

;; AUTHORITY SECTION:
imi.gov.my.             29      IN      SOA     dns1.gitn.net.my. planning.gitn.com.my. 2023072840 10800 3600 604800 38400

;; Query time: 20 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Nov 28 14:43:58 Malay Peninsula Standard Time 2023
;; MSG SIZE  rcvd: 107


So, as long as no "status: SERVFAIL" with error on DNSSEC, it is fine.
*
Alright. So if we test another one with: dnssec-failed.org
Then it should fail too on Netis?

If that's the case then it's confirmed the router drop packet solely based on SERVFAIL
kwss
post Nov 28 2023, 03:01 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
It's clear now this happen because TM never catch this problem during hardware validation.
Reason: TM DNS never validate DNSSEC

CODE

dig aaaa pbebank.com @1.9.1.9
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> aaaa pbebank.com @1.9.1.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23130
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;pbebank.com.                   IN      AAAA
;; Query time: 20 msec
;; SERVER: 1.9.1.9#53(1.9.1.9) (UDP)
;; WHEN: Tue Nov 28 14:58:08 +08 2023
;; MSG SIZE  rcvd: 40


CODE

dig aaaa dnssec-failed.org @1.9.1.9
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> aaaa dnssec-failed.org @1.9.1.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 645
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;dnssec-failed.org.             IN      AAAA
;; AUTHORITY SECTION:
dnssec-failed.org.      900     IN      SOA     dns101.comcast.org. dnsadmin.comcast.net. 2010102371 900 180 604800 7200
;; Query time: 356 msec
;; SERVER: 1.9.1.9#53(1.9.1.9) (UDP)
;; WHEN: Tue Nov 28 15:00:43 +08 2023
;; MSG SIZE  rcvd: 117

kwss
post Nov 28 2023, 03:11 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
Since you mention BGP, TM failed RPKI test
https://rpkitest.nlnetlabs.net/

Pass on Celcom.
kwss
post Nov 28 2023, 03:53 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
When I said you are a fast learner. I mean it.
Not being sarcastic, not trolling you. Purely logical judgement.

You pick stuff up real quick. This is a rare find.
kwss
post Nov 30 2023, 12:23 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(eclectice @ Nov 30 2023, 07:08 AM)
"TM AS4788 had recently installed RPKI validator and will be dropping the “Invalid” route by November 2023. Please update your ROA accordingly."

https://ipinfo.io/AS4788/42.188.192.0/19

Now, which tool is giving the correct result for UNIFI-HOME AS4788 with the prefix 60.50.0.0/32?

https://rpki.cloudflare.com/?view=bgp&valid...efixMatch=lspec

user posted image

or

https://rpkitest.nlnetlabs.net/

user posted image
*
Both tools are correct. There are 2 parts to RPKI:
1. Prefix owner to publish and sign ROA
2. Service provider who reject invalid ROA

TM did the first part. It means if somebody tried to hijack TM prefix, any ISP that reject invalid ROA will not accept the prefix announcement.
Currently TM didn't do the second part. It means if somebody hijack Amazon DNS (AWS Route53) to hijack your crypto account, TM will gladly route you to the fake prefix.

Read more here: https://www.internetsociety.org/blog/2018/0...-53-bgp-hijack/

All BGP operators must implement both to be considered secure. Everybody must do it.

November has come and gone. The test shows TM haven't rollout the changes.

This post has been edited by kwss: Nov 30 2023, 12:54 PM

2 Pages  1 2 >Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0370sec    0.76    7 queries    GZIP Disabled
Time is now: 1st December 2025 - 08:42 AM