Hi
@kriukas
Find the below changes, the debug helped a lot.
1. Implemented code for the jump from 3004 to 3006 with the changelog function
As I already gave the feedback. I can confirm:
1A. Changelog reading is completely OK both CLI and WebUI versions.
1B. Cannot tell anything about Changelog "approval" procedure, if there is one. I know nothing about that and don't want to guess without having a link to any king of the documentation, "how it should/must be implemented" POV.
2. F/W jump I will try ASAP, when we both agree to close any unfinished test scenarios, requiring "pending jump 3004=>3006" state.
2. Made some more changes related to web access restrictions; as you can see I now have it enabled, with large overlapping /12 ranges and it still detects it correctly.
View attachment 65886
Please test again and advise, sorry about the back and forth.
If this is still somehow an issue I'll call in the big guns that made that function originally
@Martinski
With all due respect and gratefullness of the solution for Mr.
@ExtremeFiretop, to anyone who it might concern, I can confirm that:
1. the "block", which negated my personal case, to set password, test login and get a success OK from the script test
is lifted. SImply said - typical end-user with high probability will be allowed to proceed with flash when IP restricition are set and there is a least one rule covering its "home" subnet.
2. After actual F/W upgrade execution I will be able to ellaborate more.
3. To my best understanding, despite *current dev level* script implementation as non-blocker, script itself is inconsistent at determining the truthnes/falseness of router's LAN IP belonging to the mathematical set IPs, and one can easy find corner cases, when scripts thinks (and passes!) as OK, but is wrong.
All this section of functionality needs careful evaluation before dev=>stable approval.
And as you know I implemented the keyboard navigation for the changelog in the WebUI.
Working perfect, as I said.
I thought, that ChangeLog approvall will be implement in current-times "standard", when TOS / PRIVACY is only allowed to be accepted as "read", when user scrolls to the end of text.