Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)I
Posts
1
Comments
340
Joined
3 yr. ago

  • I recommend switching to NixOS only after you have a basic but broad understanding of Linux, many things in NixOS are more complicated than in "normal" Linux, which is needed to archive what it does, but is overwhelming for someone who doesn't know the what and why and where that using Linux brings.

  • Sell their houses to who, Ben? Fucking Aquaman?!

  • Another way would be to create a small derivation that copies the default tor derivation, overwrites the etc folder and then use that as your system Tor. (See runCommand)

     
        
    environment.systemPackages =
    let
      my-custom-tor = pkgs.runCommand "my-custom-tor" {} ''
              mkdir $out
              cp -r ${pkgs.tor}/* $out/
              chmod -R 755 $out
              echo "config" > $out/etc/tor/torrc
              ''
    in
    [
    ...
    my-custom-tor
    ...
    ]
    
      
  • As far as I can see you don't define any way to start Tor in nix but that is how nix normally passes along the tor config.ExecStart=/nix/store/<hash1>-tor-0.4.8.14/bin/tor -f /nix/store/<hash2>-torrcExecStart=${pkgs.tor}/bin/tor -f ${localTorrcDefinition}

    You could define a file in etc that is your torrc, then point your service manager to use that as the -f argument for Tor.

    Another way would be to create a small derivation that copies the default tor derivation, overwrites the etc folder and then use that as your system Tor. (See runCommand)

  • Firsts look at what volumes are, then look at the Volume= quadlet option and remember that any data not part of a volume is going to be deleted.

    Once you set up a volume you can just copy data inside of it from the host using the path you specified in the Volume and access it inside the container using the target path you specified in the volume.

    If you only want to copy something once then you can use podman cp (though you will still need volumes if your container has any persistent data!)

  • You triggered the independent thought alarm

  • So, why are they suddenly allowed to talk about it?

  • He isn't even using that head anyways, seems like some cost cutting is in order.

  • That's why I bake my cake at 2608°C for ~1,8 minutes, it just works™

  • There's a solution you're not seeing, make the notebook part of the production cluster.

  • Run a multi-cluster k8s on your notebook to test then?

  • Check DNS, MTU and do a full wireshark capture from the Client using both curl and the browser.

  • I didn't consider it as valid, one on (phone and internal nvme1), the second one on nvme2 and the third one in the cloud.

    Though I have only two copies of normal data myself, I consider live and cloud to be enough for most data. Everything very important has more backups in other ways (bitwarden has an exportable local version on every logged in device, images are stored in immich on my server making it 3 devices)

    • Maintain three (3) copies of your data: This includes the original data and at least two copies.
    • Use two (2) different types of media for storage: Store your data on two distinct forms of media to enhance redundancy.
    • Keep at least one (1) copy off-site: To ensure data safety, have one backup copy stored in an off-site location, separate from your primary data and on-site backups.

    You have 3 copies, one on your phone and nvme, one on the backup nvme and one in the cloud. You have 2 media, internal SSD and cloud (your phone would count as a third if it wasn't auto synced) You have 1 off-site in the cloud

  • Find a new service you like, add it using rootless podman. That way you can test it without affecting your running system.

  • Try sysctl -w net.ipv4.conf.all.rp_filter=2 on the PC (not vps) or =0 if that doesn't work

  • Do a ping of 8.8.8.8 from your user, then open a new console and run tcpdump -i

    <interface>

    with first your uplink, then wg0. The packets should be seen on wg0 if they're routed correctly and the problem then is on the vps side. Otherwise it's a problem on your local config.

  • Did you add the vps IP to the routing table of your user? ip r add 10.0.0.2/32 dev wg0 table 1070?

  • To shreds you say?