!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

884 Members
Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` for interface and routing setup, use systemd-networkd, ifstate or NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org260 Servers

Load older messages


SenderMessageTime
18 Jun 2026
@whispers:catgirl.cloudwhispers [& it/fae] changed their display name from whispers [& it/fae] to meow meow.18:47:28
@whispers:catgirl.cloudwhispers [& it/fae] changed their display name from meow meow to whispers [& it/fae].19:12:58
19 Jun 2026
@matthewcroughan:defenestrate.itmatthewcroughan @k900:0upti.me erryone I show my bpi-r4 to seems to hate systemd and nixos for routers, and I show them how well networkd and the bpi-r4 are working and they are surprised 12:20:15
@matthewcroughan:defenestrate.itmatthewcroughanBut I didn't really mess with openwrt or deeply configuring it, so I don't know what I'm missing12:22:01
@k900:0upti.meK900...OK?12:24:03
@matthewcroughan:defenestrate.itmatthewcroughanAny thoughts on nixos as router and whether you still like it after doing things with networkd for a while?12:23:56
@k900:0upti.meK900Seems fine12:25:52
@k900:0upti.meK900Definitely prefer it to having to manually configure openwrt12:26:04
@matthewcroughan:defenestrate.itmatthewcroughanMatrix is slow, sorrt12:27:03
@matthewcroughan:defenestrate.itmatthewcroughan * 12:28:26
@matthewcroughan:defenestrate.itmatthewcroughanIs networkd doing something similar to ifstate then?12:50:25
@k900:0upti.meK900 I have no idea what you're trying to ask 12:52:10
@matthewcroughan:defenestrate.itmatthewcroughanlike why is networkd so good compared to whatever else, and what is "whatever else", the scripted stuff?12:51:26
@matthewcroughan:defenestrate.itmatthewcroughan Is the networking.* module in nixpkgs actually something that people want to keep around? It makes me wonder why we have it, when we have networkd 12:53:22
@k900:0upti.meK900 I don't think networkd is particularly amazing 12:54:29
@matthewcroughan:defenestrate.itmatthewcroughan the networking.* module ultimately just produces networkd config, and allows you to switch between the scripted and networkd implementation, but it seems like this would be a pain to maintain 12:54:09
@k900:0upti.meK900 But it's like 12:54:33
@k900:0upti.meK900Fine12:54:37
@k900:0upti.meK900The scripted networking predates networkd and significantly predates networkd being usable12:54:53
@k900:0upti.meK900And is in fact marked as kinda-deprecated already12:55:04
@vengmark2:matrix.org@vengmark2:matrix.org left the room.12:55:30
@matthewcroughan:defenestrate.itmatthewcroughan Yeah, so when scripted networking is completely deprecated, you could also deprecate the networking.* modules altogether, and then people can just write networkd config, right? 12:58:55
@matthewcroughan:defenestrate.itmatthewcroughan Or is the networking.* module doing more than I think? 12:59:41
@k900:0upti.meK900Yes13:00:42
@me:m4rc3l.deMarcel E.g. networking.ifstate is not part of scripted networking 13:14:36
@matthewcroughan:defenestrate.itmatthewcroughan Is it actually possible to opt out of the networking module altogether? 13:35:35
@me:m4rc3l.deMarcelI don't really know13:37:30
@me:m4rc3l.deMarcel

disabledModules = [ "services/databases/postgresql.nix" ];

Could be working, one just needs to gather all scripted related modules

13:38:23
@k900:0upti.meK900 Not currently 13:44:39
@k900:0upti.meK900Probably a bad idea really13:44:47

Show newer messages


Back to Room ListRoom Version: 6