I'm running 1.2.3
I have an IPsec tunnel to another site, which closes unless there is
traffic I want it up 24/7 so I put a remote IP in the keep alive,
automatically ping host section of the setup.
It still behaves the same way. Is this to be expected (known bug or
something) or have I done
On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote:
I'm running 1.2.3
I have an IPsec tunnel to another site, which closes unless there is traffic
I want it up 24/7 so I put a remote IP in the keep alive, automatically
ping host section of the setup.
It still behaves the same
:* pfSense support and discussion
*Onderwerp:* [pfSense] ipsec tunnel closes
** **
Hi Nick,
** **
We have many IPSEC tunnels to our customers using pfSense 1.2.3 and also
on 2.0 without any problems.
What could be the problem in your case is the lifetime of phase 1 and 2
On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote:
I'm running 1.2.3
I have an IPsec tunnel to another site, which closes unless there is
traffic I want it up 24/7 so I put a remote IP in the keep alive,
automatically ping host section of the setup.
It still behaves the
Nick Upson
On 19 December 2011 15:00, Ian Bowers iggd...@gmail.com wrote:
On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote:
I'm running 1.2.3
I have an IPsec tunnel to another site, which closes unless there is
traffic I want it up 24/7 so I put a remote IP in the
one thing to check is what IP that ping ends up getting sourced from, and
making sure it's in the right subnet. tcpdump should work
I'm thinking one reason it can get closed is if IP/50, UDP/500, and/or
UDP/4500 arent allowed in both directions on the other end. when
requesting VPN ports from
