Hi Lyle,
Which IP they are pinging exactly?
Rosen
Lyle wrote on 5/25/2016 6:54 PM:
I am trying to install a new pfSense appliance running 2.3 Release.
works fine until I setup a IPSec tunnel.
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.
I can ping and see the smb shares on their server at 192.168.75.220
from a workstation on the 192.168.1.0/24 network. However they need to
ping and access the printers on the LAN(192.168.1.0/24) network from
their 192.168.75.0/24 network.
That's where this all breaks down. The guys at the far end are using
SonicWall and want me to junk what we have and buy a much more
expensive SonicWall(not to mention the subscription costs for
filtering web access) to do what pfSense does now, using Squid and
squidGuard.
The guys at the far end are claiming that our end is rejecting their
ping packets from their server at 192.168.75.220. I am unable to see
any of their ping packets using pfSense's packet capture tool. I have
played with 1:1 nat and tried every combo I can think of and have not
come up with a working way to see their packets. I have googled and
found several pfsense docs but am not able to come up with a working
answer.
Just not even sure what you guys need from me to help troubleshoot this.
Thanks in advance,
Lyle Giese
LCR Computer Services, Inc.
_______________________________________________
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
