Re: Problem setting up wired networking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 14 November 2008 15:33:20 Chuck Anderson 
wrote:
> On Fri, Nov 14, 2008 at 03:15:40PM +0000, Anne 
Wilson wrote:
> > [root@AAO ~]# iwlist scanning
> >
> > wlan0     No scan results
>
> Either the card isn't "up" or something else is wrong.  
Can you try
> these in this order:
>
> ifconfig wlan0 up
>
> ifconfig wlan0
>
wlan0     Link encap:Ethernet  HWaddr 
00:22:33:44:55:66
          UP BROADCAST 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)

I did read somewhere that a MTU of 1400 is better.

> iwconfig wlan0
>wlan0     IEEE 802.11bg  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access 
Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 
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:0
          Tx excessive retries:0  Invalid misc:0   Missed 
beacon:0

Now that's a report I haven't seen before.  It appears that 
neither my ESSID or key are being read from the file that 
surely must be created when NM configures the 
connection.

> iwlist scanning

As before - No  scan results.

Wow - some progress, if only small.  In view of what 
appears above I renamed ifcfg-wlan0 and created a new 
one.  I immediately got a popup saying that I am now 
connected to myESSID.  BUT, the icon shows a very weak 
signal, and ifconfig shows that it has the address 
10.42.44.1, while my network is a 192.168.0.x LAN.

This is the situation I reached a couple of days ago, and 
I'm comopletely foxed by it.

Running iwconfig wlan0 again I now get

wlan0     IEEE 802.11bg  ESSID:"myESSID"
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 
36:8F:3A:45:3F:BC
          Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 
B
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid 
frag:0
          Tx excessive retries:0  Invalid misc:0   Missed 
beacon:0

I tried changing the setup from ad-hoc to Infrastructure, 
but that breaks things - I can no longer connect.

FWIW, my router does not list this netbook as a 
connected device.

Anne

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux