This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: IPSEC and libipsec


On Mon, Nov 24, 2003 at 11:02:15AM -0000, Lee Davies wrote:
> Does this mean ECOS can support VPN?

Err, possibly. Like i said, this is work in progress. There is
currently no code to actually setup IPSEC. So if you can somehow
persuade the network stack to use IPSEC it might be possible. Also, as
it says in the documentation, the network stack parts are quite
old. There could be interopibility problems with current generation
IPSEC code. It won't be until racoon is running and we run some tests
that we will know how well IPSEC works.

     Andrew
 
> Regards,
> 
> Lee
> 
> -----Original Message-----
> From: ecos-patches-owner@sources.redhat.com
> [mailto:ecos-patches-owner@sources.redhat.com]On Behalf Of Andrew Lunn
> Sent: 22 November 2003 12:55
> To: eCos Patches
> Subject: IPSEC and libipsec
> 
> 
> Hi Folks
> 
> Attached is a rather large patch which add back the IPSEC code from
> the original FreeBSD network stack and adds a new package containing
> libipsec. In order to use this new code, you also need the package
> bsd_crypto. This package contains the actual crypto functions. It is
> distributed independently and can be found in
> ftp.ecoscentric.com/pub/contrib
> 
> This is currently work in progress. I've run some of the normal
> network tests to check i've not broken any normal functionality of the
> FreeBSD stack. I've also run the libipsec test program. I have not yet
> actually used IPSEC in real communications between hosts. To do that i
> need racoon which i currently have not done anything with.
> 
>      Andrew
> 
> 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]