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

Can access LAN web GUI from DMZ

Scheduled Pinned Locked Moved Firewalling
dmzweb-guiblock
8 Posts 4 Posters 1.6k 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.
  • R
    richley
    last edited by Oct 1, 2018, 3:37 PM

    Hi,

    I have blocked access to the admin GUI from within the DMZ using the IP address of the DMZ interface.

    I am unable to block access to the admin GUI from the DMZ when I use the IP address for the LAN interface. Any help would be appreciated. No matter what I do I can access the web GUI using the LAN interface IP when in the DMZ.

    Kind regards

    Richard

    V 1 Reply Last reply Oct 1, 2018, 4:01 PM Reply Quote 0
    • V
      viragomann @richley
      last edited by Oct 1, 2018, 4:01 PM

      @richley said in Can access LAN web GUI from DMZ:

      I am unable to block access to the admin GUI from the DMZ when I use the IP address for the LAN interface.

      ?
      If you allow nothing on the DMZ there will be no access to the WebGUI.

      If you have widely opened firewall rules on the DMZ you have to set a block rule to the top of the rule set. At destination select "This firewall (self)" and enter the management port you use.
      This should block access to any interface address.

      1 Reply Last reply Reply Quote 0
      • R
        richley
        last edited by Oct 1, 2018, 4:14 PM

        Hi viragomann,

        I have created a rule that blocks access to the admin GUI from the DMZ when using the DMZ interface IP address in a browser and this works. If I enter the LAN IP address for pfsense when in the DMZ I am able to get to the login page this is what I need to block.

        Kind regards

        Richard

        1 Reply Last reply Reply Quote 0
        • N
          NogBadTheBad
          last edited by NogBadTheBad Oct 1, 2018, 4:26 PM Oct 1, 2018, 4:18 PM

          @viragomann said in Can access LAN web GUI from DMZ:

          f you have widely opened firewall rules on the DMZ you have to set a block rule to the top of the rule set. At destination select "This firewall (self)" and enter the management port you use.
          This should block access to any interface address.

          Post a screen shot of your dmz firewall rules, for a true DMZ it should look something like this:-

          0_1538410913764_Screenshot 2018-10-01 at 17.21.04.png

          g_ip_local is an alias that contains all my ipv4 & ipv6 subnets.

          Andy

          1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

          1 Reply Last reply Reply Quote 0
          • R
            richley
            last edited by Oct 1, 2018, 4:30 PM

            Hi viragomann,

            I have attached a screenshot as requested.0_1538411410020_DMZ.png.

            Kind regards

            Richard

            1 Reply Last reply Reply Quote 0
            • N
              NogBadTheBad
              last edited by NogBadTheBad Oct 1, 2018, 4:37 PM Oct 1, 2018, 4:35 PM

              Looks to me like its something in the rules you've blanked out or maybe its connecting via IPv6 and you need to change the rule to IPv4 & IPv6.

              Have a look at the states on the pass rules.

              Andy

              1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

              1 Reply Last reply Reply Quote 0
              • V
                viragomann
                last edited by Oct 1, 2018, 4:39 PM

                So that rule should block any access to pfSense on management ports.

                Maybe a floating rule is permitting the access?

                However, consider that adding a block rule does not kill already existing states (connections). So you will have to kill existing states manually in Diagnostics > States > States.

                1 Reply Last reply Reply Quote 0
                • J
                  johnpoz LAYER 8 Global Moderator
                  last edited by johnpoz Oct 1, 2018, 4:44 PM Oct 1, 2018, 4:43 PM

                  Yeah looks like your whited out a huge amount of rules?

                  Also even the rules can see make no sense

                  You have an any rule that says hey DMZ net if your NOT going to lan net your allowed. Well below that a rule that says blocking going to 192.168.2/24 which is Dev Net? Why would that not be allowed in the dmz to NOT lan net rule?

                  Do you have downstream networks other than dmz net connected... And then below another rules that says block dev net, is that not 192.168.2/24 that you already blocked above, etc.

                  Please do not hide rules if you want help.. Its very simple. Rules are evaluated top down as traffic enters an interface. If a rule matches it wins and no other rules are evaluated. So run through your rules from the top. To see if traffic should be allowed or blocked. If you have a rule that blocks before an allow - and your still seeing allowed traffic then you prob have to clear a state from before you created that rule.

                  As to that rule on top blocking - if this firewall then it should. But don't know about his states, nor what he has in the alias.

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.8, 24.11

                  1 Reply Last reply Reply Quote 0
                  1 out of 8
                  • First post
                    1/8
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received