up vote 4 down vote favorite
2
share [g+] share [fb]

i'm thinking about using dynamic routing [ OSPF or RIP ] via OpenVPN tunnels. right now i have few offices connected in full mesh, but this is not scalable solution as we add more locations. i would like to avoid situation when plenty of internal traffic is affected if one of two vpn termination points that i plan to use is down.

do you have similar configuration working in production? if so - what routing daemon did you use - quagga? something else? did you encounter any problems?

thanks!

link|improve this question
82% accept rate
feedback

1 Answer

up vote 1 down vote

We currently have multiple instances of OpenVPN AS running with static routes pointing to each one. We assigned a /24 subnet to each OpenVPN server. Currently we have users manually pointed to each server but you could use a variety of technologies to point users to the correct one.

The only issue here is that in the event an OpenVPN serve goes down, users will need to connect to another server to get traffic. This is due to the fact that we are redistributing a static route to the OpenVPN server since OpenVPN AS doesn't support OSPF.

There are open source routers that support OpenVPN such as Vyatta but we prefer the web interface of OpenVPN AS.

link|improve this answer
thanks. i'm not really looking for web interface... ; up to my knowledge vyatta uses quagga as underlying routing engine; i think that openvpn in tap mode can support anything including ospf. – pQd Mar 16 '11 at 8:06
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.