Messages

For info:
In my particular case, it was not due to tagged and untagged mix. The problem persisted, even though I only use tagged interfaces. During the update something was changed in wiregard, without wiregard everything works. If I switch back to tagged and untagged, everything also works, just without Wiregard.
I suspect that Wirecard handles the route differently than before.

I also struggled with these problems.
My solution is solved with a virtual IP.
On the IP, bind can then work normally on port 53.
Listen IP is then the virtual IP in bind.

I have no deny rule on the Lan interface. There are only the standard 2 "allow all" rules ( IPV4 , IPV6 ).
And why does it work for X years with the rules only with the update not. Additionally others have similar problems ?

Attached the patch file to configure by the GUI.
Install:
copy file to the server
call
patch --directory=/ -p0 < radius.patch
There is a new field PKS-Passwort in the user konfiguration.

The passwords will be saved in backup.xml too.
Restore, install first the patch then restore the config.xml and may be need, the change one of the user and press save.

I now think that it's not just only a tag/untag problem. My first attempt to update from 7.9 to 7.10_2 ended with the LAN interface no longer being accessible. Well, I had one untagged and 4 tagged interfaces on same hardware interface. Now I have reworked this and there is no more untagged. I now have VLAN 2,3,5,6 and 10 on my LAN interfaces. Everything runs with 24.7.9_1-amd64. I have now carried out the update. After the restart, exactly the same. During the boot phase you can briefly ping the LAN (VLAN 10). After approx. 10-15 pings the connection is lost and the router can no longer be reached via the LAN interface IP (previously untagged, now VLAN 10).   

I use Wiregard and IPsec ?!?

I use Freeradius for ppsk with my access point. The tunnel-password parameter is required in the users file. I have created a patch that patches the 3 necessary files. It is always annoying to patch them, because if you forget to do so, you lose the passwords. Is it planned to include an official parameter tunnel-password, or how to add the patch. Or is this not desired?

 24.7.9 works for me too.

Similar Problem?
https://forum.opnsense.org/index.php?topic=44531.0

Ich habe das gleich auch mit einem RJ-45 Kabel.
Wenn der Link weg ist und ich dann wieder einstecke bleibt der Router nicht erreichbar.
Nur ein Reboot hilft.

I have the same problem.

Can you ping the router? Not me, only briefly during the boot phase. Do you use wiregard ?

Ping got lost , when one of this logs where displayed
>>> Invoking start script 'freebsd'
setup igb0_vlan5
setup igb1 [egress only]
Starting flowd_aggregate.

setup igb0_vlan5, only for one of the six Vlans. No setup igb0_vlan4 while booting

Yes, could be the same. I use VLAN to on the LAN Net.

After updating to the latest version (10), ipv4 no longer works in Lan, so as a rule strikes. I have been able to reproduce this. Old version installed, backup restore, everything works, then update, Lan dead again. DHCP assigns IP addresses.
It could be due to wiregard, a ping from a computer with a fixed IP to the router goes through the ping for a while until the interface of Wiregard is started (looks like this on the boot screen). However, the interface is not activated in the GUI.
Does anyone have an idea what this could be?

Thanks

Ich habe keine Probleme mit V6 ( Niederrhein ).
Ich verwende 4 Subnetze unter V6.
Uptime 6 Tage.

Gruß