2nd wifi adapter won't successful connect.

infernosoft · #1 10th August 2010, 06:28 PM

My laptop has an internal wifi adapter, but I recently purchased another one because of its extended range.

lsusb, shows that the new adapter is:

Code:

Bus 002 Device 027: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter

After disconnecting my internal adapter from the wireless network, I can scan for networks using my new adapter, and even connect to the network. But when I try browsing online, webpages won't show up. Also, pinging various servers (ie. google.com) returns no output.

Is this a possible conflict with my internal adapter?

Thanks.

JEO · #2 10th August 2010, 07:06 PM

Maybe your routing is still going to the internal interface. After connecting the new wireless, post the output of the following commands in a terminal window:

netstat -r

iwconfig

ifconfig

infernosoft · #3 10th August 2010, 09:03 PM

Quote:

Originally Posted by JEO

Maybe your routing is still going to the internal interface. After connecting the new wireless, post the output of the following commands in a terminal window:

netstat -r

iwconfig

ifconfig

Thanks for the assistance.

netstat -r :

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.2.0     *               255.255.255.0   U         0 0          0 wlan1
default         192.168.2.1     0.0.0.0         UG        0 0          0 wlan1

iwconfig :

Code:

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  Nickname:""
          Access Point: Not-Associated   
          Link Quality:5  Signal level:0  Noise level:167
          Rx invalid nwid:0  invalid crypt:0  invalid misc:0

vboxnet0  no wireless extensions.

wlan1     IEEE 802.11bg  ESSID:"myESSID"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: (blurred)   
          Bit Rate=24 Mb/s   Tx-Power=27 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=55/70  Signal level=-55 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ifconfig :

Code:

eth0      Link encap:Ethernet  HWaddr (blurred) 
          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:18 

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:5102 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5285604 (5.0 MiB)  TX bytes:5285604 (5.0 MiB)

wlan0     Link encap:Ethernet  HWaddr (blurred)  
          inet6 addr: fe80::222:5fff:fed7:8c1e/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2528073 errors:0 dropped:0 overruns:0 frame:1265312
          TX packets:1904307 errors:130 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3180257929 (2.9 GiB)  TX bytes:382220969 (364.5 MiB)
          Interrupt:17 Base address:0xc000 

wlan1     Link encap:Ethernet  HWaddr (blurred)  
          inet addr:192.168.2.123  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::2c0:caff:fe3e:d08b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:335 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:93619 (91.4 KiB)  TX bytes:45824 (44.7 KiB)

P.S. none of the "blurred" appear more than once, if that matters.

JEO · #4 10th August 2010, 09:57 PM

can you ping the gateway 192.168.2.1 and also post "cat /etc/resolv.conf"?

GoinEasy9 · #5 10th August 2010, 10:10 PM

ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Is the same identification I get on a usb embedded wireless access point that came with one of my Asus motherboards. This is the one piece of hardware I have never been able to get working with Linux. The rtl8187b driver has had only limited success and I've never seen anyone post that they've had success with it. It may be because it was built to be a wireless access point, I don't know, but, if anyone has success here, I'd certainly be interested.

infernosoft · #6 15th August 2010, 05:35 PM

Quote:

Originally Posted by JEO

can you ping the gateway 192.168.2.1 and also post "cat /etc/resolv.conf"?

Sorry for the late reply! Yes I can successfully ping the gateway, and the output of "cat /etc/resolv.conf" is:

Code:

# Generated by NetworkManager
nameserver 192.168.2.1

Okay, this is a little weird. I just posted this reply while connected via the external one (and the internal one being disconnected). After making this post, my connection got very slow and then I couldn't ping the gateway or browse any webpage....

kurtdriver · #7 15th August 2010, 06:31 PM

Quote:

Originally Posted by GoinEasy9

ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Is the same identification I get on a usb embedded wireless access point that came with one of my Asus motherboards. This is the one piece of hardware I have never been able to get working with Linux. The rtl8187b driver has had only limited success and I've never seen anyone post that they've had success with it. It may be because it was built to be a wireless access point, I don't know, but, if anyone has success here, I'd certainly be interested.

Works well for me. It's built into a USB adapter called GSKY.

Code:

[kurt@Heimdal Downloads]$ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 0951:1607 Kingston Technology DataTraveler 100
Bus 002 Device 003: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 002 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04f2:b070 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

