Closed maghuro closed 2 weeks ago
I have identified the issue and actively working on a fix for this.
v3.0.2-beta3 has been published which includes a fix for this issue.
Release Notes: v3.0.2-beta3 - 11/02/2024 Enhancements:
Fixes:
Working flawlessly, thanks!
A question - if a range of IPs is removed from a ASN, will it also be removed on the next Cron run?
Working flawlessly, thanks!
A question - if a range of IPs is removed from a ASN, will it also be removed on the next Cron run?
That's currently not in the logic however a reload / restart would resync the ASN from a fresh load of subnets.
v3.0.2 has been released to resolve this issue. Open a new GitHub issue for any additional issues or feature requests.
I only have ASN configured. No policies. When the cronjob runs, as I don't have any policy, it stops processing and don't update ASNs range of IPs