97
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 406:
Line 406: − + − + + + − ==== Virtualbox promiscuous mode ====+ − there is the same thing in virtualbox, you need to give the argument "allow all" in the network tab configuration.+ + +
Added some information about compatibility between bridged networkin and virtual machines vSwitch when Sme is installed as VM
=== Notes ===
=== Notes ===
==== VMWare promiscuous mode ====
==== OpenVPN and SME installed in virtual machine - VMWare promiscuous mode ====
By default for at least ESX(i)3.5 and 4 VMWare rejects packets in promiscuous mode on the vSwitch, which will cause trouble with OpenVPN in bridge mode. To correct this in VMWare set:
By default for all version of ESX(i) starting from 3.5 to 7.0 (current in february 2020) VMWare rejects packets in promiscuous mode on the vSwitch, which will cause trouble with OpenVPN in bridge mode. The main symptom is that after successful authentication from your remote client you can ping/reach only the OpenVPN server while any other ip address on the LAN can't be pinged/reached. To correct this in VMWare set:
Configuration > Networking > your vSwitch: Properties > Ports-tab > vSwitch > Edit > Security-tab > Promiscuous mode: accept
Configuration > Networking > your vSwitch: Properties > Ports-tab > vSwitch > Edit > Security-tab > Promiscuous mode: accept
For ESXI hypervisor still working with vSphere client:
[[File:Promiscuous mode - Esxi.jpg|left|thumb|786x786px]]
For ESXI greater than 6.5 using webui:
==== OpenVPN and SME installed in virtual machine - Virtualbox promiscuous mode ====
There is the same thing in virtualbox, you need to give the argument "allow all" in the network tab configuration.
virtual machine > configuration > network > adapter 1
virtual machine > configuration > network > adapter 1
