!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

919 Members
Declaratively manage your switching, routing, wireless, tunneling and more.276 Servers

Load older messages


SenderMessageTime
13 Sep 2021
@lukegb:zxcvbnm.ninjalukegb (he/him)it's possible that you couldn't sync with NTP because DNS was broken, and DNS was broken because you couldn't sync with NTP02:03:55
@elvishjerricco:matrix.orgElvishJerricco I have no idea what the clock was set to, but I did notice that the logs for resolved included a lot of failures for ntp domains 02:04:37
@elvishjerricco:matrix.orgElvishJerriccoDidn't think that would be important...02:04:52
@elvishjerricco:matrix.orgElvishJerriccoYea just noticed journalctl logs thought it was June 29. Probably because that's when I last booted this device...02:07:22
@disrupt_the_flow:matrix.orgdisrupt_the_flow changed their profile picture.11:59:23
@hexa:lossy.networkhexaif your machine does not have an RTC you are in for some fun with NTP/DNSSEC setups13:34:29
14 Sep 2021
@Las:matrix.orgLas joined the room.08:04:46
@Las:matrix.orgLas Does anyone know of a nix-y way of doing this in order to make upnpc work? Should I just use networking.firewall.extraCommands? 08:07:05
@linus.heckemann:matrix.mayflower.deLinux Hackerman
In reply to @Las:matrix.org
Does anyone know of a nix-y way of doing this in order to make upnpc work? Should I just use networking.firewall.extraCommands?
Yep pretty much. Put your rules in the nixos-fw chain so that they don't get duplicated every time firewall.service gets restarted
08:10:55
@Las:matrix.orgLasThanks08:19:04

There are no newer messages yet.


Back to Room ListRoom Version: 6