Messages

Will try later today

syslog:

daemon 63386 - [meta sequenceId="41"] 00[LIB] no files found matching '/usr/local/etc/strongswan.opnsense.d/*.conf'

Hello,

IPSec legacy not syncing anymore?! (OPNSense 23.7.12_5)

@Franco

Do you know the problem with ipsec? We are talking about 30 ipsec tunnels on the machine.

same....

Hi,

since Update 23.1.4_1 the gui shows that OpenVPN S2S Tunnel are not online(green). But they are online in the menu VPN: OpenVPN: Connection Status.

Hello,

why does the HA Sync overwrites the advbase on slave? Is there a way to keep the setting?
Thanks for help!

Regards,
AMW

There might be a problem....

Same as me. Running a 4 node cluster. After Upgrade from 22.7 only 2 of 25 VLAN's have problems. Changed the VHID and then it works... Change back - same again.

I can also try and test it if you want.

anyone tried 22.7?

Debian is only working with kernel 5.10.0-10-amd64. It may work with OPNsense 22.7 (Freebsd 13.1).

Is there someone who can test this?

Hello,

regarding to https://forum.opnsense.org/index.php?topic=13987.0

Problem is that after a reboot the fourth node is going into skew 254. Result = no failover possible (Skew 240)

First node 0, second 1, third 2....

If you set the fourth to 3 manually everything works fine - except you reboot, or syncronise the nodes.

Thank you!

For example we have the same configuration as in vlan512... So all interfaces have an IP. Why is it not a case? It worked before and now not. Is there a way to debug this? Or open a case at the development?

Reload or Reboot doesn't help:

@franco: Here is the output to get it running again...

after reboot or reload:
root@XXX:~ # ps aux|grep dhc
root    11019    0.0  0.0   15460    4040  -  Ss   17:04     0:00.01 /usr/local/sbin/dhcrelay -i vlan01 -i lagg1_vlan511 -i lagg1_vlan501 -i lagg1_vlan512 -i lagg0_vlan516 192.168.X.X 192.168.X.X
root    16395    0.0  0.0   12740    2204  1  S+   17:04     0:00.00 grep dhc

To get it working again:
root@XXX:~ # kill -9 11019
root@XXX:~ # /usr/local/sbin/dhcrelay -i vlan01 -i lagg1_vlan511 -i lagg1_vlan501 -i lagg1_vlan512 -i lagg1_vlan513 -i lagg1_vlan514 -i lagg0_vlan516 192.168.X.X 192.168.X.X
Requesting: vlan01 as upstream: Y downstream: Y
Requesting: lagg1_vlan511 as upstream: Y downstream: Y
Requesting: lagg1_vlan501 as upstream: Y downstream: Y
Requesting: lagg1_vlan512 as upstream: Y downstream: Y
Requesting: lagg1_vlan513 as upstream: Y downstream: Y
Requesting: lagg1_vlan514 as upstream: Y downstream: Y
Requesting: lagg0_vlan516 as upstream: Y downstream: Y
Internet Systems Consortium DHCP Relay Agent 4.4.2-P1
Copyright 2004-2021 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on BPF/lagg0_vlan516/d4:f5:ef:37:29:60
Sending on   BPF/lagg0_vlan516/d4:f5:ef:37:29:60
Listening on BPF/lagg1_vlan514/d4:f5:ef:37:29:68
Sending on   BPF/lagg1_vlan514/d4:f5:ef:37:29:68
Listening on BPF/lagg1_vlan513/d4:f5:ef:37:29:68
Sending on   BPF/lagg1_vlan513/d4:f5:ef:37:29:68
Listening on BPF/lagg1_vlan512/d4:f5:ef:37:29:68
Sending on   BPF/lagg1_vlan512/d4:f5:ef:37:29:68
Listening on BPF/lagg1_vlan501/d4:f5:ef:37:29:68
Sending on   BPF/lagg1_vlan501/d4:f5:ef:37:29:68
Listening on BPF/lagg1_vlan511/d4:f5:ef:37:29:68
Sending on   BPF/lagg1_vlan511/d4:f5:ef:37:29:68
Listening on BPF/vlan01/d4:f5:ef:37:29:60
Sending on   BPF/vlan01/d4:f5:ef:37:29:60
Sending on   Socket/fallback
root@XXX:~ #


You see that two networks are missing, but they are enabled in the webgui.