Upgrade to 26.7.8 broke Gateways

Started by mempt, October 30, 2026, 12:44:33 PM

Previous topic - Next topic
October 30, 2026, 12:44:33 PM Last Edit: October 30, 2026, 12:48:34 PM by mempt
Hi, I was running the 26.7.7_1 (I don't remember exactly the version but was the previous to 26.7.8 for sure) and today after upgrade the gateway do not start.

Also it displays the wrong "Address Family", displays "IPv6" instead of "IPv4". I have 3 gateways, hereºs my configuration:

<Gateways version="1.0.0" persisted_at="1793359818.55" description="Gateways configuration">
  <gateway_item uuid="ef2f17e3-03d5-4927-8d04-6f38e36bcae6">
    <disabled>0</disabled>
    <name>WAN_DHCP</name>
    <descr>Interface WAN_DHCP Gateway</descr>
    <interface>wan</interface>
    <ipprotocol>inet</ipprotocol>
    <gateway/>
    <defaultgw>1</defaultgw>
    <fargw>0</fargw>
    <monitor_disable>1</monitor_disable>
    <monitor_noroute>0</monitor_noroute>
    <monitor_killstates>0</monitor_killstates>
    <monitor_killstates_priority>0</monitor_killstates_priority>
    <monitor/>
    <force_down>0</force_down>
    <nosync>0</nosync>
    <priority>254</priority>
    <weight>1</weight>
    <latencylow/>
    <latencyhigh/>
    <losslow/>
    <losshigh/>
    <interval/>
    <time_period/>
    <loss_interval/>
    <data_length/>
  </gateway_item>
  <gateway_item uuid="a11377e0-bf16-4822-a7ff-cda751a1d11c">
    <disabled>0</disabled>
    <name>VPN_1</name>
    <descr>Interface VPN_1_VPNV4 Gateway</descr>
    <interface>opt9</interface>
    <ipprotocol>inet</ipprotocol>
    <gateway/>
    <defaultgw>0</defaultgw>
    <fargw>0</fargw>
    <monitor_disable>0</monitor_disable>
    <monitor_noroute>0</monitor_noroute>
    <monitor_killstates>1</monitor_killstates>
    <monitor_killstates_priority>0</monitor_killstates_priority>
    <monitor>8.8.4.4</monitor>
    <force_down>0</force_down>
    <nosync>0</nosync>
    <priority>255</priority>
    <weight>1</weight>
    <latencylow/>
    <latencyhigh/>
    <losslow/>
    <losshigh/>
    <interval/>
    <time_period/>
    <loss_interval/>
    <data_length/>
  </gateway_item>
  <gateway_item uuid="8c5d4253-b349-4045-a15a-05dae7894b7c">
    <disabled>0</disabled>
    <name>VPN_2</name>
    <descr>Interface VPN_2_VPNV4 Gateway</descr>
    <interface>opt7</interface>
    <ipprotocol>inet</ipprotocol>
    <gateway/>
    <defaultgw>0</defaultgw>
    <fargw>0</fargw>
    <monitor_disable>0</monitor_disable>
    <monitor_noroute>0</monitor_noroute>
    <monitor_killstates>1</monitor_killstates>
    <monitor_killstates_priority>0</monitor_killstates_priority>
    <monitor>1.0.0.1</monitor>
    <force_down>0</force_down>
    <nosync>0</nosync>
    <priority>255</priority>
    <weight>1</weight>
    <latencylow/>
    <latencyhigh/>
    <losslow/>
    <losshigh/>
    <interval/>
    <time_period/>
    <loss_interval/>
    <data_length/>
  </gateway_item>
  <gateway_item uuid="97834dee-84a6-4de9-8058-bdf24c49a82a">
    <disabled>0</disabled>
    <name>VPN_3_VPNV4</name>
    <descr>Interface VPN_3_VPNV4 Gateway</descr>
    <interface>opt6</interface>
    <ipprotocol>inet</ipprotocol>
    <gateway/>
    <defaultgw>0</defaultgw>
    <fargw>0</fargw>
    <monitor_disable>0</monitor_disable>
    <monitor_noroute>0</monitor_noroute>
    <monitor_killstates>1</monitor_killstates>
    <monitor_killstates_priority>0</monitor_killstates_priority>
    <monitor/>
    <force_down>0</force_down>
    <nosync>0</nosync>
    <priority>255</priority>
    <weight>1</weight>
    <latencylow/>
    <latencyhigh/>
    <losslow/>
    <losshigh/>
    <interval/>
    <time_period/>
    <loss_interval/>
    <data_length/>
  </gateway_item>
</Gateways>

I also have a group
  <gateways>
    <gateway_group uuid="5c1d5a4b-4cd6-4e0b-92e0-c41d7ff7ad69">
      <name>PIA_Failover</name>
      <item2>PIAVPN_2_VPNV4</item2>
      <item3>PIAVPN_3_VPNV4</item3>
      <item4/>
      <item5/>
      <item>PIAVPN_1_VPNV4</item>
      <trigger>downlosslatency</trigger>
      <poolopts/>
      <descr/>
    </gateway_group>
  </gateways>

Not sure how to extract the logs

Can you see if reverting this helps?

# opnsense-patch https://github.com/opnsense/core/commit/5b6ccdb592


Cheers,
Franco

I am experiencing the same problem is there a solution to fix this

Quote from: saki22 on October 30, 2026, 02:10:04 PMI am experiencing the same problem is there a solution to fix this

Like Franco says, try the opnsense-patch command to see if that fixes (reverts) it.

Quote from: jphylips on October 30, 2026, 02:16:39 PM
Quote from: saki22 on October 30, 2026, 02:10:04 PMI am experiencing the same problem is there a solution to fix this

Like Franco says, try the opnsense-patch command to see if that fixes (reverts) it.
I did that it says the link it says the comment is unavailable

What do you mean by link? That is a command that you are supposed to enter while logged in as root to your OPNsense via SSH.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

October 30, 2026, 02:23:32 PM #6 Last Edit: October 30, 2026, 02:30:30 PM by saki22
Quote from: Patrick M. Hausen on October 30, 2026, 02:20:19 PMWhat do you mean by link? That is a command that you are supposed to enter while logged in as root to your OPNsense via SSH.
The this link # opnsense-patch https://github.com/opnsense/core/commit/5b6ccdb592 I use opnsense interface shell by com port

Did you type it with the "#"

if yes, do it without

opnsense-patch https://github.com/opnsense/core/commit/5b6ccdb592
Hardware:
DEC740

Quote from: Monviech (Cedrik) on October 30, 2026, 02:33:46 PMDid you type it with the "#"

if yes, do it without

opnsense-patch https://github.com/opnsense/core/commit/5b6ccdb592
I did not put in #

Obviously the command won't work if there's no internet connection—-which appears to be the case?

Okay I got the web link working but I did not fix the problem

One person confirmed the revert, but this appears to hit a lot softer than initially anticipated. We need another independent confirm in order to go forward with the hotfix -- otherwise we'll devise a better fix and place it in 26.7.9 directly.


Cheers,
Franco

I also had outbound VPN's. Just did the upgrade and everything is working just fine.

Today at 01:22:45 AM #13 Last Edit: Today at 01:56:36 AM by (MARLOO)
the upgrade took more than an hour, the longest one I've done so far, but everything came up fine afterwards.

No gateway issues and no wrong address family here.

Hardware: N5105 Intel Celeron  
                       OPNsense | Home Lab | Linux & Home Automation
                               "Secure the network, automate the rest."

I just upgraded from OPNsense 26.7.7-amd64 to OPNsense 26.7.8-amd64, and gateways are working as expected and the same as before the upgrade for me...
Prod: OPNsense 26.7.7-amd64 running on ESXi 6.7 U2 VM, 4Gbytes RAM, 2 x vCPU
frr OSPF + eBGP, IDS, AdGuard Home, mDNS proxy, OpenVPN, Kea DHCP

Pre-PROD LAB: OPNsense 26.7.8-amd64 running on ESXi 6.7 U2 VM, 4Gbytes RAM, 2 x vCPU
frr OSPF + eBGP, IDS, AdGuard Home, mDNS proxy, OpenVPN, Kea DHCP