@steveits Done, thanks for pointing me in the right direction. :)

@lpd7 said in PFsense Book:

PFb package

This thread may help pfblocker Documentation

@itpp21 Of course it’s not complicated, but it’s not documented that wildcards „any“ can be used.

@nogbadthebad yeah that side menu seems a bit messed up.

But if you go here

https://docs.netgate.com/pfsense/en/latest/

You can see there should be stuff under there on the menu on the left

recipes.jpg

@jimp
Thanks a lot! I have not seen this in the docs.

Sorry, my bad.

Anywayys- great information and explanation on the place you linked.

Going to disable now ;)

/KNEBB

It's a limitation of the platform used for the documentation. They did recently add case insensitive searching recently, but it may be a bit yet before it's in a stable version we use for the public docs.

@tong Thanks for sharing your link. Not sure what happened to my original upload. I have re-uploaded. Here is a new link to my copy:

https://drive.google.com/file/d/1-k0u99CjNLqbb4WM0llzXrnO49k2Q2q5/view?usp=sharing

Fixed, thanks!

@jarrod I tried getting this work, but I have problems with the correct VPN setup. Can you share which "Authentication Method" you are using? Thank you very much!

@serverteam Same here - I own an SG-1100 and looks like ~24 days ago a core developer added armv7 and aarm64 to the build servers. Hopefully, next release will contain these modules in the kernel.

https://redmine.pfsense.org/issues/7467#note-18

Wow! Thanks for this amazing guide!

@jimp said in Documentation missing L2TP client:

It really isn't.

hehe that wasn't clear but I actually was referring to pfsense as being versatile and not L2TP/IPSEC vpns

Those docs are likely in need of an update but at that time the recommendation was not to use OpenDNS because of its security but because of its blocking features which, again at the time, were available for most users to control what sort of responses were allowed.

They'll all get updated and cleaned up eventually, as time allows.