hexa- changed the topic of #nixos-on-your-router to: NixOS on your Router
clever has quit [Ping timeout: 248 seconds]
tdeo_ has joined #nixos-on-your-router
tdeo has quit [Ping timeout: 248 seconds]
clever has joined #nixos-on-your-router
clever has joined #nixos-on-your-router
clever has quit [Changing host]
v0|d has joined #nixos-on-your-router
v0|d has quit [Ping timeout: 248 seconds]
<cransom>
hrm. i connect my workstation directly to my file server (because, 10gig). every time it sleeps, the link goes down and doesn't come back up until i up/down the interface (uses the atlantic driver) on the file server.
<gchristensen>
ehh weird
* cransom
plays around with autonegotiation before resorting to watching kernel logs to bounce the interface when it goes down
<cransom>
if i go read the very fine print, 'due to a known kernel issue, GRO and LOR must be burned off when routing/bridging'.
<cransom>
and after a couple sleep cycles, that seems to be it.
v0|d has joined #nixos-on-your-router
<Shados>
cransom: You don't need to watch kernel logs. Use something that listens to netlink events. `ip monitor` may be sufficient, depending on your needs.
<Shados>
This has reminded me that there's an item on my todo which basically boils down to "write tiny netlink watcher that shits out json messages on events"...