Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. s2s
    Log in to post
    • All categories
    • A

      Firewall Rules for Wireguard S2S VPN in a Multi-WAN Environment with Multiple LAN

      Watching Ignoring Scheduled Pinned Locked Moved WireGuard s2s vpn wireguard
      4
      0 Votes
      4 Posts
      295 Views
      A

      @Bob-Dig

      EDIT:

      Changing the default gateway under the "Routing" tab again caused the remote site to be inaccessible via the S2S VPN.

    • A

      Route-Based IPSec vs Wireguard Tunnel Subnet Choice for S2S VPN

      Watching Ignoring Scheduled Pinned Locked Moved IPsec s2s ipsec wireguard vpn
      5
      0 Votes
      5 Posts
      317 Views
      A

      @Gblenn

      Just tested it with /31 and it works. For route-based IPsec the gateway is created automatically when you assign the tunnel to an interface. I haven't tried with /32 tho. But I tried with larger subnet like /24. I guess it's like what you said, as long as they are on the same subnet it will work. Just that for point-to-point connection with a single transit network it doesn't make sense to use something larger that contains more than 2 IPs.

    • I

      VPN S2S - Bytes-Out: 0 (0 B) Packets-Out: 0

      Watching Ignoring Scheduled Pinned Locked Moved IPsec ipsec vpn s2s
      2
      0 Votes
      2 Posts
      184 Views
      E

      can you share P2 subnet/IPs of both end, and firewall rule configured on IPSec interface - both ends,

    • C

      OpenVPN S2S client daemon get's killed

      Watching Ignoring Scheduled Pinned Locked Moved OpenVPN openvpn s2s daemon dies
      1
      0 Votes
      1 Posts
      311 Views
      No one has replied