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

    Firewall rule for 67/68 on wan inet not working

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 2 Posters 1.1k 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.
    • M
      Mad Professor
      last edited by

      I'm having an issue with my pfsense box.
      The issue I'm having is that I'm losing the connection due to expiring dhcp leases. I have to manually renew the connection to reestablish my connection to my cable provider.

      I keep getting these

      
      Blocked Jan 4 20:54:12 	WAN 	10.50.64.1:67		 255.255.255.255:68
      
      

      I've added the rule to wan interface

      
      IPv4 UDP 	* 	67 - 68 	* 	67 - 68
      
      

      Yet it's still being blocked.

      How can I fix this?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That is probably being blocked by "Block Private Networks" on the WAN interface, a custom rule won't override that.

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • M
          Mad Professor
          last edited by

          @jimp:

          That is probably being blocked by "Block Private Networks" on the WAN interface, a custom rule won't override that.

          I have the modem bridged so pfsense takes the public facing ip.
          Any harm unchecking it?

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Not really, you could uncheck that, then make an RFC1918 alias (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and add a block rule under your pass rule for equivalent protection

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • M
              Mad Professor
              last edited by

              @jimp:

              Not really, you could uncheck that, then make an RFC1918 alias (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and add a block rule under your pass rule for equivalent protection

              Does this look correct?

              edit yes I caught the 192/16 block, had a typo it's been corrected.

              firewall.jpg
              firewall.jpg_thumb

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                your udp 67-68 rule should be on top. Otherwise, yes (assuming the typo you already spotted has been fixed)

                Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

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