freeatlantis.com is one of the many independent Mastodon servers you can use to participate in the fediverse.

Administered by:

Server stats:

197
active users

#homelab

2 posts2 participants0 posts today

#Proxmox virtualization often goes along with the great Proxmox Backup Server - and we always want statistics! Let's get our metrics of PBS in Grafana!

In this HowTo, we will quickly install and configure the pbs-exporter for hashtag#Prometheus on a Proxmox Backup Server system, add a token for the user and install the hashtag#Grafana dashboard. - #devops #homelab #netops #virtualization #backup #pbs #proxmoxbackupserver

gyptazy.com/howto-proxmox-back

Last night I was amazed that even the most remote devices remained connected to the 'small' MikroTik CAP AC. This morning one of the devices disconnected and couldn't reconnect. I conducted a brief survey (using WifiMan on the Pixel 7 with GrapheneOS, disabling the polling frequency limit for wifi from developer options) and indeed, the difference compared to the Ruckus is quite marked. At the limits of the house, even though the Ruckus shows a weak signal, the devices can still communicate well without packet loss. The MikroTik signal is definitely weaker and more unstable. I expected this for two reasons: I'm comparing two devices from completely different ranges, from totally different generations, and with significantly different prices. In fact, for the price of one Ruckus, you could buy about 12 or 13 CAP AC units. So the question I now ask myself is: was it more sensible to keep two separate access points in two key areas of the house (as I did years ago) or a central Ruckus? I will answer this once I get a more recent generation MikroTik for a client. That will be a clearer test. Ruckus excels in particularly crowded environments, which is certainly not my home.

Is this the year of Linux desktop?

I bought a ”new” laptop. (It’s actually second hand, 5 years old, worn out Lenovo.) I actually didn’t need a new laptop because I already have perfectly good 13” MacBook Pro from 2011 running #LinuxMint. And I’m using it mostly to test and play around with #Linux and to control my #homelab. But there was few things bothering me about the MBP. The display is pretty bad. I didn’t remember it was this bad back in the days. Also because of the old hardware it is strugling to play even 1080p Youtube videos I occasionaly want to watch. And for a change I would like to try to run Linux on more modern hardware instead of this more than a decade old laptop.

This Lenovo has much better display and more modern hardware so it has no problems playing 4k Youtube videos. But suprisingly the Lenovo trackpad is way worse than the old MBP’s trackpad. Also while the MBP is very old at this point, the aluminium unibody still looks better than the boring black Lenovo, which actually just looks identical to my work laptop.

I had choosen to run Linux Mint on the old MacBook, because it works out of the box. It even comes with all the neccesary drivers to get the MBP wifi to work. Not all distros are like that. Mint is very much usable right out of the box. You don’t need to tweak it to make it work. Though it looks and feels more lika a Windows, so I wanted to tweak it a little bit to make it more macOS like by adjusting few settings and installing a dock.

With the Lenovo I wanted to try #Fedora Linux, because it should work with Lenovo laptops right out of the box. And that is the case. I didn’t have any problems installing the Fedora. It comes with Gnome desktop which already is kind of macOS like. But I still wanted to make few small tweaks. I was suprised about the lack of settings to adjust the UI. For few small adjustments I had to install multiple extensions and an app. And what I’ve learned from the internet is that those extensions will probably break at the next major Fedora version update. Which there seems to be about every six months. So let’s see how long this will go.

I doubt this will be the year of Linux desktop. Even though there are distros like Mint which are pretty easy to use, it still might be too steep learning curve for your average computer user who might not know the difference between the internet and a browser.

Hey #homelab users!

You probably already know me by my free @BoxyBSD project and I often got asked about IPv4 addresses. Currebtly, I tinker with a new but also honestly not free service. The idea is creating a static IP service for homelab users. I'm aware that there're already some around, so what could be some benefits here?

- Static single #IPv4 & #IPv6 /48 (so you can subnet your homelab to several /64 without breaking #slacc)
- Bigger subnets (IPv4: /29, /28, /27 | IPv6: /32)
- Full RIPE personalization (inc. abuse & Co)
- #OpenVPN, #Wireguard, #GRE Support
- Auto configure (e.g., you load the wireguard config on any client and the addresses Arena immediately bound to that interface)
- Split usage / multiple tunnels: Use different IPs from your subnets at different locations
- Integration into #BoxyBSD
- Location in Germany or Netherlands (selectable)
- Hosted on redundant #FreeBSD nodes

Pricing:
- The starter package probably around 10€/month (not more) + 15€ setup including 2T traffic
- Pricing for addiriinal/larger subnets not yet sure, probably higher setup fees to avoid hoppers and spamers to keep the addresses clean
- Optional traffic packages (when exceeding speed Limit of 10Mbit which should still be ok for most homelabs)

World this be interesting? Im aware that many ones already do this by VPS themselves, so this might just be a bit easier and optionally offering whole networks including RIPE personalizations.

to sum up what I figured out last night:

Wireguard point-to-point links are as easy to set up as the reverse-proxy apps ('frp' and 'rathole') I've used in the past, and likely more reliable, performant, and secure.

I used this guide to set up such a link: docs.vultr.com/how-to-install-

