{"id":9233,"date":"2024-02-29T13:09:38","date_gmt":"2024-02-29T13:09:38","guid":{"rendered":"https:\/\/cheapwindowsvps.com\/blog\/step-by-step-guide-to-installing-wireguard-vpn-on-opnsense-firewall\/"},"modified":"2025-01-20T11:34:16","modified_gmt":"2025-01-20T11:34:16","slug":"step-by-step-guide-to-installing-wireguard-vpn-on-opnsense-firewall","status":"publish","type":"post","link":"https:\/\/cheapwindowsvps.com\/blog\/step-by-step-guide-to-installing-wireguard-vpn-on-opnsense-firewall\/","title":{"rendered":"Step-by-Step Guide to Installing WireGuard VPN on OPNsense Firewall"},"content":{"rendered":"
If you are employing an OPNsense firewall, the option to configure WireGuard as a VPN server instead of OpenVPN is a viable option. WireGuard’s clients are available for all major operating systems, proving very fast and lightweight. This can easily be installed as an OPNsense extension and configured via the web console.<\/div>\n

For implementing a VPN Infrastructure with WireGuard on OPNSense, the following steps have to be executed:<\/p>\n

    \n
  1. Install WireGuard<\/li>\n
  2. Construct and configure a WireGuard instance<\/li>\n
  3. Implement a network interface for the VPN server<\/li>\n
  4. Develop a firewall rule for VPN<\/li>\n
  5. Download and calibrate WireGuard client<\/li>\n
  6. Classify clients on the VPN server<\/li>\n
  7. Examine the connection to the WireGuard server<\/li>\n<\/ol>\n

    How to integrate WireGuard as an extension<\/h2>\n

    WireGuard VPN needs to be installed initially via System => Firmware => Extensions<\/em>. The label for this is os-wireguard<\/em>. Post installation, you can find a new item titled WireGuard<\/em> under the VPN<\/em> menu. If this is not visible, you could try refreshing your browser.<\/p>\n

    WireGuard is installed as an OPNsense extension<\/a><\/p>\n

    Creating a new WireGuard instance<\/h2>\n

    First off, you should create a new WireGuard server on the Instances tab, which is found under VPN => WireGuard<\/em>. This can be done by clicking the ‘+’ sign. It is possible to run multiple servers on an OPNsense firewall with WireGuard – give your new server a name that will appear on the interface.<\/p>\n

    <\/div>\n

    Configuring a new WireGuard server<\/p>\n

    For Listen Port<\/em>, specify the TCP port on which the VPN server will listen for requests. This must also be unlocked in the firewall later. For Tunnel address<\/em>, enter the subnet where the VPN interface and the clients will be located.<\/p>\n

    In our example, we work with the subnet 172.16.2.1\/24, where the VPN interface receives the IP address 172.16.2.1.<\/p>\n

    All other fields do not need to be filled. You can disable routes here if you want to create the routing rules yourself. After saving the server’s configuration in OPNsense, click Apply<\/em>.<\/p>\n

    Overview of the created WireGuard instances<\/a><\/div>\n

    OPNsense automatically generates a public key for the VPN server. The key is later needed for the handshake with the clients.<\/p>\n

    If you open the server’s configuration again, the public key and private key fields are automatically filled in. Copy the key to a text file because we will need it later.<\/p>\n

    Then, you can activate WireGuard under General<\/em>, which must be confirmed again by applying.<\/p>\n

    Activating the WireGuard server on OPNsense<\/a><\/p>\n

    Activating the WireGuard server on OPNsense<\/p>\n

    Configuring network interfaces for WireGuard<\/h2>\n

    To connect the VPN with OPNsense, the configuration of the VPN interface is required under Interfaces<\/em>. Under Assignments<\/em>, the existing interfaces are visible. Here, create the new interface and assign it to the WireGuard VPN.<\/p>\n

    Assigning an interface to the VPN server<\/a><\/p>\n

    Assigning an interface to the VPN server<\/p>\n

    By clicking on the new interface, the window with its configuration opens. Here, activate it via the respective checkbox. Moreover, I recommend setting Prevent interface removal<\/em> to avoid accidental deletion.<\/p>\n

    Configuration of the network interface for the VPN server<\/a><\/p>\n

    Unbound DNS can be set up on OPNsense for name resolution in the internal network.<\/p>\n

    OPNsense also offers a DNS service<\/a><\/p>\n

    Creating firewall rules for WireGuard VPN<\/h2>\n

    Next, create a rule under Firewall => Rules => WAN<\/em> that allows access to the VPN server over the internet.<\/p>\n

    Select the action Allow<\/em> and the interface WAN<\/em> when defining a new rule. For Destination<\/em>, choose the option in<\/em>; for TCP\/IP Version<\/em>, select IPv4; for Protocol<\/em>, select UDP<\/em>; and for Source<\/em>, select Any<\/em>.<\/p>\n

    It is crucial to select the Destination port range<\/em> under from<\/em> and for to<\/em> to set the port number given during the server’s creation. The setting can be found under VPN => WireGuard<\/em>. At this point, you can also activate the option Log packets that are handled by this rule<\/em>.<\/p>\n

    Defining firewall rules for the VPN network<\/a><\/div>\n

    With another rule, you specify how the traffic of the VPN clients is forwarded to the internal network. When clients connect via VPN, they initially find themselves in the VPN network, whose IP range was specified during the creation of the server.<\/p>\n

    From this point, they need to access the respective applications in the local network. The configuration of these rules can be done through Firewall => Rules => <WireGuard Interface><\/em>. It’s recommended to design these rules in such a way that VPN clients can only access the necessary devices.<\/p>\n

    For doing so, when creating a new rule, select the action Allow<\/em> and the interface of WireGuard. For the Direction<\/em> option, choose in<\/em>, and for the Protocol<\/em> option, choose any<\/em>. Concerning Source and Destination<\/em>, you can select any<\/em> if you wish to allow access to all resources in the network.<\/p>\n

    <\/div>\n

    Firewall rule controlling access to internal resources<\/p>\n

    Installing and adjusting WireGuard clients<\/h2>\n

    Afterward, install the WireGuard client, for example, on Windows<\/a>. Then, you can configure a new connection by adding a tunnel.<\/p>\n

    In the first step, assign a name for the VPN connection. Save the value for Public Key<\/em> again in a text file, as it needs to be entered on the server later.<\/p>\n

    Under Interface<\/em>, provide the IP address of the client in the VPN subnet. This was pre-determined during the set up of the VPN server. For illustration, we allot the IP address 172.16.2.11 to the Windows PC. For DNS, input either an internal DNS server or the IP address of the VPN server.<\/p>\n

    Under PEER<\/em>, provide the name or the IP address of the VPN server, along with the port under Endpoint<\/em>. Under AllowedIPs<\/em>, identify which IP addresses should route the traffic via the VPN tunnel. Here, the subnet 10.0.0.0\/16 corresponds to the OPNsense firewall’s LAN.<\/p>\n

    If you decide that all traffic should direct through the VPN post connection, including the internet, you should provide 0.0.0.0\/0 here.<\/p>\n

    For the PublicKey<\/em>, input the public key of the WireGuard VPN server, which you had stored earlier in a text file. The public key of the client goes into the WireGuard server’s configuration.<\/p>\n

    Configuring VPN clients in WireGuard<\/h2>\n

    Configure the VPN clients on the OPNsense web interface on the Peers<\/em> tab under VPN => WireGuard => Settings<\/em>. Create a new client by clicking the plus sign and setting its name.<\/p>\n

    Copy the client’s public key into the Public Key<\/em> field. For Allowed IPs<\/em>, enter the IP address assigned to the client in its configuration.<\/p>\n

    Creating and configuring a VPN client<\/a><\/p>\n

    A pre-shared key can be helpful in a production environment, but we omit it in the test environment. Save to create the client.<\/p>\n

    Then, switch to Instances<\/em> and open the settings of the WireGuard server. Under Peers<\/em>, check the new client so the server accepts it upon connection.<\/p>\n

    Here is a visual guide<\/a> of allowing a new client through the OPNsense console.<\/p>\n

    Afterward, I recommend restarting the WireGuard service via Lobby => Dashboard<\/em>.<\/p>\n

    Establishing a connection with the VPN client<\/h2>\n

    You can now test a connection on the client. The value for received and sent data should increase. If it remains at 0, the handshake did not work.<\/p>\n

    In this case, check if the server and client’s public key have been configured correctly. Also, the client must be entered in the server’s settings under Peers.<\/p>\n

    The protocol shows information about the connection, and the OPNsense firewall displays the connections under VPN => WireGuard => Diagnostics<\/em>. Here, all active clients are visible.<\/p>\n

    <\/div>\n

    Overview of connected VPN clients<\/p>\n

    Summary<\/h2>\n

    To install WireGuard on OPNsense, you need to add an extension. After configuring its interface, the name resolution is handled with Unbound DNS<\/em>, another OPNsense service.<\/p>\n

    \n

    Subscribe to 4sysops newsletter!<\/h2>\n<\/div>\n

    Firewall rules determine which resources the clients can access. Finally, the VPN clients are set up, for which the server’s public keys and clients must be entered into each other’s configuration.<\/p>\n","protected":false},"excerpt":{"rendered":"

    If you are employing an OPNsense firewall, the option to configure WireGuard as a VPN server instead of OpenVPN is a viable option. WireGuard’s clients are available for all major operating systems, proving very fast and lightweight. This can easily be installed as an OPNsense extension and configured via the web console. For implementing a […]<\/p>\n","protected":false},"author":1,"featured_media":9234,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[92,167,133,114],"tags":[],"class_list":["post-9233","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles","category-firewall","category-networking","category-security"],"_links":{"self":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/9233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/comments?post=9233"}],"version-history":[{"count":1,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/9233\/revisions"}],"predecessor-version":[{"id":10452,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/posts\/9233\/revisions\/10452"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/media\/9234"}],"wp:attachment":[{"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/media?parent=9233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/categories?post=9233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cheapwindowsvps.com\/blog\/wp-json\/wp\/v2\/tags?post=9233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}