I appreciate your kind gesture mate sharing me a few insights. I will read the given article tomorrow.

we only care about the main gateways that running ip that can support ttl

What do you mean? TTL is a required headers for all packets, regardless of it's TCP, UDP or ICMP.
There's no such thing as main gateway as every router along the path is technically a gateway. But not all of them will reduce the TTL by 1, in the case of MPLS.
Now there's no way for the web site to know how the packet route at all, including if it went through a tunnel.

Is there a gateway that don't run IP? I am not sure what do you mean.

Is that a question or a statement? Every gateway process TTL. Every gateway runs IP.

if telco does not show mpls routing, do u think ttl is enabled in their mpls network?

Me too. They deduct RM89 (balance RM0.90) from the Ultimate Max Pack charge and convert it as a discount plus discount value from HSI charge. Discount value from HSI cost becomes less than before

anyone on SWU3.0 received call from TM offering 500mbps and free router again?

the CS said in system it's still 300mbps despite me being on SWU3.0 since last year.

my colleague received call from telemarketing offering free router, 300 mbps @ RM129 free 6 months or 500mbps @ RM129 free 3 months.

Why is Discord and some other website so freaking slow now.... (on ip 115.xxx)

i'm interrupting here. i've never dealt with MPLS before.
but what i understand is every gateway router passed along will reduce TTL inside packet by 1. else stale packet will never age and will never get removed. imagine packets from the original 1970s network still bouncing around because TTL never reach 0.

it make sense that a packet outside whatever-kind-of-tunnel will get TTL reduced as it hops by each gateway router.

it also makes sense for a packet inside whatever-kind-of-tunnel get not get modified by MITM gateway routers in-between, but only by the ingress and egress devices of that the tunnel.

--

website is generally at application leyer. OSI 7.
unless the webserver is built ground up to access and retrieve the test packets all the way from layer 3 where TTL is, it is correct to assume that whatever hop information is unreliable and at best only a guess. plus, on an IP network, back-to-back packets don't have to travel on same route to same destination. you can see the effect by repeating traceroutes again and again to distant targets.

This post has been edited by Oltromen Ripot: Jun 21 2024, 11:41 AM

Huh Unifi will still offer free stuff if you're already on SWU3.0 meh? LOL

At least i got it free upgrade from 300 to 500mbps + 6 months free when i walk in tmpoint last april.

Thanks sifus for the advice. Puas hati bila speedtest.

https://www.lowyat.net/2024/325032/malaysia...rating-to-ipv6/

I wonder how will this affect current private / public ipv4 users?

Sorry man, I think my brain is having some problem. I still don't quite get your question.

If your question is "Is the hop count accurate if your telco don't use MPLS?"
The answer is most probably not. When your packet crosses to another AS, that AS might very well use MPLS / SRv6 in their network. This is a common deployment pattern used by a lot of service provider called "BGP-Free Core".
The implementation can be straight MPLS, Control-plane using MPLS with data-plane using SRv6, or straight SRv6, but the concept is still the same, with the same implication.

If your question is "Telco use MPLS routing, but you do not know if you are crossing a MPLS segment, which TTL is used?"
MPLS header has a TTL field. If it crosses the MPLS segment, the TTL field in the MPLS packet will be reduced. But your packet is never processed because it is the payload inside the MPLS packet.
Once the packet exit the MPLS tunnel, then processing of your packet from subsequent routing decision will reduce the TTL from your packet. Of course this also applies when the packet leave your device because MPLS tunnel don't exist in your home network.


Hello there, great to see you chime in. What you said is correct. Layer 3 packet don't carry routing information. You are also correct about routing being asymmetric on the Internet so whatever information gather from Layer 3 then becomes irrelevant..

This is actually what a lot of country want but don't have the stamina to push through.
The hidden issue with IPv4 right now is all the American dinosaur company are holding the world ransom.
During the early days, they were given a lot of IPv4 addresses. When IPv4 address starts to run out, they do what all capitalist do, by renting out those addresses and try to delay IPv6 adoption.
This is exactly what MCMC means by "does not have full authority over IP addresses which are an important asset of the country"

oh dang, 115.xx was actually fine for me bro

where you at though cause I'm in pj

as in for most 60.xx used to be a cursed range, but was always good to me and those I know nearby 🫠

I'm in Semenyih, slow loading at certain website this morning, speedtest web also long loading

what if the behaviour is like this --> https://www.stigviewer.com/stig/cisco_ios_x...inding/V-216790

what is the different between swu3.0 vs 4.0, looks like same only