From: Steven W. <st...@st...> - 2006-08-17 22:10:32
|
To add some more detail, I found ssh -v told me some really neat stuff. ssh -v root@192.168.11.11 OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to 192.168.11.11 [192.168.11.11] port 22 debug1: Connection established. debug1: identify file /home/Steve/.ssh/identity type -1 debug1: identify file /home/Steve/.ssh/id_rsa type -1 debug1: identify file /home/Steve/.ssh/id_dsa type -1 Then there was a 20 second pause followed by debug1: Remote protocol version 2.0, remote software version dropbear_0.44 debug1: no match: dropbear_0.44 debug1: Enabling compatibility mode for protocol 2.0 and then everything was lightning fast. I guess my ssh has never heard of dropbear. Now what? Steve Steven Waslander wrote: > Hi all, > > I've got wifi working on my gumstix through a compact flash card and > was wondering why there is a 20 second delay when I try to ssh to the > gumstix. I removed all other network interfaces and still the delay > persists. I then ssh-ed from the gumstix back to another computer on > the same wifi network and it took almost no time to get the password > prompt, but the password verification step took 20 seconds. > > I'm guessing a wireless network issue, any ideas? Anyone seen this > behavior before, or know where I should look for error messages? > > Thanks, > Steve > > Dave Hylands wrote: >> Hi Craig, >> >> >>> Dave -- are you using the latest pcmcia & smc91x drivers? >>> >> SVN 1079. Did an svn update last night, plus an rm -f of the >> build_arm_nofpu and toolchain_arm_nofpu directories. >> >> >>> Quick test >>> is to remove the "auto eth0" from /etc/network/interfaces. There was >>> a bug I just recently fixed where the smc91x driver would yoink a >>> GPIO line away from CF. The line it was stealing was only used for >>> the 2nd ethernet port on the netDUO, so I changed the code to detect >>> first if there is in fact a 2nd ethernet controller there, and only >>> take the line if there is. The problem came because of the order in >>> which modules were being loaded: >>> >>> /etc/modules: pcmcia would load >>> /etc/init.d/S20network would load /etc/network/interfaces which would >>> load smc91x before trying to start mwlan0, meaning that the GPIO >>> setup would be bad by the time it got to trying to talk to the wifi >>> module. >>> >> So, it's not that the wifi doesn't work. It works fine with my AP if I >> turn WEP off. I can't get it to work when I turn WEP on. >> >> > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |