• 2 Posts
  • 21 Comments
Joined 11 months ago
cake
Cake day: January 5th, 2024

help-circle
  • Persistent keep alive is configured per connection by all peers (server and client typically). As I understand it, Wireguard’s peer-based architecture will let both client and server peers define an optional persistent keep alive timer in order to send heartbeat packets on interval. Otherwise Wireguard on either peer may keep opening and closing connections for inactivity (or get its connections forcefully closed externally) if traffic isn’t being regularly sent. This can occur even though the network interfaces for Wireguard on both communicating peers remain up.

    I do agree that running some kind of health-check handshake service over the Wireguard tunnel is an easy enough way to periodically check the state of the connection between peers.


  • Depending on how your connection is negotiated, it may partially not be possible due to the architecture of Wireguard. There is likely some way to hook into capturing handshakes between clients (initial handshake, key rotations). To determine disconnects and reconnects however is a challenge. There are no explicit states in the connection. The closest thing to disconnect monitoring is utilizing a keep alive timeout on the connections. There are some caveats to using a keep alive timer, however. Additionally, not every connection may use a keep alive timeout, making this a full solution infeasible.

    Detailed information about Wireguard session handling can be found in section 6 of this PDF.





  • Reading through the link chain, it seems the Western Digital drives being shipped in those laptops really should have never made it into consumers’ hands.

    The kernel argument nvme_core.default_ps_max_latency_us=5500 is being used to restrict the power state latency in order to keep the drive out of its lowest power state (because of course yet another cheaply-made device has terrible power state management).

    While most distros generally expect NVMe drive to not completely cease functioning while at idle (as should be expected really), AntiX is likely keeping the drive above its minimal power state. Whether this is intentional, unintentional, or from a lack of general power state management provided by the distro isn’t something I know. It would require some digging in the source tree for the distro most likely to find if there are any deliberate restrictions to power saving, especially regarding NVMe.


  • Just note that with Bambu printers about past data collection practices and their in general mid to atrocious after-sales support. If this doesn’t deter you, then go ahead and get one.

    I do a lot of my functional parts in ABS, ASA though printing such material may be difficult on an open-air machine. The two obvious choices will generally be PLA or PETG. PLA is one of the most common printed materials, and is fairly balanced in material strength. PETG parts are more likely to permanently deform heavily before fully snapping, as well as they have a but more temperature resistance than PLA. Additionally most PETG plastics hold up decently well to UV, often making them more suitable for parts that need to be outdoors.

    PLA takes not much consideration on surface to print, as most printers come with a smooth PEI build sheet by default. It will however need more cooling than printing with PETG at equivalent speeds. If you use a PEI sheet for PETG, make sure it is textured. You will destroy a smooth sheet if it doesn’t have some kind of release coating to lower its adhesive properties to PETG.

    There is no guarantee for spools of filament to actually arrive dry, so a filament dryer isn’t a bad idea. I don’t have any particular recommendations for a good filament dryer. I have a Filadryer S2 from Sunlu, but am not impressed by it.







  • The headphones you have don’t have any actual surround sound capabilities. The only thing they do is have a software driver that maps a set of channels from 7.1 surround sound to the binaural sound mapping of the headphones.

    The pipewire sound server can do the same thing as iCue with filter chains and specific plugins. See this post for some pointers and guidance if you wish to set it up for yourself.

    Do note that unless you have content built with actual 5.1 or 7.1 surround sound, there won’t be much actual benefit to using virtual surround sound on headphones in the first place.





  • https://librewolf.net/

    A summary from its site and known technical details:

    • no telemetry by default
    • includes uBlock Origin
    • has sane privacy-respecting defaults
    • prepackages arkenfox user.js
    • relatively well-maintained fork of Firefox that keeps up with upstream
    • No major controversies AFAIK

    As for Windows 7, nobody should really need to install Librewolf anyway on such a device. No device running Windows 7 should have access to the internet at this point. If you are asking about compatibility intending this use case, you have bigger problems to worry about than your choice of browser. If you just need to view HTML files graphically, even Internet Explorer or an older firefox ESR will do.


  • Assuming you are installing your Steam library on your ext4 partition rather than ntfs one for your Windows install, BeamNG will likely be the easier game to diagnose for your game crashes on launch. The log file to find for BeamNG is located by default in steamapps/compatdata/284160/pfx/drive_c/users/steamuser/AppData/Local/BeamNG.drive/0.32/ as beamng.log. By default in a standard Steam install, your steam library is located at ~/.steam/root/. I am unsure if Bazzite installs Steam as a Flatpak. If it does, the default Steam library should be at ~/.var/app/com.valvesoftware.Steam/data/Steam/. If you chose a custom location for your Steam library, it will be wherever you chose it to be.