ssh_exchange_identification: Connection closed by remote host PART II
Greetings again:
I have sshd working again after adding an entry in my firewall/router's
/etc/hosts.allow file, but I am rather concerned that sshd included
tcp_wrappers without alerting users that are upgrading software via apt or
dselect! Unless I missed something, I always read all the notifications
during each Woody upgrade.
My question now is this: do I need to make these hosts_allow entries into
each of my linux computers? I still find it very odd that all the other
computers were able to connect to my firewall/router as it was, and only my
Woody box was banned from connecting.
The only other thing that might add to the syndrome is that I have a user
logged (ssh) into my box via the router for several weeks compiling kde3.
shrug
ke6sls@arrl.net
----original msg----
Greetings:
I am unable to connect to my cable firewall/router from my desktop box
suddenly. I have gone so far as to wipe out my known_hosts file from my .ssh
directory, but this still gives me the same error. What is unusual is that I
can ssh to any of the other computers on my lan, *then* ssh to my router
without difficulty. What did I do wrong? Any help gleefully excepted. I am
running woody on both boxes, and updated them an hour ago. I also ran
dpkg-reconfigure for ssh on the router just in case I had an update and
entered a wrong value.
PS plz mail me direct as I am not on this list.
thank you
--
Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls
If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN.
Free software, in a free world, for a free spirit. Please Support freedom!
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: