Hello, putting that one back to list, it's not silly ;-)
I tried ssh [EMAIL PROTECTED] -> same result. So the nic isn't the problem ... I looked into dmesg again, the bios is mentioned as AT/286+ there?! Is that normal? Btw, the IP-Address is unique ;-) Are there known bugs on VIA-CPUs? Which informations do I need to provide? (dmesg is hard, I have to write it up, but if that helps, let me know and I'll do it). Regards Hagen Volpers -----Urspr|ngliche Nachricht----- Von: Maxim Belooussov [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 19. Juli 2007 21:38 An: openbsd misc Betreff: Re: hardware problem?! strangely ssh error Hi Hagen, Doing this off-the list in case I sound too silly. For starters, have you tried to ssh [EMAIL PROTECTED] This would give a clue where the problem could be. Further make sure that there is no machine with the same ip on your net - I've seen before that some connections were 'dying' all over sudden when another (linux) box with same IP was closing 'illegal' connection. Hope it helps, Maxim > > On Thu, 19 Jul 2007, openbsd misc wrote: > > >> > misc(at)openbsd.org wrote: > >> >> Hello, > >> >> > >> >> I have a system with openbsd 4.1 installed. Everything works fine > >> (lynx > >> >> / ping / ...) but I'm not able to connect to another system via > ssh. > >> I'm > >> >> not able to connect to the system, too. > >> >> The error I got: > >> >> > >> >> 2: Bad packet length <integer> > >> >> > >> >> I googled a bit, but I wasn't able to find out what exactly is > wrong. > >> >> Here are the informations from dmesg about the nics: > >> >> > >> >> sis0 at pci0 dev 8 function 0 "NS DP83815 10/100" rev 0x00, > DP83816A: > >> >> irq 11, address 00:02:b6:33:50:dd > >> >> > >> >> Btw, I'm talking about a fresh 4.1 installation, completly > untouched. > >> >> > >> >> Has anyone an idea for me? Driver problem? Unsupported hardware? > The > >> >> hardware was checked twice by producer (and I don't have the > problems > >> >> using linux), I don't think that is a hardware defect. > >> >> > >> >> Thanks. > >> >> > >> >> Regards > >> >> Hagen Volpers > >> >> > >> > > >> > Have you tried: > >> > > >> > ssh -vvv host.to.connect.to > >> > > >> > That might give some clues. > >> > > >> > HTH > >> > Fred > >> > -- > >> > http://www.crowsons.com/puters/x41.htm > >> > >> Hello, > >> > >> here are the last lines: > >> > >> debug1: SSH2_MSG_NEWKEYS sent > >> debug1: expecting SSH2_MSG_NEWKEYS > >> debug2: set_newkeys: mode 0 > >> debug1: SSH2_MSG_NEWKEYS received > >> debug1: SSH2_MSG_SERVICE_REQUEST sent > >> > >> followed by the error mentioned in my first mail. > >> > >> Does that help? Do you need more informations? > >> > >> Regards > >> Hagen Volpers > > > > Try to determine where the error occurs. For example: is this a > network > > driver issue? To find out put another type network card into the > > machine and try to use ssh over it. > > > > Another test would be to connect to another machine (running a > > different version of sshd?), to test if this is a ssh protcol problem > > on the local or remote side. > > > > Can you ssh INTO the machine? > > > > Make notes of what works and what not, etc. Try to be smart and rule > > out possible causes, this enable you to zoom in into the real problem. > > > > > -Otto > > Hello, > > unfortunately I'm not able to test another nic, the system doesn't have > a pci slot (we are talking about a all-in-one board - e.g. > http://www.visionsystems.de/1_2_5_4.html). I already did all the other > tests you mentioned, except changing the ssh protocol - lynx / ping > works, ssh from to machine to different machines doesn't work (I can > connect from other systems without any problem), ssh to the machine > doesn't work, too. > > Any other ideas? > > Regards > Hagen Volpers
