!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

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

Load older messages


SenderMessageTime
4 Oct 2025
@aleksana:mozilla.orgaleksana 🏳️‍⚧️ (force me to bed after 18:00 UTC)
In reply to @k900:0upti.me
https://github.com/K900/linux/tree/bpi-r4-test
Okay thanks
06:31:02
@k900:0upti.meK900That's continuing my previous train of thought06:31:02
@k900:0upti.meK900The wireless actually works just fine on mainline06:31:09
@flokli:matrix.orgflokliAka, getting most of the fixes massaged upwards is still worthwhile 06:31:04
@k900:0upti.meK900At this point the only things 6.17 is missing is the Ethernet06:31:21
@k900:0upti.meK900 It's not that it's not worthwhile 06:31:34
@k900:0upti.meK900It's that no one has found the time, so far06:31:43
@flokli:matrix.orgflokliSo no more custom hacks needed for fixed regulator stuff to get it not to oops?06:31:47
@k900:0upti.meK900The regulator stuff is not a hack06:31:54
@k900:0upti.meK900I've verified with the schematics06:32:07
@flokli:matrix.orgflokliOk, but then the device tree is incomplete?06:32:44
@k900:0upti.meK900Well, one line of it, yes06:33:03
@k900:0upti.meK900I'm not counting all the tiny fixes all over06:33:32
@k900:0upti.meK900 The only big missing bit that will be hard to get merged is the Ethernet 06:33:43
@k900:0upti.meK900Because the netdev people can't agree on shit06:35:22
@flokli:matrix.orgflokliAck06:47:11
@elisaado:matrix.orgelisaado hm yeah fair enough 07:21:43
@elvishjerricco:matrix.orgElvishJerricco(I have more patches because I use mine just as a switch, and mainline doesn't have hardware fastpath support for bridges yet)07:28:48
@elvishjerricco:matrix.orgElvishJerricco(i.e. if you bridge the two 10Gbps ports you'll only get like ~3.5Gbps through them)07:29:34
@aleksana:mozilla.orgaleksana 🏳️‍⚧️ (force me to bed after 18:00 UTC)
In reply to @elvishjerricco:matrix.org
(I have more patches because I use mine just as a switch, and mainline doesn't have hardware fastpath support for bridges yet)
Thanks, I'll ask you after I buy it
07:29:46
@aleksana:mozilla.orgaleksana 🏳️‍⚧️ (force me to bed after 18:00 UTC) changed their profile picture.08:41:07
@aleksana:mozilla.orgaleksana 🏳️‍⚧️ (force me to bed after 18:00 UTC) changed their profile picture.08:41:29
5 Oct 2025
@rouven:rfive.de@rouven:rfive.de left the room.19:27:33
6 Oct 2025
@frederic:scs.ems.hostFrédéric Christ changed their display name from Frédéric Christ (🚄 15.09. - 29.09.) to Frédéric Christ.09:24:51
7 Oct 2025
@x10an14:matrix.orgx10an14 How can I add an interface to networking.firewall.interfaces? My Nebula VPN interface does not show up there =S 13:27:45
@x10an14:matrix.orgx10an14This might be an XY questien, becaulse I'm trying to debug why my Nebula VPN doesn't seem to work once a connection relies on a port (pings to/from lighthouse work, but nothing else, nor pings between non-lighthouses)13:29:10
@jappie:jappie.devjappieis `networking.firewall.trustedInterfaces` what you're looking for?13:35:25
@x10an14:matrix.orgx10an14It is not set by the module authors/maintainers (https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/networking/nebula.nix#L317), so I doubt it, but I'll give it a try!13:37:24
@x10an14:matrix.orgx10an14 This change allows dig dns queries to a (non-lighthouse) node to work again, but so far seems only from lighthouse itself (where ping worked already in both directions) 13:41:34
@x10an14:matrix.orgx10an14 Lemme double-check whether or not trustedInterfaces made the difference 13:41:53

Show newer messages


Back to Room ListRoom Version: 6