From: Dave H. <dhy...@gm...> - 2006-08-17 07:37:32
|
Hi, I have a WRT54G AP. I can connect fine if I turn WEP off. If I turn WEP on, and edit my /etc/network/interfaces file from: iface mwlan0 inet dhcp pre-up /sbin/iwconfig $IFACE essid any txpower 100mW to this: iface mwlan0 inet dhcp pre-up /sbin/iwconfig $IFACE essid "MySSID" key 26-hex-digits txpower 100mW All I get is an error: NET: Registered protocol family 17 udhcpc (v0.9.9-pre) started Dec 31 16:01:07 udhcpc[247]: udhcpc (v0.9.9-pre) started smc91x: not found (-19). m Dec 31 16:01:07 udhcpc[247]: [truncated] m Error for wireless request "Set ESSID" (8B1A) : SET failed on device mwlan0 ; Connection refused. Is WEP supported? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Darren G. <ts...@ya...> - 2006-08-17 15:28:17
|
Hi Dave, Seems that I remember figuring this out months ago for my MA701 but unfortunately I apparently didn't save the results. Are you able to get it to work from the command line using iwconfig incantations? On Aug 17, 2006, at 12:37 AM, Dave Hylands wrote: > Hi, > > I have a WRT54G AP. > > I can connect fine if I turn WEP off. If I turn WEP on, and edit my > /etc/network/interfaces file from: > > iface mwlan0 inet dhcp > pre-up /sbin/iwconfig $IFACE essid any txpower 100mW > > > to this: > > iface mwlan0 inet dhcp > pre-up /sbin/iwconfig $IFACE essid "MySSID" key 26-hex-digits > txpower 100mW > > All I get is an error: > > NET: Registered protocol family 17 > udhcpc (v0.9.9-pre) started > Dec 31 16:01:07 udhcpc[247]: udhcpc (v0.9.9-pre) started > smc91x: not found (-19). > m > Dec 31 16:01:07 udhcpc[247]: [truncated] m > Error for wireless request "Set ESSID" (8B1A) : > SET failed on device mwlan0 ; Connection refused. > > Is WEP supported? > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ---------------------------------------------------------------------- > --- > 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 |
From: Dave H. <dhy...@gm...> - 2006-08-17 15:35:06
|
Hi Darren, > Seems that I remember figuring this out months ago for my MA701 but > unfortunately I apparently didn't save the results. Are you able to > get it to work from the command line using iwconfig incantations? So far no. I couldn't get it to work from the command line with my unprotected WAP until I rebooted either. Whenever I try entering the ESSID from the command line, I get a Connection refused error (same as when booting with the essid and key provided in the interfaces file). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Darren G. <ts...@ya...> - 2006-08-17 15:50:42
|
Hi Dave, In case it may help, I found underneath pile on desk my gumstix that was working on an open WAP and its /etc/network/interfaces has: auto wlan0 iface wlan0 inet dhcp pre-up /sbin/modprobe pcmcia; sleep 1; /sbin/iwconfig wlan0 mode managed; /sbin/iwconfig essid any post-down /sbin/modprobe -r pcmcia IIRC the modprobe of pcmcia will solve your smc91x not found problem. On Aug 17, 2006, at 8:33 AM, Dave Hylands wrote: > Hi Darren, > >> Seems that I remember figuring this out months ago for my MA701 but >> unfortunately I apparently didn't save the results. Are you able to >> get it to work from the command line using iwconfig incantations? > > So far no. > > I couldn't get it to work from the command line with my unprotected > WAP until I rebooted either. > > Whenever I try entering the ESSID from the command line, I get a > Connection refused error (same as when booting with the essid and key > provided in the interfaces file). > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ---------------------------------------------------------------------- > --- > 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 |
From: Craig H. <cr...@gu...> - 2006-08-17 16:00:52
|
On Aug 17, 2006, at 8:33 AM, Dave Hylands wrote: > Hi Darren, > >> Seems that I remember figuring this out months ago for my MA701 but >> unfortunately I apparently didn't save the results. Are you able to >> get it to work from the command line using iwconfig incantations? > > So far no. > > I couldn't get it to work from the command line with my unprotected > WAP until I rebooted either. > > Whenever I try entering the ESSID from the command line, I get a > Connection refused error (same as when booting with the essid and key > provided in the interfaces file). Dave -- are you using the latest pcmcia & smc91x drivers? 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. C |
From: Dave H. <dhy...@gm...> - 2006-08-17 19:45:30
|
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. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Steven W. <st...@st...> - 2006-08-17 21:17:43
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi all,<br> <br> 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.<br> <br> I'm guessing a wireless network issue, any ideas? Anyone seen this behavior before, or know where I should look for error messages?<br> <br> Thanks,<br> Steve<br> <br> Dave Hylands wrote: <blockquote cite="mid...@ma..." type="cite"> <pre wrap="">Hi Craig, </pre> <blockquote type="cite"> <pre wrap="">Dave -- are you using the latest pcmcia & smc91x drivers? </pre> </blockquote> <pre wrap=""><!----> SVN 1079. Did an svn update last night, plus an rm -f of the build_arm_nofpu and toolchain_arm_nofpu directories. </pre> <blockquote type="cite"> <pre wrap="">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. </pre> </blockquote> <pre wrap=""><!----> 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. </pre> </blockquote> </body> </html> |
From: Craig H. <cr...@gu...> - 2006-08-17 23:21:57
|
Almost every time I've had ssh login delays on any platform, it's been due to problems with DNS when sshd tries to reverse-lookup the IP address you're connecting from. Does the logfile on the gumstix say anything? C On Aug 17, 2006, at 3:10 PM, Steven Waslander wrote: > 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 >> > > ---------------------------------------------------------------------- > --- > 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 |
From: Steven W. <st...@st...> - 2006-08-18 02:01:16
|
Good idea, Unfortunately, I see no related log messages on the gumstix. In the options.h file for dropbear, the option to do a reverse-lookup is disabled, per build 773. I looked in /var/log/any file I could think of opening, and found related stuff in messages, but no reverse-lookup data. It could be our router too, as it happens between two laptops as well. Thansk for the help, though. Steve Craig Hughes wrote: > Almost every time I've had ssh login delays on any platform, it's > been due to problems with DNS when sshd tries to reverse-lookup the > IP address you're connecting from. Does the logfile on the gumstix > say anything? > > C > > On Aug 17, 2006, at 3:10 PM, Steven Waslander wrote: > > >> 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 >>> >>> >> ---------------------------------------------------------------------- >> --- >> 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 >> > > > ------------------------------------------------------------------------- > 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 > |
From: Miguel P. C. <mig...@gm...> - 2006-08-18 04:21:27
|
It usually happend to me when a machine uses a DNS to reverse the direction your are conneting to . On Linux boxes I usually fix it on /etc/ssh/sshd_config with the following line VerifyReverseMapping no I dont know how you can fix this on the gumstix thoug... I hope it helps |
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 > |
From: Dominic J. E. <sa...@th...> - 2006-08-19 17:58:47
|
On Thu, 17 Aug 2006, Craig Hughes wrote: > Dave -- are you using the latest pcmcia & smc91x drivers? 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: I am using root_fs_arm.r1078 from sf.net (while I recompile after fixing the texinfo issue), and get the same issue when trying to change the ESSID. I have edited /etc/network/interfaces: # cat /etc/network/interfaces # Configure Loopback auto lo iface lo inet loopback auto usb0 iface usb0 inet dhcp iface bnep0 inet dhcp #auto eth0 #iface eth0 inet dhcp #iface wlan0 inet dhcp auto mwlan0 iface mwlan0 inet dhcp pre-up /sbin/iwconfig mwlan0 mode managed essid <myessid> key <mykey> txpower 100mW And trying to run the individual commands at the commandline: # iwconfig mwlan0 mwlan0 MRVL-CF8385 ESSID:"" Mode:Managed Access Point: Not-Associated Bit Rate:1 Mb/s Tx-Power=20 dBm Retry limit:8 RTS thr=2347 B Fragment thr=2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:3 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 # iwconfig mwlan0 mode managed # iwconfig mwlan0 key <mykey> # iwconfig mwlan0 txpower 100mW # iwconfig mwlan0 essid <myessid> Error for wireless request "Set ESSID" (8B1A) : SET failed on device mwlan0 ; Connection refused. - d. -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli ------------------------------------------------------------------------------- http://www.the-infinite.org/ |
From: Dominic J. E. <sa...@th...> - 2006-08-19 20:02:24
|
On Sat, 19 Aug 2006, Dominic J. Eidson wrote: > I am using root_fs_arm.r1078 from sf.net (while I recompile after fixing > the texinfo issue), and get the same issue when trying to change the > ESSID. I just recompiled r1080 from the repository, and get the exact same behaviour. > I have edited /etc/network/interfaces: > # cat /etc/network/interfaces > # Configure Loopback > auto lo > iface lo inet loopback > > auto usb0 > iface usb0 inet dhcp > > iface bnep0 inet dhcp > > #auto eth0 > #iface eth0 inet dhcp > > #iface wlan0 inet dhcp > > auto mwlan0 > iface mwlan0 inet dhcp > pre-up /sbin/iwconfig mwlan0 mode managed essid <myessid> key > <mykey> txpower 100mW > > And trying to run the individual commands at the commandline: > > # iwconfig mwlan0 > mwlan0 MRVL-CF8385 ESSID:"" > Mode:Managed Access Point: Not-Associated Bit Rate:1 Mb/s > Tx-Power=20 dBm > Retry limit:8 RTS thr=2347 B Fragment thr=2346 B > Encryption key:off > Power Management:off > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:3 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > # iwconfig mwlan0 mode managed > # iwconfig mwlan0 key <mykey> > # iwconfig mwlan0 txpower 100mW > # iwconfig mwlan0 essid <myessid> > Error for wireless request "Set ESSID" (8B1A) : > SET failed on device mwlan0 ; Connection refused. I did some more digging around (I compiled strace for other reasons), and saw this: open("/dev/urandom", O_RDONLY) = 4 read(4, "\\fF\17", 4) = 4 close(4) = 0 mq_notify(2, ptrace: umoven: Input/output error {...}) = 4 open("/proc/net/wireless", O_RDONLY) = 5 ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbe8157d0) = -1 ENOTTY (Inappropriate ioctl for device) brk(0) = 0x21000 brk(0x23000) = 0x23000 read(5, "Inter-| sta-| Quality |"..., 4096) = 238 close(5) = 0 ioctl(4, SIOCSIWESSID, 0xbe815cac) = -1 ECONNREFUSED (Connection refused) FD 4 is invalid at tis point - it was the result of the /dev/urandom open, but got closed earlier... .. goes downhill from here... write(2, "Error for wireless request \"", 28Error for wireless request ") = 28 write(2, "Set ESSID", 9Set ESSID) = 9 ... more error message ... write(2, "Connection refused", 18Connection refused) = 18 write(2, ".\n", 2. ) = 2 close(4) = 0 _exit(-6) = ? I also saw a few of these in dmesg, not sure if it's related: mwlan0 (WE) : Driver using old /proc/net/wireless support, please fix driver ! - d. -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli ------------------------------------------------------------------------------- http://www.the-infinite.org/ |
From: Angus C. <an...@an...> - 2006-09-01 10:21:49
|
I had exactly the same problem but after some fairly random attempts, I found the following configuration to work (in /etc/network/interfaces): auto mwlan0 iface mwlan0 inet dhcp pre-up /sbin/iwconfig $IFACE key s:XXXXX key open essid XXXXX txpower 100mW (the key needs to be set before authentication is set to 'open'). By the way, I'm using buildroot r1083 Cheers, Angus -- Dr Angus Clark University of Bristol On 8/19/06, Dominic J. Eidson <sa...@th...> wrote: > On Sat, 19 Aug 2006, Dominic J. Eidson wrote: > > > I am using root_fs_arm.r1078 from sf.net (while I recompile after fixing > > the texinfo issue), and get the same issue when trying to change the > > ESSID. > > I just recompiled r1080 from the repository, and get the exact same > behaviour. > > > I have edited /etc/network/interfaces: > > # cat /etc/network/interfaces > > # Configure Loopback > > auto lo > > iface lo inet loopback > > > > auto usb0 > > iface usb0 inet dhcp > > > > iface bnep0 inet dhcp > > > > #auto eth0 > > #iface eth0 inet dhcp > > > > #iface wlan0 inet dhcp > > > > auto mwlan0 > > iface mwlan0 inet dhcp > > pre-up /sbin/iwconfig mwlan0 mode managed essid <myessid> key > > <mykey> txpower 100mW > > > > And trying to run the individual commands at the commandline: > > > > # iwconfig mwlan0 > > mwlan0 MRVL-CF8385 ESSID:"" > > Mode:Managed Access Point: Not-Associated Bit Rate:1 Mb/s > > Tx-Power=20 dBm > > Retry limit:8 RTS thr=2347 B Fragment thr=2346 B > > Encryption key:off > > Power Management:off > > Link Quality:0 Signal level:0 Noise level:0 > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:3 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > # iwconfig mwlan0 mode managed > > # iwconfig mwlan0 key <mykey> > > # iwconfig mwlan0 txpower 100mW > > # iwconfig mwlan0 essid <myessid> > > Error for wireless request "Set ESSID" (8B1A) : > > SET failed on device mwlan0 ; Connection refused. > > I did some more digging around (I compiled strace for other reasons), and > saw this: > > open("/dev/urandom", O_RDONLY) = 4 > read(4, "\\fF\17", 4) = 4 > close(4) = 0 > mq_notify(2, ptrace: umoven: Input/output error > {...}) = 4 > open("/proc/net/wireless", O_RDONLY) = 5 > ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbe8157d0) = -1 ENOTTY (Inappropriate ioctl for device) > brk(0) = 0x21000 > brk(0x23000) = 0x23000 > read(5, "Inter-| sta-| Quality |"..., 4096) = 238 > close(5) = 0 > ioctl(4, SIOCSIWESSID, 0xbe815cac) = -1 ECONNREFUSED (Connection refused) > > FD 4 is invalid at tis point - it was the result of the /dev/urandom open, > but got closed earlier... > > .. goes downhill from here... > > write(2, "Error for wireless request \"", 28Error for wireless request ") = 28 > write(2, "Set ESSID", 9Set ESSID) = 9 > > ... more error message ... > > write(2, "Connection refused", 18Connection refused) = 18 > write(2, ".\n", 2. > ) = 2 > close(4) = 0 > _exit(-6) = ? > > > I also saw a few of these in dmesg, not sure if it's related: > > mwlan0 (WE) : Driver using old /proc/net/wireless support, please fix > driver ! > > > - d. > > -- > Dominic J. Eidson > "Baruk Khazad! Khazad ai-menu!" - Gimli > ------------------------------------------------------------------------------- > http://www.the-infinite.org/ > > > ------------------------------------------------------------------------- > 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 > |
From: Dave H. <dhy...@gm...> - 2006-09-03 06:00:30
|
Hi Angus, On 9/1/06, Angus Clark <an...@an...> wrote: > I had exactly the same problem but after some fairly random attempts, > I found the following configuration to work (in > /etc/network/interfaces): > > auto mwlan0 > iface mwlan0 inet dhcp > pre-up /sbin/iwconfig $IFACE key s:XXXXX key open essid XXXXX > txpower 100mW > > (the key needs to be set before authentication is set to 'open'). Thanks - I can now connect to WRT54G with WEP enabled. I used the hex digits instead of s:XXXX (the s:XXXX is for using an ASCII version of the key). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |