search

jumaris / sshtunnel

Automatically exported from code.google.com/p/sshtunnel
GNU General Public License v3.0
1 stars 0 forks source link

Can't browser website after connect #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. After connect success
2. Browser the website
3. Can't load any url

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.
Here is the log.

02-13 17:26:59.956  8320  8320 E SSHTunnel: Service Start
02-13 17:27:00.338  8320  8320 E SSH     : Sent SSH_MSG_KEXINIT 522 bytes 
payload
02-13 17:27:00.502  8320  8711 E SSH     : Received SSH_MSG_KEXINIT 769 bytes 
payload
02-13 17:27:00.502  8320  8711 E SSH     : 
kex_algo=diffie-hellman-group-exchange-sha1
02-13 17:27:00.502  8320  8711 E SSH     : server_host_key_algo=ssh-rsa
02-13 17:27:00.502  8320  8711 E SSH     : enc_algo_client_to_server=aes256-ctr
02-13 17:27:00.502  8320  8711 E SSH     : enc_algo_server_to_client=aes256-ctr
02-13 17:27:00.502  8320  8711 E SSH     : 
mac_algo_client_to_server=hmac-sha1-96
02-13 17:27:00.502  8320  8711 E SSH     : 
mac_algo_server_to_client=hmac-sha1-96
02-13 17:27:00.502  8320  8711 E SSH     : 
comp_algo_client_to_server=zlib@openssh.com
02-13 17:27:00.502  8320  8711 E SSH     : 
comp_algo_server_to_client=zlib@openssh.com
02-13 17:27:00.502  8320  8711 E SSH     : Sent SSH_MSG_KEX_DH_GEX_REQUEST 13 
bytes payload
02-13 17:27:00.729  8320  8711 E SSH     : Received 
SSH_MSG_KEXDH_REPLY/SSH_MSG_KEX_DH_GEX_GROUP 139 bytes payload
02-13 17:27:00.760  8320  8711 E SSH     : Sent SSH_MSG_KEX_DH_GEX_INIT 134 
bytes payload
02-13 17:27:00.995  8320  8711 E SSH     : Received SSH_MSG_KEX_DH_GEX_REPLY 
692 bytes payload
02-13 17:27:01.065  8320  8711 E SSH     : Decoding ssh-rsa signature string 
(length: 256)
02-13 17:27:01.065  8320  8711 E SSH     : Verifying ssh-rsa signature
02-13 17:27:01.073  8320  8711 E SSH     : Sent SSH_MSG_NEWKEYS 1 bytes payload
02-13 17:27:01.112  8320  8711 E SSH     : Received SSH_MSG_NEWKEYS 1 bytes 
payload
02-13 17:27:01.112  8320  8320 E SSH     : Sent SSH_MSG_SERVICE_REQUEST 17 
bytes payload
02-13 17:27:01.112  8320  8320 E SSH     : Sent SSH_MSG_USERAUTH_REQUEST 35 
bytes payload
02-13 17:27:01.417  8320  8711 E SSH     : Received SSH_MSG_SERVICE_ACCEPT 17 
bytes payload
02-13 17:27:01.596  8320  8711 E SSH     : Received SSH_MSG_USERAUTH_FAILURE 24 
bytes payload
02-13 17:27:01.604  8320  8320 E SSH     : Sent SSH_MSG_USERAUTH_REQUEST 53 
bytes payload
02-13 17:27:01.846  8320  8711 E SSH     : Received SSH_MSG_USERAUTH_SUCCESS 1 
bytes payload
02-13 17:27:01.846  8320  8320 E SSHTunnel: Forward Successful
02-13 17:27:13.588  8320  8715 E SSH     : Sent UNKNOWN MSG 120 50 bytes payload
02-13 17:27:14.784  8320  8711 E SSH     : Received UNKNOWN MSG 120 34 bytes 
payload
02-13 17:27:14.784  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 100)
02-13 17:27:15.018  8320  8715 E SSH     : Sent UNKNOWN MSG 128 10 bytes payload
02-13 17:27:15.195  8320  8711 E SSH     : Received SSH_MSG_GLOBAL_REQUEST 8 
bytes payload
02-13 17:27:15.393  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 101)
02-13 17:27:15.401  8320  8715 E SSH     : Sent UNKNOWN MSG 0 10 bytes payload
02-13 17:27:15.573  8320  8711 E SSH     : Received UNKNOWN MSG 64 8 bytes 
payload
02-13 17:27:15.581  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 102)
02-13 17:27:15.604  8320  8715 E SSH     : Sent UNKNOWN MSG 194 9 bytes payload
02-13 17:27:15.776  8320  8711 E SSH     : Received UNKNOWN MSG 16 8 bytes 
payload
02-13 17:27:15.776  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 103)
02-13 17:27:15.807  8320  8715 E SSH     : Sent UNKNOWN MSG 132 9 bytes payload
02-13 17:27:15.979  8320  8711 E SSH     : Received SSH_MSG_DEBUG 7 bytes 
payload
02-13 17:27:15.987  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 104)
02-13 17:27:16.229  8320  8715 E SSH     : Sent UNKNOWN MSG 8 9 bytes payload
02-13 17:27:16.404  8320  8711 E SSH     : Received UNKNOWN MSG 0 8 bytes 
payload
02-13 17:27:16.404  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 105)
02-13 17:27:16.432  8320  8715 E SSH     : Sent UNKNOWN MSG 16 9 bytes payload
02-13 17:27:16.604  8320  8711 E SSH     : Received UNKNOWN MSG 64 8 bytes 
payload
02-13 17:27:16.604  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 106)
02-13 17:27:16.698  8320  8715 E SSH     : Sent SSH_MSG_KEX_DH_GEX_INIT 9 bytes 
payload
02-13 17:27:16.877  8320  8711 E SSH     : Received UNKNOWN MSG 16 8 bytes 
payload
02-13 17:27:16.877  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 107)
02-13 17:27:16.916  8320  8715 E SSH     : Sent UNKNOWN MSG 64 9 bytes payload
02-13 17:27:17.088  8320  8711 E SSH     : Received SSH_MSG_DEBUG 7 bytes 
payload
02-13 17:27:17.088  8320  8711 E SSH     : Got SSH_MSG_CHANNEL_OPEN_FAILURE 
(channel 108)

Original issue reported on code.google.com by pengjianqing@gmail.com on 13 Feb 2011 at 9:29

GoogleCodeExporter commented 9 years ago 
Sorry,now i t works with my own SSH .
It need to run a http proxy on the SSH Server and set the Proxy Port as the 
Remote Port.
I have installed the squid on my SSH server.
Now it works,thanks for your good work.

Original comment by pengjianqing@gmail.com on 13 Feb 2011 at 10:11

GoogleCodeExporter commented 9 years ago 
Please add this tip in the User Guard,thanks.

Original comment by pengjianqing@gmail.com on 13 Feb 2011 at 10:12

GoogleCodeExporter commented 9 years ago 
Thanks for your suggestions and contributions. This issue is closed.

Original comment by max.c...@gmail.com on 13 Feb 2011 at 10:23