eyJhb changed the topic of #nixos-on-your-router to: NixOS on your Router || https://logs.nix.samueldr.com/nixos-on-your-router
rb2k has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rb2k has joined #nixos-on-your-router
rb2k has quit [Ping timeout: 272 seconds]
rb2k has joined #nixos-on-your-router
rb2k has quit [Ping timeout: 240 seconds]
rb2k has joined #nixos-on-your-router
rb2k has quit [Ping timeout: 246 seconds]
lukegb has quit [Quit: ~~lukegb out~~]
lukegb has joined #nixos-on-your-router
stites[m] has quit [Quit: Idle for 30+ days]
srk has quit [Remote host closed the connection]
srk has joined #nixos-on-your-router
rb2k has joined #nixos-on-your-router
thibm has quit [Quit: WeeChat 2.9]
rb2k has quit [Ping timeout: 264 seconds]
rb2k has joined #nixos-on-your-router
rb2k has quit [Read error: Connection reset by peer]
rb2k_ has joined #nixos-on-your-router
rb2k_ has quit [Read error: Connection reset by peer]
rb2k has joined #nixos-on-your-router
rb2k has quit [Ping timeout: 264 seconds]
<gchristensen> hexa-: want to look at that network problem with me? :P
<gchristensen> I haven't fixed the cabling, and it cropped up -- if you want to figure out more specifically why it is happening
<gchristensen> for intellectual curiosity
rb2k has joined #nixos-on-your-router
<mdlayher> an interesting 10GbE router option popped up in my twitter feed this weekend: https://shop.solid-run.com/product/SRC9132S00D00GE008P00CH/?_ga=2.229877397.802706140.1613422518-587500422.1610122864
<mdlayher> i wonder if this can run mainline kernels/NixOS with full hardware acceleration
<hexa-> gchristensen: i'm relocating now, how about in 45?
<mdlayher> it claims "Marvell based Linux Kernel 4.14x, Mainline Linux"
<gchristensen> nah, gotta fix it now
<gchristensen> but it'll happen again :P
<hexa-> lovely :FD
<gchristensen> (unless I really fix it ... which I will, I promise :))
<hexa-> (suuuure(
<gchristensen> haha
<gchristensen> I mean
<gchristensen> it is very annoying when it breaks :P
<hexa-> agreed
<gchristensen> lol
<gchristensen> the interface replying to the arpping is the interface that does not have that IP address assigned https://gist.github.com/grahamc/ffc10d30c546251b647d611a830e099f
<andi-> Yeah, linux networking is lying ;-)
<andi-> Well if those two interfaces are on the same l2 that is not surprising
<cransom> this is a dell? i hate it when the on board management stuff play tricks like that to make OOB management 'easier'
<gchristensen> asrock rack
<gchristensen> it appears the board decided to bond the two interfaces
rb2k has quit [Ping timeout: 264 seconds]
<gchristensen> I assume it did that because they're both on the same network
<gchristensen> upgrading its firmware has been a general mistake
srk has quit [Remote host closed the connection]
srk has joined #nixos-on-your-router
rb2k has joined #nixos-on-your-router
<hexa-> gchristensen: x470/x570?
<hexa-> with the unusable ivkm mount feature
<hexa-> ikvm*
<hexa-> gchristensen: why do you have the same subnet on two interfaces?
<hexa-> 10.5.3.0/24
<gchristensen> no good reason
<hexa-> kill that with fire if possible
<gchristensen> I had this idea in my head that if I plugged in both nics it would dedicate one to the bmc
<gchristensen> instead of sharing it with the host
<gchristensen> but it doesn't seem to be panning out
srk has quit [Remote host closed the connection]
srk has joined #nixos-on-your-router
<cransom> when i had physical gear, i remember many strange network errors pop up if we didn't run the management nic to a different network.