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

    Obtained ip from dhcp lan is blocked by firewall

    Problems Installing or Upgrading pfSense Software
    3
    3
    284
    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.
    • B
      booruszuru
      last edited by booruszuru

      Hello, i have dhcp running o my lan

      when i obtained the ip adress (136...225) from a client i can access the intenet inside the client

      but i have a problem i cant figure it out

      i have a webserver running on port 9999 ( or 80 it does not make a difference )
      but the firewall is blocking it
      if i disable the firewall temporarily i can access the port 9999

      i tried many options in lan rules but nothing worked

      how can i create a rule to allow access to port 9999 for the lan dhcp ip ?

      alt text

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by

        pfSense != OPNsense

        Suggest you ask here:-

        https://opnsense.org/

        Andy

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

        1 Reply Last reply Reply Quote 0
        • johnpozJ
          johnpoz LAYER 8 Global Moderator
          last edited by johnpoz

          Other than using that distro that will not be named here..

          Your blocking on SA, ie syn,ack - this screams out of state traffic and asymmetrical traffic flow.

          First question I would ask is what IPs are you using internal on your network? 81.x and 136.x are not rfc1918 space.. You shouldn't be using public space you do not own, even if internally..

          But blocking of SA means that the firewall did not see the SYN (S) to create the state. This is normally because of some asymmetrical routing problem.

          How did 81 talk to 136 on port 9999? If not through your stateful firewall so it could create a state, then yes the return traffic sent to your firewall - ie the SA, would be blocked because it doesn't match a state.

          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.7.2, 24.11

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