I found two bugs in Winbox, easy to reproduce.
Run Winbox, open Firewall window, Filter Rules tab.
Right click for popup menu, mark ‘Show Categories’,
next mark ‘Detail Mode’, next mark ‘Inline Comments’.
Scroll vertical scrollbar down and bug no. 1 appear.
Latest rules are not visible.
Next unmark ‘Inline Comments’, next unmark ‘Detail Mode’,
next unmark ‘Show Categories’ and scroll vertical scrollbar up.
Second bug, big black rectangle at the top of list.
Tested on MT demo routers , as you can see ROS 4.16 and 5.0rc8 is affected.
I just tested this on following configurations:
WinXP SP3, Winbox 2.2.18
MS Server 2003 R2, Winbox 2.2.17
Win7 Home Premium, Winbox 2.2.16
At the momement I’m not able to test on Linux platform.
These bugs appear every time, just mark/unmark and scroll
down/up in order described in my first post.
i have noticed some winbox bugs on 4.16.When i press filter in /ip arp I see “unknown” in all fields.It can be fixed by disabling enabling any arp entry.
Not entirely sure when this started, but that’s a view of a 5.0rc7 accessed via Winbox. When you start Winbox it looks normal. You make the window slightly bigger, that isn’t reflected and a dead area to the right and bottom appears. You add a CPU, memory, or uptime gauge and the window finally resizes. The gauge never sits flush to the right hand side anymore.
Had the same issue with WinBox running latest ROS 5.5 & 5.6.
Guess what was the root cause? It was the TeamViewer application’s feature “QuickConnect”. Once I disabled it - the issue went away.
I guess this might help to someone.
linux users that have black screens, you can check if you have compositioning enabled and how much RAM your video device has, or how much it has assigned. Try to increase the size. As my experience goes - with 256MB i could open 8 to 9 applications when i started to get black areas. getting graphic card with larger memory solved problem.
Could you kindly fix winbox, so it isn’t useless when I dare to open pppoe connection on my windows 7 machine, or have virtualbox running? It’s as trivial as adding a listbox to choose transmit interface. Pretty please?
please use IP address to connect to router. Check if ehrn you create tunnel route that is added does not send all of the traffic through the tunnel causing your local network to become inaccessible. There is nothing we can do about it if your routing information is wrong for what you want to do. (add additional routes, so your local network is still reachable when tunnel is created)
There’s a bug, why can’t you fix it? - sometimes I need to reset devices that don’t have any IP address on LAN side, so I can’t use IP connection, only L2 mac-telnet connection.
I have (RB 750G v5.7) that problem but I think effect from my pc… I just login winbox with mac than disable and enable port winbox (8291). restatr my pc, login winbox with ip…until now it’s ok.
, as you can see ROS 4.16 and 5.0rc8 is affected.
- sometimes I need to reset devices that don’t have any IP address on LAN side, so I can’t use IP connection, only L2 mac-telnet connection.