We have a pfSense 1.2 setup at 2 offices that maintain an IPsec VPN
connection. The systems at each each can ping/access systems at the
other end. In addition, systems at each end can
ping/ssh-into/web-connnect-to the pfSense systems at both ends.
However, while ssh'd into either pfSense system, the other pfSense system
can't be ping'd/etc.
I'm assuming this is the same reason that TinyDNS can't sync from one of
the pFSense systems to the other.
Both sides have rules to allow all LAN-based traffic via IPsec tunnel and
it works for all LAN-connected systems but not the pfSense system,
itself. I've tried everything I can think of but can't seem to get any
kind of rule/route specified that'll enable the pfSense system, itself,
to communicate to the pfSense system at the other end of its IPsec tunnel.
Is there some way to route the pfSense router's LAN interface to the
remotely VPN'd pfSense router's LAN interface (i.e., via it's own IPsec
tunnel)?
--
-----------------------------------------------
Bryan Derman Derman Enterprises Incorporated
http://www.derman.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
