Fedora Linux Support Community & Resources Center

Home Forums Posting Rules Linux Help Fedora Set-Up Guides Ask Fedora Fedora Project
Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
Reload this Page Fedora 10 Driving Realtek RT8187B Wireless Almost But No Ping
FedoraForum Search
Forgot Password? Join Us!
Register All Albums FAQ Search Today's Posts Mark Forums Read

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 21st December 2008, 10:08 AM
HighClockBitBot Offline
Registered User
  
Join Date: Dec 2008
Posts: 1
Fedora 10 Driving Realtek RT8187B Wireless Almost But No Ping
Wireless adapter finds desired wireless access point, NetworkManager shows strong signal strength, connects, gets proper IP/gateway/DNS, but I still can’t ping anything other than localhost.

Access point uses no security or encryption and works fine for other computers.

Wireless device (wlan0):
050d:705e Belkin USB F5D7050 ver. 5012 featuring Realtek RTL8187B

System:
i686 custom desktop running Fedora 10 kernel 2.6.27.10
Fresh install from Fedora 10 DVD, then compiled new kernel 2.6.27.10 to incorporate Linux driver for wireless device. Not using ndiswrapper.

Wired NIC (eth0) is usually not connected because there is no wired net at the desired location, but if the system is temporarily relocated and connected to a wired LAN, connectivity via wired DHCP works fine.

I've been searching for a solution all over the net for weeks, but no one seems to have this problem. They either seem to have basic problems getting driver to run wireless device at all, or else total network failure. In my case, I have wired networking that works fine and wireless networking that almost seems to work. Where to look? How to troubleshoot further? Any clue would be very helpful. Output from iwconfig, ifconfig, plus some lines from /var/log/messages are below.

Thank you very much for your time to consider this issue.

Code:
*** iwconfig ***

lo        no wireless extensions.

usb0      no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"BGLB-Point-2"  
          Mode:Managed  Frequency:2.442 GHz  Access Point: 00:0F:B5:92:D4:59   
          Bit Rate=54 Mb/s   Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Power Management:off
          Link Quality=64/100  Signal level:-39 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

pan0      no wireless extensions.

virbr0    no wireless extensions.


*** ifconfig ***

eth0      Link encap:Ethernet  HWaddr 00:14:D1:11:39:2C  
          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)
          Interrupt:5 Base address:0xc000 

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:800 (800.0 b)  TX bytes:800 (800.0 b)

usb0      Link encap:Ethernet  HWaddr E6:5C:7A:1F:A6:DD  
          inet6 addr: fe80::e45c:7aff:fe1f:a6dd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:8 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

virbr0    Link encap:Ethernet  HWaddr CE:27:B3:3D:64:65  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::cc27:b3ff:fe3d:6465/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:4528 (4.4 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:17:3F:34:B6:7C  
          inet addr:192.168.3.119  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::217:3fff:fe34:b67c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:361 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:35491 (34.6 KiB)  TX bytes:5140 (5.0 KiB)

wmaster0  Link encap:UNSPEC  HWaddr 00-17-3F-34-B6-7C-F4-9F-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)


*** Possibly relevant lines from /var/log/messages ***

Dec 20 22:24:19 bglb nm-system-settings:    ifcfg-fedora: parsing /etc/sysconfig/networkscripts/ifcfg-lo ...
Dec 20 22:24:19 bglb nm-system-settings:    ifcfg-fedora:     error: Ignoring loopback device config.

Dec 20 22:24:46 bglb avahi-daemon[2192]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

