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

Can't get firewall rules to work

Scheduled Pinned Locked Moved Firewalling
5 Posts 4 Posters 1.0k 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.
  • P
    philled
    last edited by Apr 12, 2014, 7:19 AM

    I'm pretty new to pfSense, having from from Smoothwall.

    My pfSense setup has 3 NICs:

    • WAN

    • LAN 192.168.0.0

    • DMZ 192.168.1.0

    I have quite a few firewall rules to set up but can't even get a basic rule working. For example, I want a machine in my DMZ (192.168.1.100) to connect to port 80 on a machine on my LAN (192.168.0.120). I thought that would be simple but the rule I created still doesn't allow the connection when I try it from 192.168.1.100. I've attached a screenshot of the firewall rules on LAN. Can anyone please advise why this wouldn't work?

    As I say, I thought this would be simple. On Smoothwall a lot of this stuff is pre-configured. I'm starting to get an uneasy feeling that pfSense doesn't do anything like that for you - it just provides a web interface as a slightly more convenient way of setting up firewall rules by hand.

    DMZ_firewall_rule_1.gif
    DMZ_firewall_rule_1.gif_thumb

    1 Reply Last reply Reply Quote 0
    • C
      chpalmer
      last edited by Apr 12, 2014, 7:25 AM

      Can anyone please advise why this wouldn't work?

      Yep-  You need to add a nat rule.

      /firewall_nat.php

      https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

      Triggering snowflakes one by one..
      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

      1 Reply Last reply Reply Quote 0
      • P
        philled
        last edited by Apr 12, 2014, 7:57 AM

        @chpalmer:

        Can anyone please advise why this wouldn't work?

        Yep-  You need to add a nat rule.

        /firewall_nat.php
        https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

        OK, I'll look into that.
        Would the lack of a NAT rule explain why I have no access to the DMZ from my LAN? I'm worried I may not have set up my DMZ correctly in the 1st place. I followed the instructions at http://pfsensesetup.com/pfsense-setup-part-four-setting-up-a-dmz but I can't ping the machine in the DMZ or telnet to port 80. It's totally inaccessible. Would that also be because I haven't set up any NAT rules (that article didn't state that as necessary)?

        1 Reply Last reply Reply Quote 0
        • B
          biggsy
          last edited by Apr 13, 2014, 2:48 AM Apr 13, 2014, 2:46 AM

          What rules do you have on the DMZ interface?

          Rules are applied to the interface on which the traffic will enter.

          LAN can access anywhere (see the descriptions at the end of lines two and three in your screenshot).

          WAN and OPT (your DMZ) interfaces need to have rules to allow traffic in.

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by Apr 13, 2014, 4:26 PM

            What biggsy said - that last rule you have on LAN in your screenshot has to be on DMZ, where the traffic originates.
            You do not need NAT to get between local subnets (like a DMZ and LAN). Do not mess with the NAT settings, or you might break something else accidentally.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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