On Sun, 13 Jun 2021 14:11:53 -0400 David W. Hodgins wrote:
On Sun, 13 Jun 2021 11:36:57 -0400, Markus Robert Kessler <[email protected]> wrote:
Hi all,
first: reason for asking this here is, that the behaviour of VirtualBox
seems to heavily depend on the target for which this is packaged.
I have to set the parameters of VirtualBox in the way that (vpnc) tun0
is available for the client OS which is booted from VirtualBox.
Unfortunately, none of the tricks from stackoverflow etc., like
"activate IP forwarding" and so on, worked.
Any idea how to get this to work?
I suspect, with vpnc running on the host that the vbox guest network
will have to use bridged networking to see the tun0 network interface.
I've never tried it though, and have very limited experience with using
a vpn.
Hi Dave, thanks for answering.
Well, using bridged mode, I was fully surprised to NOT see tun0 in the
list of interfaces, just eth0 ("enps..."). There was no working route
through the VPN tunnel.
But, finally I selected NAT-mode for the client, established a VPNC
connection on the host machine (mga7-x64) and the remote target was
reachable.
I still don't know, why, but it works...
Thanks again,
best regards,
Markus
--
Please reply to group only.
For private email please use
http://www.dipl-ing-kessler.de/email.htm
--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)