@SteveITS It is nearly instant. Think it has to do with writing to the aliases?

@Pipe Não seria possível, essa não é a proposta do pfblockerNG.
Para tal, você precisaria de um proxy, no caso do pfsense, o Squid.

Mas vale ressaltar que o Squid está sendo descontinuado nas próximas instalações do pfSense, não sei quando mas o anúncio já foi feito.

https://www.netgate.com/blog/deprecation-of-squid-add-on-package-for-pfsense-software

Edit: De repente o ntopng possa te mostrar isso em tempo real, tem muitos anos que não uso então não sei, também não lembro sobre a questão de relatórios...

@areckethennu
Yes what @SteveITS said

_8 was 23.09.1
_9 was installed with the update 24.03
_10 was then released to correct the category edit issue that has been discussed

@Gertjan I did a liitle bit different)))

New Text Document.txt

@pslinn Not a specific answer for you but I have seen it before.
https://forum.netgate.com/topic/185383/suricata-php-fatal-error-str_ireplace-cannot-use-output-buffering-in-output-buffering-display-handlers-in-usr-local-www-csrf-csrf-magic-php-on-line-165

https://redmine.pfsense.org/issues/14778

https://redmine.pfsense.org/issues/14498

@Gertjan
Thanks, I'll try

@kuschi I now received feedback from Spamhaus that the list is now realably available again.

@anishkgt said in Blocking YouTube Shorts with Regex:

Since it was done in the link mentioned here ->(https://forum.netgate.com/topic/164732/python-regex-list)

That link shows you you can block 'anything that contains "yahoo" in the host name".
Fasten your seat belts now.
Example :
https://www.youtube.com/shorts/wEVVhumRrHI is an URL
youtube.com is a host name
www.youtube.com is a sub domain of that host name.

pfBlockerng has access - can see in the clear - the domain name, "youtube.com" and the sub domain name, www.youtube.com. So it can 'filter' these. The the app or web browser on the device gets an A (IPv4) or AAAA (IPv4) as an asnwer, and it connects to this (the "youtube") server.
TLS is established first.
Only now the browser gets the actual 'page' : the video : with this command "GET /shorts/wEVVhumRrHI/".
The thing is : you can't get 'into' this TLS stream. Its encrypted. You want it be encrypted. You don't want to have access to this data stream. Like never.

There is one possibilities left : use a proxy, and do MITM. Be warned : this is pure rocket science.

So, as @SteveITS said : you need a proxy.

If the shorts where accessible by the usage of a sub domain name, then it would be easy :
shorts.youtube.com can be filtered at a DNS request level, as the link shown above already shows.

But Youtube (Google) etc are doing there best so nobody can filter there content. They are hiring the "best" for doing just that. So, part of the mission is : you have to be better as these couple of thousands of network engineers they employ.

edit : It's youtube that has given us a partial solution. Youtube, without a premium access, is ... well ... IHMO, its just not possible. If I had to wade through the publicity to see these 'shorts' I presume I have a problem way bigger as 'watching shorts'. But hey, its a free world. Smoking is also bad. And I should drink (not water) less.

@SteveITS said in List of problems/bugs in HA/CARP setups:

@JeGr said in List of problems/bugs in HA/CARP setups:

Syncing only by Cron or by "force run cron/update all":

That's a known issue, https://redmine.pfsense.org/issues/14189#note-16 links to https://forum.netgate.com/topic/179060/pfblockerng-sync-not-working/55 which has a one-line workaround/fix.

@JeGr said in List of problems/bugs in HA/CARP setups:

can't save the settings when selecting "Sync to system configured backup server"

That has a redmine also: https://redmine.pfsense.org/issues/15159

Not sure about the others offhand.

Sure :) I know some of the things listed are already known or in case of the sync are "working as documented" - the update handling is documented in the notices and package infos. Just wanted to provide a list to tackle together to make the package itself more stable and better to work in a clustered environment. My main criticism refers to it being the "standout" of all core and additional packages as every package syncs normally by saving settings etc. and only pfBNG is behaving differently. I'm all for reading documentation, release notes and changelogs :) But I'm really asking myself if that has to be the way it's done at the core of it. Normally in UX/UI you'd advertise to go the route of least surprises to do things and that's a prime example. If any component does X and only one does Y it's bound to cause friction :)

@SteveITS said in List of problems/bugs in HA/CARP setups:

Let me throw out what I believe is another symptom...I've seen a few cases in the past year or so where the backup router sees an alias error during the sync/cron period:

Yeah, me too. Couldn't exactly pinpoint it to a specific occurence yet so I didn't list it but sometimes you have the "unknown alias" messages popping up on the standby node with pfB running, updating and working fine and if you check the state tables or aliases you find the pfB_aliases working just fine. So yes, there's another bug slightly hidden in the stack here :)

Cheers
\jens