From: Jan J. K. <ja...@ni...> - 2009-04-07 13:58:37
|
Daniel wrote: > Hi there, > > I'm currently using OpenVPN 2.1_rc7 on Ubuntu 8.04 Hardy Heron. > I have three Ethernet interfaces where 2 being WAN, 1 being LAN. > Currently, to get one instance of openvpn (running as client) to use > WAN1, I had to bind it to WAN1's IP address. Similarly, second > instance of openvpn is binded to WAN2's IP. > All this, can be done using the 'local' directive. binding an instance of openvpn to a particular interface does not guarantee that all traffic is flowing through that interface: return traffic to the client will most likely go over the default route. > However, what I've found is that, even if openvpn is running in client > mode, if given the 'local' directive, it will open and listen on its > default UDP 1194 port. > The only way I know, to not listen is to use 'nobind' directive. But > apparently nobind and local directives do not go in tandem. > > Is there a way to force particular instance of openvpn client to use > particular WAN interface? Order is not concerned. As long as two do > not use one WAN interface. > FYI, both instances are logging into same openvpn server, so, I can't > differentiate one instance from another by looking at destination IP > or the PORT number. > the 'local' directive will cause openvpn to bind to the local IP address (and port if given, if not, is uses 1194). In client mode this does not do much... From what I read you are really looking for source routing. Search the openvpn archives on how to route traffic over a particular interface on both client and server side. HTH, JJK |