[Openswan Users] OpenSWAN load balancing setup

plug bert plugbert at yahoo.com
Thu Jul 8 21:28:25 EDT 2010


bump ...thanks



--- On Wed, 7/7/10, plug bert <plugbert at yahoo.com> wrote:

> From: plug bert <plugbert at yahoo.com>
> Subject: Re: [Openswan Users] OpenSWAN load balancing setup
> To: users at openswan.org
> Date: Wednesday, 7 July, 2010, 8:15 PM
> bump...thanks
> 
> 
> 
> --- On Tue, 7/6/10, plug bert <plugbert at yahoo.com>
> wrote:
> 
> > From: plug bert <plugbert at yahoo.com>
> > Subject: [Openswan Users] OpenSWAN load balancing
> setup
> > To: users at openswan.org
> > Date: Tuesday, 6 July, 2010, 2:49 PM
> > Hello,
> > 
> > 
> >     Please advise if the following setup will
> > work; end goal is to distribute VPN traffic over the
> two
> > ISPs, and possibly set up automatic failover.
> > 
> >     Say that the OpenSWAN box is configured as
> > follows:
> > 
> >                
> >              
> >    +------------>(eth0) ISP1
> >                
> >              
> >    |
> > subnet1 <-->(eth2) OpenSWAN box--+
> >                
> >              
> >    |
> >                
> >              
> >    +------------>(eth1) ISP2
> > 
> > If i configure load balancing over the two links via
> > iproute command
> > 
> > ip route add default scope global nexthop via $ISP1
> dev
> > eth0 weight 1 nexthop via $ISP2 dev eth1 weight 1 
> > 
> > 
> > and set 
> > 
> > leftnexthop=%defaultroute
> > 
> > 
> > will this do the job? tia
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Users at openswan.org
> > http://lists.openswan.org/mailman/listinfo/users
> > Building and Integrating Virtual Private Networks
> with
> > Openswan: 
> > http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
> > 
> 
> 
> _______________________________________________
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
> Building and Integrating Virtual Private Networks with
> Openswan: 
> http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
> 




More information about the Users mailing list