Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    2.5.2 interface not configured

    Scheduled Pinned Locked Moved WireGuard
    5 Posts 4 Posters 901 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      simmarn
      last edited by

      Hi. Using pfSense 2.5.2 and Wireguard package I configured a Wireguard client using the following recepie https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-client.html.

      A difference that I noticed was that IP address was not added to interface automatically (WG_VPN in the recepie). Interface did not have any IP address (IPv4 Configuration Type = None). There were also no GW created (WG_VPN_WGV4).

      I had to set static IP and create GW manually to get it working. Is this a bug in the Wireguard package or a fault in the recepie?

      1 Reply Last reply Reply Quote 2
      • Jim-bob-the-grandJ
        Jim-bob-the-grand
        last edited by Jim-bob-the-grand

        I would like to know what's up here too.

        I tried following those exact instructions and nothing worked in the end. I have seen on other guides you need to assign an interface for it to work but I am unsure exactly why that's the case (especially since I have not had to assign any interfaces for my OpenVPN configurations and they work fine).

        If you got yours working, could you just add a tiny bit more detail about what you did? I would appreciate it.

        L S bthovenB 3 Replies Last reply Reply Quote 0
        • L
          latimeria @Jim-bob-the-grand
          last edited by

          That documentation does not apply to the current WG package. I think the developer is working on it.

          J3455M-E Asus motherboard
          8gb ram (2x 4gb Micron MT8JTF51264AZ-1G6E1)
          128Gb SSD
          Kolink Satellite midi tower case micro-atx
          quad lan card HP NC364T

          1 Reply Last reply Reply Quote 1
          • S
            simmarn @Jim-bob-the-grand
            last edited by simmarn

            @jim-bob-the-grand
            For the Interface WG_VPN I did the following:

            • Enable
              Checked
            • IPv4 Configuration Type
              Static IPv4
            • MSS
              1420

            Ipv4 Address
            The interface address in my .conf file I got from the provider. In the recipe this is tunnel address 10.6.210.2/24

            Then "Add a new gateway"
            The gateway address I am not so sure about. This should be an address that is possible to ping only when tunnel is up. I set up Wireguard on my laptop and did a traceroute. I used the first hop address as the gateway. That worked. I guess it could be 10.6.210.2 here as well. But I haven't tried it.

            Save

            Gateway details can be changed by System -> Routing -> WG_VPNGW -> Edit Gateway
            I had to check Use non-local gateway through interface specific route. since the GW address was not in the subnet and also increase Packet Loss threshold to 50-60% since I had problem with GW failover.

            ba41023f-6375-4477-9f62-2cbad236bc75-image.png

            I hope it helps. Rest of the recipe I was able to follow if I remember correctly.

            1 Reply Last reply Reply Quote 1
            • bthovenB
              bthoven @Jim-bob-the-grand
              last edited by

              @jim-bob-the-grand I've just set up with my VPN provider (vpnunlimited) and wrote an instruction here. I believe it could apply to most VPN provider:

              WireGuard to VPN provider

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.