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

    Changing Network Subnet Limited User Access

    Scheduled Pinned Locked Moved General pfSense Questions
    24 Posts 5 Posters 5.4k 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.
    • DerelictD
      Derelict LAYER 8 Netgate
      last edited by

      If you don't need anything different from what auto provides, I'd leave it auto.

      Does /tmp/rules.debug show anything interesting now?

      Deleted the OpenVPN package?  What version of pfSense is this?

      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
      • A
        alltime
        last edited by

        @Derelict:

        If you don't need anything different from what auto provides, I'd leave it auto.

        Does /tmp/rules.debug show anything interesting now?

        Deleted the OpenVPN package?  What version of pfSense is this?

        Auto it is then.

        /tmp/rules.debug shows as follows (related to 192.168.2.*)

        Outbound NAT rules

        Subnets to NAT

        tonatsubnets = "{ 192.168.2.0/23 192.168.1.0/24 127.0.0.0/8  }"
        nat on $LIME  from $tonatsubnets port 500 to any port 500 -> 209.59.59.194/32 port 500 
        nat on $LIME  from $tonatsubnets to any -> 209.59.59.194/32 port 1024:65535

        –--

        Reflection redirects and NAT for 1:1 mappings

        rdr on { em3 bge0 em2 em1 em0 } from any to 209.59.59.194 -> 192.168.1.4 bitmask
        no nat on em2 from em2 to 192.168.1.4
        nat on em2 from 192.168.1.0/24 to 192.168.1.4 -> 192.168.1.1 port 1024:65535

        rdr on { em3 bge0 em2 em1 em0 } from any to 209.59.59.196 -> 192.168.3.4 bitmask
        no nat on em3 from em3 to 192.168.3.4
        nat on em3 from 192.168.2.0/23 to 192.168.3.4 -> 192.168.3.1 port 1024:65535

        I removed the configured settings of OpenVPN first, then deleted the package entirely. We are running: 2.1.5-RELEASE (i386)

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

          There is no OpenVPN package on 2.1.5.  It's part of the base system.  Are you talking about the client export utility?

          Anyway. Now that all that is out of there, step back and take another look at the /tmp/rules.debug and all your interfaces and rules.

          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
          • A
            alltime
            last edited by

            @Derelict:

            There is no OpenVPN package on 2.1.5.  It's part of the base system.  Are you talking about the client export utility?

            Anyway. Now that all that is out of there, step back and take another look at the /tmp/rules.debug and all your interfaces and rules.

            My apologies, yes the client Export Utility for OpenVPN.

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