I was running packet capture on the IPSec interface looking for traffic
to/from 192.168.75.x and 192.168.85.x and only saw traffic when I pinged
their server.
Lyle
On 5/26/2016 9:32 AM, ED Fochler wrote:
I agree. I typically ssh in as root and tcpdump to get a more interactive view
of the network, but packet capture should give you the same data. You should
be seeing traffic even if it is rejected or dropped by your firewall rules. If
you’re not seeing ping, it’s not showing up at your interface.
ED.
On 2016, May 26, at 8:44 AM, Vick Khera <[email protected]> wrote:
On Wed, May 25, 2016 at 8:54 PM, Lyle <[email protected]> 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
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
