Messages

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.

No panic as I've solved the problem but thought it might be worth reporting. Just upgraded my system to 24.1 and it froze during reboot. Connected a monitor and nothing, wouldn't boot at all. After an hour of trouble shooting I finally, in desperation, switched the Bios to boot in Legacy mode rather than UEFI and, wonder of wonders, with sighs of relief, it came up!

Does the 24.1 upgrade disable UEFI booting in some way? I'm now running Legacy - which is fine, but it was all very odd that I had to change it.

Hi, the release notes for 23.7 say "The new OpenVPN instances pages and API create an independent set of instances more closely following the upstream documentation of OpenVPN.  Legacy client/server settings cannot be managed from the API and are not migrated, but will continue to work independently."

The text is ambiguous to me, it says that legacy clients (which I take to read as my OpenVPN clients set up in 23.1.11) will not be migrated but then it goes on to say they they will continue to work. How will they continue to work if not migrated and, if they do, how would they be managed?

In either case, what is the recommended way to transfer existing OpenVPN clients to 23.7? Do we have to delete the existing client definitions before upgrading and then recreate them in the new system?

Thank you.

I made one change and things are working again. Specifically I found a suggestion to add a firewall rule to WAN to allow incoming ICMP. I didn't have this before, but adding it now seems to have fixed things. :-)

This thread can be closed - thank you.

I think this problem just started today when I upgraded to 23.1, but it's possible it happened recently with a prior version. Symptoms:

1. IPv6 works fine from router to ISP. ISP assigns an IPv6 address (starting 2605 - this is Spectrum) and I can ping6 from the OPNSense shell successfully.

2. Computers on LAN have IPv6 addresses correctly assigned (starting 2603 - not link local addresses). They show up as leases in the DHCPv6 leases list on OPNSense and display as 'active'.

3. The problem is that none of the LAN devices can access the outside world on IPv6.

EDIT: The outgoing IPv6 ping6 data shows in the firewall logs, but nothing seems to come back


AFAIK I have changed nothing and I can't see where the problem lies. What is blocking the incoming ipV6 data? What do you need from me to help me fix the problem?

Help much appreciated - thank you.

I only reverted OPNSense itself using opnsense-revert -r 22.1.4 opnsense . I did not revert Python or the kernel.

Running audit/health check shows the following:

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.4_1 (amd64/OpenSSL) at Fri Apr  8 13:57:23 CDT 2022
>>> Check installed kernel version
Version 22.1.5 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 22.1.5 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
os-dyndns 1.27_3
os-theme-cicada 1.29
os-theme-tukan 1.25
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" has 65 dependencies to check.
Checking packages: .........................
opnsense-22.1.4_1 repository mismatch: unknown-repository
opnsense-22.1.4_1 version mismatch, expected 22.1.5
Checking packages: .......................................... done
***DONE***

Update: Reverted to 22.1.4 and the errors went away. Please advise.