On Mon, 2010-04-19 at 14:07 +0200, mayak-cq wrote: > On Mon, 2010-04-19 at 07:27 -0400, Jim Pingle wrote: > > On 4/19/2010 5:40 AM, mayak-cq wrote: > > > i have a pfsense box with two interfaces (not sharing the same media or > > > gateway). > > > > > > i need for openvpn to use a specific interface/gateway to bind to. > > > > > > as packets are internally generated, standard policy routing won't work > > > here -- i tried the openvpn --bind option to no avail. > > > > Try adding 'local x.x.x.x;' to the custom options box on the config, > > that should allow it to use a specific local IP on the box from which to > > source its traffic. > > brain dead -- i meant "local" instead of "bind" > > turns out that the problem is running 2 openvpn instances -- if i use > "local" for different openvpn declarations, its doesn't seem to work. > > cant reboot the unit until tonight. > > have you successfully bound openvpn to two different adapters in > pfsense?
ok -- so i have used the "local" option for each openvpn instance, but the openvpn client process still uses the lowest numbered gateway and starts the packets going out the wrong interface. i guess the question is: how do you tell openvpn what gateway to use to establish the vpn? one would have thought that if the openvpn process was bound to sis4's interface, that it would have used sis4's gateway to send packets. indeed, it does not. badly need help! thanks m --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
