If yes, I suppose you need to change the WAN subnet for the LTE Router X using /30 or /31.
This is what have been explained by the ref that you shared. The ref explaining the issue when both remote site is assigned IP addresses are in the same network at multiple locations this will cause issue for the Internal router to connect.
For Peplink Router Cellular WAN, we have automated this to avoid the issue and this is the reason why you are getting /31 network without IPPT. When IPPT enabled, we will let the module to calculate the subnet based on the IP obtained and it will normally in /30 network because some of the device cannot support /31 network.
I second this request. I work with a lot of customers and multiple vendors. We currently have a customer starting a big migration from Cradlepoint to Peplink and this feature has the customer questioning if it’s worth it due to having to reprogram all his actively deployed Firewalls. The CP’s are setup with the "force /24 subnet option now.
Just to confirm the /24 subnet setting use case is just to help on on the migration without require to change the firewalls settings ? Normally, for IPPT settings , the device connected will use the DHCP WAN, by default the firewall will just obtained the IP from DHCP and it should not require any changes.
For the /24 option, from the discussion with the Engineering team, so far we don’t see the real use case for the /24 network IP for Cellular will help to resolve any issue/use case. Would it be possible that you can help to check why they need to set the subnet using /24 for the firewall via the Cellular ?
We are seeing it pull .254 /31 subnets in both NAT and IPPT and many of these firewalls are not allowing it to connect. I’ve got customers using laptops to log in to see what network it pulls form the carriers and then put that into their firewall. We used to see that on peplink in NAT mode for manual setup. The /24 would be helpful for us and our customers if the option was available. That way when manual setup is required, we could give them network info that would work.
I just got another ticket from a customer because the /31 network doesn’t work on his equipment. "Yes, Site Name is the only one we cannot connect to because any host device (like a laptop that we are currently using) cannot accept the /31 subnet mask as valid. I don’t believe this is a firmware issue. The problem is that in order to use the IP passthrough functionality, the user must assign the static ip to their device, Windows operating systems do not allow the assignment of a /31 subnet for network access. We have never had this problem with the previous Peplinks because they all have subnet sizes larger than /31. "