> > The iptables suggestion is good. But unfortunately it
> > won't work in my scenario. What I want to achieve is to
> > bind OpenVPN on TCP 443 over two WAN interfaces and Apache
> > on TCP 443 over two LAN interfaces (for management traffic).
>
> It should still be possible to use iptables to
Thanks all for your inputs.
The iptables suggestion is good. But unfortunately it won't work in my
scenario. What I want to achieve is to bind OpenVPN on TCP 443 over two WAN
interfaces and Apache on TCP 443 over two LAN interfaces (for management
traffic).
Thanks,
Keyur
> >>
> > openvp
Greetings!
I have a linux box connected to two ISPs and having two LAN facing interfaces.
I would like to bind OpenVPN (in TCP mode) on two WAN facing interfaces only
(not all).
I have tried following in server.conf but no success.
(1) local WAN-1-IP
local WAN-2-IP
(2) local WAN-1-IP W
sourceforge.net, openvpn-devel@lists.sourceforge.net
> Date: Saturday, December 6, 2008, 2:02 PM
> Keyur Pujara wrote:
> >> Which release candidate of 2.1 series is
> recommended for
> >> "Production Use"?
> >>
> >> Cross-Posting on Development m
> > > > Looking for a GA Quality load for 2.1
> series. Would
> > > help to know when it
> > > > might be available.
> > >
> > > What is "a GA Quality load"?
> > >
> >
> > GA refers to "General Availability" -> It
> refers to a release
> > which is "Fit for Production Use".
> ...
>
> Hahah.
