Messages

Have you tried uninstalling & then reinstalling the plugin?

If your ISP is IPv4 only (as is mine) have a look at my post here: https://forum.opnsense.org/index.php?topic=45612.msg231178#msg231178


This solved many problems for me post upgrade, one of which was the same Plex remote access problem that you're experiencing

Does your ISP use IPv4 or IPv6?

Ah ha. Yes that makes sense.


Will there be a way that you can stop it looking for IPv6, maybe after a short timeout, if it's not available?

Probably not. Then it would stop trying for legitimate ipv6 setups that have a temporary failure.

Fair point.

Well I'm not too fussed, now I was able to locate the source of my problem & put it right anyway

Ah ha. Yes that makes sense.


Will there be a way that you can stop it looking for IPv6, maybe after a short timeout, if it's not available?

This was exactly the same problem I have been having & discovered yesterday that disabling IPv6 on the WAN was the solution.


My ISP also only provides IPv4



I wonder, is there a way that OPNsense could be told to disable IPv6 automatically if it detects that it is not available?

Yes, I am

No, this default predates the fork even.


Cheers,
Franco

No idea why then that on 24.7.12 (and prior versions that I have used) this gateway IPv6 Configuration Type stayed set as None, but the update to 25.1 definitely switched it to DHCPv6 which then caused my problems.

It's possible that when I first joined OPNsense at version 24.1.x I may have manually set the gateway IPv6 Configuration Type to None during my initial set up, but all upgrades after that point did not set it back to DHCPv6, but the 25.1 upgrade definitely did

Looks to be working OK for me.


Thanks

> It had set itself to IPv6 Configuration Type: DHCPv6

That's the default in an attempt to auto-configure IPv6. Doesn't always work, especially when the ISP mangled their stack.


Cheers,
Franco

Is this something new for 25.1? I'm still fairly new to *sense but I had previously been running the past couple of 24.x versions and had no problems.
Like I say, IPv6 is not offered by my ISP so I've got zero experience with anything to do with it

In the interest of marking this as solved, I finally got to the bottom of the cause of the problem.


It seems that the upgrade had enabled something to do with IPv6 on the gateway. I only have IPv4 available to me so changing the following has completely fixed this problem for me:


Interfaces -- [WAN] -- IPv6 Configuration Type: None



It had set itself to IPv6 Configuration Type: DHCPv6


This was somehow causing the system to consume all of it's available RAM and the system load was going crazy high until eventually the system and my whole network became unusable. Presumably it was attempting over and over again to obtain a DHCPv6 address which it was never going to get as DHCPv6 is unavailable to me

I'm not sure unfortunately as I'm not currently in a position where I am able to do a clean install

This is the only port forward rule I remember setting up in OPNsense for MeshCentral:

Port 445 TCP/UDP


I am using an Apache reverse proxy as well though, so I can forward support.mydomain.co.uk to my MeshCentral Server VM

I am currently running 24.7.12_4 on an HP T730 Thin Client with 8GB of RAM.

My RAM usage sits at around 4 - 4.5GB and the system load is often below 1.00 although this does sometimes creep up to around ~1.5 or so under heavy usage.


When I have tried upgrading to the latest 25.1, the RAM usages goes through the roof after the upgrade has completed and pretty much maxes out, and the system load averages go crazy as well. The system then becomes unusable and I even lose connectivity for a minute or so before it comes back but then the same thing happens again, over and over.


For the time being I have rolled back to a snapshot that I took before attempting the upgrade and everything is back to normal again.


Something is not happy when I do the upgrade. Any advice on what it could be?

You could always just leave the interface speed manually set to 1Gbps.


But I suppose when set to Auto it is auto negotiating to a slower speed because it has detected some kind of an error in the connection so perhaps it is better to get to the bottom of what is causing it