View Single Post
  #6   (View Single Post)  
Old 28th August 2011
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,131
Default

By default ssh does a reverse DNS lookup of the server it is connecting to. But your server does not have a reverse DNS entry
Code:
$ dig -x 188.120.102.175 

; <<>> DiG 9.4.2-P2 <<>> -x 188.120.102.175
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18872
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;175.102.120.188.in-addr.arpa.  IN      PTR

;; Query time: 510 msec
;; SERVER: 192.168.222.10#53(192.168.222.10)
;; WHEN: Mon Aug 29 00:07:46 2011
;; MSG SIZE  rcvd: 46
So it could be that your workstation is just retrying this lookup, which could take up to 2 minutes. Just try to wait for that long......

If you manage to log in after that long delay, you could add an entry for your server in your /etc/hosts file of your workstation:
Code:
188.120.102.175 freeland.brokenbyte.org
You did not give us a lot of details about the network topology, but you can check whether http://www.openbsd.dk/faq/pf/rdr.html#reflect applies to your situation
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote