|
|
On 10/5/05, James Yonan <jim@xxxxxxxxx> wrote:
>
>
> While the basic load balancing and failover capability provided by putting
> multiple "remote" directives on the client is almost a clustering
> solution, it falls a bit short when you want (for example) a client to
> keep the same IP address even when connecting to a different server, or
> when clients are serving as a VPN gateway for a local, private LAN.
>
> To make this work, we need a dynamic routing capability so that when a
> user with a given VPN IP address ('IP') connects from server 'A'
> to server 'B', the server-side routers will be aware that return packets
> to IP must now be routed through server 'B' rather than server 'A'.
>
> One way to make this work would be to use a dynamic routing protocol such
> as RIP2 or OSPF. When the user connects to server 'B', a RIP2 message
> would be multicast, telling all the local routers of the new gateway for
> 'IP'.
>
> This would require adding some code to OpenVPN to advertise its internal
> routing table to local, neighboring routers using RIP2 or OSPF.
OSPF gets my vote.
--
Leonard Isham, CISSP
Ostendo non ostento.
|