Messages

No problem! :)  All friends here and it all worked out in the end.

PS - I've seen users with similar problems to me in understanding the migration assistant on Reddit. It all actually works fine, it just isn't that intuitive.

I'm using Safari on a Mac and apparently, unlike Chrome and Firefox, it is default behavior to display CSV rather than save it as a file. Maybe add to the instructions that it is a CSV file and to right-click and select save file?

Comments that I should have read all the discussion topics are somewhat elitist and not really helpful. I'm a regular user, not a power user, and only visit these forums to ask questions and seek solutions. I'm sure you have a lot of users like me! I'll also say that comments I did read from earlier versions said that there was no hurry to migrate, so I didn't.

Rather than blaming me for not reading pages and pages of forum posts, can I suggest a more positive approach:

1. Adding some more detail to the Migrate instructions as to what you will see.
2. As I mentioned before, make it clear in the table which are old and which are new rules. Colored background would work.

PS - It would be nice if the rules export actually created and saved a file rather than just opening a web page that you have to cut and paste yourself. If you'll forgive me, this seems half done.

Thank you both, that does indeed do the trick. It seemed non-intuitive to import rules into a table which apparently already had all those rules. I was expecting to be importing them into a new, empty, table. Not one that was already populated with the exact same rules.

I'm sure all this is very clear if you've worked through the betas, but the 'old' rules appearing in the new interface with no indication that they are the old rules, not the new, and need to be migrated is IMHO weird! :-)

Can I humbly suggest that this is still really confusing for those of us who didn't follow the process through the RCs? The images shown in the forum show the Rules (new) and Rules menu entries, which apparently don't appear now. It was also disconcerting that all the rules show up twice for a while and you don't know which are the old and which the new. Maybe the old rules should all have a colored background both before and after they are migrated? Something that makes it clear which is which?

In contrast the NAT migration was very clear as it moved rules from one place to another, not to the same place again.

Anyway - all done now and the migration Assistant has disappeared. Thanks again for the help.

Thanks for the reply. I am definitely guilty of not reading through all the RC notes. :-) I only read the 26.7 release notes which don't seem to mention it at all. Now I dig back through the RC notes this is what I found:

"The static PHP pages for firewall rule management have been moved to the "os-firewall-legacy" plugin that can be optionally installed. Note that the upgrade will not install it as rules will continue to work and are easily migrated using the given assistant."

The phrase, "easily migrated using the given assistant" and the fact that the plugin isn't automatically installed suggests to me that the migration assistant will just work without it. I'm still confused! If the plug-in is necessary for the migration assistant to run, then shouldn't it either install it, or at least include text in the instructions to tell you to do so? Otherwise why show the Migration Assistant in the menu at all if it isn't going to work?

Perhaps I did already migrate the rules and have forgotten (I've slept since 26.1). Is there a way to tell if the rules are migrated or not?

Updated to 26.7. All working fine, thank you.

However I'm confused by the Migration Assistant. This is what I see in the menu:



(Posted an image here but it doesn't show up for some reason, here's the url: https://shottr.cc/s/1B0N/SCR-20260717-fmu.png )

There is only a 'Rules' entry, not a 'Rules(new)'. Does this mean that I already did the migration (which I might have done in a prior release, but forgotten)? If I have done it why is the Migration Assistant still saying I haven't? However, if I haven't run the migration, then how do I do it without the 'Rules (new)' option?

Thanks Franco! :) Glad to know it wasn't just me doing something stupid for once.

I reported the same problem with Health data here: https://forum.opnsense.org/index.php?topic=43641.0

In the end I tried disabling then re-enabling the 'RRD graphing backend' in Reporting/Settings. I've lost 3 years of data, which is very frustrating but the graphs have started up again.

@hgkdd - try that. Disable RRD graphing backend, click 'Save', then re-enable it and click 'Save' again.

Looks like this might be the problem reported here: https://github.com/opnsense/core/issues/7753  where the RRD routines fail. Was supposed to be fixed but it appears it isn't.

I updated to 24.7.7 this morning and since then the graphs under Reporting/Health do not update. They are frozen at the time I performed the update, 09:43 this morning. A reboot does not fix this.

All other graphs under 'Reporting' are fine, it's just the 'Health' ones that are broken.

Grateful for any suggestions on how to get this running again. I'm tracking this data as I've been getting a lot of loss from Spectrum cable, so I really don't want to lose the historical data.

I have the same question for much the same reason. I'm suffering short, 2 or 3 minute, dropouts from Spectrum internet and I'd like to be able to tweak the RRD parameters so I can get more than 20 hours day of the 1 minute resolution WAN_DHCP data.

Posting here as well: the web server seems to have too few configured concurrent processing threads:
Cheers,
Franco

Thank you - that fixed it for me with viewing on the Desktop and iPad at the same time. :-)

I have observed a weird behavior with the new GUI:

1. Multiple devices connected to GUI
If this happens on both sessions the Widgets start to fail load

Same here. Dashboard on desktop alone works fine, however if I try and open it on an iPad at the same time then both fail. Only seems to work with one client at a time. This is a problem as I habitually leave the dashboard open in a tab on the desktop and I know I'll forget to close it just so I can use the iPad.

I'd appreciate help with what I hope is a simple question.

I'm getting a Tesla Powerwall installed which has a fixed IP address of 192.168.91.1. This cannot be changed. It will be connected to my Wi-Fi for connection to the Tesla cloud but I'd also like to be able to access this from within my LAN which is at 192.168.0.1/23.

Can I set up a static route and give the 192.168.91.1 address an alias IP within my normal LAN range?

I know I could do this on a computer using, for example, something like :

Code Select Expand

sudo ip route add 192.168.91.1 via 192.168.0.100

How do I do the same with OPNSense so that any computer on the LAN can access it?

Yes, I upgraded through the GUI. It downloaded all the upgrade files including the new kernel, then rebooted. That's the last I saw of it! :-) It took me a long time to find the problem. Switching Bios boot options is not the first thing I thought of.

PS - I have since done a new install over the top of the old (importing the old configuration) just to make sure all was squeaky clean. I've left the Bios in Legacy mode.