Comments
-
I don't have access to the network operator's router. They provide us a /29 class without any VLAN or anything more…
-
the "trunk" solution would work… but only using WAN1 IP and not WAN1.1 one. If i set outgoing SNAT to anything different than "outgoing-interface", when the primary wan fails, the traffic would not failover on the other. It would work if trunk configuration would allow to add "virtual" interfaces, but this don't seem to be…
-
The production environment is not easy as the example: we have multiple services on a single WAN ip (Mail, Web, Xmpp, Voip…). This prevent the "1:1 Nat" solution and make the "two LAN IP" solution quite hard to implement….
-
1.1.1.x and 2.2.2.x are placeholders for our public IP addresses. 192.168.x.x are private IPs. All NATs have NAT Loopback enabled, but the problem is present when the call comes from the internet.