| 1 Jul 2025 |
 magic_rb | In reply to @zhaofeng:zhaofeng.li
Is there a netbox alternative by any chance? Somehow every time I try to upgrade this thing, it ends up in disaster... 🙃 https://github.com/oddlama/nix-topology may work for you | 20:51:33 |
 Zhaofeng Li | interesting, might give it a try as an additional tool | 20:55:20 |
| Zhaofeng Li | but I'm specifically looking for a IP management tool | 20:55:42 |
 hexa | i use a plain text file for that 😄 | 20:56:20 |
| Zhaofeng Li | I don't really use many of netbox's features besides ipam | 20:56:20 |
| hexa | 172.23.42.0/28 fd42:23:42::/52
172.23.42.1 fd42:23:42:b100::/56 juno
172.23.42.2 fd42:23:42:b200::/56 snafu
172.23.42.3 fd42:23:42:b300::/56 ganymede
172.23.42.4 fd42:23:42:b400::/56 helios
172.23.42.5 fd42:23:42:b500::/56 eris
172.23.42.8 fd42:23:42:b800::/56 io
172.23.42.9 fd42:23:42:b900::/56 nyx
172.23.42.10 fd42:23:42:ba00::/56 helix
172.23.42.11 fd42:23:42:bb00::/56 titan
172.23.42.64/26 fd42:23:42:100::/64 io LAN
172.23.42.128/26 fd42:23:42:110::/64 io WLAN
172.23.42.224/31 fd23:42:ff00::/64
172.23.42.224 fd42:23:42:ff00::1 io
172.23.42.225 fd42:23:42:ff00::2 ganymede
172.23.42.226/31 fd42:23:42:ff01::/64
172.23.42.226 fd42:23:42:ff01::1 io
172.23.42.227 fd42:23:42:ff01::2 juno
172.23.42.228/31 fd42:23:42:ff02::/64
172.23.42.228 fd42:23:42:ff02::1 ganymede
172.23.42.229 fd42:23:42:ff02::2 pixel3a
172.23.42.230/31 fd42:23:42:ff03::/64
172.23.42.230 fd42:23:42:ff03::1 ganymede
172.23.42.231 fd42:23:42:ff03::2 juno
172.23.42.232/31 fd42:23:42:ff04::/64
172.23.42.232 fd42:23:42:ff04::1 ganymede
172.23.42.233 fd42:23:42:ff04::2 helios
172.23.42.234/31 fd42:23:42:ff05::/64
free
172.23.42.236/31 fd42:23:42:ff06::/64
172.23.42.236 fd42:23:42:ff06::1 ganymede
172.23.42.237 fd42:23:42:ff06::2 titan
172.23.42.238/31 fd42:23:42:ff07::/64
172.23.42.238 fd42:23:42:ff07::1 juno
172.23.42.239 fd42:23:42:ff07::2 helios
172.23.42.240/31 fd42:23:42:ff08::/64
172.23.42.240 fd42:23:42:ff08::1 juno
172.23.42.241 fd42:23:42:ff08::2 nyx
172.23.42.242/31 fd42:23:42:ff09::/64
free
172.23.42.244/31 fd42:23:42:ff0a::/64
free
172.23.42.246/31 fd42:23:42:ff0b::/64
172.23.42.246 fd42:23:42:ff0b::1 ganymede
172.23.42.247 fd42:23:42:ff0b::2 nyx
| 20:57:00 |
| hexa | well, this is wildly outdated | 20:57:18 |
 adamcstephens | i have a pretty simple nix attrs in a file for my networks, and store the rest of the reserved IPs in the dnsmasq config | 20:57:27 |
| hexa | what is the real crime? | 20:57:46 |
| adamcstephens | my HA dnsmasq failover setup is the crime indeed | 20:58:07 |
| hexa | having your ip address plan in a plain text file or having it in dnsmasq? | 20:58:13 |
| adamcstephens | dnsmasq in nixos config to be clear | 20:58:32 |
| Zhaofeng Li | this is probably doable, but I kind of miss the visualization netbox gives me | 20:58:56 |
| Zhaofeng Li | as well as the one-click assignment feature | 20:59:17 |
| 2 Jul 2025 |
|  shx228 set a profile picture. | 01:50:06 |
|  blocklisted joined the room. | 14:48:26 |
| magic_rb | In reply to @zhaofeng:zhaofeng.li
this is probably doable, but I kind of miss the visualization netbox gives me What id do is have it all in nix, rhen rely on nix-topology or similar for visualization | 21:24:37 |
| Zhaofeng Li | yeah, I might consider it, but there's just a bunch of abstractions that I've need to build (mostly wrangling with CIDRs) | 21:40:44 |
| Zhaofeng Li | by the way, migrated everything over to babel from OSPF and it's actually working quite well | 21:41:22 |
| magic_rb | In reply to @zhaofeng:zhaofeng.li
yeah, I might consider it, but there's just a bunch of abstractions that I've need to build (mostly wrangling with CIDRs) Makes me wish we had bitshifts in nix | 21:44:58 |
| Zhaofeng Li | * yeah, I might consider it, but there's just a bunch of abstractions that I'll need to build (mostly wrangling with CIDRs) | 21:45:22 |
| 3 Jul 2025 |
 Christian Theune | hexa (clat on linux when): i'm debugging some scalability issues with the ACME unit structure we're having. after a couple of interesting bits I now face https://github.com/NixOS/nixpkgs/pull/81371#issuecomment-605526099 and would like to consider alternatives to adding the renew services to multi-user.target. Specifically, you mention that you'd like changes to be applied, however, in our situation this always causes service restarts and massive (local) lego calls that add up in unfortunate ways - even if nothing has changed. aside from bolting on an option whether to do this or not, I'm wondering whether we can change it in a way that will leverage the regular "this service has changed, lets restart it". I'm currently playing around with remainafter exit, but that causes other things to explode. It's a bit of a minefield ... I'm available to chat basically the whole day if you'd like to give some input on this ... | 05:09:22 |
 @emma:rory.gay | this might be offtopic for here, but what's the mostefficient way to mount a remote filesystem? | 09:56:50 |
| @emma:rory.gay | currently using sshfs and its slow as molasses (and doesnt keep its parallel connections alive it seems) | 09:57:11 |
 K900 | NFSv4 is decently fast | 09:58:18 |
| @emma:rory.gay | (latency is probably the biggest blocker here) | 09:58:20 |
| @emma:rory.gay | does it support clientside caching? | 10:01:28 |
| K900 | Yeah | 10:02:32 |
| @emma:rory.gay | ooh neat, guess ill still be dealing with running a few recursion commands to preload data, but sounds like it might be less painfully slow than sshfs | 10:03:11 |
| @emma:rory.gay | okay, so if i undertand it right, the format of /etc/exports is like this, right?
/path/to/exported/dir client_ip(flags)? | 10:11:31 |
