but at first glance I unplugged the ethernet to the peer and 10 minutes later its still thinking its connected...
Confirmed. Same in all kinds of Interfaces. Wireless and Ethernet.
bgp thinks session is up and established. Routes don't get to be used though since next-hop is unreachable. At least something works there
I assume hold-time etc don't work at all.
Also for unknown reasons if a peer goes down or up the router either forgets to update the other peers or it thinks it has. Sure thing is no updates on the other side and thus we need to disable/enable by hand or script in order to work. This came up on 2.9.x and up to 2.9.7 so far on routing-test package.
One more bad thing that came up is that router goes 100% cpu after a period of time.
Anybody else has these issues?