Messages

1

General Discussion / Re: Dynamic DNS plugin os-ddclient not supporting Route53?

« on: January 09, 2023, 02:16:31 am »

Or linode! the new client doesn't support nearly as many useful dns options as the legacy one. PLEASE DON'T REMOVE THE OLD ONE!

2

22.1 Legacy Series / Re: Alias based firewall rules doesn't work after upgrade to 22.1.8

« on: January 09, 2023, 12:28:59 am »

For others that find this when having an issue it is still present in 22.7.10 as of 8Jan2023.... <---almost did the 2022 thing. too early in the year.

I created "approved_ips" alias in my firewall and all IPs are failing the check. Like one of the users suggested that there could be something broken in the system, when I go to Firewall > diagnostics > aliases and view the statistics, all of them are 0s. Even if I create a pass rule with a /8 network, it always comes back 0.   I've rebooted and enabled / disabled / enabled aliases, firewall rules, moved the order around and modified rdr rules with no affect. ITS BROKEN.   

EDIT: found a weird solution, but this still needs to be addressed. As mentioned 2-3 pages ago on this forum that if you were go navigate to Firewall > Ddiagnostics > Aliases     and adjust the alias you are working with you will see zero packets 0 bytes and just completely useless. if you add the ip address you want to use and click the "+" quick add which is supposed to add the address to the alias, it will start working. If you navigate back to Firewall > Aliases you will not see the added entries into that alias.

Core problem at hand I think is when you enter data into the actual alias page, its not really being added as it should. Next I'm going to try different browsers and facing my computer different directions.

Furthermore when you view the entry under Firewall > Aliases, my alias now says 4 entries, but when I click on it there are only 2. When I go into Firewall > Diagnostics and select the alias, it has the 4 entries I put on there in that page earlier.   FYI this is 22.7.10 despite the forum being for version 22.1.7. So this has been a problem for a while.