Messages

For me the same. No LTE connection but standard DSL connection. signature invalid

Problem solved - mirror probably has incomplete files. Changing mirror to "default" solved the problem. All files were downloaded witout problems.

For me the same. No LTE connection but standard DSL connection. signature invalid

Hello,
no one has an idea?

Hello,

I'm running a wireguard tunnel from my smartphone to my home network.
OPNsense is the central routing instance and FW between WAN, LAN, DMZ and Guest networks.
In the WAN network is my DSL internet router (and only that one).

All (0.0.0.0/0) my traffic from my smartphone is routed through the wireguard tunnel to OPNsense.

After rebooting OPNsense I can reach from my smartphone all devices in my local networks, but no traffic is routed to (or from?) the internet.

Now the wierd thing:
When I change something of the firewall configuration, the traffic to the internet starts going being routed.
E.g. I can stop and start an service or I can enable/disable logging of a particular rule...
As soon as such an action happens traffic from and to the internet is routed through my wireguard tunnel.
Until the next reboot of OPNsense...

Any ideas what could be going on here?
How could that be debugged?
This happens since months (from the beginning I was using OPNsense - at least 12 Months)

Greetings,
Martin

Thanks for your suggestion - I didn't yet know about this possibility.
I tried again the upgrade from 25.1 to 25.1.1 and this time no problems with bind.
It worked directly after the upgrade. So I couldn't test your suggestion...

Martin

Hello,

while upgrading from 25.1 to 25.1.1 I get an error as shown in the attached hardcopy.
After reboot bind won't start and I have no DNS for my clients.
After reverting back to 25.1 (by proxmox snapshot) everything works fine.

Martin

as assumed yesterday - it works with 24.1
everything ok.

shame over me...

few hours after I had reverted my OPNsense to the snapshot taken before, I got network problems and had to reboot the FW. Everything worked again except mDNS - on the old release!!

Checking a bit more I found out that I had no rule to enable multicast into my server net. Adding that rule and mDNS worked again  (in the old release). Don't know why it worked before - maybe there were some caching effects from my setup three weeks ago...
I'll try tomorrow with the new 24.1 release. I'm sure it will work...

Thanks!

Hello,

I upgraded my OPNsense from 23.7.12_5 to 24.1.
Everything went fine, but after some testing I noticed that the mDNS repeater didn't work.
My Homeassistant Server (in server net) couldn't resolve the clients in the client net.

Reverted back to the snapshot before the upgrade and immediately the mDNS repeater worked as before and the clients could be resolved.

Martin