Bridged VM not accessible from VPN whereas all the lan is

brunoc68

Dear all,

I have a networking issue (I suspect a bug) with the following situation :

One Linux serveur with the following :
- eth0 (192.168.0.1/24=lan) and a virtual host (192.168.0.2) (Virtualbox, bridge mode with eth0)
- eth1 (internet connexion dedicated to OpenVPN)
- tun0 (OpenVPN server)
- eth2 (internet connexion for web browsing)
This server is the router / gateway for the lan.

The problem :
- linux server 192.168.0.1 can access any device (lan + vpn clients + internet + VM)
- lan can access linux server + VM + vpn clients + internet
- VPN clients can access lan except VM : there is no answer while telnet 192.168.0.2
- VM can not access VPN client

I want VPN client to access VM and vice versa.

The tests I did :
- VM can ping tun0 on linux server
- VPN client can ping tun0 on linux server
So it looks like the packets can not be routed from tun0 to the VPN and vice-versa but only when the VM is involved.

Any clue what the problem could be ?

This situation is very similar to this (not solved) one : https://forums.openvpn.net/post24533.html?hilit=virtualbox%20bridge%20problem#p24533

Thanks in advance,
Bruno

Mimiko

VirtualBox have some issues with routing from virtual interfaces other than its own. Try to do an update for VirtualBox. Also try asking for help on their forums.