QUOTE(zellleonhart @ Jul 29 2024, 11:35 AM)
Hmm sorry I am not technical enough to understand - so there's no issue actually? Just tried again and still can't access/ping on IPv4... Can't afford to get a new public IP now since I am outside, but will see if a new IP range works.
Tried your command and it's loading forever:
CODE
curl -v -4 http://tailscale.com
* Trying 76.76.21.21:80...
Can you post your traceroute to tailscale.com?
What if you use https in curl? Does it work?
If you have IPv6, try -6 instead of -4 to see if it works.
QUOTE(Anime4000 @ Jul 29 2024, 12:43 PM)
kwss seem Unifi IPv6 has broken IX or potential MITM attack?
My Mikrotik cannot join my friend BGP

Bogon IX?
https://bgpview.io/ip/2001:8f8:0:10:0:21:58:2a This one is definitely TM at fault. I take a look and Etisalat do not even have IPv6 peering anywhere except Etisalat Dubai EmIX.
They do have a looking glass here:
http://lg.emix.net.ae/lg/So I check their BGP:
CODE
Command: show bgp ipv6 2403:cfc0:1100:ff00::2
BGP routing table entry for 2403:cfc0:1100::/48
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
132337 133210 135134
2001:8f8::58 (metric 1) from 2001:8f8::36 (195.229.0.58)
Origin IGP, localpref 120, valid, internal, best
Community: 8966:41 8966:8888
Originator: 195.229.0.58, Cluster list: 195.229.0.36
Last update: Wed Jul 24 04:49:07 2024
AS132337 Axclusive > AS133210 EN Technologies Pte Ltd > AS135134 Soon Keat Neo.
Based on this alone it is impossible for Etisalat to take in traffic destinated for AS135134. They are not even adjacent AS. It also clearly stated "Not advertised to any peer"
Trying to figure out where they peer, seems to be Equinix SG:
CODE
traceroute to 2404:160:815c:6f5a:8bb3:d730:f8da:dd5a (2404:160:815c:6f5a:8bb3:d730:f8da:dd5a), 30 hops max, 80 byte packets
1 2001:8f8:0:10:0:22:209:1 (2001:8f8:0:10:0:22:209:1) 3.670 ms 3.797 ms 3.926 ms
2 * * *
3 * * *
4 * 10030.sgw.equinix.com (2001:de8:4::1:30:1) 87.628 ms *
5 * * *
They indeed has direct peering to TM, presumably over a route server
CODE
Command: show bgp ipv6 2001:e68:5427:3c12:164:5ba5:d348:18dd
BGP routing table entry for 2001:e68::/32
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
4788
2001:8f8::21 (metric 1) from 2001:8f8::36 (195.229.0.21)
Origin IGP, localpref 100, valid, internal, best
Community: 4788:6200 4788:6210
Originator: 195.229.0.21, Cluster list: 195.229.0.36
Last update: Sat Jun 1 10:09:34 2024
However, none of this explains why TM will dump traffic to Etisalat when they don't have direct route to your friend. They don't even advertise the prefix.
This Etisalat also sucks at IPv6 so I am not surprised they have a routing loop (your traceroute is an example of routing loop).
This is further evident by how they configure their DNS AAAA record:
CODE
dig +short www.etisalat.ae aaaa
www.global.etisalat.ae.
::213.42.167.153
::213.42.214.53
I really wanna laugh. What kind of sorcery is "::213.42.167.153"
Since TM don't have a Looking Glass, I cannot tell for sure what is wrong.
In this specific case, bogon IP is basically prefix that is not publicly routable because they are used internally in IXP. It is done using BGP filtering.
Sorry man, I don't have an exact answer for this question. If you have a working traceroute from last time maybe we can infer something from there.
Alternatively, since your friend has control on his end, maybe ask him to run a traceroute to you?
I do have a theory: TM is leeching other people's pipe by configuring a static route and dump traffic onto other AS.
In a lot of peering policy, this is illegal. Maybe Etisalat do not have this written in their policy and TM is abusing it.
QUOTE(kerolzarmyfanboy @ Jul 29 2024, 12:55 PM)
TM technician came this morning & just replaced my old ONU with the Fibrehome HG6145F3, might as well, since still under warranty anyway. guy was puzzled as well as to why so many disconnections when he read the logs haha.
but could confirm fibre is fine, so problem could just be between my router and the old ONU, could be just the LAN cable between the two devices even. he just ended up replace the whole thing with HG6145F3 and just disconnect my old router as well. let's see if that might've solved the intermittent disconnect issue, will monitor. gonna use my old router as repeater for 2nd floor.
and now I have another new minor problem since the new Fibrehome installed; for some reason, even after changing DNS to Google DNS & flush computer's DNS, some websites still blocked for me. especially the torrent ones

have changed dns on the router too. weird.

Assuming you are using Windows, did "ipconfig /all" shows you are actually using Google DNS? Sorry I don't run Windows so anyone out there feel free to chime in for the correct command.
You can verify with Android phone too by going to your WiFi and tap the gear icon beside your SSID. Tap advanced and scroll down to DNS.
If you don't mind, maybe you can post the problematic domain and I look it up for you.
Also for the DNS poisoning, it don't happen all the time. I think they are still kind of field testing it. I just caught them doing it.
This post has been edited by kwss: Jul 29 2024, 03:17 PM