!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

892 Members
on your Router! Declaratively manage your switching, routing, wireless, tunneling and more.267 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
22 Nov 2025
@raboof:matrix.orgraboofnot sure, dmesg is pretty quiet on this machine at least16:47:55
@raboof:matrix.orgraboof ha, disabling networking.firewall.checkReversePath seems to have done the trick :). thanks for pointing in that general direction 16:56:40
@hexa:lossy.networkhexayeah, same shit, different stack16:59:12
@raboof:matrix.orgraboofout.png
Download out.png
17:06:17
@raboof:matrix.orgraboofyay17:06:20
@hexa:lossy.networkhexa why aren't you buying into orb instead? https://orb.net/ 17:37:02
@hexa:lossy.networkhexa(anyway, I think they're a nice product to take inspiration from)17:37:33
@raboof:matrix.orgraboofNeat, never seen it before. Yeah I thought "I'll just throw something together real fast". A blackbox-exporter patch, autossh conflicting with nixos-rebuilder-ng and this rp thing later it didn't quite turn out like that, but still enjoying the learning 😊18:40:48
@elisaado:matrix.orgelisaado [moved to @elisaado:elisaado.com]the topic mentions "do not rely on networking.*", why is that? networking. options are so comfy :(23:02:45
@tom:dragar.deTomFrom my understanding: networking.* (without the networking.useNetworkd Option which is problematic in itself) is a bunch of scripts and systemd services which try to configure networking. It's just not the way to do it and networkd and networkmanager will be more robust.23:27:26
@hexa:lossy.networkhexanobody really maintains those scripts23:28:51
@hexa:lossy.networkhexaand they don't keep pace with the network management tools out there23:29:04
@hexa:lossy.networkhexaand in fact no other reasonable distro does this23:30:26
@hexa:lossy.networkhexadebian did this with ifupdown, but that's largely a legacy project23:30:33
@hexa:lossy.networkhexaand ubuntu doubled down on another abstraction layer with netplan23:30:43
@hexa:lossy.networkhexafor headless setups we have networkd and ifstate23:31:13
@hexa:lossy.networkhexaand for headful ones the only reasonable contender is networkmanager23:31:31
@hexa:lossy.networkhexa mellanox did develop ifupdown2, which provided ifreload for gradual migrations between old and new config, really neat 23:32:03
@hexa:lossy.networkhexa * cumulus did develop ifupdown2, which provided ifreload for gradual migrations between old and new config, really neat 23:32:13
@hexa:lossy.networkhexanot sure how well maintained it is these days, but it builds upon the config format established by ifupdown itself, which is … not so nice23:33:01
@hexa:lossy.networkhexahttps://github.com/CumulusNetworks/ifupdown223:33:02
@hexa:lossy.networkhexaand of course there is ifupdown-ng (e.g. provided on alpine) in that ifupdown lineage https://github.com/ifupdown-ng/ifupdown-ng23:34:00

Show newer messages


Back to Room ListRoom Version: 6