Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2533 > unrolled thread
| Started by | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| First post | 2013-10-16 11:32 +0000 |
| Last post | 2013-10-16 16:02 +0000 |
| Articles | 11 — 4 participants |
Back to article view | Back to comp.os.linux.networking
obfuscated-openssh cann't let me login to server. Hongyi Zhao <hongyi.zhao@gmail.com> - 2013-10-16 11:32 +0000
Re: obfuscated-openssh cann't let me login to server. ein <ein@no.spam> - 2013-10-16 14:06 +0200
Re: obfuscated-openssh cann't let me login to server. Hongyi Zhao <hongyi.zhao@gmail.com> - 2013-10-17 01:47 +0000
Re: obfuscated-openssh cann't let me login to server. unruh <unruh@invalid.ca> - 2013-10-18 08:22 +0000
Re: obfuscated-openssh cann't let me login to server. ein <ein@no.spam> - 2013-10-21 04:21 +0200
Re: obfuscated-openssh cann't let me login to server. Hongyi Zhao <hongyi.zhao@gmail.com> - 2013-11-02 06:55 +0000
Re: obfuscated-openssh cann't let me login to server. Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-11-02 10:15 +0100
Re: obfuscated-openssh cann't let me login to server. Hongyi Zhao <hongyi.zhao@gmail.com> - 2013-11-03 03:15 +0000
Re: obfuscated-openssh cann't let me login to server. Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-11-03 08:31 +0100
Re: obfuscated-openssh cann't let me login to server. Hongyi Zhao <hongyi.zhao@gmail.com> - 2013-11-04 02:09 +0000
Re: obfuscated-openssh cann't let me login to server. unruh <unruh@invalid.ca> - 2013-10-16 16:02 +0000
| From | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| Date | 2013-10-16 11:32 +0000 |
| Subject | obfuscated-openssh cann't let me login to server. |
| Message-ID | <l3ltg7$6ul$2@aspen.stu.neva.ru> |
Hi all, I own a account on the ssh server ssh.sshcenter.info, see here http:// www.sshcenter.info/site-sshcenter/pay-ssh-account.php for detail, which supports the obfuscated ssh login method now. When I login with the following command, I always failed with the following information: werner@debian-asus:~$ ssh -Nfx -D 7070 hszhao@ssh.sshcenter.info -p 60001 -Z key ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out Why does this happen? Regards -- .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
[toc] | [next] | [standalone]
| From | ein <ein@no.spam> |
|---|---|
| Date | 2013-10-16 14:06 +0200 |
| Message-ID | <l3lvgn$fln$1@node1.news.atman.pl> |
| In reply to | #2533 |
[Multipart message — attachments visible in raw view] — view raw
Hongyi Zhao wrote:
> Hi all,
>
> I own a account on the ssh server ssh.sshcenter.info, see here http://
> www.sshcenter.info/site-sshcenter/pay-ssh-account.php for detail, which
> supports the obfuscated ssh login method now.
>
> When I login with the following command, I always failed with the
> following information:
>
> werner@debian-asus:~$ ssh -Nfx -D 7070 hszhao@ssh.sshcenter.info -p
> 60001 -Z key
> ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out
^^^^^^^^^^^^^^^^^
> Why does this happen?
Reason is obvious. Please see above.
It means that, ssh connection was not established. TCP handshake was
interrupted after sending first packet with SYNC flag. Possible problems
are:
1. Hostname may be wrong.
2. SSH port may be wrong.
3. Something block this connection, for instance a firewall.
[toc] | [prev] | [next] | [standalone]
| From | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| Date | 2013-10-17 01:47 +0000 |
| Message-ID | <l3nfip$ehs$1@aspen.stu.neva.ru> |
| In reply to | #2534 |
On Wed, 16 Oct 2013 14:06:45 +0200, ein wrote: > 1. Hostname may be wrong. > 2. SSH port may be wrong. > 3. Something block this connection, for instance a firewall. The port and the hostname all are right ;-) I've check them again and again. And I can use the http://www.sshcenter.info/site-sshcenter/ software/myentunnel-unicode-3.5.2-obfuscated.zip to login this server when I use Windows 7 OS. I've use the -v argument to obtain more information, see below for detail: ----------- werner@debian-asus:~$ ssh -l hszhao ssh.sshcenter.info -p 60001 -Z key -v OpenSSH_5.2p1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /usr/local/etc/ssh_config debug1: Connecting to ssh.sshcenter.info [218.30.64.199] port 60001. debug1: connect to address 218.30.64.199 port 60001: Connection timed out ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out ---------- Furthermore, I also checked the file /usr/local/etc/ssh_config, all of the content are commented out in this file, and this is the default case. See below for detail: -------- werner@debian-asus:~$ cat /usr/local/etc/ssh_config # $OpenBSD: ssh_config,v 1.25 2009/02/17 01:28:32 djm Exp $ # This is the ssh client system-wide configuration file. See # ssh_config(5) for more information. This file provides defaults for # users, and the values can be changed in per-user configuration files # or on the command line. # Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. # Site-wide defaults for some commonly used options. For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page. # Host * # ForwardAgent no # ForwardX11 no # RhostsRSAAuthentication no # RSAAuthentication yes # PasswordAuthentication yes # HostbasedAuthentication no # GSSAPIAuthentication no # GSSAPIDelegateCredentials no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/identity # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # Port 22 # Protocol 2,1 # Cipher 3des # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128- cbc,3des-cbc # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160 # EscapeChar ~ # Tunnel no # TunnelDevice any:any # PermitLocalCommand no # VisualHostKey no --------- Any hints will be highly appreciated, thanks again. Regards -- .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-18 08:22 +0000 |
| Message-ID | <Uc68u.52278$uR1.43315@fx19.iad> |
| In reply to | #2536 |
On 2013-10-17, Hongyi Zhao <hongyi.zhao@gmail.com> wrote: > On Wed, 16 Oct 2013 14:06:45 +0200, ein wrote: > >> 1. Hostname may be wrong. >> 2. SSH port may be wrong. >> 3. Something block this connection, for instance a firewall. > > The port and the hostname all are right ;-) I've check them again and > again. And I can use the http://www.sshcenter.info/site-sshcenter/ > software/myentunnel-unicode-3.5.2-obfuscated.zip to login this server > when I use Windows 7 OS. > > I've use the -v argument to obtain more information, see below for detail: > > ----------- > werner@debian-asus:~$ ssh -l hszhao ssh.sshcenter.info -p 60001 -Z key -v > OpenSSH_5.2p1, OpenSSL 0.9.8o 01 Jun 2010 > debug1: Reading configuration data /usr/local/etc/ssh_config > debug1: Connecting to ssh.sshcenter.info [218.30.64.199] port 60001. > debug1: connect to address 218.30.64.199 port 60001: Connection timed out > ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out > ---------- Well that tells you that the other side is not responsding. You have to take it up with them. Nothing you can do. What is it wirth 60001 port? > > Furthermore, I also checked the file /usr/local/etc/ssh_config, all of > the content are commented out in this file, and this is the default case. > > See below for detail: There are none. All lines are comments. None do anything. > > -------- > werner@debian-asus:~$ cat /usr/local/etc/ssh_config > # $OpenBSD: ssh_config,v 1.25 2009/02/17 01:28:32 djm Exp $ > > # This is the ssh client system-wide configuration file. See > # ssh_config(5) for more information. This file provides defaults for > # users, and the values can be changed in per-user configuration files > # or on the command line. > > # Configuration data is parsed as follows: > # 1. command line options > # 2. user-specific file > # 3. system-wide file > # Any configuration value is only changed the first time it is set. > # Thus, host-specific definitions should be at the beginning of the > # configuration file, and defaults at the end. > > # Site-wide defaults for some commonly used options. For a comprehensive > # list of available options, their meanings and defaults, please see the > # ssh_config(5) man page. > > # Host * > # ForwardAgent no > # ForwardX11 no > # RhostsRSAAuthentication no > # RSAAuthentication yes > # PasswordAuthentication yes > # HostbasedAuthentication no > # GSSAPIAuthentication no > # GSSAPIDelegateCredentials no > # BatchMode no > # CheckHostIP yes > # AddressFamily any > # ConnectTimeout 0 > # StrictHostKeyChecking ask > # IdentityFile ~/.ssh/identity > # IdentityFile ~/.ssh/id_rsa > # IdentityFile ~/.ssh/id_dsa > # Port 22 > # Protocol 2,1 > # Cipher 3des > # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128- > cbc,3des-cbc > # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160 > # EscapeChar ~ > # Tunnel no > # TunnelDevice any:any > # PermitLocalCommand no > # VisualHostKey no > --------- > > Any hints will be highly appreciated, thanks again. > > Regards
[toc] | [prev] | [next] | [standalone]
| From | ein <ein@no.spam> |
|---|---|
| Date | 2013-10-21 04:21 +0200 |
| Message-ID | <l4232j$3af$1@node2.news.atman.pl> |
| In reply to | #2536 |
[Multipart message — attachments visible in raw view] — view raw
Hongyi Zhao wrote:
> On Wed, 16 Oct 2013 14:06:45 +0200, ein wrote:
>
>> 1. Hostname may be wrong.
>> 2. SSH port may be wrong.
>> 3. Something block this connection, for instance a firewall.
>
> The port and the hostname all are right ;-) I've check them again and
> again. And I can use the http://www.sshcenter.info/site-sshcenter/
> software/myentunnel-unicode-3.5.2-obfuscated.zip to login this server
> when I use Windows 7 OS.
Sorry for late answer, I was busy. According to my nmap's results:
Starting Nmap 5.51 ( http://nmap.org ) at 2013-10-21 04:07 CEST
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is
disabled. Try using --system-dns or specify valid servers with --dns-servers
Initiating SYN Stealth Scan at 04:07
Scanning 218.30.64.199 [1 port]
Completed SYN Stealth Scan at 04:07, 2.02s elapsed (1 total ports)
Nmap scan report for 218.30.64.199
Host is up.
PORT STATE SERVICE
60001/tcp *filtered* unknown
Read data files from: /usr/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 2.06 seconds
Raw packets sent: 2 (88B) | Rcvd: 0 (0B)
The host is down and was down in the day you wrote this massage.
According to 'nslookup ssh.sshcenter.inf':
;; Truncated, retrying in TCP mode.
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
ssh.sshcenter.info canonical name = c-ssh.luozhucheng.info.
Name: c-ssh.luozhucheng.info
Address: 108.61.74.44
Name: c-ssh.luozhucheng.info
Address: 142.4.60.109
Name: c-ssh.luozhucheng.info
Address: 162.210.39.138
Name: c-ssh.luozhucheng.info
Address: 162.218.93.91
Name: c-ssh.luozhucheng.info
Address: 162.220.218.146
Name: c-ssh.luozhucheng.info
Address: 173.252.246.216
Name: c-ssh.luozhucheng.info
Address: 173.254.227.21
Name: c-ssh.luozhucheng.info
Address: 184.95.43.34
Name: c-ssh.luozhucheng.info
Address: 192.30.35.196
Name: c-ssh.luozhucheng.info
Address: 198.23.227.195
Name: c-ssh.luozhucheng.info
Address: 198.56.129.15
Name: c-ssh.luozhucheng.info
Address: 198.98.103.195
Name: c-ssh.luozhucheng.info
Address: 198.199.101.80
Name: c-ssh.luozhucheng.info
Address: 199.68.199.229
Name: c-ssh.luozhucheng.info
Address: 199.91.71.205
Name: c-ssh.luozhucheng.info
Address: 199.119.224.224
Name: c-ssh.luozhucheng.info
Address: 199.231.227.191
Name: c-ssh.luozhucheng.info
Address: 209.141.63.131
Name: c-ssh.luozhucheng.info
Address: 216.24.199.57
Name: c-ssh.luozhucheng.info
Address: 216.158.84.79
Name: c-ssh.luozhucheng.info
Address: 23.90.4.123
Name: c-ssh.luozhucheng.info
Address: 69.163.34.77
Name: c-ssh.luozhucheng.info
Address: 69.197.147.91
Name: c-ssh.luozhucheng.info
Address: 69.197.147.92
Name: c-ssh.luozhucheng.info
Address: 74.82.164.28
This hostname resolves to few different IP addresses. So try different:
Starting Nmap 5.51 ( http://nmap.org ) at 2013-10-21 04:15 CEST
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is
disabled. Try using --system-dns or specify valid servers with --dns-servers
Initiating SYN Stealth Scan at 04:15
Scanning 25 hosts [1 port/host]
Discovered open port 60001/tcp on 162.210.39.138
Discovered open port 60001/tcp on 192.30.35.196
Discovered open port 60001/tcp on 142.4.60.109
Discovered open port 60001/tcp on 198.56.129.15
Discovered open port 60001/tcp on 184.95.43.34
Discovered open port 60001/tcp on 173.254.227.21
Discovered open port 60001/tcp on 173.252.246.216
Discovered open port 60001/tcp on 162.218.93.91
Discovered open port 60001/tcp on 162.220.218.146
Discovered open port 60001/tcp on 198.23.227.195
Discovered open port 60001/tcp on 199.231.227.191
Discovered open port 60001/tcp on 108.61.74.44
Discovered open port 60001/tcp on 199.68.199.229
Discovered open port 60001/tcp on 199.119.224.224
Discovered open port 60001/tcp on 199.91.71.205
Discovered open port 60001/tcp on 69.197.147.92
Discovered open port 60001/tcp on 23.90.4.123
Discovered open port 60001/tcp on 69.197.147.91
Discovered open port 60001/tcp on 209.141.63.131
Discovered open port 60001/tcp on 216.158.84.79
Discovered open port 60001/tcp on 216.24.199.57
Discovered open port 60001/tcp on 198.199.101.80
Discovered open port 60001/tcp on 74.82.164.28
Discovered open port 60001/tcp on 198.98.103.195
Discovered open port 60001/tcp on 69.163.34.77
> I've use the -v argument to obtain more information, see below for detail:
>
> -----------
> werner@debian-asus:~$ ssh -l hszhao ssh.sshcenter.info -p 60001 -Z key -v
> OpenSSH_5.2p1, OpenSSL 0.9.8o 01 Jun 2010
> debug1: Reading configuration data /usr/local/etc/ssh_config
> debug1: Connecting to ssh.sshcenter.info [218.30.64.199] port 60001.
> debug1: connect to address 218.30.64.199 port 60001: Connection timed out
> ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out
> ----------
>
> Furthermore, I also checked the file /usr/local/etc/ssh_config, all of
> the content are commented out in this file, and this is the default case.
>
> See below for detail:
>
> --------
> werner@debian-asus:~$ cat /usr/local/etc/ssh_config
> # $OpenBSD: ssh_config,v 1.25 2009/02/17 01:28:32 djm Exp $
>
> # This is the ssh client system-wide configuration file. See
> # ssh_config(5) for more information. This file provides defaults for
> # users, and the values can be changed in per-user configuration files
> # or on the command line.
>
> # Configuration data is parsed as follows:
> # 1. command line options
> # 2. user-specific file
> # 3. system-wide file
> # Any configuration value is only changed the first time it is set.
> # Thus, host-specific definitions should be at the beginning of the
> # configuration file, and defaults at the end.
>
> # Site-wide defaults for some commonly used options. For a comprehensive
> # list of available options, their meanings and defaults, please see the
> # ssh_config(5) man page.
>
> # Host *
> # ForwardAgent no
> # ForwardX11 no
> # RhostsRSAAuthentication no
> # RSAAuthentication yes
> # PasswordAuthentication yes
> # HostbasedAuthentication no
> # GSSAPIAuthentication no
> # GSSAPIDelegateCredentials no
> # BatchMode no
> # CheckHostIP yes
> # AddressFamily any
> # ConnectTimeout 0
> # StrictHostKeyChecking ask
> # IdentityFile ~/.ssh/identity
> # IdentityFile ~/.ssh/id_rsa
> # IdentityFile ~/.ssh/id_dsa
> # Port 22
> # Protocol 2,1
> # Cipher 3des
> # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-
> cbc,3des-cbc
> # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
> # EscapeChar ~
> # Tunnel no
> # TunnelDevice any:any
> # PermitLocalCommand no
> # VisualHostKey no
> ---------
>
> Any hints will be highly appreciated, thanks again.
SSH client configuration is irrelevant now. Not until TCP handshake is
established.
[toc] | [prev] | [next] | [standalone]
| From | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| Date | 2013-11-02 06:55 +0000 |
| Message-ID | <l527kg$tmi$1@aspen.stu.neva.ru> |
| In reply to | #2539 |
On Mon, 21 Oct 2013 04:21:07 +0200, ein wrote: > According to 'nslookup ssh.sshcenter.inf': > > ;; Truncated, retrying in TCP mode. > Server: 127.0.0.1 Address: 127.0.0.1#53 > > Non-authoritative answer: > ssh.sshcenter.info canonical name = c-ssh.luozhucheng.info. > Name: c-ssh.luozhucheng.info Address: 108.61.74.44 Name: > c-ssh.luozhucheng.info Address: 142.4.60.109 Name: > c-ssh.luozhucheng.info Address: 162.210.39.138 Name: > c-ssh.luozhucheng.info Address: 162.218.93.91 Name: > c-ssh.luozhucheng.info Address: 162.220.218.146 Name: > c-ssh.luozhucheng.info Address: 173.252.246.216 Name: > c-ssh.luozhucheng.info Address: 173.254.227.21 Name: > c-ssh.luozhucheng.info Address: 184.95.43.34 Name: > c-ssh.luozhucheng.info Address: 192.30.35.196 Name: > c-ssh.luozhucheng.info Address: 198.23.227.195 Name: > c-ssh.luozhucheng.info Address: 198.56.129.15 Name: > c-ssh.luozhucheng.info Address: 198.98.103.195 Name: > c-ssh.luozhucheng.info Address: 198.199.101.80 Name: > c-ssh.luozhucheng.info Address: 199.68.199.229 Name: > c-ssh.luozhucheng.info Address: 199.91.71.205 Name: > c-ssh.luozhucheng.info Address: 199.119.224.224 Name: > c-ssh.luozhucheng.info Address: 199.231.227.191 Name: > c-ssh.luozhucheng.info Address: 209.141.63.131 Name: > c-ssh.luozhucheng.info Address: 216.24.199.57 Name: > c-ssh.luozhucheng.info Address: 216.158.84.79 Name: > c-ssh.luozhucheng.info Address: 23.90.4.123 Name: > c-ssh.luozhucheng.info Address: 69.163.34.77 Name: > c-ssh.luozhucheng.info Address: 69.197.147.91 Name: > c-ssh.luozhucheng.info Address: 69.197.147.92 Name: > c-ssh.luozhucheng.info Address: 74.82.164.28 According your above results, you can find all of the ip addreses that binded with the FQDN ssh.sshcenter.info. But in my case, I only can find one IP of them: ------- werner@debian-asus:~$ nslookup ssh.sshcenter.info Server: 192.168.0.1 Address: 192.168.0.1#53 Non-authoritative answer: Name: ssh.sshcenter.info Address: 216.24.199.57 ---------- Why does this happen? Regards -- .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> |
|---|---|
| Date | 2013-11-02 10:15 +0100 |
| Message-ID | <l52fr3$2vo2$1@saria.nerim.net> |
| In reply to | #2549 |
Hello, Hongyi Zhao a écrit : > > According your above results, you can find all of the ip addreses that > binded with the FQDN ssh.sshcenter.info. But in my case, I only can find > one IP of them: > > ------- > werner@debian-asus:~$ nslookup ssh.sshcenter.info > Server: 192.168.0.1 > Address: 192.168.0.1#53 > > Non-authoritative answer: > Name: ssh.sshcenter.info > Address: 216.24.199.57 > ---------- > > Why does this happen? Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or lies. It does not even mention that ssh.sshcenter.info is a CNAME (alias). Can't you use another one ?
[toc] | [prev] | [next] | [standalone]
| From | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| Date | 2013-11-03 03:15 +0000 |
| Message-ID | <l54f4e$itp$1@aspen.stu.neva.ru> |
| In reply to | #2552 |
On Sat, 02 Nov 2013 10:15:28 +0100, Pascal Hambourg wrote:
> Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or
> lies. It does not even mention that ssh.sshcenter.info is a CNAME
> (alias). Can't you use another one ?
I don't know how to find the recursive DNS server for my case, see the
following output on my Debian box:
----------
werner@debian-asus:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr c8:60:00:df:24:23
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::ca60:ff:fedf:2423/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34079 errors:0 dropped:0 overruns:0 frame:0
TX packets:32438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25156142 (23.9 MiB) TX bytes:4868917 (4.6 MiB)
Interrupt:20 Memory:f7300000-f7320000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:346591 (338.4 KiB) TX bytes:346591 (338.4 KiB)
-----------
Regards
--
.: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> |
|---|---|
| Date | 2013-11-03 08:31 +0100 |
| Message-ID | <l54u4g$o13$1@saria.nerim.net> |
| In reply to | #2554 |
Hongyi Zhao a écrit : > On Sat, 02 Nov 2013 10:15:28 +0100, Pascal Hambourg wrote: > >> Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or >> lies. It does not even mention that ssh.sshcenter.info is a CNAME >> (alias). Can't you use another one ? > > I don't know how to find the recursive DNS server for my case The nameserver addresses are defined in /etc/resolv.conf. However you can test a different nameserver with nslookup,dig,host without modifying the file. E.g. if you want to test one of Google's open DNS servers : $ nslookup ssh.sshcenter.info 8.8.8.8
[toc] | [prev] | [next] | [standalone]
| From | Hongyi Zhao <hongyi.zhao@gmail.com> |
|---|---|
| Date | 2013-11-04 02:09 +0000 |
| Message-ID | <l56vk2$mpm$1@aspen.stu.neva.ru> |
| In reply to | #2555 |
On Sun, 03 Nov 2013 08:31:41 +0100, Pascal Hambourg wrote: > $ nslookup ssh.sshcenter.info 8.8.8.8 Good, thanks. Regards -- .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-16 16:02 +0000 |
| Message-ID | <7My7u.66541$Us6.42900@fx12.iad> |
| In reply to | #2533 |
On 2013-10-16, Hongyi Zhao <hongyi.zhao@gmail.com> wrote: > Hi all, > > I own a account on the ssh server ssh.sshcenter.info, see here http:// > www.sshcenter.info/site-sshcenter/pay-ssh-account.php for detail, which > supports the obfuscated ssh login method now. > > When I login with the following command, I always failed with the > following information: > > werner@debian-asus:~$ ssh -Nfx -D 7070 hszhao@ssh.sshcenter.info -p > 60001 -Z key > ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out > > Why does this happen? Ask them. This would seem to indicate that they are not listening to port 60001 or are very slow to respond. Note, are you sure you did not actually want 6001? I have no idea what "obfuscated ssh login" means. Nor can I read chinese I am afraid. Try ssh -vvv ... to see what your ssh side sent out the other side and is waiting for. > > Regards
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.networking
csiph-web