eyJhb changed the topic of #nixos-on-your-router to: NixOS on your Router || https://logs.nix.samueldr.com/nixos-on-your-router
betawaffle has quit [*.net *.split]
v0|d has quit [*.net *.split]
locallycompact has quit [*.net *.split]
disasm has quit [*.net *.split]
danderson has quit [*.net *.split]
pie__ has quit [Quit: pie__]
pie_ has joined #nixos-on-your-router
pie_ has quit [Ping timeout: 276 seconds]
pie_ has joined #nixos-on-your-router
stears_ has quit [Quit: WeeChat 2.6]
lopsided98 has quit [Quit: No Ping reply in 180 seconds.]
lopsided98 has joined #nixos-on-your-router
stears has joined #nixos-on-your-router
locallycompact has joined #nixos-on-your-router
betawaffle has joined #nixos-on-your-router
danderson has joined #nixos-on-your-router
disasm has joined #nixos-on-your-router
v0|d has joined #nixos-on-your-router
pie_ has quit [Ping timeout: 245 seconds]
pie_ has joined #nixos-on-your-router
stears has quit [Ping timeout: 276 seconds]
stears has joined #nixos-on-your-router
<mdlayher> i'm running a wireguard tunnel and am having some difficulty getting the systemd dependency ordering correct so that things like nftables, coredns, and dhcpcd start up after wireguard. it appears that wireguard requires network-online.target by default and i'm unsure if there's a way to bring it up earlier
<mdlayher> fwiw it seems like i can just make nftables require wireguard-wg0.service but that doesn't seem to work when i try to do the same with other targets. and i'm not super happy that my machine has no firewall until the tunnel is up.
<mdlayher> i guess i could just rework and remov wg0 from my firewall rules, but meh
<mdlayher> tldr, i guess i'm looking for someone else who's running wireguard and trying to bind services on it so i can take a peek at your config and see how you're doing it :)
<mdlayher> i've tried enough different combinations that i'm having a hard time keeping it straight
stears has quit [Quit: WeeChat 2.6]