Indeed it seems like a bug. You can get it running again by hitting the Clear button and then select “Stopped” from the list and the Clear button.
I think that this is a too convoluted way of clearing a stopped state. There should be an extra button like “Run” similar to the “Stop” that there is now.
Just found this bug:
/terminal/inkey with a timeout=_X_s value hangs forever, instead of actually timing out.
e.g. /terminal/inkey timeout=5s should return after $timeout seconds (or sooner if a key is pressed)
Based on this forum posting below from @Seán in v7.4beta topic tracks with my experience since I know /terminal/inkey has worked in some V7 versions.:
The terminal inkey timeout parameter bug remains since reporting in the 7.4 beta release. This parameter worked fine up until v7.2.
For example, /terminal inkey timeout=5 does not timeout after 5 seconds and just waits endlessly for a key press.
While esoteric, this makes interactive input and “refreshing” output in RSC pretty difficult. Anyone else noticed this?
Can anyone tell what is meant by
Certificate - improved…
Does it improve Let’s encryptypted integration as well?
can confirm on 4 eBGP sessions (but since v7.5 anyways)
possibly, I am facing a bug in CHR version 7.6beta10.
When I open “Sessions” tab of Routing/BGP menu and select a session and click “Refresh” and then refresh, session is stopped. The only way I found to bring session online again is rebooting the router.
i have the same experience, is it okay v7 call as stable version?
thx
I think that this is a too convoluted way of clearing a stopped state. There should be an extra button like “Run” similar to the “Stop” that there is now.
Yeap. It took me a while to figure it out.
Frankly, everything about the v7 BGP is needlessly convoluted.
Complete disappointment.
RouterOS v7.6rc1 has been released
http://forum.mikrotik.com/t/v7-6rc-is-released/161262/1