Skip to main content
17 events
when toggle format what by license comment
Aug 14, 2015 at 22:31 comment added tuk0z Same $§@#! issue here: SSH client gets the server OpenSSH's version, so it looks like I'm hitting the sshd server and all of the routing stuff seems okay. Then hangs on debug1: SSH2_MSG_KEXINIT sent. Finally discovered that the router (Orange Sagem "Livebox") wouldn't NAT connection from inside the LAN (needs to connect from the Internet) Reference (in French)
Nov 26, 2009 at 17:43 history edited justinhj CC BY-SA 2.5
added 63 characters in body
Nov 11, 2009 at 17:03 history edited justinhj CC BY-SA 2.5
added 102 characters in body
Nov 1, 2009 at 20:30 history edited justinhj CC BY-SA 2.5
added some output from wireshark
Oct 22, 2009 at 17:00 vote accept CommunityBot
Oct 22, 2009 at 17:00 history bounty ended justinhj
Oct 22, 2009 at 3:33 comment added justinhj Not sure, what changes do you make in sshd_config to allow that?
Oct 21, 2009 at 10:39 comment added mr-euro Can you actually login with password instead of passkey when outside?
Oct 19, 2009 at 21:45 answer added Heath timeline score: 2
Oct 15, 2009 at 16:30 history bounty started justinhj
Oct 14, 2009 at 18:12 comment added quack quixote this link indicates problems stemming from the wireless. their symptoms were disconnects well after the authentication, tho. still, might be helpful: ubuntuforums.org/showthread.php?t=838873
Oct 14, 2009 at 17:50 answer added mattikus timeline score: 0
Oct 12, 2009 at 20:55 comment added justinhj And yes I am testing on my home network, just using the external IP so it has to go out and come back in again. I've also tried using my neighbours wifi to connect. With their permission, of course
Oct 12, 2009 at 20:54 comment added justinhj Yeah good point, I was being rushed out the door
Oct 12, 2009 at 20:53 history edited justinhj CC BY-SA 2.5
added 6761 characters in body
Oct 12, 2009 at 2:58 comment added avelldiroll you could add more details - tell if it works on your home network (you can also test an ssh connexion from the server) and give the full error message of the client (not just the last line - use ssh -vvv), and if possible, post the relevant parts of sshd logs on the server (/var/log/auth.log ... that might be another file depending on your logger daemon config), .... - to satisfy everybody's paranoia, consider modifying your login/host names from your logs.
Oct 12, 2009 at 0:57 history asked justinhj CC BY-SA 2.5