One small rule to keep things valuable for everyone: this isn’t a place just for advertising. If someone joins only to promote themselves or post offers without contributing, they may be removed. That said, if you want to let people know you’re available for work or that you're looking someone for hire, that’s totally fine - just do it in a helpful way: - Show something you’ve built or a problem you solved - Share a bit of how you approached it - And then, if you want, mention that you're open to opportunities or that you're hiring This way others can actually see what you can do.

I recently switched my Omarchy Linux setup to give QEMU/KVM VMs direct LAN access using a native bridge (br0) and systemd-networkd. Here is the exact config I used to get it running without sudo. I dropped three files into /etc/systemd/network/ to define the bridge and attach my interface (eno1). - /etc/systemd/network/10-br0.netdev [NetDev] Name=br0 Kind=bridge - 20-eno1.network [Match] Name=eno1 [Network] Bridge=br0 - /etc/systemd/network/20-br0.network [Match] Name=eno1 [Network] Bridge=br0 - /etc/systemd/network/20-br0.network [Match] Name=br0 [Network] DHCP=yes Then I just ran sudo systemctl restart systemd-networkd.service To let my VMs use this bridge without root, I updated two config files. - /etc/qemu/bridge.conf allow br0 - /etc/libvirt/qemu-bridge-helper.conf allow br0 After a sudo systemctl restart libvirtd, my VMs connect directly to the network via br0 instantly. Clean, native, and no sudo needed for launch.

This is a space for anyone interested in programming, Linux, self-hosting, networking, and IT in general. Whether you're just starting out or already experienced, you're very welcome here. The idea is simple: learn together, share what you know, help others, and show what you're building along the way. Feel free to ask questions at any level. If you're working on something—home lab setups, ESPHome, Node-RED, Proxmox, scripts, or anything else—don’t hesitate to share it. Even small projects or experiments are worth posting. I’ll also be sharing my own learning journey, especially around Proxmox, networking, and IoT. Expect real setups, things that worked, and things that didn’t. Introduce yourself To get started, say hello in the comments: - What are you learning right now? - What are you building or experimenting with? - What would you like to improve or achieve next? Looking forward to seeing what you’re working on.

Hello Engineers, I'm currently testing a self-hosted file-sharing solution, Syncthing. Below is a list of options that help achieve a reasonably secure configuration. I haven't described these options in detail, all of them can be found in the documentation. Settings -> General -> Device name -> Fill in the device name Settings -> General -> Anonymous Usage Reporting -> Disable Settings -> GUI -> Start Browser -> Disable Advanced -> GUI -> Address -> Fill in the local network interface ip address Advanced -> GUI -> Enabled -> Leave Enabled Advanced -> GUI -> Password -> Fill in (password to log in to the GUI) Advanced -> GUI -> Use TLS -> Enable Advanced -> GUI -> User -> Fill in a user name (user to log in to the GUI) Advanced -> Options -> Always Local Nets -> Fill in a local network interface Advanced -> Options -> Announce LAN Address -> Disable Advanced -> Options -> Crash reporting Enabled -> Disable Advanced -> Options -> Global Announce Enabled -> Disable Advanced -> Options -> Nat Enabled -> Disable Advanced -> Options -> Relays Enabled -> Disable Advanced -> Options -> Local Announce enabled -> Enabled by default, should be enabled only if local address explicitly specified by the option "Always Local Nets" Advanced -> Options -> Overwrite Remote Device Names On -> Enable Advanced -> Options -> Listen Address -> Left default

When I spin up a new Ubuntu VM on Proxmox, I like to keep the setup minimal but fully functional. My goal is always the same: get proper integration with Proxmox and enable quick remote access via RDP. Here’s the exact workflow I use. Initial Setup After Installation After installing Ubuntu, I skip all optional extras: - Ubuntu Pro → I choose “Skip for now” - Help Improve Ubuntu → I select “No” Once I land on the desktop, I immediately update everything: - sudo apt update - sudo apt upgrade -y Installing QEMU Guest Agent One of the first things I install is the QEMU Guest Agent. It makes Proxmox much more aware of what’s happening inside the VM. - sudo apt install qemu-guest-agent -y After that, I shut the VM down: - sudo poweroff Then on the Proxmox side: - I remove the installation ISO (Hardware → CD/DVD → Remove) - I enable the QEMU Guest Agent (Options → QEMU Guest Agent → Enable) When I boot the VM again, I quickly check if it worked by looking at the Summary tab, if I see the IP address there, I know everything is working correctly. Setting Up XRDP For remote access, I usually go with XRDP since it’s simple and works well enough for most use cases. First, I install it: - sudo apt install xrdp -y Then I fix a small but common permission issue: - sudo adduser xrdp ssl-cert Next, I tweak the XRDP startup script: - sudo nano /etc/xrdp/startwm.sh At the top of the file, I add: - export DESKTOP_SESSION=ubuntu - export GNOME_SHELL_SESSION_MODE=ubuntu - export XDG_CURRENT_DESKTOP=ubuntu:GNOME After saving the file, I restart the service: - sudo systemctl restart xrdp Connecting to the VM At this point, I just grab the IP address from the Proxmox Summary tab and connect using any RDP client (Remmina). I log in with the same user I created during installation, and that’s it, I have a working GNOME desktop over RDP. Optional Notes If I happen to be using UFW, I also open the RDP port: