Bug 1125 - packet_get_int() returns -1 (serverloop.c)
Summary: packet_get_int() returns -1 (serverloop.c)
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: 3.7.1p2
Hardware: All Linux
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-25 23:39 AEDT by Tristan Cebulla
Modified: 2006-10-07 11:43 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Cebulla 2005-11-25 23:39:27 AEDT
Hi there.

This morning I connected via ssh to my server:

[09:41:16][equinox@abmahnung]
[~] $ .goth
connecting to domain: lichtspiele.org (217.160.131.3) for equinox
ssh options: -XC -i /home/equinox/.ssh/neogoth.key
Received disconnect from 217.160.131.3: 2: server_input_channel_req: unknown channel -1
[09:41:17][equinox@abmahnung]
[~] $ .goth
connecting to domain: lichtspiele.org (217.160.131.3) for equinox
ssh options: -XC -i /home/equinox/.ssh/neogoth.key
Last login: Fri Nov 25 00:12:43 2005 from acb6bd31.ipt.aol.com
[09:41:20][equinox@neogoth]
[~] $

As you can see, the connection attempt was fine the second time, but the first time I got that error.
This problem is not reproducible because it only appear twice in a year, but it seems to be a bug.

If you need any more information please let me know.

--
Tristan Cebulla
Comment 1 Darren Tucker 2005-11-26 14:04:10 AEDT
There's insufficient information here to do anything other than guess, so here's a guess: perhaps the X11 forward port is busy, the bind fails and that's the unknown channel?

You can test this with "netcat" on the server.  Make sure there's nothing listening on port 6010 (use netstat -an), then make netcat listen on that port ("nc -l -p 6010"), connect to the port ("nc localhost 6010") then quit both netcats.  This should leave port 6010 in a "TIME_WAIT" state (check with netstat).   

Now quickly try your ssh connection (the TIME_WAIT will only last about 2 minutes).  If this reproduces your problem then it's a known bug that will be fixed in the 4.3 release.  If it doesn't, then I'm out of ideas.
Comment 2 Tristan Cebulla 2005-11-29 01:14:21 AEDT
I couldn't reproduce that problem with your suggestion.
I set loglevel to DEBUG now and if this happens again I hope I can give you more information.

Btw, I just saw that "X11Forwarding no" is set in my sshd-config but I used -XC as connection parameters, could this cause the error?
Comment 3 Damien Miller 2005-12-27 10:33:17 AEDT
Could you please try to replicate the problem with a more recent version? I.e. 4.2 or the soon to be released 4.3.
Comment 4 Damien Miller 2006-03-12 15:39:07 AEDT
3 months and no reply == no bug
Comment 5 Darren Tucker 2006-10-07 11:43:30 AEST
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.