Tom Bin said:
>
> It's really a good idea.
> I think the syntax is good enough...,
> maybe you can take the metric(route cost) into consideration.
That's a good idea. It looks like most IP stacks support metric, I see that
Windows does too so that is good.
> I would like to suggest the route
It's really a good idea.
I think the syntax is good enough...,
maybe you can take the metric(route cost) into consideration.
I would like to suggest the route is added once the vpn is up
and deleted when the vpn is down.
Moreover, is it possible to have multiple routes added ?
> I would like t
I would like to implement a --route option that will be a proxy for the route
command, similar to the way that the --ifconfig option is a proxy for the
ifconfig command.
The goal would be to present a kind of least-common-denominator route
functionality which is basic enough to be portable across
> > What I need right now in order to make the TAP version of --ifconfig work
> > correctly, is the correct ifconfig command syntax for setting the IP address
> > and netmask of a TAP device, on all the OSes which OpenVPN supports. I've
> > already coded templates for Linux and Windows, but I stil
On Wed, 03 Sep 2003, James Yonan wrote:
> One of the nice things about the --ifconfig option is that it lets you set TUN
> adapter endpoint addresses (i.e. the virtual IP addresses for each end of the
> tunnel) in a platform independent manner -- OpenVPN then translates the
> --ifconfig option to
