I’d recommend avoiding spinning disks and going all ssd if possible.
You can get 12v in atx power supplies.
You may want to consider something like a Lenovo tiny with a few large ssds.
Infrastructure nerd, gamer, and Lemmy.ca maintainer
I’d recommend avoiding spinning disks and going all ssd if possible.
You can get 12v in atx power supplies.
You may want to consider something like a Lenovo tiny with a few large ssds.
I spent a year tracking down random afci circuit breaker trips, until I realized it was my powerline Ethernet. Never again.
Also just to be clear, everything in the sata section of your motherboard bios is irrelevant unless you’re using onboard ports for something
If everything is in the hba, you could turn off sata on your mobo if you wanted.
You won’t see Drives from an hba, in your bios. Those drives aren’t plugged into a controller managed by your bios.
Do you see them if you boot into Linux and run lshw, or if you go into the bios for the controller card?
If you don’t get prompted or see the controller bios loading, you may need to enable something like “option Rom” in your normal bios.
Lspci doesn’t care about drivers. What’s lshw say?
Sounds like maybe a fake card or something. Do you also have a 3060 in there?
If you need support outside of business hours, you’re fucked.
Friend had a network misconfig on their side take his server out on Friday night and they didn’t fix it until Monday.
SMB.
The windows nfs implementation sucks, but everything talks SMB.
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.
Yes it’s really that easy. Raid in Linux is usually at the partition level, not the whole device. The bootloader resides in the first few blocks of the disk before your partitions, and isn’t included in the raid.
Use grub-install on the new disk device, ie /dev/sda
Replace one disk, let the raid rebuild. Do the same with the other disk. Do an mdadm grow, then maybe fdisk / lvm / resize fs depending on your setup. Don’t forget to install a bootloader when you put a new disk in.
Making a new array and migrating data is for chumps.
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.
The tailscale client should have created an interface, but I’ve never used it on a box also running wg. You don’t have a tailscale specific interface in ip addr show
at all? That’s… odd.
Do you have a device at /dev/net/tun
?
How do I do this?
Run ip route show table all
I would expect to see a line like:
192.168.178.0/24 dev tailscale0 table 52
Out of curiosity on a remote node do tcpdump -i tailscale0 -n icmp
and then do a ping from the other side, does tcpdump see the icmp packets come in?
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.
That should be all that’s required. Are you using ACLs? If so you need to provide access to the subnet router as well as a rule to the IP behind it
Did you enable the route in the admin web ui?
Not home lab specific, but a few things around my house to help inspire you.
Cable fingers
Nuc wall mount
Tool peg board mounts
Heavy ass speaker onto a vesa pole mount to get them above my monitors
Couch gaming gear
Sonos wall mount
If you have a router, you already own one.
Pointing a hostname to your ip doesn’t do anything meaningful.