I think they would ping 192.168.85.x and incoming pfSense would forward
that traffic to 192.168.1.x, doing a 1:1 type NAT.
Lyle
On 5/26/2016 7:44 AM, Vick Khera wrote:
On Wed, May 25, 2016 at 8:54 PM, Lyle <l...@lcrcomputer.net> wrote:
The other end has a conflict with our LAN addressing(192.168.1.0/24). So
in phase 2, we setup a Tunnel IPv4 using 193.168.1.0/24
for the local Network. NAT/BINAT network of 192.168.85.0/24. Their
remote network is 192.168.75.0/24.
So if they have a conflicting 192.168.1.0/24 network on their end already,
how the heck do they expect traffic to *your* version of that network to
get routed to you? That is, if they type "ping 192.168.1.42" which network
is it supposed to go to? I don't see how some Sonicwall magic could make
that happen either.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
