Hi All,
I'm getting the following behavior on bering 2.3. I just rebooted my
firewall (which was working
beautifully) and now I'm having problems with my windows VPN. Here's
what I get.
Pinging [192.168.0.13] with 32 bytes of data:
Negotiating IP Security.
Negotiating IP
Hello Julie,
Hi All,
I'm getting the following behavior on bering 2.3. I just rebooted my
firewall (which was working beautifully) and now I'm having problems with
my windows VPN. Here's what I get.
Pinging [192.168.0.13] with 32 bytes of data:
Negotiating IP Security.
Hi
interesting, so the KLIPS not working will break windows VPN but not VPN
for linux boxen? i have a remote user using linux VPN and he's fine.
curious.
--jsl
Eric Spakman wrote:
Hello Julie,
Hi All,
I'm getting the following behavior on bering 2.3. I just rebooted my
firewall
Hi Julie,
Hi
interesting, so the KLIPS not working will break windows VPN but not VPN
for linux boxen?
I'm not sure about that. If you never change rp_filter before (left it
in its default enable state) and it was working, I doubt if that's the
problem. The KLIPS may not work message is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julie S. Lin wrote:
Hi
interesting, so the KLIPS not working will break windows VPN but not VPN
for linux boxen? i have a remote user using linux VPN and he's fine.
curious.
The KLIPS warning, and the route filtering, is a problem with some
