Route all traffic through Araknis Router when using Open VPN

Route all traffic through Araknis Router when using Open VPN

When using Open VPN with an Araknis router you may wish to amend the configuration so that all traffic passes through the VPN, especially if you are connecting from overseas and need to present a local IP address to the website you are connecting to.

To do this:

Open the .ovpn config file that is downloaded from the router in Notepad or Notepad++, and add “redirect-gateway def1” to the top section as shown below.  This should route all traffic through the VPN.



    • Related Articles

    • How to Access Other VLAN Segments using Open VPN

      When VPN tunnelling into a network you will by default land on the main VLAN segment. If you want to land on a different segment you edit the Open VPN config file to specify this.  Let us say the the main LAN on the clients site in this instance is ...
    • How to set up an Araknis 310 Switch to use with AVProEdge MXNet

      We always recommend using the AVProEdge switch range when installing an MXNet system. These switches are very high end and come with a 10 year warranty and are pre configured out of the box to work with MXNet. However, if budget is a concern and you ...
    • Araknis Spanning Tree

      By default Spanning Tree, is enabled in Araknis 210 and 310 switches, but the Root Bridge is usually an overlooked element.  Spanning Tree Protocol (STP) is a Layer 2 protocol that decides the best path for LAN traffic when multiple options exist, ...
    • Araknis/OvrC devices cant be reached via dashboard when using ISP router

      A new installation of an OvrC hub and 4x AP's on a site with latest SkyQ hub, OvrC dashboard works fine but you cant connect to Araknis devices in the device list you get the following error message the ports required to be opened are 53, 443
    • Araknis Spanning Tree CIST

      This was highlighted by a SnapOne TierII engineer, which we have summarised into the below information.  Enabling Spanning Tree protocol is fine, but you aren't telling the switch what ports need to participate in the Spanning Tree. In the STP menu ...