I get connect to the wifi but I have no internet connection

[Bodegas]

I have a Realtek rtl8188ce and Ubuntu 13.10 with kernel version 3.11 "06:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)"

I followed all the instructions to install your driver and now I get to connect to the wifi but I have no internet connection. When I ping the router, can not find it, nor find any internet domain.

I have spent a lot of hours ... not hours, days and can not get past this point.

I used the 13.10 branch, and during compilation only has given me some warning, no errors.

Before installation of your driver the output of lsmod |grep rtl was: rtl8192ce 53550 0 rtl_pci 26641 1 rtl8192ce rtlwifi 63229 2 rtl_pci,rtl8192ce rtl8192c_common 48877 1 rtl8192ce mac80211 597268 3 rtl_pci,rtlwifi,rtl8192ce cfg80211 480503 2 mac80211,rtlwifi

After installation of your driver: rtl8192ce 137725 0 rtlwifi 110108 1 rtl8192ce mac80211 597268 2 rtlwifi,rtl8192ce cfg80211 480503 2 mac80211,rtlwifi

What could be the problem?

[FreedomBen]

How do you know you are connected? When you get connected, run "iwconfig" and "ifconfig" and paste the results here. You may try running "sudo dhclient" a few times once connected to make sure you're requesting a DHCP configuration.

[Bodegas]

Hello and thanks for your answer.

I know I am connected because network manager tell me that is connected to wifi. Output of iwconfig is: wlan0 IEEE 802.11bgn ESSID:"wifialba" Mode:Managed Frequency:2.457 GHz Access Point: 00:25:9C:4B:82:98 Bit Rate=1 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Power Management:off Link Quality=48/70 Signal level=-62 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:8 Missed beacon:0

Output of ifconfig is: wlan0 Link encap:Ethernet direcciónHW 80:1f:02:9a:83:67 Direc. inet:192.168.1.110 Difus.:192.168.1.255 Másc:255.255.255.0 Dirección inet6: fe80::821f:2ff:fe9a:8367/64 Alcance:Enlace ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST MTU:1500 Métrica:1 Paquetes RX:12 errores:0 perdidos:0 overruns:0 frame:0 Paquetes TX:138 errores:0 perdidos:0 overruns:0 carrier:0 colisiones:0 long.colaTX:1000 Bytes RX:2146 (2.1 KB) TX bytes:19118 (19.1 KB)

ACTIVO = UP FUNCIONANDO = RUNNING

I executed sudo dhclient and there is no change. Second time I executed sudo dhclient the output was: $ sudo dhclient RTNETLINK answers: File exists

Any idea?

[FreedomBen]

Hmm, everything looks good from what I've seen, with only the exception that your signal level seems a bit weak. One of the existing issues with this driver (which I'm slowly trying to compensate for in the driver when I have time, which is currently not very often, sigh) is that the actual transmit power is often much lower than the reported power. This is particularly frustrating since we have no way of knowing what happens to our Tx frames after they leave. This could be what you're seeing based on the Rx power level.

One workaround I have is to set the regulatory domain to a less restrictive one (like Bolivia (BO)) and crank up the Tx power to 30 dBm. You can do this with "sudo iw reg set BO". This might be illegal where you are so be advised (in the US the legal limit is 20 dBm). See if that helps you. You may also try getting closer to the access point and see if it improves. Since you're associated with the AP I suspect this could be the problem. If not it may be an OS network config error. Based on your output it looks like the driver is working properly. You can also monitor the output of "dmesg" and see if there are any log messages indicating network problems.

[Bodegas]

I have proven your suggestion: "sudo iw reg set BO" and in fact now I get this:

wlan0 IEEE 802.11bgn ESSID:"wifialba" Mode:Managed Frequency:2.457 GHz Access Point: 00:25:9C:4B:82:98 Bit Rate=1 Mb/s Tx-Power=33 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Power Management:off Link Quality=46/70 Signal level=-64 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:14 Missed beacon:0

Before: Tx-Power=20 dBm Signal level=-62 dBm

After: Tx-Power=33 dBm Signal level=-64 dBm

But I still not receive any packet from router when I do a ping.

With dmesg I obtain this, since I turn on wifi: [ 923.883896] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 928.480674] wlan0: authenticate with 00:25:9c:4b:82:98 [ 928.489816] wlan0: send auth to 00:25:9c:4b:82:98 (try 1/3) [ 928.492917] wlan0: authenticated [ 928.493171] rtl8192ce 0000:06:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [ 928.493180] rtl8192ce 0000:06:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [ 928.495340] wlan0: associate with 00:25:9c:4b:82:98 (try 1/3) [ 928.497720] wlan0: RX AssocResp from 00:25:9c:4b:82:98 (capab=0x11 status=0 aid=9) [ 928.497879] wlan0: associated [ 928.497895] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

I'm absolutely stuck.

[farindk]

Exactly the same problem here. Card is a rtl8188ce, pci id 10ec:8178 running on ubuntu 13.10. With this driver, I can connect to the network, I get an IP address from the router, but data does not go through. Signal level is -58 dBm, but same problem also with a mobile access point and -40dBm, so probably not related to signal quality.

[Bodegas]

Hello again, I have good and bad news. I have solved my problem, finally I have internet connection. But...the solution was change the router. The problem was there...seems like router and wireless card was incompatible.

Thanks for your time and farindk, I hope that you fix your problem

[farindk]

As the card works fine with Windows 7, there must be a way to get it to work. Might be that exchanging the router may solve the problem, but still, I see this as a driver issue. My router is a dd-wrt on Asus WL500, if that helps.

[FreedomBen]

I suspect that it is probably both. The driver is probably not following the protocol to the tee. Some router firmwares are quite tolerant of that and will continue to function while others will not. That is likely the problem.

[obedlink]

I have two routers an U.S. Robotics 9108A and a Thomson TG585 v7 and in both the same problem.

[FreedomBen]

@obedlink Do you know which firmware version you are running on each of your routers?

[obedlink]

@FreedomBen in the U.S Robotics I'm using the lastest (BETA Version 1.8 - Annex A only), and in the Thomson the lastest international firmware (v.7.4.3)

[FreedomBen]

I don't know if you're still having any of these issues, but it may be a problem with Ubuntu. Unfortunately I don't have the problem myself so I can't troubleshoot it, but others have moved to other distros like Fedora, Arch, Manjaro, Chakra, etc. and everything worked fine. It may be something wrong with Ubuntu's NetworkManager config or something.

I've been asked what distro(s) I run, and the answer is Fedora and Arch. I put Fedora on boxes that I don't use at least every other day (since Arch wants to be updated frequently and Fedora is highly tolerant of large intervals between updates) and Arch on my daily driver. Arch takes some work to get installed but once done, I actually think Arch is easier to maintain than the others because its internals are so transparent.

If you want to stick with Ubuntu, perhaps try disabling NetworkManager and using an alternative like wicd.