Infrastructure nerd, gamer, and Lemmy.ca maintainer
Ntfs isn’t going to care or even be aware of the hypervisor FS, zfs or btrfs would both work fine.
Making sure you don’t have misaligned sectors, is pretty much the only major pitfall. Make sure you use paravirt storage and network drivers.
Edit: I just realized you’re asking for the opposite direction, but ultimately the same guidelines apply. It doesn’t matter what filesystems are on what, with the above caveats.
Oh look, it’s another old white guy trying to solve a problem he’s not affected by and probably hasn’t personally experienced.
Edit: Sorry that was so negative, but these are all pretty basic things you’re stating. Anyone likely to read this list and action items like this, is likely already staunchly pro black.
Would be good to see some more items that would make people do a double take and say “oh, I do that, I didn’t realize that could be construed as anti black”. Use your experience as a non black person to try and identify ways that a white person might be impacting black people unintentionally.
Wow that’s really disappointing.
Fuck Montague. https://www.vancouverisawesome.com/local-news/vancouver-city-councillor-cleared-in-thin-blue-line-controversy-brian-montague-7730362
Uh, CBSA can’t refuse you if you’re a Canadian citizen for an American DUI. She definitely wasn’t a full Canadian if she had to do anything.
It’s in our charter of Rights.
I have a sliding door that I want to toss a stepper motor on, so my dog can push a button and let himself in / out.
A lot of reasonably competent geeks just never get deep into networking, and VPNs can be overwhelming. It doesn’t really help that for a long time it was all IPSec which basically you need to learn voodoo to manage. Thankfully we have much better tools now, but it’s still just a tech layer that many people don’t touch frequently.
Relay “ams” means you’re using tailscales DERP node in amsterdam, this is expected if you don’t have direct connectivity through your firewall. Since you opened the ports that’s unusual and worth looking into, but I’d worry about that after you get basic connectivity.
So to confirm your behavior, you can tailscale ping each other fine and tailscale ping to the internal network. You cannot however ping from the OS to the remote internal network?
Have you checked your routing tables to make sure the tailscale client added the route properly?
Also have you checked your firewall rules? If you’re using ipfw or something, try just turning off iptables briefly and see if that lets you ping through.
Can your nodes ping each other on the tailscale ips? Check tailscale status
and make sure the nodes see each other listed there.
Try tailscale ping 1.2.3.4
with the internal IP addresses and see what message it gives you.
tailscale debug netmap
is useful to make sure your clients are seeing the routes that headscale pushes.
More aimed towards network operators than self hosters, but https://ring.nlnog.net/
I updated the post to include it. https://youtu.be/ZSC4Bc8LHGM?si=etDbG0Sld2DMdOda
What are you seeing, and what steps have you done to troubleshoot so far?
Yeah but then you have a customer calling and screaming at you “We just launched our big sale of the year and our site has been down for an hour!!!”.
If you let them burst and bill them, you end up with angry clients. If you don’t, you end up with angry clients. Letting them burst and being forgiving with the bill is the better approach IMHO.
https://web.archive.org/web/20241007050114/https://www.thetimes.com/life-style/parenting/article/we-only-learnt-of-our-sons-secret-online-life-after-he-died-at-20-rj3bqfnqn
Trailer of the netflix movie they’re talking about - https://www.youtube.com/watch?v=lM_hkJ0Rl-c