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

    PfBlocker

    Scheduled Pinned Locked Moved pfSense Packages
    896 Posts 143 Posters 1.5m 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.
    • ?
      Guest
      last edited by

      Hey guys I'm new here and to pfsense. I noticed that when I enable pfblocker my wireless clients can longer connect to the internet but my wired. Any ideas. I'm using a linksys wireless router with dd-wrt loaded on it. It has worked forever until I enable pfblocker without any rules created. I'm a complete noob to linux/unix. Thanks in advance!!!

      1 Reply Last reply Reply Quote 0
      • marcellocM
        marcelloc
        last edited by

        PfBlocker does not remove or include any rule different from its own rules.
        Try disabling it and see what happens.

        Also try to include some lists and see how it include aliases and rules.

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • RonpfSR
          RonpfS
          last edited by

          You might add something about the rule being under pfBlocker control in the rules description.

          2.4.5-RELEASE-p1 (amd64)
          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

          1 Reply Last reply Reply Quote 0
          • marcellocM
            marcelloc
            last edited by

            Don't you think pfBlocker Inbound/outbound rule description is less robotic?  :)

            Treinamentos de Elite: http://sys-squad.com

            Help a community developer! ;D

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              I created an outbound rule using the ads, spyware, and level 3 list. Once I enabled pfblocker all wireless client stopped accessing the internet. My wired desktop worked perfectly fine. I disabled pfblocker and the wireless clients started working again. Any ideas?

              1 Reply Last reply Reply Quote 0
              • RonpfSR
                RonpfS
                last edited by

                i know ….  but the warning about the alias is very robotic  :D DO NOT EDIT THIS ALIAS

                but I did modify one of them and got surprised when the modification was lost  :o after a pfBlocker restart.

                I'm not sure now,  but maybe copy or the rule disappeared too !?

                In the end it is easier to just use aliases, that way you can choose the order of the rules.

                2.4.5-RELEASE-p1 (amd64)
                Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                1 Reply Last reply Reply Quote 0
                • marcellocM
                  marcelloc
                  last edited by

                  @RonpfS:

                  but I did modify one of them and got surprised when the modification was lost  :o after a pfBlocker restart.

                  I'm not sure now,  but maybe copy or the rule disappeared too !?

                  When you copy a rule, you must change pfblocker description to something without pfblocker and rule

                  @RonpfS:

                  In the end it is easier to just use aliases, that way you can choose the order of the rules.

                  yes, it's realy usefull.

                  Treinamentos de Elite: http://sys-squad.com

                  Help a community developer! ;D

                  1 Reply Last reply Reply Quote 0
                  • marcellocM
                    marcelloc
                    last edited by

                    @WarMachine357:

                    I created an outbound rule using the ads, spyware, and level 3 list. Once I enabled pfblocker all wireless client stopped accessing the internet. My wired desktop worked perfectly fine. I disabled pfblocker and the wireless clients started working again. Any ideas?

                    Do your wireless clients are on the same subnet as LAN users?

                    Check rules with pfBlocker enabled and disabled

                    Treinamentos de Elite: http://sys-squad.com

                    Help a community developer! ;D

                    1 Reply Last reply Reply Quote 0
                    • ?
                      Guest
                      last edited by

                      Yeah, they are are the same subnet. The pfsense box hands out dhcp to them. The outbound rule I created comes before the default LAN rule LAN NET. Also, the ntp server in pfsense provides service to the wireless ap.

                      1 Reply Last reply Reply Quote 0
                      • marcellocM
                        marcelloc
                        last edited by

                        @WarMachine357:

                        Yeah, they are are the same subnet. The pfsense box hands out dhcp to them. The outbound rule I created comes before the default LAN rule LAN NET. Also, the ntp server in pfsense provides service to the wireless ap.

                        If wired and wireless machines are on the same subnet and using the same dhcp, I have no idea how pfsense or pfblocker could block one and do not block other. It's weird to me.

                        Treinamentos de Elite: http://sys-squad.com

                        Help a community developer! ;D

                        1 Reply Last reply Reply Quote 0
                        • ?
                          Guest
                          last edited by

                          I have found by moving the rule after the allow rules the wireless clients work. But, that doesn't seem right does it?

                          1 Reply Last reply Reply Quote 0
                          • ?
                            Guest
                            last edited by

                            I agree that it doesn't make sense. What happens to one should happen to the other. But, did you see what I said about moving the rule to the bottom?

                            1 Reply Last reply Reply Quote 0
                            • marcellocM
                              marcelloc
                              last edited by

                              @WarMachine357:

                              I have found by moving the rule after the allow rules the wireless clients work. But, that doesn't seem right does it?

                              No it's not.

                              An outbound rule blocks access from any to pfblockerAlias.

                              If you have one rule that permits traffic, the deny rule will have no effect.

                              Treinamentos de Elite: http://sys-squad.com

                              Help a community developer! ;D

                              1 Reply Last reply Reply Quote 0
                              • marcellocM
                                marcelloc
                                last edited by

                                Maybe level3 list is blocking all your network and the pfsense keep-state for your machine gives you a false diagnostics.

                                Remove level3 list and see if it works.

                                Treinamentos de Elite: http://sys-squad.com

                                Help a community developer! ;D

                                1 Reply Last reply Reply Quote 0
                                • marcellocM
                                  marcelloc
                                  last edited by

                                  HI everybody,

                                  Version 0.1.4.5 is out with all planned features coded.  8)

                                  main changes:

                                  • Dashboard widget includes package hit on applied aliases (10 second update)

                                  • Change in rule description to allow widget package count

                                  • Update frequency implemented

                                  Important note for custom rules

                                  keep aliasname in the beggining of rule description and do not end description with 'rule'.

                                  Once again, thank you for testing this amazing new tool for pfsense. ;)

                                  Treinamentos de Elite: http://sys-squad.com

                                  Help a community developer! ;D

                                  1 Reply Last reply Reply Quote 0
                                  • RonpfSR
                                    RonpfS
                                    last edited by

                                    Just reinstalled.

                                    Strange things happens when you switch to Alias
                                    Description: pfblockerWAN Inbound rule will disappear
                                    Description: pfblockerWAN Inbound   will persist

                                    Still showing 0 in the widget after 10 minutes

                                    2.4.5-RELEASE-p1 (amd64)
                                    Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                    Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                                    1 Reply Last reply Reply Quote 0
                                    • marcellocM
                                      marcelloc
                                      last edited by

                                      I've changed important note for better understanding.

                                      Aliasname something rule will be removed by package.

                                      To test rule packet count, block your own country While you are locally on your office/home.

                                      DO NOT TRY THIS REMOTELY.

                                      A less risky test is:

                                      • define your own country action as alias only

                                      • create a rule that deny outbound icmp access on lan.

                                      • include description as described

                                      • apply rules

                                      • Open Dashboard

                                      • try to Ping someone on your country.

                                      Treinamentos de Elite: http://sys-squad.com

                                      Help a community developer! ;D

                                      1 Reply Last reply Reply Quote 0
                                      • RonpfSR
                                        RonpfS
                                        last edited by

                                        Still showing 0

                                        I picked one host in the Diagnostics: Tables pfblocker table.
                                        I can ping from LAN or pfsense no problem
                                        Nothing is showed as blocked in the firewall logs !??

                                        rules are on WAN only

                                        Reject and log * 	* 	* 	pfBlockerWAN 	* 	* 	none 	  	pfBlockerWAN Outbound  
                                        Block and log * 	pfBlockerWAN 	* 	* 	* 	* 	none 	  	pfBlockerWAN Inbound  
                                        
                                        

                                        2.4.5-RELEASE-p1 (amd64)
                                        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                                        1 Reply Last reply Reply Quote 0
                                        • marcellocM
                                          marcelloc
                                          last edited by

                                          If you are testing from lan, the blocking rule must be on lan.

                                          It's a statefull firewall. All rules are set where communication begins.

                                          Treinamentos de Elite: http://sys-squad.com

                                          Help a community developer! ;D

                                          1 Reply Last reply Reply Quote 0
                                          • RonpfSR
                                            RonpfS
                                            last edited by

                                            So I should have

                                            on the LAN 
                                            Reject and log * * * pfBlockerWAN * * none   pfBlockerWAN LAN - Outbound 
                                            on the
                                            WAN Block and log * pfBlockerWAN * * * * none   pfBlockerWAN WAN - Inbound

                                            I see the widget Packet number changes ;o)

                                            How do you block the pfsense box from accessing these aliases?

                                            2.4.5-RELEASE-p1 (amd64)
                                            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

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