eyJhb changed the topic of #nixos-on-your-router to: NixOS on your Router || https://logs.nix.samueldr.com/nixos-on-your-router
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-on-your-router
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-on-your-router
hexa- has quit [Ping timeout: 265 seconds]
hexa- has joined #nixos-on-your-router
ottidmes_ has joined #nixos-on-your-router
ottidmes has quit [Ping timeout: 264 seconds]
andi- has quit [Ping timeout: 240 seconds]
andi- has joined #nixos-on-your-router
<andi-> I am now offically part of this club.. last Debian box is finally gone.. So lang and thanks for all the fish ;) # uptime
<andi-> 23:12:21 up 943 days, 22:16, 7 users, load average: 0.71, 0.70, 0.49
<gchristensen> nice
<gchristensen> nice
<gchristensen> a lot of days
<andi-> Yeah
<andi-> those disks will never spin up again
<andi-> not even if I wanted.
<hexa-> hrm
<hexa-> did a third party router on nixos, because it was easiest
<hexa-> but never got ia_pd running there, so I wasn't motivated doing the migration at home
<hexa-> by now I think it was due to the ISP not providing IPv6 on that product
<andi-> I am very happy with networkd (with some patches and a few custom nixos options, all pending merge / in staging on nixos)
<andi-> It just works(tm). Only a few weekends testing
<hexa-> how is ia_pd with networkd?
<hexa-> works on 20.03?
<andi-> no
<andi-> works on staging
<hexa-> :)
<cransom> i'm not super keen on networkd yet. mostly because i think it really wants me to use resolved and resolved's workings bother me at the moment.
<hexa-> nope, it does not
<hexa-> fairly easy to use any resolver you'd like
andi- has quit [Ping timeout: 244 seconds]
andi- has joined #nixos-on-your-router