| 1 Jul 2025 |
 magic_rb | Interesting | 12:26:26 |
 hexa (clat on linux when) | wireguard just provides a transfer network, just make sure AllowedIPs= does not block the traffic you intend to send over it | 12:27:50 |
| magic_rb | Mhm yeah thats how i understood things too, cool, maybe one day | 12:28:58 |
 Zhaofeng Li | Yeah, AllowedIPs is a pain for dynamic routing... each edge in my mesh is on a separate interface with AllowedIPs=::/0 | 12:40:54 |
| hexa (clat on linux when) | yeah, same here | 12:41:08 |
 xanderio | Ok after looking deeper into this issue, I'm not convinced that this is the initial networking issue i've assumed. The more I look into this the more confused I get. | 12:58:52 |
| Zhaofeng Li | actually I was thinking of modifying the wireguard client to have a fake ethernet header that's solely used to select the peer 🙃 | 13:01:16 |
| Zhaofeng Li | but I never got to do it, and being able to see the peer name in bird (since it's the interface name) is a nice side-effect of having separate interfaces | 13:02:58 |
| xanderio | I thing the issue is that the nginx on that host is configured to listen on "localhost" and not on 0.0.0.0. This probably cases this issue. Fun times debugging this 🫠| 13:16:02 |
|  shx228 joined the room. | 19:17:09 |
| Zhaofeng Li | Is there a netbox alternative by any chance? Somehow every time I try to upgrade this thing, it ends up in disaster... 🙃 | 20:32:35 |
| hexa (clat on linux when) | sheets | 20:33:53 |
| Zhaofeng Li | like... literally google sheets? | 20:36:47 |
| hexa (clat on linux when) | the answer is … not really, no great solutions | 20:44:36 |
| hexa (clat on linux when) | so write your small number of things into a document with a structure that works for you | 20:44:53 |
| hexa (clat on linux when) | setting up a netbox for private use is usually overkill | 20:45:04 |
| 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 (clat on linux when) | 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 (clat on linux when) | 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 (clat on linux when) | 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 (clat on linux when) | what is the real crime? | 20:57:46 |
| adamcstephens | my HA dnsmasq failover setup is the crime indeed | 20:58:07 |
| hexa (clat on linux when) | 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 |
