this is an old bug but still a problem, and one that
would be nice to see fixed in the 3.0 release.
the documentation of vtun is, unfortunately, rather
terse. An explanation of what the more obscure tunnel
types (pipe and tty) do, and especially what they are
good for and how to use them, would be nice.
Also, advice on building virtual ethernet segments
would be welcome. Some questions:
- what's the best way to make a small private network
that has a dynamic connection to the internet, part of
a company ethernet? The company network has global IPs;
should I assign IPs from that range to the private
network and then bridge? Or should I create a simple
p-t-p tunnel between the router of the private net and
the router of the company net, and route?
- how about making several disjunct ethernets appear to
be a single segment? It's easy if you don't have to
have hosts with global IPs in them, but what if you do?
Is there a better way than to make those dual-homed
(with a virtual interface in the VPN and another with a
The sourceforge site for vtun does have a single
example setup; maybe you could package and ship that,
too. The rest of this bug report is probably a case for
Log in to post a comment.