As an added note on this, I don't know if I made myself too clear.
Being that the tunnel only forms when pinging from the left, this is a
big problem for us, since I can't do it during working hours because
users (on the right) sessions get severed.
Our business structure has sessions initiating on the right end, but
m0n0wall only builds the tunnel when pinging from the left.
After that, everything seems fine.
I don't know what added info to include on this issue, but will be glad
to provide it if needed.
On Fri, 2008-04-18 at 21:57 -0400, Joe wrote:
> I have an ipsec 1.3b10 - 1.3b11 tunnel running between two static IP
> I also have a m0n0wall server at home where I have a non-static DSL
> When I power up my home systems, I check the home IP address of my
> m0n0wall server here. Then I log into one of the static IP m0n0wall ends
> of the tunnel and change the ipsec page to save my home IP address as a
> static IP end of a new tunnel.
> I save it. I "apply changes". Then I have a tunnel from home and I'm
> The problem is that when I press "apply changes" to save the ipsec page,
> the original tunnel is severed and won't come up until something like a
> ping is issued from one end only.
> If something like a ping or telenet session is issued from the second
> end, it hangs until the tunnel is brought up from the first end.
> Any help would be appreciated. m0n0wall is appreciated.