Sharing my experience on success invasion

[SimZhou]

I succeed invasion after a bunch of failures, and here I am to share what I did.

firmware: 2.28.38

Failure message before my procedure:

Router IP address [press enter for using the default 'miwifi.com']: 192.168.31.1
Enter router admin password: mypassword
There two options to provide the files needed for invasion:
   1. Use a local TCP file server runing on random port to provide files in local directory `script_tools`.
   2. Download needed files from remote github repository. (choose this option only if github is accessable inside router device.)
Which option do you prefer? (default: 1)
****************
router_ip_address: 192.168.31.1
stok: 318636cb692b46ce39d1756e515312eb
file provider: local file server
****************
start uploading config file...
start exec command...
local file server is runing on 0.0.0.0:57391. root='script_tools'
Warning: the process has finished, but seems like ssh connection to the router is not working as expected.
* Maybe your firmware version is not supported, please have a look at https://github.com/acecilia/OpenWRTInvasion/blob/master/README.md#unsupported-routers-and-firmware-versions
* Anyway you can try it with: telnet 192.168.31.1

What I did:

1. Adding a proxy server of my own into the invade script script.sh, line 16:
   
2. Use download from github option (option 2)

Then everything works fine:

Router IP address [press enter for using the default 'miwifi.com']: 192.168.31.1
Enter router admin password: mypassword
There two options to provide the files needed for invasion:
   1. Use a local TCP file server runing on random port to provide files in local directory `script_tools`.
   2. Download needed files from remote github repository. (choose this option only if github is accessable inside router device.)
Which option do you prefer? (default: 1)2
****************
router_ip_address: 192.168.31.1
stok: 4e8f429cc49fb54846a1e56793d02d9d
file provider: remote github repository
****************
start uploading config file...
start exec command...
done! Now you can connect to the router using several options: (user: root, password: root)
* telnet 192.168.31.1
* ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oHostKeyAlgorithms=+ssh-rsa -c 3des-cbc -o UserKnownHostsFile=/dev/null root@192.168.31.1
* ftp: using a program like cyberduck

However, I don't know why this is happening. Probably there is a issue connecting the router to the local server using TCP?