[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian VPN IPSEC interface



On Tue, Feb 17, 2009 at 10:03:40AM +0100, Martin Hilpert wrote:
> okay i am a native german speaker so there was a mistake in the last post,
> 
> my setup looks like this
> 
> 
> 
> 
> Site A ( cisco 1841 ) => Openswan A  ( Debian)
> Site B ( cisco 1841 ) => Openswan A  ( Debian)
> Site C ( cisco 1841 ) => Openswan A  ( Debian)
> Site D ( cisco 1841 ) => Openswan A  ( Debian)
> Openswan B(Debian) => Openswan A  ( Debian)
> Openswan C(Debian) => Openswan A  ( Debian)
> 
> Site A ..D  ip:10.30.0.0/16 ..10.33.0.0/16
> Openswan B  ip 10.0.0.0/16 .. 10.20.0.0/16
> Openswan C ip 192.168.0.0/24
> 
> so if the VPN is up i need quagga to manage the routing stuff.
> 
> now i tryed to make a kernel-module for KLIPS to get a ipsec0 device.
> 
> but i want for all tunnel a seperate device but only get one.

why do you need a ipsecX device  ?  the ipsecX device where the old way
of doing ipsec.

> 
> 
> martin 
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 

-- 
"If affirmative action means what I just described, what I'm for, then I'm for it."

	- George W. Bush
10/18/2000
St. Louis, MO
during the third presidential debate

Attachment: signature.asc
Description: Digital signature


Reply to: