Changes

From SME Server
Jump to navigationJump to search
111 bytes added ,  21:08, 17 March 2020
Line 475: Line 475:     
https://wiki.contribs.org/OpenVPN_Routed
 
https://wiki.contribs.org/OpenVPN_Routed
=== Advanced configuration ===
+
== Advanced configuration ==
    
Some advanced options are not presented in the panel. The goal was to keep the panel as simple as possible as most installations won't need to change advanced settings. But advanced options are still available with some DB keys:
 
Some advanced options are not presented in the panel. The goal was to keep the panel as simple as possible as most installations won't need to change advanced settings. But advanced options are still available with some DB keys:
Line 510: Line 510:  
Once you have configured the service like you want, just run the command
 
Once you have configured the service like you want, just run the command
 
  signal-event openvpn-bridge-update
 
  signal-event openvpn-bridge-update
=== Désinstallation ===
+
 
 +
== Désinstallation ==
 
Pour enlever la contribution, lancer seulement :
 
Pour enlever la contribution, lancer seulement :
 
  yum remove smeserver-openvpn-bridge
 
  yum remove smeserver-openvpn-bridge
Line 516: Line 517:  
Vous pouvez également vouloir retirer les autres dépendances si vous ne les utilisez plus :
 
Vous pouvez également vouloir retirer les autres dépendances si vous ne les utilisez plus :
 
  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 ====
+
==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
Line 528: Line 530:  
[[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 ====
+
=== 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.
Line 544: Line 546:  
[[Image:virtualbox-Sme8-Settings.png]]<br />
 
[[Image:virtualbox-Sme8-Settings.png]]<br />
   −
==== OpenVPN and SME installed in virtual machine - Other hypervisors ====
+
=== 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 ====
+
=== 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.}}
   Line 563: Line 565:     
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-openvpn-bridge|noresultsmessage="No open bugs found."}}
 
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-openvpn-bridge|noresultsmessage="No open bugs found."}}
 +
==Autres articles dans cette catégorie==
 +
{{#ask: [[Category:VPN]]}}
 +
 +
----
 +
[[Category:Administration:VPN]]
 +
[[Category:VPN]]
    
----
 
----
 
[[Category: Contrib/fr]]
 
[[Category: Contrib/fr]]
3,054

edits

Navigation menu