Wireless Joint

I have a WG1608 + RM502Q-AE on T-Mobile. The 5G connects just fine but some devices cannot ping to the internet. I have tried various firmware for the WG1608 and the RM502Q-AE is on the latest firmware.

Devices that can ping just fine:
Arch Linux Laptop
Router / Modem itself

Devices that cannot:
Mac Pro
PFSense

If I enable LTE only and use the IPv4 APN everything works just fine. The problem is I bought this to be a 5G setup.

Some observations, T-Mobile provides an IPv4 address of 192.0.0.2/32 to the device and some IPv6. On my old EM7565 modems it receives a standard public IPv4 address.

I would like to think this on T-Mobile's side, but it makes no sense that the router can ping the internet but devices behind it can't. Any ideas?

I have seen an ping issue with a windows-10, PC. It was a setting in the Advance firewall settings.

I have Mac laptops but they alway just work, so my troubleshooting skills are weak for a Mac.

I have a t-Mobile home internet will see if I can Reproduce the Error you are seeing.

Can you ping all your Devices on your LAN??

Yeah I can, My LAN sits behind a PFSense router. You have a WG1608 + RM502Q-AE?

The devices behind PFSense can even ping out, but PFSense itself cannot when on "LTE/NR EN-DC". When forced into LTE-FDD everything works just fine.

I'm using GoldenOrb_20201-09-13 and the RM502Q-AE is on the latest firmware.

I have found that after a while something on the router's firmware "breaks" or "reverts" or something and the ping stops working every month or so. To fix this, i have to reflash the firmware without saving settings exactly 3 times in a row, no less. Then set the modem to 4g only. after that it works again with ipv4 games etc on tmobile

Hello,

shaneomac182 wrote: Fri Dec 03, 2021 7:59 am Yeah I can, My LAN sits behind a PFSense router. You have a WG1608 + RM502Q-AE?
The devices behind PFSense can even ping out, but PFSense itself cannot when on "LTE/NR EN-DC". When forced into LTE-FDD everything works just fine.
I'm using GoldenOrb_20201-09-13 and the RM502Q-AE is on the latest firmware.

I am using pfSense myself but don't have access to 5G. Therefore, I will try to suggest one theory to check:
a) your WG1608 does not force TTL;
b) your devices MacOS /FreeBSD use different (from) TTL settings for ping and that somehow affects the final result;

Can it be the case? If so then try to use the same TTL value (copied from Linux) on both MacOS /FreeBSD and see if it helps.

Or may be even more - ping uses ICMP packets, described here:

https://en.wikipedia.org/wiki/Ping_(networking_utility)

first of all, lets talk about IPv4 part:



Now you have to run Wireshark and check the packets attributes (version etc) to see what is the difference (apart from before mentioned TTL (if there is any)), I mean the packets sent from Linux and MacOS machines.

Or you can even use pfSense for this purpose (assuming that both computers are connected to pfSense), use Diagnostics -> Packet Capture feature. To see the complete information set "Level of details" to "full".

Using Wireshark would provide more user friendly GUI experience but would require more tweaking.

So an update, I setup a private IPv6 network on my lan and setup pfsense to route over the /64 provided by T-Mobile. This allows me to ping (IPv6) hosts. After lots of reading the T-Mobile home internet guys have been complaining for months about T-Mobile blocking ICMP for IPv4, apparently this is only rolled out on 5G where they are using 464xlat which is setup really badly.. basically it seems T-Mobile is purposefully butchering the connection.

Anyways, my hosts on my LAN can connect via IPv4 and IPv6 now. I can ping (IPv6) for my WAN status, and I setup a Wireguard VPN terminated at PFSense through T-Mobile over IPv6 which works well for my traffic that doesn't need to be seen. I did this because T-Mobile is also blocking IPv4 VPN's with their stupid 464xlat implementation on 5G.

Hopefully this hopes some with the same issues.

Additionally, I tried all the TTL things and it did not seem to make a difference.

In fact I have noticed that no matter WG1608 or a X86 with R00ter, the ipv4 ping wont work.

Even more I found I can ping V4 and V6 from router with ssh login when it's in 5G mode.

My smart devices stop working as well, they displayed offline.

At 5G mode, WAN cannot get normal ipv4 address, only 192.0.0.2/32

I believe the problem is at LAN settings / DNS , but have no idea where to check.

I already apply a TMO 5G home internet since it's in promotion for free trial and $50 gift card.

Will check the ips from the trashcan.

I just built a 3526/RM502Q-AE with Rooter on TMO. It defaulted to 5G SA mode on n71. I couldn't ping from Win10PC and had weird connectivity issues like not being able to stream AppleTV+ content from multiple devices. I disabled SA mode and my problems disappeared. Speeds are also a lot faster in NSA mode with it connecting to B66+n41.

so update on this. As of this morning I switched over to 5G and suddenly IPv4 ICMP and IPv4 VPN is working as intended. T-Mobile must have finally fixed their settings on their 464xlat deployment.

shaneomac182 wrote: Mon Jan 10, 2022 9:47 am so update on this. As of this morning I switched over to 5G and suddenly IPv4 ICMP and IPv4 VPN is working as intended. T-Mobile must have finally fixed their settings on their 464xlat deployment.

Really? I need to connect for a try.
But my fiber already connected, may continue with Frontier