3,070
edits
Changes
From SME Server
Jump to navigationJump to search→Notes
yum remove smeserver-phpki phpki smeserver-bridge-interface perl-Net-OpenVPN-Manage perl-Net-Telnet
yum remove smeserver-phpki phpki smeserver-bridge-interface perl-Net-OpenVPN-Manage perl-Net-Telnet
==Notes ==
=== OpenVPN and SME installed in virtual machine - VMWare promiscuous mode ===
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:
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
[[File:Promiscuous mode - Webui.jpg|border|frameless|784x784px]]
[[File:Promiscuous mode - Webui.jpg|border|frameless|784x784px]]
=== 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.
There is the same thing in virtualbox, you need to give the argument "allow all" in the network tab configuration.
[[Image:virtualbox-Sme8-Settings.png]]<br />
[[Image:virtualbox-Sme8-Settings.png]]<br />
=== OpenVPN and SME installed in virtual machine - Other hypervisors ===
It's documented that you can experience such problems in other hypervisors like OVirt, Proxmox, XEN or others. Keep in mind to search for equivalent settings concerning "promiscuous mode" of vSwitch.
It's documented that you can experience such problems in other hypervisors like OVirt, Proxmox, XEN or others. Keep in mind to search for equivalent settings concerning "promiscuous mode" of vSwitch.
=== Transparent proxy settings ===
{{Note box|Keep in mind you need to disabled your transparent proxy else your host can no longer browse the http protocol.}}
{{Note box|Keep in mind you need to disabled your transparent proxy else your host can no longer browse the http protocol.}}
