Upgrade deleted Manualy added WAN gateway

[rudiservo]

Somehow the upgrade deleted the upstream Gateway.

The system has a fixed IP address on a WAN with vlan.

[KC515]

Same thing happened to me as well.

WAN:
Static IP (no vlan)

But it also deleted manually defined gateways for my L3 routed networks.
Oddly enough, restoring from a config/settings backup taken just prior didn't restore them either.

I had to manually re-add all GWs that were not default.  Only 6, so not a huge deal but I could see it being an issue for larger networks.

[franco]

Can you provide a config.xml partial dump of the removed gateway_item sections only? The migration is discarding them for a specific reason.


Thanks,
Franco

[Moonshine]

Lost mine also..

Code: [Select]

    <gateway_item>
      <interface>wan</interface>
      <gateway>x.x.x.x</gateway>
      <name>WAN_GW</name>
      <priority/>
      <weight/>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr>Spectrum Cable Gateway</descr>
      <defaultgw>1</defaultgw>
    </gateway_item>


[muchacha_grande]

Same thing happened to me. I had to add the gateway by hand again.
Only the IPv4 gateway disappeared, the v6 one was still there.

[Andreas_]

Same thing with me. Not only the gateway assignment in the WAN interface was removed, the gateway definition itself was gone.
All other gateways were still present.

[clst]

Same here. in log/system/latest I get this line: 

Code: [Select]

config 76918 - [meta sequenceId="1"] Migration skipped gateway GWName (GW-IP)

EDIT: this line might be caused by restoring the config when troubleshooting, not the upgrade itself.

[marcquark]

Encountered the same issue today. GW config XML looks exactly like Moonshine's. Both IPv4 and IPv6 gateways on WAN were affected. In my case however, there's no LAN interface, i'm running this instance as a VPN hub. Other than that there's nothing special going on

[Jckf]

Same here. Gateway for v4 disappeared after upgrade, but v6 did not. Looks like a failed migration of the config.

The removed item looked like this:

Code: [Select]

<gateway_item>
<interface>wan</interface>
<gateway>x.y.z.209</gateway>
<name>E1_WAN_GWv4</name>
<priority/>
<weight/>
<ipprotocol>inet</ipprotocol>
<interval/>
<descr/>
<defaultgw>1</defaultgw>
</gateway_item>


[emaba]

<gateways>
    <gateway_item>
      <interface>wan</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>WAN_GWv4</name>
      <priority/>
      <weight/>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr/>
      <defaultgw>1</defaultgw>
    </gateway_item>
    <gateway_item>
      <interface>opt2</interface>
      <gateway>xx.xx.xx.5xxgateway>
      <name>xxxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr>GW Wireiguard</descr>
    </gateway_item>
    <gateway_item>
      <interface>opt5</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>xxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr/>
      <monitor>xx.xx.xx.xx</monitor>
      <fargw>1</fargw>
    </gateway_item>
    <gateway_item>
      <interface>opt6</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>xxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr>GW Wireiguard 2 </descr>
    </gateway_item>
  </gateways>

WAN_GWv4 was the one deleted during update.

Can you provide a config.xml partial dump of the removed gateway_item sections only? The migration is discarding them for a specific reason.


Thanks,
Franco

[lshantz]

Encountered the same issue today. GW config XML looks exactly like Moonshine's. Both IPv4 and IPv6 gateways on WAN were affected. In my case however, there's no LAN interface, i'm running this instance as a VPN hub. Other than that there's nothing special going on

I tried that on my system and that did not work. Something changed enough that it doesn't help. My REDIS database will not come up either. So I'm guessing legacy stuff is getting updates and borking some things. 

[grufo]

Same here - I had to remove the gateways in old style format from the config.xml file.

Changed

<Gateways version="1.0.0">
....
</Gateways>

To:

<Gateways version="1.0.0"/>

After a reboot the gateways from

<gateways>
    <gateway_item>
     ...

were active again and everything online as expected!

[franco]

A fix was in 24.1.2 but the upgrade path from 23.7 hasn't been updated so far.


Cheers,
Franco

[lshantz]

YAY! Thanks for the update.