!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

795 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.org231 Servers

Load older messages


SenderMessageTime
2 Jan 2025
@hexa:lossy.networkhexa (clat on linux when)enable debug logging for networkd and grep for dhcp to find out why it enables it14:54:18
@antifuchs:asf.computerantifuchsjust noticed that I had vestigial dhcp relaying from that workaround activated14:54:50
@antifuchs:asf.computerantifuchsare you using useNetworkd or enabling manual networkd configuration?14:55:05
@antifuchs:asf.computerantifuchs* just noticed that I had vestigial dhcp relaying from that workaround activated; rebuilding14:55:30
@k900:0upti.meK900No useNetworkd here14:59:59
@hexa:lossy.networkhexa (clat on linux when)systemd.network.enable14:58:33
@antifuchs:asf.computerantifuchsic. ok, so disabling DHCP serving for systemd on all interfaces (even those without kea) does allow kea to listen on :6714:59:59
@antifuchs:asf.computerantifuchssmells like an annoying trap tbh15:00:10
@hexa:lossy.networkhexa (clat on linux when)well, given that the socket is bound to a wildcard address, that is to be expected15:00:26
@antifuchs:asf.computerantifuchsI mean, systemd manages to bind multiple times to the wildcard there too, so I assumed that would work15:02:12
@hexa:lossy.networkhexa (clat on linux when)probably use SO_REUSEPORT15:03:26
@hexa:lossy.networkhexa (clat on linux when) * probably uses SO_REUSEPORT 15:03:43
@antifuchs:asf.computerantifuchs* ic. ok, so disabling DHCP serving for systemd-networkd on all interfaces (even those without kea) does allow kea to listen on :6715:04:29
@jassu:kumma.juttu.asiaJassukoIf only systemd-networkd finally supported network namespaces as a first class citizen... -_-15:05:09
@hexa:lossy.networkhexa (clat on linux when)ideally, yes15:08:20
@hexa:lossy.networkhexa (clat on linux when)but make sure you can't live with a vrf instead15:08:28
@hexa:lossy.networkhexa (clat on linux when)someone probably has to lobby yuwata a bit 😄 15:09:11
@hexa:lossy.networkhexa (clat on linux when)https://github.com/systemd/systemd/pull/1491515:09:13
@hexa:lossy.networkhexa (clat on linux when) * someone probably has to lobby yuwata a bit to make netns support happen 😄 15:09:23
@adam:robins.wtfadamcstephensRIP15:28:36
@adam:robins.wtfadamcstephens* RIP that pR15:28:48
@adam:robins.wtfadamcstephens* RIP that PR15:28:50
@hexa:lossy.networkhexa (clat on linux when)uh, yeah15:31:44
@hexa:lossy.networkhexa (clat on linux when) * https://github.com/systemd/systemd/pull/14915 ðŸŠĶ15:31:53
@hexa:lossy.networkhexa (clat on linux when)updated 😄 15:31:56
@nazarewk:matrix.orgkdncan bonding 2x2.5GbE interface reduce the throughput? I'm observing ~400 mbps from desktop/laptop > switch1 > switch2 > BOND > router, but not desktop <> switch1 > laptop17:12:18
@k900:0upti.meK900Very possibly17:12:47
@nazarewk:matrix.orgkdn it's 802.3ad bonding 17:12:53
@k900:0upti.meK900You'd have to measure every hop separately to know17:12:57
@k900:0upti.meK900Especially cheap hardware I'd expect to not handle this correctly17:13:06

Show newer messages


Back to Room ListRoom Version: 6