JEO · #8 15th August 2010, 10:44 PM

Quote:

Originally Posted by infernosoft

Sorry for the late reply! Yes I can successfully ping the gateway, and the output of "cat /etc/resolv.conf" is:

Code:

# Generated by NetworkManager
nameserver 192.168.2.1

Okay, this is a little weird. I just posted this reply while connected via the external one (and the internal one being disconnected). After making this post, my connection got very slow and then I couldn't ping the gateway or browse any webpage....

Sounds like your user experience is the same as mine (I have the rtl8187B model). The supplied driver seems to produce a weak transmitted signal as seen by the router (at least 20db down). What works well is blacklisting the rtl8187b driver and going with ndiswrapper and using that to wrap the windows XP version of the driver. You can find ndiswrapper and the associated kmod in the rpmfusion software repository. This works well using 32 bit F13 (i686), not so sure if the 64 bit (x86_64) works right with ndiswrapper and the XP driver as I don't have it.

GoinEasy9 · #9 15th August 2010, 11:32 PM

@kurtdriver
OK, I'm interested ... how? What driver are you using. I haven't experimented in a while, your not going to tell me the driver is in the kernel are you? I tried the windows driver with ndiswrapper a long time ago, the best I got with it is 1b/sec (yes that's 1 bit per second).

kurtdriver · #10 16th August 2010, 04:34 AM

Quote:

Originally Posted by GoinEasy9

@kurtdriver
OK, I'm interested ... how? What driver are you using. I haven't experimented in a while, your not going to tell me the driver is in the kernel are you? I tried the windows driver with ndiswrapper a long time ago, the best I got with it is 1b/sec (yes that's 1 bit per second).

I just plugged it in and it worked. My laptop has a rtl8192se built in and and I use the one from the manufacturer and have to make install with each kernel update.

Code:

[kurt@Heimdal kurt]$ lsmod |grep rtl8187
rtl8187                31286  0 
mac80211              197073  1 rtl8187
cfg80211              117166  2 rtl8187,mac80211
eeprom_93cx6            1607  1 rtl8187

infernosoft · #11 16th August 2010, 04:56 PM

Quote:

Originally Posted by JEO

Sounds like your user experience is the same as mine (I have the rtl8187B model). The supplied driver seems to produce a weak transmitted signal as seen by the router (at least 20db down). What works well is blacklisting the rtl8187b driver and going with ndiswrapper and using that to wrap the windows XP version of the driver. You can find ndiswrapper and the associated kmod in the rpmfusion software repository. This works well using 32 bit F13 (i686), not so sure if the 64 bit (x86_64) works right with ndiswrapper and the XP driver as I don't have it.

Blacklisting the driver and using ndiswrapper means no more packet injection when auditing networks, correct?

Quote:

Originally Posted by kurtdriver

I just plugged it in and it worked. My laptop has a rtl8192se built in and and I use the one from the manufacturer and have to make install with each kernel update.

Code:

[kurt@Heimdal kurt]$ lsmod |grep rtl8187
rtl8187                31286  0 
mac80211              197073  1 rtl8187
cfg80211              117166  2 rtl8187,mac80211
eeprom_93cx6            1607  1 rtl8187

I'm unsure what this exactly means but I get the exact output when doing "lsmod |grep rtl8187":

Code:

rtl8187                31286  0 
mac80211              197073  1 rtl8187
cfg80211              117166  2 rtl8187,mac80211
eeprom_93cx6            1607  1 rtl8187

Great discussion we're having here!

GoinEasy9 · #12 16th August 2010, 05:54 PM

I have the same output from lsmod | grep rtl8187
For me, it doesn't just work. I did try again last night. I looked at the manufacturers site and there still is no Linux driver for this chipset.
I always thought that it would be interesting to use the computer with it's onboard wireless access point, so, I guess it's time to experiment a little. I don't see much discussion of the rtl8187b very often, let's see where this thread takes us.

infernosoft · #13 22nd August 2010, 04:50 PM

Any updates anyone? This thread became so stagnant all of a sudden..

JEO · #14 22nd August 2010, 08:08 PM

"Blacklisting the driver and using ndiswrapper means no more packet injection when auditing networks, correct?"

Sorry, first I've heard of it. I only use mine to connect normally.