When I enable the SSH Daemon, it listens on port 22. Its available to me via LAN or WAN.
A) There is only Remote Access (on or off) option,
B) Remote Forwarding (on or off) option.
Regardless of A or B, I can access Port 22 from WAN Side.
When A is Checked and set to Port 11, and B is Checked or Unchecked, I can access port
22 and 11 and log in from WAN Side.
I don't believe the SSH Daemon should be "listening" on multiple ports, but on one port, and other ports forwarded to the listening port via rules, either implemented by a switch, or by port fowarding.
From a stability stand point, I would expect someone who needed a function like this to be
able to make the rules or forwards, instead of having an option for them on the admin page.
At the same time, should enabling the SSH Daemon make it accessible by Lan or WAN?
I created a new Port forward that took BOTH port 22 and forwarded to port 1, on 192.168.1.1 and saved, now WAN port 22 is Connection Refused. :)
Port 11 works fine.
It may not match DD-WRT's behavior, but thats the reason I use tomato.
I think by Default SSH should not listen on the WAN, and anyone who wants access to it, should be able to forward the port themselves.