Navigation

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

    Blocking inter vlan traffic blocks access to website

    Firewalling
    2
    12
    729
    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.
    • ?
      A Former User last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • Derelict
        Derelict LAYER 8 Netgate last edited by

        You have to pass traffic to the private addresses and ports you want passed before blocking access to the server VLAN on the firewall rules on the GUEST interface.

        NAT happens before firewall rules are checked.

        So if your web server is 192.168.1.100 ports 80 and 443 you would do something like this on the GUEST interface:

        pass tcp source GUEST net dest 192.168.1.100 port 80
        pass tcp source GUEST net dest 192.168.1.100 port 443
        reject any source GUEST net dest SERVER net

        As a trailer I would also say it would be better to pass traffic to "this firewall" that they need access to (like DNS) then block everything else to "this firewall" instead of just blocking the management ports.

        That way things can change (like changing the webgui port) and you are still secure without having to remember to change that alias.

        Chattanooga, Tennessee, USA
        The pfSense Book is free of charge!
        DO NOT set a source 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 Former User last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • ?
            A Former User last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • Derelict
              Derelict LAYER 8 Netgate last edited by

              If it works with SERVER Net and not specific addresses I would posit you are using the wrong addresses.

              You might want to post the actual port forwards and firewall rules. Should only be necessary to post the GUEST rules.

              Configure it to something you think should work but doesn't and post that.

              Chattanooga, Tennessee, USA
              The pfSense Book is free of charge!
              DO NOT set a source 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 Former User last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • Derelict
                  Derelict LAYER 8 Netgate last edited by

                  Does Diagnostics > Tables look sane when you examine the exchange table?

                  Is the DNS answer the public WAN address or the inside address?

                  What does the port forward on WAN look like?

                  Chattanooga, Tennessee, USA
                  The pfSense Book is free of charge!
                  DO NOT set a source 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 Former User last edited by A Former User

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • Derelict
                      Derelict LAYER 8 Netgate last edited by

                      Well, yeah. There's your problem.

                      What DNS servers do you want pfSense itself to use to resolve names?

                      Do any clients rely on pfSense for DNS server functionality?

                      Chattanooga, Tennessee, USA
                      The pfSense Book is free of charge!
                      DO NOT set a source 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 Former User last edited by

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • Derelict
                          Derelict LAYER 8 Netgate last edited by

                          If you do not need any DNS services on pfSense:

                          Set the DNS servers you want pfSense itself to use in System > General

                          Make sure DNS server override is unchecked

                          Check Disable DNS Forwarder (removes 127.0.0.1 from the list of nameservers)

                          Disable both DNS Forwarder and DNS Resolver in Services.

                          Chattanooga, Tennessee, USA
                          The pfSense Book is free of charge!
                          DO NOT set a source 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 Former User last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post