i got 1 bug of ROS 5.0 when i connected via winbox, this is the problem.

try to make 1 mangle rule via winbox,
1. click arrow button of protocol and set protocol value = "tcp"
2. set dst-port = "80", last click apply.

then,
1. click up button of dst-port,
2. click up button of protocol.

you will see dst-port will set back to "80" without user do nothing. , is it bug?

Additional bug... no huge priority:

Telnet seems to be forcing SSL encapsulation and thus doesn't connect... I can't telnet to any routers on V5.0 only SSH.. Not a big issue for me since i really only SSH, but something I did notice.

Additional bug:
WebFig does not handle Radius AAA - not even do Radius request
(every other login methods like telnet/ssh/ftp/winbox works over Radius AAA)

Additional bug:
WebFig does not handle Radius AAA - not even do Radius request
(every other login methods like telnet/ssh/ftp/winbox works over Radius AAA)

we are looking into it - problem is webfig uses HTTP digest MD5 authentication, while RADIUS works with CHAP. So it is not that trivial.

i found problem again using winbox 2.2.18(correct me if i'm wrong maybe i'm newbie ).

in my RB750 ROS V5.0, when i torch filter by src-address and port, on the torch result double click one of them and torch cannot started although press the start button, winbox must be closed and open it again. is it bug?