Crashplan free port forwarding full#
Crashplan free port forwarding trial#

You find it time consuming to test very few possibilities but you're willing to write a tutorial after someone explains it all to you? the router itself)? Or does this apply to 'dynamic' forwarding where the router is used as http proxy? Thanks phuzi0n!ĭo you also happen to know what the 'SSH TCP Forwarding' option in the ssh daemon section of the SERVICES tab does? I can still tunnel into the router GUI even if this is disabled, so my guess would be it limits forwarding to localhost (i.e. The remote access admin setting only creates a nat rule in iptables to forward the port but will not enable the daemon.Īh, finally it makes sense to me. The services page is what enables and configures dropbear, the ssh daemon. Ok, here is the setup: dd-wrt v.24 std build 12553 on whr-hp-g54, internet via cable modem (dhcp), lan ip 192.168.1.1, nothing special.Ĭomputers are perfect for solving problems the on-board help does either not pop up or does not contain any hints, where the former seems to have to do with %&'ß§!!! Internet Explorer 8, but firefox and safari also gives me trouble with dd-wrt (frequent disconnects). I would volunteer and overhaul the ssh tutorial. so please, does anybody know about these things?

Crashplan free port forwarding trial#

I find it very time consuming to figure all these things out via trial and error, specifically since each test requires switching my internet connection. Some tutorial even suggested that one needs to (via command line) open the port in the router firewall that one wants to use for ssh access - which doesn't seem true to me because it works without - or is it just my weird setting? Even with 'ssh management' enabled, one still needs to set up (within putty or whatever ssh client one uses) the actual port forwarder from localhost:xxxxx to router:80, right? So what is the point of specifically enabling 'ssh management' - it does not seem to block any attempt to do anything else one can do over ssh (by simply forwarding another port somewhere else). (For me, only one of them worked at the same time)

However, it seems to mess things up if one actually specifies two different ports. And if so, why would you be able to specify a different port in both places? So I guess these are redundant GUI options that in effect cause the same behaviour. It is unclear whether, as some tutorial says, (a) is a prerequesite for (b) or not. sshd can be activated in (a) SERVICES > SECURE SHELL as well as under (b) ADMINISTRATION > REMOTE MANAGEMENT.

Crashplan free port forwarding full#

ssh 'TCP forwarding' ?Ĭan someone shed some light on the differences between the two ssh setup options within v.24_std_generic (12533)? I know there are many ssh tutorials out there, but they all seem to be guessing and full of contradictions. Posted: Wed 22:22 Post subject: ssh - 'remote management' vs.