On 2007-Apr-19 23:50:00 +1000, Alan Garfield <[EMAIL PROTECTED]> wrote: >debug1: Local version string SSH-2.0-OpenSSH_3.4p1 >debug1: SSH2_MSG_KEXINIT sent >d475 078f 7eae aef6 >Disconnecting: Bad packet length -730527857. >debug1: Calling cleanup 0x1001fc68(0x0) >localhost $
'Bad packet length' is coming from ssh (packet.c:packet_read_poll2()) and (as Yar suggested) is related to SSH's own packetisation, rather than TCP. The reported packet length is the 'd475 078f' immediately above. Note that at this stage, SSH has not negotiated encryption so working thru a tcpdump output is still practical. I suspect that there's a problem with the packet sizes. >> > Yeah it's what the Linux driver is called. Can be something else, got a >> > better name? :) >> >> Perhaps just "jn"? Some utilities still have trouble with long >> interface names[1], and they are a drag to type in. :-) So I'd >> rather keep the name as short as possible. > >Yeah 'jn' sounds ok to me. Although it's really not going to be that >common unless you have these SunFire or NewISys servers. :) All the utilities I've seen will just truncate the names. Since we already have 4-character interface names (eg vlan), and there will never be more than one of these, I'd prefer to leave it as jnet. There are a limited number of 2-letter combinations and 4 letters is more descriptive. (I would far prefer that "vlan" be truncated to something shorter so that my daily reports don't have 48 lines stating 'vlan1'). -- Peter Jeremy
pgptPqZ2Apexk.pgp
Description: PGP signature
