Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I have a similar issue. I have a IPv4 client which establishes a wireguard connection on his own to a remote server.
Whenever I reboot Opnsense the wireguard connection is stale forever. With 22.7 I mitigated this by enabling 'Dynamic state reset' which has been removed in 23.1. I now have to manually reset the state table to ensure after a reboot that everything works.
Yes, the dashboard widget is still monitoring the wireguard-go service and not the kernel module. It would be nice if the dashboard widget monitored the kernel module and allowed us to start stop and restart the kernel module, if possible.
Thanks,
Al
o plugins: os-wireguard switches to kernel module with a separate os-wireguard-go variant available for installation to keep the old behaviour
Wenn ich es richtig verstehe, würde man die Kommunikation innerhalb eines Netzes auf dem Switch regeln? Weil die IP-Pakete gar nicht durch den Router (in meinem Fall die OPNsense) laufen?Was willst du denn da regeln? Alle Geräte, die man in dasselbe Netz steckt, können miteinander sprechen. Das ist der Sinn der Übung. Wenn du Geräte isolieren möchtest, brauchst du getrennte Netze. Da Ports an Routern und Firewalls meist wenige und eher "teuer" sind, benutzt man dazu gerne einen Switch und VLANs.
Aber im Ernst: ein PC oder Mac, ein paar Telefone, ein Drucker, ein Apple-TV oder Firestick - natürlich quatschen die alle fröhlich miteinander. Sollen sie ja auch. Und da will ich mich auch nicht drum kümmern, was ein iPad jetzt genau macht, wenn ich eine Datei an meinen Mac "airdroppe" oder was der Mac tut, wenn ich einen Film zum Fernseher streame ... funktionieren soll es.
... I can't talk to the interwebs if I can't talk to the ISP gateway.
it is NOT advisable to use your ISP gateway as monitor, because there could be cases wherein you have "full" connection to your ISP but there backbone is down or there external access outside is down. in which case their gateway will respond to your pings.
you should set known "good" internet IP, usually public DNS IP address
8.8.8.8, 1.1.1.1 or 9.9.9.9 and their secondary IPS
these IPs will rarely go down, and will ensure that your ISP has "Internet" connection to ping them.
How many times has this happened to your ISP where their external links went down but your last mile connection was still up? Because I can not recall a single instance of this happening to me.
As I already mentioned, I'm much more concerned about the status of my last mile connection which is why I don't want to use any ip that transits outside of my ISP.
...Huawei E3372h...