I'm going to replace my existing setups with this, and I'm pleased that upon finally taking the time to look into it, #Wireguard proved very simple to use.

as for my claims of its likely superiority:

* more reliable due to more highly proficient eyes on the codebase and a bigger userbase smoking out bugs

* more performant due to less copying bytes to/from userspace

* more secure because one point of Wireguard is to have as small a codebase as possible, and again (being in the kernel in part) it has more smart sets of eyes on it; further, it makes use of existing IP networking security practices.

this is a major step forward for Surfhosting. I had a big mental block on deploying Wireguard for quite a while, and now I'm past it. :blobfoxcomfycomputer:

docs.vultr.comHow to Install Wireguard VPN on Debian 12 | Vultr Docs

We techies really are nerds living in our own little bubble. Every time I talk to friends outside of IT, they just laugh at the things we take for granted. In our world, it’s completely normal to assume that everyone has their own domain, self-hosts everything, avoids anything proprietary like it’s the plague, and probably has a dozen side projects running on some self-built server in their closet.

But then there’s my friend, a mechanic, who finds this absolutely hilarious. To him, it’s like expecting every car mechanic to not only have their own repair garage at home but also to manufacture their own tools and, while they’re at it, maybe even start their own car brand. It sounds ridiculous when you put it that way - but to us, that’s just how things should be!

#nerds#geek#geeky

F/LOSS supply chains...

Anyone 'curious' about it these days?

Differences in the way Linux and FreeBSD operate?

Differences in the large stakeholders associated with each project?

Differences in where critical infrastructure is located?

Thoughts?

#FOSS#FLOSS#Linux

#FediHire #GetFediHired 🥳

I'm a
#Programmer/#SoftwareEngineer. I'm most fluent in #Python, have some basics in #Java and #C++, but I'm also taking up new languages like #Javascript and others in my eternal journey of getting better and minimising the impostor syndrome that befalls pretty much all programmers (I feel). I'm also very experienced in #CloudNative/#DevOps technologies, and have been the one devising solutions and maintaining infrastructure in a fast-paced startup environment in my previous employment.

I'm passionate in what I do and those that know me here or IRL would know that I'm always
yapping about the things I'm learning or working on - I love discussing them, and I love helping people out - esp those on the same boat as me.

This passion has led me into writing and maintaining tons of
#FOSS projects like Mango: a content distribution framework based on #Django for #Mastodon and #Bluesky that powers various bots of mine like @lowyat@mastodon.social and @waktusolat@mastodon.social, Charts: a #Helm chart repository for an easy and reproducible deployment strategy for all my projects and everything else I self-host on my #homelab, and Orked: O-tomated #RKE2 distribution, a collection of scripts I wrote that are comprehensively documented to enable everyone to self-host a production-grade #Kubernetes cluster for absolutely free in their homes.

I'm based in Malaysia, but I'm open to just about any on-site, hybrid, or remote job opportunities anywhere. In the meantime though, I'm actively looking for a job in countries like
#Japan and #Singapore, in a bid for a desperate lifestyle change. I've linked below my Portfolio (which you too, could self-host your own!), for those who'd wish to connect/learn more of me. Thank you ❤️

🔗 https://l.irfanhak.im/resume

Mastodon bot module for Django. Contribute to irfanhakim-as/mango development by creating an account on GitHub.
GitHubGitHub - irfanhakim-as/mango: Mastodon bot module for DjangoMastodon bot module for Django. Contribute to irfanhakim-as/mango development by creating an account on GitHub.

Today I took my first baby step into the #homelab world! Got a used HP ProDesk 405 G4 (my first AMD machine!) with Linux Mint 22 “Wilma” on it, from our local nonprofit Free Geek ❤️ freegeek.org

I’ve only 1) built 1 desktop (bought a case + all the components then put them together like LEGOs) 10+ years ago and 2) assembled my Framework 13 in 2023, so it’s all quite intimidating, but this video was so clear and jargon-free that I’d recommend it for all newbies: youtu.be/FnB12C4Npus

For those that #selfhost and have a #homelab and use something like a #minipc for #proxmox, #docker and other small projects e.g. #PiHole, Bluesky, Mastodon, VPN server, #Nextcloud, what hardware would you recommend? Budget around AUD4-500 (USD250-300), dual-NIC in case I do something routery with it later, doesn't need any wireless connectivity, not going to be connected to monitors or do any media serving/transcoding, won't be a NAS (but I reckon 512GB storage is minimum), power and noise not a problem as it'll be in a comms rack in garage (but would prefer not some huge 2U ProLiant or whatever just so it doesn't wrench it off the wall. I don't mind having "last year's" spec, or considering a refurbed SFF desktop I can load with RAM, storage and NICs.

💻 HomeLab Chanukah 💻

Ok not really, but every HomeLab hardware weekend feels like a wonderful gift! 🎁

Today I'll be setting up a new 25U rack, and then mostly recuperating. I'm also working on the FreeBSD port of this OSS KVM: crowdsupply.com/techxartisan/o .. couple of Qt6 bugs with serial usb handling but otherwise can get video just fine. It arrived yesterday, so of course the first thing to do is de-pack the Debian package and start reviewing repo source. Love it.

Disregard the boxes and living room clutter in these photos, we're still unpacking from the move.