Upgrade to 23.1.5 - No wireguard traffic (empty alias problem?)

[franco]

Odd. It might be related to https://forum.opnsense.org/index.php?topic=33297.0 and wrong time in the system.

# opnsense-patch 4ac3e1d57368
# killall ntpd
# pluginctl -s ntpd start
# /usr/local/opnsense/scripts/filter/update_tables.py

(this is only a theory but can't hurt)


Cheers,
Franco

[cstevens]

Thanks rsk this saved my ass.

If I went to Firewall -> Aliases -> Search for alias things looked fine
When I went to Firewall -> Diagnostics -> Aliases and selected the alias, it was empty.

I took your advice and did rm -f /var/db/aliastables/* && /usr/local/opnsense/scripts/filter/update_tables.py and now everything works again.  Firewall -> Diagnostics -> Aliases -> selected alias now shows what should be in the alias, which fwiw is an ipv6 /32 network alias.

[vOoPtNa]

for me it is not related to ntpd.

it is the same behaivor again as descripted here:
https://github.com/opnsense/core/issues/5788

- Create an alias with only one network in it
- reboot
- pfctl -t $ALIAS_NAME -T show - returns nothing

[rsk]

for me it is not related to ntpd.
it is the same behaivor again as descripted here:
https://github.com/opnsense/core/issues/5788

me too. ntpd / system time was fine. I also think that there is a regression regarding alias #5788

[meepmeep]

23.1.5_2 fixed it.