This involves both pepwave max-BR1 and balance 710
We support a large number of pizza restaurants. Most have the same untagged subnet like 192.168.3.0/24
We add a private subnet for VoIP, routed over pepvpn to our data centers, with B710s at the hub
We also use 1 to 1 NAT to map unique /24 subnets to the common 192.168.3.0/24 subnets in oprder to deliver callerid to the POS systems. This does work (it is a one way, UDP packet from central server to remote systems)
The subnets we map are 10.123.x.0/24.
i.e. first pepwave has 10.123.1.0/24 mapped to 192.168.3.0/24
next has 10.123.2.0/24 mapped to 192.168.3.0/24
etc
But we recently have need to open TCP connections to remote systems over the 1 to 1 NAT mapping. When we tested this for the first pepwave it worked perfectly. So we developed the program that would use it and started rolling it out
But…it only works for the first remote site…It appears that return traffic is not making it back to the core for any other subnets
from a central server I can reach anything on 10.123.1.0/24 UDP or TCP
but for 10.123.2.0 and up I can send one way packets but TCP will not work as no return packets make it back
This includes even ping.
I can ping 10.123.1.1 (the pepwave LAN interface for first pepwave) but not 10.123.2.1
