Re: Using putty to debug ssh through a firewall
- From: "Richard E. Silverman" <res@xxxxxxxx>
- Date: 20 Aug 2007 06:30:11 -0400
"NS" == NightStrike <nightstrike@xxxxxxxxx> writes:
NS> On Aug 18, 9:46 am, Jacob Nevins <jac...@xxxxxxxxxxxxxxxxxxxxxx>
NS> wrote:
>> NightStrike <nightstr...@xxxxxxxxx> writes: >I currently use ssh to
>> access things outside of a firewall. [...] >debug1:
>> SSH2_MSG_KEXINIT sent
>>
>> >And it just hangs there until the connection times out. Any ideas
>> on >what might be causing a hang at that stage?
>>
>> KEXINIT messages can be quite large. Guess: could it be
>> <http://www.snailbook.com/faq/mtu-mismatch.auto.html>?
NS> It's possible, but I don't think so. I will post tomorrow similar
NS> information but where I force SSH v1 protocol. There will be a
NS> similar hanging point. What would be a good tool to use to see if
NS> a KEXINIT message is in fact being transmitted, however slowly?
Wireshark will show you this, as that portion of the protocol is not yet
encrypted.
--
Richard Silverman
res@xxxxxxxx
.
- Follow-Ups:
- Re: Using putty to debug ssh through a firewall
- From: NightStrike
- Re: Using putty to debug ssh through a firewall
- References:
- Using putty to debug ssh through a firewall
- From: NightStrike
- Re: Using putty to debug ssh through a firewall
- From: Jacob Nevins
- Re: Using putty to debug ssh through a firewall
- From: NightStrike
- Using putty to debug ssh through a firewall
- Prev by Date: Re: Using putty to debug ssh through a firewall
- Next by Date: sshd and dynamic firewall rules?
- Previous by thread: Re: Using putty to debug ssh through a firewall
- Next by thread: Re: Using putty to debug ssh through a firewall
- Index(es):
Relevant Pages
|