OPNsense Forum

Archive => 23.1 Legacy Series => Topic started by: dmo on June 04, 2023, 12:26:10 pm

Title: Direct Upgrade from 22.7.11 to most recent 23.1 (e.g. 23.1.9?)
Post by: dmo on June 04, 2023, 12:26:10 pm
Recently I updated via WebUpdater from 22.7.11 to 23.1.
But with 23.1 I'm experiencing major issues that are rendering the management interface (WebUI, Connection to router/internet) unusable - with 23.1 I have no working internet connection at all.
Quote
arpresolve: can't allocate llinfo for 192.168.xx.xx on igb2

Therefor once I upgraded to 23.1 I'm unable to perform further upgrades within the 23.1.x upgrade path.

I learned that the official download mirrors only provide installer images for version 23.1, but not for die minor (bugfix) updates 23.1.x. Is that true? Or I do missing something?

How can I offline Upgrade my 22.7.11 to the latest 23.1.x without having a working internet connection?
Does anyone have ideas or the solution?

P.S.: Clean install of 23.1 with importing my recent 22.7.11 configuration results in the same errror state mentioned above.
Title: Re: Direct Upgrade from 22.7.11 to most recent 23.1 (e.g. 23.1.9?)
Post by: franco on June 04, 2023, 03:24:29 pm
What's your WAN connectivity? It sounds like you have a far gateway but not set it to allow a far gateway.

The error comes from trying to reach a gateway outside of your WAN subnet.


Cheers,
Franco
Title: Re: Direct Upgrade from 22.7.11 to most recent 23.1 (e.g. 23.1.9?)
Post by: dmo on June 04, 2023, 04:45:09 pm
I don't have a far gateway.

The management port igb2 is in the same network as the LAN ports of the internet router.
And the router is the gateway to the internet, its WAN port has a public IP of the ISP.

I've attached a simple network diagram for better understanding.

EDIT: OPNsense is operating in filtering bridge mode.
Title: Re: Direct Upgrade from 22.7.11 to most recent 23.1 (e.g. 23.1.9?)
Post by: dmo on June 04, 2023, 06:57:12 pm
I've reinstalled OPNsense from the scratch - without import configuration and with manually recreate the network configuration.

Now everything is working as expected. But have have to rebuild all the filtering rules yet.
I will compare the configuration - maybe I find the issue....