I need to be able to use winbox with a SOCKSv5 proxy I create with an SSH session.
As far as I've seen neither v2 nor the v3beta allow it.
Is this a missing feature or am I missing something?
TIA.
what have winbox to do with SOCKSv5 proxy?? Winbox is only for conneccion to RouterOS devices.I need to be able to use winbox with a SOCKSv5 proxy I create with an SSH session..
Current RouterOS v is v6.xx (there are some that uses v5.xx)As far as I've seen neither v2 nor the v3beta allow it..
I'm pretty sure you are missing a lot.Is this a missing feature or am I missing something?
You don't know what a SOCKSv5 proxy is for, do you?what have winbox to do with SOCKSv5 proxy?? Winbox is only for conneccion to RouterOS devices.I need to be able to use winbox with a SOCKSv5 proxy I create with an SSH session..
It looks lilke Winbox is still a v3RC.Current RouterOS v is v6.xx (there are some that uses v5.xx)As far as I've seen neither v2 nor the v3beta allow it..
I fear I am not alone, after all.I'm pretty sure you are missing a lot.Is this a missing feature or am I missing something?
Really? A lot of people like me finds that feature really useful so OpenSSH is STILL supporting and maintaining it since looong time now.1) SOCKSv5 is ancient history - RFC is from 1996. I do not see any need for it in modern networking.
My qustion was about winbox, not SSH.2) you can use SSH to configure router from command line directly.
I didn't find any reference to the encryption used. I'll check with wireshark.3) winbox connection is secure enough already.
"I need to be able to use winbox with a SOCKSv5 proxy I create with an SSH session."Please, next time describe your feature request in more details, like.
"Is it possible to add SOCKSv5 proxy support for winbox?"
Your first post is impossible to understand.
I am sorry for not having been clear enough.What is the purpose of your request? Is the router in some private LAN, accessible only over SOCKS proxy? Otherwise, use direct connection.
OK. I saw it, though it's optional.Winbox uses TLS, it is in the manual.
The use of SSH TCP Port forwarding and SOCKSv5 proxy is very popular among system and network administrators, AFAIK.Yes.
Same applies to Dude. To be honest, this is the first time I have heard a similar request.
Are you saying you have already got this working, or you wish to do it?You see, I open an SSH connection through which I access the HTTP webfig and ftp.
Modern browsers still have a field to enter "Gopher proxy" address, but that was not so much popular after 1993Why else would e.g. all current web browsers still support it?.
Yes: my browser and my ftp client support SOCSKv5 proxy.Are you saying you have already got this working, or you wish to do it?You see, I open an SSH connection through which I access the HTTP webfig and ftp.
The SSH server running into RouterOS v6.32 already supports it. Connect to it with a "dynamic forwarder" (a nickname for SOCKS proxy) and you'll see.SOCKS5 is too new for MikroTik, look at SOCKS server in RouterOS, still limited to SOCKS4 only. It would be nice to see it upgraded one day too. But that's OT here.
It happens I need to connect from the Internet and, while I can use destination port TCP:22, I cannot use TCP:8291 because of restriction policies.But seriously, even though SOCKS is old and not much used today, it can be useful. Why else would e.g. all current web browsers still support it? It's simple and extremely easy to implement for TCP client. I admit, I did not miss it in WinBox so far. But it's one of those nice little things to have, an extra option, just in case.
Which browser are you using?Modern browsers still have a field to enter "Gopher proxy" address, but that was not so much popular after 1993Why else would e.g. all current web browsers still support it?.
None of the "big ones". I though it was not so long ago when I saw it there, but apparently, if Wikipedia does not lie, Gopher support is gone from major browsers for several years now. But clearly, we all know that Gopher is long dead, no one cares about it anymore (nostalgic interest excluded).Modern browsers still have a field to enter "Gopher proxy" address, but that was not so much popular after 1993
For what it's worth, I've used redsocks to socksifie winbox's traffic.I need to be able to use winbox with a SOCKSv5 proxy I create with an SSH session.
As far as I've seen neither v2 nor the v3beta allow it.
Is this a missing feature or am I missing something?
TIA.
Hi.For anyone who stumbles upon this as I do for the third time: it is possible to use WinBox via SSH tunnel.
If you use PuTTY, go to Connection, SSH, Tunnels and add a tunnel:
OpenSSH is more straightforward
- Source port: your-local-port (say, 8090)
- Destination: mikrotik.local:8291 (i.e, 10.0.0.1:8291)
- Local
- Auto
Then connect WinBox to 127.0.0.1:your-local-port (127.0.0.1:8090) and it will connect you to mikrotik.local:8291 (10.0.0.1:8291).
- ssh -L local-address:local-port:target-address:target-port
- given same example addresses: ssh -L 127.0.0.1:8090:10.0.0.1:8291
There's still people using Internet Explorer, Windows and even DOS. And even PDP-11s.btw Safari still has Gopher support