Missing default gateway after importing config to upgraded VM

Started by kamoon, January 09, 2025, 01:09:10 AM

Previous topic - Next topic
Hi

I am upgrading 22.7 (source) to 24.7 (target) as follows:

- build new VM identical to source
- configure a single interface to access web front end
- install 24.7 from iso
- take config extract from source & shut it down to avoid IP number clashes
- import config to target

(I realise there are other ways to do this but this approach deals with a few constraints I have)

This works fine in that my target VM appears to be indentical to the source - it just doesn't return traffic. The only difference I can see is by inspecting the routing table from the shell - here I can see that there is no default gateway assigned. I would have expected this to have come across with the config - any ideas why it has not?

Thanks

On the wild offchance that anyone else hits something similar...

It seems my original instance had a legacy upstream WAN gateway still in place.. Of the two WAN GWs in place, neither was flagged as an upstream GW (i.e. a candidate for default in my understanding) in the OPNsense GUI, although checking the routing table in the shell showed it to be correct and expected one. Once I removed the redundant gateway, marked the remaining one as upstream and re-exported my config, all was well after import to the target.

All the best.