Gargoyle Forum

I've tried on port 22 (which I thought may be kept by the gargoyle router) and port 563.

The rule seems to exist:

config 'redirect' 'redirect_enabled_number_0'
option 'name' 'SSH'
option 'src' 'wan'
option 'dest' 'lan'
option 'proto' 'tcp'
option 'src_dport' '563'
option 'dest_ip' '192.168.1.2'
option 'dest_port' '563'

But a port checker utility lists the port as closed (however another port I have for plex is listed as open).

This was working under 1.4.2 (as was PPTP on port 1723) - neither of these work under 1.5.5 (btw I manually redid all the settings incase it was that).

I would downgrade, but I can't do it from the UI, just doesn't accept the lower version.

There was no change in any port forward logic between the versions you are contemplating. I doubt that the version of Gargoyle is involved in this problem.

There is nothing in Gargoyle which would prevent you from down grading to a previous version.

There have been reports of WRT54 series routers having insufficient RAM to perform upgrades. If you have this type reset all your settings back to default, reboot your router and try again.

Hi.

Thanks for the reply. Have tried the factory reset thing a number of times with no success. From the web GUI however.

I've since bought a new router (wr1043nd) and put gargoyle 1.4.7 on it which I'll move into the gateway. Leaving this wrt54g or playing with.

Incidentally as part of the tp link upgrade I stuffed it up and had to telnet to it and mtu -r erase rootfs_data to get it back. I'll try this on the wrt54g I get it to factory settings.

I heard there were issues using tftp (client) on w2k8 and w7 to sen the firmware image is that why I'd never get It transferred?

I do not know why some WRT54G users have trouble with this and other do not. I have one and it works for me if I reset to defaults using the web page, reboot the router and immediately upgrade.

The TFTP method documented in the Wiki will work.
http://www.gargoyle-router.com/wiki/dok ... e_recovery

Surely this has nothing to do with the router running it's own ssh server on port 22...

mix wrote:Surely this has nothing to do with the router running it's own ssh server on port 22...

This was my guess.....but I do actually port forward from 563 (nntps) to 22. I did also wonder about the dest machine being 192.168.1.2 (router is .1) is it a "special" address (like for tftp'ing from for new firmware).

Well I had the same issue (with 1.4.7 on a new router).

Out of my suspicions that 198.168.1.2 was a protected address, I changed the SSH server (it's also a VPN server) to .254.

Wo and behold it worked.