Brian Rak

No, but this would probably be more useful for that anyway: https://github.com/devicenull/ipmi_firmware_tools Just replace the binary with something more useful.

I'm not sure that's related - the issues in #87642 are not relevant to content not appearing on the public side of things. I looked at your simple test page...

I'm seeing this with Putty and pagent as well (only after upgrading to v12.0.4) I was able to work around it by removing the teleport keys from pagent and rerunning...

Yea, it's a kernel route (not staticd)

I bisected this down to 212df1de28ae2a21145389c01cc3a1952f95c1a8 - The comment there isn't super clear to me, but removing routes entirely when the interface goes down sounds like the wrong behavior. Any...

Yes - prior to that commit the route came back just fine. I was bisecting with this test case: ``` vtysh -c 'sh ip route 10.20.20.0/24' ip link set veth1...

This is on 3.10.0-1127.19.1.el7.x86_64 (default cent7 kernel) ``` [root@vultr ~]# ip mon 5: veth1@veth0: mtu 1500 qdisc noqueue state DOWN group default link/ether 8a:81:50:6b:57:b2 brd ff:ff:ff:ff:ff:ff Deleted ff02::16 dev veth1...

This is on `5.9.0-1.el7.elrepo.x86_64` ``` [root@vultr ~]# ip monitor route Deleted fe80::/64 dev veth1 proto kernel metric 256 pref medium Deleted local fe80::d4b6:56ff:fea7:f05e dev veth1 table local proto kernel metric...