Antonio Olivares wrote:
> Dear folks,
>
> I am having a difficult time connecting at decent speeds to a wireless network
> setup by my nephew with Fedora 14. I installed Fedora 14 on a quad core machine
> that had Fedora 12 happily running. IT has a built in wireless device
> integrated in it. The installation worked beautifully and connected the first
> time around. The driver rtl8187 loaded fine and I browsed the web and applied
> all the updates and got new kernel too. I was very happy. I turned off the
> machine and yesterday and today tried to connect to internet with it and it not
> longer works the way it did the first time :(, I cannot connect to any page like
> I did before and networkmanger in KDE tells me that I am connected but cannot
> browse. In windows, I can browse the web without troubles, here is output from
> ipconfig /all
>
> Microsoft Windows [Version 6.1.7600]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>
> C:\Users\Antonio>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Antonio-PC
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Wireless LAN adapter Wireless Network Connection 3:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11g 54Mbps U
> SB 2.0 Network Adapter #2
> Physical Address. . . . . . . . . : 00-15-AF-28-DC-7C
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . : fe80::105a:7fb5:99a3:17fa%16(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Wednesday, November 24, 2010 8:00:15 PM
> Lease Expires . . . . . . . . . . : Thursday, November 25, 2010 8:00:15 PM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 419435951
> DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-65-BA-DA-00-1D-60-33-D1-16
>
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Ethernet adapter Local Area Connection 2:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
> net Controller
> Physical Address. . . . . . . . . : 00-1D-60-33-CA-B0
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
>
> Ethernet adapter Local Area Connection:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family PCI Gigabit E
> thernet NIC (NDIS 6.20)
> Physical Address. . . . . . . . . : 00-1D-60-33-D1-16
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter isatap.{360ECDCC-3E91-498C-BD12-65F1412852FA}:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Microsoft ISATAP Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Teredo Tunneling Pseudo-Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:3064:3f6:3f57:fef8(Prefe
> rred)
> Link-local IPv6 Address . . . . . : fe80::3064:3f6:3f57:fef8%14(Preferred)
> Default Gateway . . . . . . . . . : ::
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> C:\Users\Antonio>
>
>
> What can I do in Linux to make my connection work the same way that it did the
> first time? I appreciate any advice given and hope all users around the world
> have a nice Thanksgiving Holiday :)
>
Do you get a connection? On the top bar of your desktop (after login) should be
a symbol which looks like a bar graph, indicating the network is connected. If
you hover the mouse over it you will get information.
If you have two little fireballs chasing each other in circles, it means the
wireless can't connect to the router. And if you have a console with an "X" at
the base, it means the connect was tried and failed.
What to do: if you have the bar graph your issue is with routing, you do have a
connection. See other posts here which have thoughts on that.
If you have no bar graph, but the console and X, clicking on the icon will give
you some status. It may give you a list of available access points, in which
case look for yours and click it on the menu. With luck you will connect and can
come back to ask about making that automatic. Note that you may need to provide
a password if you have your access point set up right. Security is another
issue, but default passwords (or none) are dangerous.
Hopefully that gets you going, or to more info you can report.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