Dec 20 22:25:52 bglb avahi-daemon[2192]: Registering new address record for fe80::217:3fff:fe34:b67c on wlan0.*.
Dec 20 22:25:54 bglb dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Dec 20 22:25:55 bglb dhclient: DHCPOFFER from 192.168.3.1
Dec 20 22:25:55 bglb dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 20 22:25:56 bglb dhclient: DHCPACK from 192.168.3.1
Dec 20 22:25:56 bglb NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound
Dec 20 22:25:56 bglb NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Dec 20 22:25:56 bglb NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Dec 20 22:25:56 bglb NetworkManager: <info>    address 192.168.3.119
Dec 20 22:25:56 bglb NetworkManager: <info>    prefix 24 (255.255.255.0)
Dec 20 22:25:56 bglb NetworkManager: <info>    gateway 192.168.3.1
Dec 20 22:25:56 bglb NetworkManager: <info>    hostname 'new-host'
Dec 20 22:25:56 bglb NetworkManager: <info>    nameserver '192.168.3.1'
Dec 20 22:25:56 bglb NetworkManager: <info>    domain name 'public.bglbnet.com'
Dec 20 22:25:56 bglb NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 20 22:25:56 bglb NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Dec 20 22:25:56 bglb NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 20 22:25:56 bglb avahi-daemon[2192]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.3.119.
Dec 20 22:25:56 bglb avahi-daemon[2192]: New relevant interface wlan0.IPv4 for mDNS.
Dec 20 22:25:56 bglb avahi-daemon[2192]: Registering new address record for 192.168.3.119 on wlan0.IPv4.
Dec 20 22:25:56 bglb dhclient: bound to 192.168.3.119 -- renewal in 13375 seconds.
Dec 20 22:25:57 bglb NetworkManager: <info>  (wlan0): device state change: 7 -> 8
Dec 20 22:25:57 bglb NetworkManager: <info>  Policy set 'Auto BGLB-Point-2' (wlan0) as default for routing and DNS.
Dec 20 22:25:57 bglb NetworkManager: <info>  Activation (wlan0) successful, device activated.
Dec 20 22:25:57 bglb NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

= = = = = = = = = =
Reply With Quote
  #2  
Old 21st December 2008, 12:03 PM
David Becker Offline
Registered User
  
Join Date: Feb 2006
Posts: 780
Quote:
Originally Posted by HighClockBitBot View Post
Wireless adapter finds desired wireless access point, NetworkManager shows strong signal strength, connects, gets proper IP/gateway/DNS, but I still can’t ping anything other than localhost.

Access point uses no security or encryption and works fine for other computers.

Wireless device (wlan0):
050d:705e Belkin USB F5D7050 ver. 5012 featuring Realtek RTL8187B

System:
i686 custom desktop running Fedora 10 kernel 2.6.27.10
Fresh install from Fedora 10 DVD, then compiled new kernel 2.6.27.10 to incorporate Linux driver for wireless device. Not using ndiswrapper.
I have no experience with this hardware, but it would seem to be supported by the stock 2.6.27 kernels. There's explicit support for 8187b. Any reason why you had to compile the kernel?

Other than that, your entire setup would seem to be correct.

David
Reply With Quote
  #3  
Old 21st December 2008, 07:35 PM
darethehair Offline
Registered User
  
Join Date: Nov 2007
Posts: 23
Sorry, no help from me on this either, but yesterday I tried the same thing and got the same results i.e. everything *appeared* to be working, but could not ping (or otherwise communicate) with my LAN. My experiment used a Trendnet TEW-424UB wireless USB device.
Reply With Quote
  #4  
Old 22nd December 2008, 01:49 AM
totalnoob Offline
Registered User
  
Join Date: Dec 2008
Posts: 8
Problem with Belkin usb adapter with Realtek 8187b chipset
edited out to avoid threadjacking. new thread started for my (much more basic) problem
Last edited by totalnoob; 22nd December 2008 at 02:40 AM.
Reply With Quote
Reply

Tags
driving, fedora, ping, realtek, rt8187b, wireless

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Xp can ping fedora10 but fedora can't ping xp. atifshakeel Servers & Networking 8 22nd May 2009 09:36 AM
Ping (and connection) problem between 2 wireless in Fedora 10 itisspeedy Servers & Networking 0 8th January 2009 01:52 PM
fedora,realtek wireless network card and network manager lodore Servers & Networking 4 5th January 2009 12:39 AM
Finding wireless driving and using yum NoobTillILearn Hardware & Laptops 4 5th June 2007 07:51 PM


Current GMT-time: 16:31 (Friday, 24-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

 FedoraForum is Powered by RedHat