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

    [SOLVED] OpenVPN : can't get internet to the clients (firewall rules issue)

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 2 Posters 1.3k 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.
    • E
      echo4201
      last edited by

      Hello everyone!
      First of all, thanks to anyone reading this post. I'm pretty sure my problem is about a firewall rule, but I may be wrong.

      So, I have a OpenVPN server on my main pfSense. I whish that my connected clients get internet access, but not access to the whole local network for security reasons. So I configured NAT and OpenVPN firewall rules as the pictures included in this post. (I tried destination WAN NET and WAN ADDRESS with no luck).

      What I've discovered is that if I put * as destination for the firewall rule, I now get internet access, but also full access to the local network which is not wanted.

      Example of what I see from the firewall log:
      Apr 8 12:51:46 ovpns1 Default deny rule IPv4 (1000000103)   192.168.99.2:57908   54.190.179.118:443 TCP:RA

      OpenVPN subnet : 192.168.99.0/24
      Redirect gateway is enabled for the VPN Server.

      Thanks!

      nat_outbound_rules_ovpn.gif_thumb
      nat_outbound_rules_ovpn.gif
      firewall_rules_ovpn.gif
      firewall_rules_ovpn.gif_thumb

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Destination WAN net is not the internet. Destination any is the internet.

        If your WAN interface is 198.51.100.18/29, then WAN net = 198.51.100.16/29 - those are the only destinations that will be passed by that rule. I'm sure you can see how that is NOT the whole internet.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • E
          echo4201
          last edited by

          Oh. So then, if I make it destination "any", I have to make rules to block each individual VLANs right ?

          Thanks!

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Pass the specific local assets you want them to access
            Block the less-specific local assets you do not want them to access (This can often be an RFC1918 alias or similar - Do not neglect This firewall as well)
            Pass everything else (the internet)

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • E
              echo4201
              last edited by

              Thank you very much for the solution!

              I made an alias for localdomain so it makes things easier and cleaner in the rules. Thanks again!

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