!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

906 Members
Declaratively manage your switching, routing, wireless, tunneling and more.265 Servers

Load older messages


SenderMessageTime
4 Jul 2025
@hexa:lossy.networkhexa I think the greatest benefit we get out of networking.domain is networking.fqdn 03:17:55
@hexa:lossy.networkhexabut not for the price of shipping net-tools in 202503:18:15
@hexa:lossy.networkhexawhich has a CVE merged into master since May, but not done a release since03:18:35
@hexa:lossy.networkhexa should have moved on in 2017 already 03:18:58
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/42227003:50:42
@hexa:lossy.networkhexait is still passed into the path of many units, probably for user-defined scripts03:51:13
@hexa:lossy.networkhexaif it doesn't leak into my system closure I'm okay for now03:51:25
@hexa:lossy.networkhexayeah, it's gone04:32:08
* @hexa:lossy.networkhexa happy04:32:13
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/42228205:00:17
@hexa:lossy.networkhexaand one more05:00:21
@hexa:lossy.networkhexa💤05:00:24
@emilazy:matrix.orgemily
In reply to @hexa:lossy.network
https://github.com/ecki/net-tools/issues/47#issuecomment-2959613030
we're not going to even ship Most of the binarstes inthronisiert net-Tools packte any,ore?
09:24:58
@k900:0upti.meK900Call the bondulance09:25:17
@sandro:supersandro.deSandro 🐧do you have no xdg-open?12:38:06
@hexa:lossy.networkhexawhy do you ask?12:38:32
@sandro:supersandro.deSandro 🐧https://github.com/NixOS/nixpkgs/blob/ee63ec601c0c6c5c09d399f087a4aa846461a563/pkgs/by-name/xd/xdg-utils/package.nix#L20912:40:23
@hexa:lossy.networkhexawhat I meant is … nettools is no longer in PATH12:42:11
@hexa:lossy.networkhexawhether we can migrate xdg-open to hostname-debian depends on whether it only uses it for the hostname lookup12:42:40
@sandro:supersandro.deSandro 🐧I think they do https://gitlab.freedesktop.org/xdg/xdg-utils/-/blob/master/scripts/xdg-open.in#L9712:43:11
@hexa:lossy.networkhexaok, can add it to the PR in a bit12:56:31
@toonn:matrix.orgtoonn Anyone familiar with Nspawn container networking? A setup that was working has recently stopped, get `Failed to connect to selfoss.local port 80: No route to host` when curl'ing the container now. 18:30:27
@toonn:matrix.orgtoonn I can still ping it from the host though. 18:31:52
@sandro:supersandro.deSandro 🐧Did you do a reboot after updating? I kinda remember when I used nspam containers back on Ubuntu sometimes the state was just broken and I needed to reboot19:35:50
@toonn:matrix.orgtoonn I haven't updated between when it was working and when it broke. 19:38:56
@toonn:matrix.orgtoonn It's a remote machine so I'm somewhat reluctant to reboot it while there are potential network issues I don't understand. 19:39:36
@toonn:matrix.orgtoonn Figured out the issue, my default gateway changed from under me. 20:25:06
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/42227021:18:49
@hexa:lossy.networkhexareviewers welcome21:19:10
@hexa:lossy.networkhexaideally per commit21:19:15

Show newer messages


Back to Room ListRoom Version: 6