opnsense / core

OPNsense GUI, API and systems backend
https://opnsense.org/
BSD 2-Clause "Simplified" License
3.31k stars 738 forks source link

firewall alias not updating in a timely manner #6404

Closed Bugz000 closed 1 year ago

Bugz000 commented 1 year ago

i have a locally hosted blocklist i wish to poll ideally every 5 seconds for new entries, i update this list live as people are scanning my network - the moment they go somewhere they shouldn't - they are added to the list back when i ran openwrt i could use an api to invoke a job to tell openwrt to re-pull the list and apply it opnsense support for this infrastructure is either SEVERELY lacking, or i'm doing something wrong

i have set the alias refresh frequency to 0 days 0.10 hours - (where's the minutes?, this should have a seconds parameter ideally) i have system -> settings -> cron -> job set to */1 minutes to update lists i have floating firewall rule using the alias to drop all packets incoming and outgoing from these ip addresses but it can still take upwards of 20 mins to ACTUALLY reflect changes

by this point, the bot has already completely scanned my network and moved on - it's completely useless WHY is faster poll rates seemingly not allowed? is there something i am doing wrong? how would YOU do this system, because i'd imagine a simple ip list and using the alias system is the way to go no? i just cannot fathom why this should not be working, in my mind */1 should be running every 60 seconds, right? but it does not

it should not be performance based, it is running on proxmox vm with 40 cores, 16gb ram and 180gb bootdisk it should not have any trouble

issue supposedly fixed here; c5555b2 but i cannot apply this patch; "1 out of 1 hunks failed while patching etc/inc/system.inc"

it is at this point i am at a complete loss

OPNsense-bot commented 1 year ago

Thank you for creating an issue. Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

williamdes commented 1 year ago

Hi @Bugz000 Any chance you for you to update your system ?

OPNsense-bot commented 1 year ago

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.