Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
24.1 Legacy Series
»
Upgrade from 23.7 to 24.1 possible browser error when updating rules
« previous
next »
Print
Pages: [
1
]
Author
Topic: Upgrade from 23.7 to 24.1 possible browser error when updating rules (Read 492 times)
pasha-19
Newbie
Posts: 34
Karma: 0
Upgrade from 23.7 to 24.1 possible browser error when updating rules
«
on:
February 22, 2024, 02:54:05 pm »
Things worked great for a while (the router is still in test mode that is incomplete). I have around 80 floating firewall rules that cover 9 vlans. I was updating descriptions around 70 rules down the list and when I pressed accept the rule disappeared. I repeated this 2 or three times - credit to Einstein the results were the same. I added one of the rules back in -- it did not appear on the screen. I rebooted the router and dumped the configuration.
The configuration does not contain the updated rules that disappeared.
The configuration does contain the added rule after the previous last rule in the configuration file (where I expected it to be). However said added rule does not appear on the screen at all.
I was updating the router using FireFox. (I had a previous problem with firefox when updating a switch.) I tried again to look at the configuration using Chrome. The rule that was present in the configuration that was not shown by Firefox now appears on the screen using Chrome. I will see if I can finish the update I was attempting.
UPDATE: This may well be a browser issue. I updated my version of Firefox to 123.0 the missing rule is back again. The problem may have been with a 122.x version of Firefox.
I completed the desired updates using the upgraded FireFox, my review of the configuration was incorrect the previous updates that "disappeared" from the screen DID NOT disappear from the configuration file (I just did not see them in the initial review after the download.)
Is there a limit to the number of floating rules allowed? Was that change effective in 24.1?
I had this large number of floating rules because there were several common rules to all vlans. There were also unique rules for each vlan (where intervlan communication was not allowed). I was hoping to present these rules with a request for an IP wildcard character such as @. My vlans are Class C x.x.x.0/24 and what I was hoping was to be able to use @.@.@.x-@.@.@.y in an alias to specify a subset of the vlan associated for the traffic being tested by the rule.
I can switch back to non-floating rules and give up hoping for a more concise version of my rules where I would not have to create multiple versions of the same rules with the inherent potential for error by having to do this multiple times.
Thanks for any assistance possible.
«
Last Edit: February 22, 2024, 04:09:39 pm by pasha-19
»
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
24.1 Legacy Series
»
Upgrade from 23.7 to 24.1 possible browser error when updating rules