When I follow this guide and get to the part where DNS server of wwan to the root router's IP, I am not able to ping anything from a ssh session into the router (I get "bad address 'google.com'". So, I set the DNS address to 1.1.1.1 which restored ping's functionality. However, with this configuration the network does not appear to be shared at all. My PC, connected to the LAN port, cannot access the internet (regardless of forcing a static IP for the pc)
mat
joined 2 years ago
Have you asked whether they'd be okay with a dual-boot? I recently started work as well (gamedev) and while most of the studio is on Windows I was able to set up a NixOS install for productivity (and to test the game on more configs).
You can't self-host Ghost? I'd like to stay on the same domain indeed, not wanting to also mess up folks subscribed to RSS.
Awesome! Once this is out, I think I will migrate my blog from WriteFreely to Ghost. I hope I can reduce disruption for existing followers though...
I like this picture of a cat that shows up every time this repo is linked. Good things are to come when this cat appears on my feed.
Thank you! It definitely does, I will be using that Restic article for sure! I actually use NixOS on my main laptop, which I found via Vimjoyer's videos. It's great, though I wish documentation for more advanced usage was more readily available. I started making the server, currently my biggest roadblock is testing the infrastructure without going live (I made the flake generate a VM for now but it takes a long time to build it every edit and I can't even get ssh working) and figuring out how I'll eventually install it with minimal downtime.
I want to move my whole server to NixOS. It's gotten to the point where I have no idea where all the Ubuntu config files went, and handling half of it via Docker vs baremetal. I hope this will allow me to set up proper backups as well, and maybe get better at Nix! I started a few days ago using the VM feature, but it's tricky to work on for now, perhaps I haven't found the right workflow.
The "immutable" type of distros could be worth a shot. They don't let you break the system and if anything does break, you can undo it with a reboot, so they tend to be pretty stable. My family runs a few flavors of Universal Blue, which are based on Fedora and hasn't broken for them, but I don't know the exact hardware. I've been running NixOS (also immutable) on a Framework 16 since the laptop came out, I can't count a single hardware issue I encountered. However, NixOS does come with a steep learning curve, so it's hard to recommend, and it also has trouble running software that hasn't been already packaged for it.
Genuinely curious, how do they update? My server (ubuntu) yells at me every time I ssh in to reboot "as soon as possible" because "livepatch has fixed vulnerabilities". So if you don't reboot, you don't get kernel updates, and your server becomes vulnerable?
I realize I never replied, but thank you! I got into contact with them and am now in the final stages of getting it all set up to start in a couple months. They seem awesome and I am excited to work with them!
My parents run a business, and besides having me install it and do the initial setup, they both use Linux fine and have adjusted great from their previous machines. I moved them to it mainly because of performance and being tired of fixing printers on Windows. LibreOffice runs, Firefox runs, a video editor works, and OBS runs, so it's enough for their use. They're both on Wayland, one on EndeavourOS (w/ a graphical app store set up ofc) and the other on Fedora Kinoite, w/ nouveau drivers and no issues so far!
I've tried to match your setup, but to no avail.
Interfaces:
lan
Static address (192.168.2.1) Firewall zone: lan
wwan
Static address (192.168.0.211) Device: phy0-sta0 (listed as the client in the dropdown) Gateway: 192.168.0.1 Use custom DNS servers: 1.1.1.1 (using root router's IP causes DNS to stop working) Firewall zone: WLAN
repeater_bridge
Relay bridge Relay between: lan wwan Firewall zone: unspecified
Firewall zones: lan ⇒ WLAN accept accept accept WLAN ⇒ lan accept accept accept
With this, I am able to ping google.com from a openwrt ssh session, but not my laptop connected w/ ethernet (and a static ip). In the interfaces list, lan is green, repeater_bridge is grey, and wwan is red. I tried running /etc/init.d/firewall stop but still no luck.