|
|||||||||||
|
Re: [Users] Using native pluto with native Linux ipsec...
From: Sam Sgro <sam(at)freeswan.org>
Date: Fri Oct 10 2003 - 15:47:52 EDT -----BEGIN PGP SIGNED MESSAGE-----
On Friday 10 October 2003 08:01, Giacomo Mulas wrote:
The algo patches have not been updated for 2.03. However, I know that Herbert did make available some patches for the SuperFreeS/WAN source; these should allow you to use AES with the native kernel code: http://gondor.apana.org.au/~herbert/freeswan/sfs/2.00rc8/ I'm certain that SFS have a 2.03 based release soon enough. > 2) I had configured some iptables firewalling rules on the basis of how
They'll go through your iptables rules twice incoming. However, you won't be able to rely on the virtual IF to find ipsec sourced/destination traffic. Best method: use the default _updown script to insert rules based on IP address, and only allow that traffic through the tunnel. Read /usr/local/lib/ipsec/_updown for tips. You can either modify that script, or reference your own, custom _updown. > 3) well, this is more like a comment: I had compiled ah_key as a module,
You mean af_key, right? _startklips should be doing the right thing: if test ! -f $ipsecversion && test ! -f $kamepfkey then
# statically compiled KLIPS not found; try to load the module
insmod ipsec
if test ! -f $ipsecversion && test ! -f $kamepfkey then
modprobe -v af_key
-----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: For the matching public key, finger the Reply-To: address.
iQCVAwUBP4cM8EOSC4btEQUtAQEE9QP+KrRexzHyV7cZkPzwZI7HvFQBuItNYBv6
QKdCp3ETczZWsSBsBO2ZVahbmJASsOG6+7mxyU64/kTc1l2Yfw1fqVYw/LjWL45U
lfE2oBHkEAnvkJBD9D4vRwx3lP3J9IeJlwtkXLMF3gtUz8f2dvKIQgYSHgSkvv0d
o/sD+/iXjWg=
FreeS/WAN Users mailing list users@lists.freeswan.org https://mj2.freeswan.org/cgi-bin/mj_wwwusr Received on Fri Oct 10 15:58:37 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:02:05 EDT |
||||||||||
|
|||||||||||