I am still not able to connect. My system sees my wireless but when I try to connect to it it does not connect. I just downloaded ndiswrapper but I do not know what to do now.
The uname command tells me that the fedora is using an i386 installation ..I guess.. ------------------------------- uname -a Linux localhost.localdomain 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 15:12:59 EST 2007 i686 athlon i386 GNU/Linux ---------------------------- Still trying :-) On Mon, Feb 25, 2008 at 7:48 AM, Néstor <[EMAIL PROTECTED]> wrote: > DJA, Jim, > > I will continue when I get home, this evening. > > Thanks, > > Nestor :-) > > > On Sun, Feb 24, 2008 at 11:50 PM, James G. Sack (jim) <[EMAIL PROTECTED]> > wrote: > > > Néstor wrote: > > > James, > > > > > > iwlist scan - shows my network and my neighbords > > > *wlan0 Scan completed : > > > Cell 01 - Address: 00:11:95:3A:9D:D1 > > > ESSID:"mondongo" > > > Mode:Master > > > Channel:3 > > > Frequency:2.422 GHz > > > Quality=14/64 Signal level=47/65 > > > Encryption key:on > > > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 > > Mb/s > > > 12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 > > Mb/s > > > 48 Mb/s; 54 Mb/s > > > Extra:tsf=0000005f46022be2* > > > > > > > > > I tried this command: > > > iwconfig wlan0 essid mondongo channel 3 key xxxxxxxxxxxxxxxxxx > > > > > > After an ifconfig, I get: > > > *wlan0 Link encap:Ethernet HWaddr 00:C0:A8:CE:D8:DE > > > inet6 addr: fe80::2c0:a8ff:fece:d8de/64 Scope:Link > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:1470 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:480090 (468.8 KiB) TX bytes:5080 (4.9 KiB) > > > > > > wmaster0 Link encap:UNSPEC HWaddr > > > 00-C0-A8-CE-D8-DE-48-5A-00-00-00-00-00-00-00-00 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)* > > > > > > > > > But how do I know if the wireless communication is working? > > > > Hey, that's great so far. it shows the wireless driver is talking to the > > hardware, and the radio is working, as well. > > > > Presuming that a command > > iwconfig wlan0 > > reports back the essid (etc) you set, that gives more confidence the > > sowtware is working. > > > > The next step to do it manually might be as simple as trying > > dhclient wlan0 > > > > But, wireless is fussy, and I don't understand all the manual steps as > > well as for wired, so I usually fall back on the system tools. > > > > I see that dja is explaining NM, so that's what I'd suggest as well. > > > > Good luck, and keep us posted. > > > > Regards, > > ..jim > > > > > > -- > > [email protected] > > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list > > > > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
