Does This RouterOS SOCKS Service Support Your Password Login?
Check the installed RouterOS release and client’s SOCKS5 authentication support, then keep SOCKS accounts separate from web-proxy and router administration settings.
The RouterOS SOCKS manual documents SOCKS5 password authentication and a dedicated SOCKS users list. That answers a feature question for releases supporting those controls, not a promise that an older router has them.
For the documented arrangement, both sides need to agree:
- The router selects SOCKS5 and an authentication method requiring password negotiation, with a dedicated enabled SOCKS user.
- The client implements SOCKS5 username/password negotiation. An HTTP proxy login box or unauthenticated-only SOCKS implementation is insufficient.
Use the fields supported by the installed release. For a release lacking them, choose its supported design or an approved alternative rather than copying a newer manual's fields.
These are SOCKS accounts. They neither establish that RouterOS's separate HTTP web proxy exposes the same interface nor require granting router management access. Keep source/destination access policy and the router firewall restricted as well.
The password method itself does not encrypt credentials: RFC 1929 negotiation precedes any later website HTTPS session. Use an appropriately protected client-to-router path; destination TLS cannot protect that earlier exchange retroactively.