3,250
edits
Changes
Jump to navigation
Jump to search
Line 42:
Line 42: + + + + + − ==== Configure ====+ Line 56:
Line 61: − If you already run the [[OpenVPN_Bridge]] contrib, you can just copy all the certificates:+ − cp -a /etc/openvpn/bridge/{priv,pub} /etc/openvpn/routed/ Line 105:
Line 109: + Line 116:
Line 121: − Line 245:
Line 249: − + −
→Default key properties
you will then have to configure by hand
you will then have to configure by hand
If you already run the [[OpenVPN_Bridge]] contrib, you can just copy all the certificates:
cp -a /etc/openvpn/bridge/{priv,pub} /etc/openvpn/routed/
</tab>
</tab>
</tabs>
</tabs>
=== Configure ===
This contribs is really minimal and doesn't have a panel to configure everything. You have to configure all by hand. Except on SME10 if you already have smeserver-openvpn-bridge installed and configured.
This contribs is really minimal and doesn't have a panel to configure everything. You have to configure all by hand. Except on SME10 if you already have smeserver-openvpn-bridge installed and configured.
* /etc/openvpn/routed/priv/takey.pem (an optional shared key)
* /etc/openvpn/routed/priv/takey.pem (an optional shared key)
and an available port to bind to.
==== Configure as running in parallel of bridge contrib ====
==== Configure as running in parallel of bridge contrib ====
Not needed for SME10, the contrib does it for you.
#install
#install
# signale event to regenerate all you need
# signale event to regenerate all you need
signal-event openvpn-routed-update
signal-event openvpn-routed-update
===Client configuration - iOS===
===Client configuration - iOS===
|}
|}
you can also set the property PushRoute to disable to any network in networks db to avoid the contrib to push the network to the client
you can also set the property PushRoute to disabled to any network in networks db to avoid the contrib to push the network to the client
===Workarounds and known issues===
===Workarounds and known issues===