Quote from: Waldus66668 on January 19, 2026, 08:45:33 AMI find EFI version on NVM tool easier to use. Simply grab eeupdate64e.efi form Intel driver pack, boot into EFI shell and run command like:What about doing a backup before it flashes, or just wanting to get NIC info, or create a log file. Does efi method do that?eeupdate64e.efi /nic=1 /d=FXVL_125C_V_1MB_2.32.bin
You only specify nic number and name of NVM file to flash. No need to worry about configuration file.
Quote from: Monviech (Cedrik) on January 21, 2026, 09:14:10 AMIf your connection via wireguard is inbound, it means that your devices resolve the DNS entry. On your OPNsense, I would not expect any hostname in the configuration, wireguard just binds to all interfaces (* 51820).
So I assume your clients resolve the wrong IP address and send packets to the wrong destination.
Quote from: meyergru on January 21, 2026, 09:41:56 AMI wrote the stale connection job and of course, it only does half of the job...Thanks Uwe for contributing to the project - didn't realize you were the author of this little helper :-)
QuoteIn your scenario, with a road warrior, the cron job on the "server" side does not help at all, because the road warrior peer has to initiate a new connection. If he fails to notice the stale connection, it will never restart and thus the DynDNS update will go unnoticed.Yes I fully get that, and that is not my issue tbh, since I just could restart a road-warrior-client while travelling. However restarting the server without a "dial-in" option is not possible. More on my analysis below.
QuoteLuckily, for M-Net, there is a fix to that: They usually do not change their IPv6 prefix on reconnection, much unlike the IPv4. Thus, if you use IPv6 only or IPv6 and IPv4 in your DynDNS, it will effectively work as if you have a fixed IP(v6). In that case, your roadwarrior clients will regain contact within the same Wireguard session.I know they say they only change the IPv6 prefix after a set amount of "offline" time. A simple restart of my opnsense VM, only lasting <60sec triggers a new IPv6 prefix. But that's also fine, since reconnects don't happen that often...
QuoteCall me any time if you have questions, you have my number!Yeah we can have a chat on the weekend, I'm very busy until friday (business trip).
Quote from: manki_09 on January 14, 2026, 05:32:09 PMSo, I did a little more testing and replaced the Xfinity XB8 gateway with a Hitron CODA56. I'm not a fan of running ISP equipment especially Xfinity.
Quote from: mooh on January 21, 2026, 07:11:53 PMI'm guessing that physical bandwidth below pipe bandwidth may mess with the scheduling.