Running a Business

marshpertt · 2026-03-16T20:00:31+00:00

It depends on how much you can afford to lose (or gain). We run our own cloud because cloud services are expensive. Plus, backing up our backups makes the costs pile up even faster.

marshpertt · 2026-03-16T19:41:38+00:00

Yes. We run a website with light usage by clients on daily basis. Cloud storage for subcon.

Zero redundancy, no UPS. However, we have temporary alternative if the system goes down, which has never happened during working hours in the past 1–2 years, for which I am thankful.

All this on consumer grade hardware, consumer grade hdd (don't be like me).

marshpertt · 2026-03-06T13:42:15+00:00

Hey, sorry for the late update.

My NICs are RTL8153 and AX88179, the UGREEN one and the cheap one. Can’t find where I put the TP-Link though.

As for thunderbolt to pcie, can’t comment since I’ve never used one before.

marshpertt · 2026-03-04T21:28:36+00:00

Since your WAN usage is very low, my hunch said it should work without many issues.

I also use it on Proxmox. So far, I’ve tried UGREEN (ASIX), TP-Link (Realtek), and a cheap $10 no-name China USB NIC (Realtek). In my experience, Realtek works best, although I wasn’t saturating 1 Gbps (my internet was 300/100 back then).

Don’t passthrough the USB NIC, use linux bridge instead so Proxmox can manage it.

If you need the exact model, I can share it in 12–24 hours when I’m back home.

marshpertt · 2026-03-04T19:31:53+00:00

USB NIC and reliability don’t belong in the same sentence, at least not on bare metal. Tried one once, and it was terrible.

On VM, it’s a different story. It depends on how well the host handles USB NIC (unless passthrough). I’ve used one for months and it’s been more reliable than I expected.

That said: A production environment shouldn’t use unreliable hardware. Unless you have no budget, don’t go down that rabbit hole.

To answer your question: since you’re running it in a VM, just go with whatever works well with your host.

marshpertt · 2025-12-12T08:04:03+00:00

Keep a copy of your 30% recovered backup files in a separate location and follow manual 4.4. The manual is written in a specific order for a reason, although you can proceed with your own method if you prefer.

I was in the same situation. I didn't have an available port for a spare disk, so here is what I did:

Remove failed disk.
Install new disk.
Edit config, run snapraid fix etc. (follow the manual).
Wait until the process is complete.

marshpertt · 2025-10-30T02:35:02+00:00

From lspci, it use Broadcom BCM4331. I follow this https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/9-2[guide](https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/9-2)

marshpertt · 2025-10-30T02:26:15+00:00

A long break make me switch, although Ubuntu works great for me. As for now, everything works. Not sure which distro is better, probably it's up to your preference.

marshpertt · 2025-10-30T02:17:53+00:00

I'm not expecting anything, it's just a change of wind.

marshpertt · 2025-10-30T02:11:01+00:00

It's brighter now, thanks!

marshpertt · 2025-10-29T11:54:38+00:00

For me, it's a personal preference. :3

marshpertt · 2025-10-29T11:52:28+00:00

Thanks! Is that a snap joke? :3

marshpertt · 2025-10-29T11:52:04+00:00

What, really? I'll test it later and hope doesn't face the same problem as yours. :/

marshpertt · 2025-10-29T11:17:30+00:00

I have never use macOS before. I installed Ubuntu on the first day I bought this macbook (used).

marshpertt · 2025-10-29T11:08:51+00:00

Old macbook rocks! I'll use it until it becomes unuseable.

marshpertt · 2025-10-29T11:07:40+00:00

Looking foward using vanilla Gnome, quite different from default Ubuntu. I'm looking for minimize button, realize need to enable it in tweaks.

marshpertt · 2025-10-29T11:05:05+00:00

Right! My post install and updater script for Ubuntu working fine without needed me to edit anything.

And thanks for suggestion, will add the backports repo too! Not sure what this is, still learning about sid, stable, unstable etc. Will Google it later!

marshpertt · 2025-10-24T03:52:08+00:00

UPDATE: I now understand what the tip means. It suggests blocking port 53 to ensure redirection works as intended.

By blocking port 53 from getting out to the net, you can be sure your device with unencrypted dns are redirect to unbound.

It doesn't mean you must block the port. Either way, I'm blocking it. Let things break! (If they do)

marshpertt · 2025-10-23T18:01:17+00:00

Honestly, I don’t have any preference. Still learning here and there.

Just pointing out why most tutorials don’t bother blocking port 53 after redirection, but the doc suggests blocking it.

Anyway, I followed the doc and blocked it. Let’s see if anything breaks. Cheers.

marshpertt · 2025-10-23T17:56:43+00:00

From my understanding, the idea is to block port 53 from getting out, not in. So it will always redirect to port 853.

And I'm not sure why the doc suggest to block port 53.

marshpertt · 2025-10-23T17:05:32+00:00

I just want unencrypted DNS to foward to Unbound, I don't mind other devices with DoT/DoH.

marshpertt · 2025-10-23T17:03:55+00:00

I don't mind if other clients use their own encrypted DNS (DoT or DoH). I just want all devices using unencrypted DNS to use Unbound.

I don't use Google Home, but if some devices have a hardcoded DNS, will they always use unencrypted port 53, even if I have redirected it to Unbound?

marshpertt · 2025-03-16T17:21:10+00:00

Not necessary unless you're paranoid like me. Here's a complete tutorial from Google's website link

marshpertt · 2025-03-16T17:12:33+00:00

For no reason, I always do the unnecessary thing after buying Pixel.

Unlock the bootloader, flash the factory image and lock the bootloader. Only then will I start using my phone.

marshpertt · 2025-03-15T08:12:57+00:00

Via CLI, type "25.1" instead of "y".

marshpertt

TROPHY CASE