• 0 Posts
  • 211 Comments
Joined 3 年前
cake
Cake day: 2023年6月16日

help-circle


  • Until very recently, I exclusively used the /56 prefix I get from my ISP exclusively. This is still relatively annoying in my case as this prefix changes at least daily for some reason. Clients get their IP via SLAAC.

    I’ve added ULA literally less than a week ago as I have a local reverse proxy I want to handle both local and external request, in both v6 and v4. Obviously more hosts should be accessible from local clients. But I can’t tell local clients apart except by IP, and since the prefix is unstable this would require some sort of hook to update the proxy with that new prefix (might be possible, but seems like a real hassle). So here we are.









  • If you’re using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific “companion” apps. That’s what I use. In my case, it’s backed by my NextCloud, but it used to be Google drive before.

    Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and “just works”.

    Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.