Upgrade to 26.7.8 broke Gateways

Started by mempt, Today at 12:44:33 PM

Previous topic - Next topic
Today at 12:44:33 PM Last Edit: Today at 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