Charles, it appears you are FreeSWAN very aware. I'll appeal
to you first but if you don't want to handle I'll turn to freeswan
because technically I'm working on non LEAF right now.
And it looks like I'm going to have quite a few questions.
IPSec(1.5) works like a charm on Eiger but I wanted to do thorough
QA on 2.4 with iptables before going to LEAF 2.4 ( Bering ?)
Netfilter is very different from the 2.2 stack.
Anyway I loaded freeswan 1.94 and 1.96 on RH7.2(linux 2.7) and
am seeing strange things:
1: One scenario is getting a connection to my office from dialup
at home(which was tough) but then don't have a tunnel, can't telnet
to machines behind the router.
But What I observe that is really weird is on the corp. gateway the packets
are hitting the input chain instead of the forward chain.
It seems that would have been proper on 2.2 but not 2.4.
Packets destined thru the box are not supposed to traverse the input chain.
Perhaps that is different with ipsec ???
2. The other scenario is a Lan Lab. One Eiger with ipsec 1.5, one Red Hat
with ipsec 1.94 on a dedicated lan.
These 2 units create a tunnel for 2 other machines to talk to each other.
They talk allright but not thru ipsec, they are routing around the tunnel.
The eiger machine builds its routing table correctly.
The RH 2.4 with ipsec 1.94 does not correctly add an ipsec route when the
connection
comes up. ???
I am studying the _updown script to understand this but I was wondering if you
have
seen this phenom ?
thanx.
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
