can't connect to wireless router with F7

Robert P. J. Day rpjday at mindspring.com
Wed Jun 20 14:34:56 UTC 2007


On Wed, 20 Jun 2007, John DeDourek wrote:

> Robert P. J. Day wrote:
> >   the scenario:
> >
> >   * linksys WRT45GL (WAP with 4 wired ports)
> >   * dell inspiron 9200 with linksys pcmcia card
> >
> >   i've used this pcmcia card successfully with linksys routers for a
> > long time, and i just installed one of the above routers in the home
> > of a friend.  both of their windows systems (vista and XP) connected
> > flawlessly, but now my inspiron can't connect.
> >
> >   previously, under FC6, in this situation, i would go into the
> > network administration dialog, delete the wired entry and create a new
> > wireless entry, which would also be labelled as "eth0".  never had a
> > problem, at least under FC6.
> >
> >   now, with F7, trying this for the first time, i get these new
> > interface entries:
> >
> > # iwconfig
> > lo        no wireless extensions.
> >
> > wifi0     IEEE 802.11b  ESSID:"porthos"
> > Nickname:"localhost.localdomain"
> >           Mode:Master  Frequency:2.437 GHz  Access Point: 00:06:25:0B:84:25
> >           Bit Rate:11 Mb/s   Sensitivity=1/3
> >           Retry limit:8   RTS thr:off   Fragment thr:off
> >           Encryption key:xxxxxxxxxx   Security mode:restricted
> >           Power Management:off
> >
> > wlan0     IEEE 802.11b  ESSID:"porthos"  Nickname:"localhost.localdomain"
> >           Mode:Master  Frequency:2.437 GHz  Access Point: 00:06:25:0B:84:25
> >           Bit Rate:11 Mb/s   Sensitivity=1/3
> >           Retry limit:8   RTS thr:off   Fragment thr:off
> >           Encryption key:xxxxxxxxxx   Security mode:restricted
> >           Power Management:off
> >           Link Quality:0  Signal level:0  Noise level:0
> >           Rx invalid nwid:0  Rx invalid crypt:11306  Rx invalid frag:0
> >           Tx excessive retries:24  Invalid misc:51846   Missed beacon:0
> >
> > sit0      no wireless extensions.
> >
> >
> > # ifconfig
> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:3292 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:3292 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:18159745 (17.3 MiB)  TX bytes:18159745 (17.3 MiB)
> >
> > wifi0     Link encap:UNSPEC  HWaddr
> > 00-06-25-0B-84-25-08-DF-00-00-00-00-00-00-00-00
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:289538 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1025 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:7111118 (6.7 MiB)  TX bytes:207248 (202.3 KiB)
> >           Interrupt:3 Base address:0xe100
> >
> > wlan0     Link encap:Ethernet  HWaddr 00:06:25:0B:84:25
> >           inet6 addr: fe80::206:25ff:fe0b:8425/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:940 errors:0 dropped:288569 overruns:0 frame:0
> >           TX packets:981 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:167658 (163.7 KiB)  TX bytes:198076 (193.4 KiB)
> >           Interrupt:3 Base address:0xe100
> >
> > and any attempt to run "service network start" just hangs.
> >
> >   is there a new incantation i need for this to work under F7?
> > thanks.
> >
> > rday
> >
> > p.s.  the WRT54GL is specifically listed as a wireless "G", but it's
> > been configured to auto-select the speed.  i'm assuming it's not
> > something as simple as a speed mismatch.
> >
>
> It looks to me like you are using the "madwifi" driver.  Is
> that correct?

um ... i'm not sure.  there's certainly no module loaded with that
name.  i'm working with a stock F7 system, on which i haven't loaded
any extra networking functionality, and my current setup worked great
under FC6 on this same system.

> If you're not sure, I can suggest some ways to check.  If you're
> using some other WLAN driver, the following is not applicable.
>
> Are you using WEP or WPA for the security mode?

WEP, which worked fine until now.

rday




More information about the fedora-list mailing list