Hello,
how to launch WB4 in weston with xwayland enabled (Debian12)
Warning: could not connect to display :0 (:0, )
Warning: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. (:0, )
Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. (:0, )
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
(:0, )
Aborted
i make a short internet search:
libxcb-cursor0 installed, libxcb-xinerama also,
adding QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/platform/plugins does not work
adding QT_DEBUG_PLUGINS=1
ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
Using the linux version, when there are overlapping windows on the workspace, and you click on something on the top window, it selects the window on the bottom instead. It makes it very difficult to use.
if connection is not on the default port but gets redirected internally to 8291 (def. port) with a NAT redirect i cannot login from the WAN side
winbox v3 - no problem
winbox v4 - no login possible
(tried a static user and a 2FA user - v3 was OK but v4 error on both tries)
service itself is running on default port 8291:
/ip service print
Flags: X - DISABLED, I - INVALID
Columns: NAME, PORT, ADDRESS, CERTIFICATE, VRF
# NAME PORT ADDRESS CERTIFICATE VRF
6 winbox 8291 main
The first time you open the DHCP Server / Leases window, the Bridge Port displays the value āunknownā. After switching to another tab and back or reopening the window, the correct value is displayed.
Ability to disable labels, like āCPUā or āMemory (Free/Used/Total)ā, in the āResource panelā aka status bar. i.e. have some āicons onlyā option in settings for status/āresource panelā. Currently, it often wraps the labels, which looks weird and wastes space when CPU etc are pretty obvious without any labels:
It takes a VERY big window (> ~1400px wide) to get all on one-line:
Am I doing something wrong or 4.0 beta6 does not save/remember any windows position or settings?
For example, under IP/Firewall, I am arranging the window just how I like it. If I close the Firewall window and open it again in the same session, everything is just how I set it, but if I disconnect and reconnect, everything is back to default.
spippan Are you using 4.0beta6? Could you please create a support ticket regarding the NAT login issue along with supuout.rif file made after the issue appears and other details - what system is the WinBox running on?
I tried reproducing the issue, but it seems to work as expected. Is the āauth challange failedā error present both for 2FA and static user?
hi guntis
running winbox4 beta6 (but occured with previous winbox4 versions too) on windows 10 (22H2 19045.4894)
i rechecked that on 2 different machines today and it seems this rather is a local problem on my machine
is there a possibility on windows wo start winbox4 in āverbose modeā like on linux via shell?
I played a little with SSH dynamic port forward in linux and it seems possible to combine Winbox 4 and SOCKSv5 proxy to access remote devices.
If remote machine for SSH tunneling is Mikrotik, then enable SSH forwarding:
/ip ssh set forwarding-enabled=local
Connect to remote machine using -D parameter of SSH:
ssh user@remote -D 1080
Install tsocks and check file ā/etc/tsocks.confā for similar configuration:
server = 127.0.0.1
server_type = 5
server_port = 1080
Run:
tsocks ./WinBox
Now it is possible to connect to devices that are available from remote machine only. (Neighbor protocol will not be tunneled and also mac winbox feature cannot be used this way).
This approach can be useful in special cases when remote devices are not available directly (and it is not possible or necessary to use RoMON). Also additional security may be involved. It can be useful to connect to remote mikrotik over SSH using public/private key pair instead of passwords - and then winboxing to the same machine using internal IP only (127.0.0.1 will not be available because it is used by SOCKS itself, but any other IP which is already present in the router, can be used - or add special IP to loopback just for purpose for winbox login).
Iām also of the opinion that table content rendering in old winbox is better (all white background + grid lines). And also on old winbox I like how white color is dedicated to data(content) background, and light gray - to controls. Very clear that way.
Better contrast in lists and tables would definitely be better. If list/table/editable object background would be white or darker (on dark theme) then disabled entries will be better visible then now.
Just tested beta6 and this one is still showing the password in plain text, most likely missing parameter to hide passw if āhide passwordā is enabled
Iāve noticed that in the current version of Winbox, if I make a Winbox session full-screen while connected to a device, opening a new Winbox defaults to the same size as the full-screen window, but itās not actually full-screen. In previous versions, the sizing for unconnected Winbox instances was different from connected ones, which was more convenient. Could we have this behavior reinstated, so the default window size for an unconnected Winbox is separate from that of a connected session? This would help in managing multiple sessions more efficiently.
