Wireless problems with HomeHub 3

[iclestu]

Hey folks,

I am having some big issues using wireless internet through my homehub 3.

The homehub works fine on my desktop (and equally fine if i plug my kubuntu netbook to it with a network cable) but for some reason it misbehaves when i connect wirelessly...

The netbook works fine in other wireless networks and, equally, other devices (smartphones and windows laptops) work fine wirelessly with my homehub. The netbook goes through the motions and connects to the homehub ok but when I try to load a webpage it times out at 'looking up google.com...' or whatever. I suspected DNS issues but when i tried to change it to googledns it still wouldnt work. Could the connection to the homehub be overrulling the dns server entries in resolv.conf?

any help gratefuly recieved!

[iclestu]

i should add that changing to Wicd makes no difference... symptoms exactly the same

[iclestu]

and neither does using a puppy linux live usb....

I have no idea whats wrong here

[iclestu]

forgive the shameless bump.

Has anyone got any ideas?

[chili555]

What is in resolv.conf, and how it is used, is different between versions of Ubuntu. What is in there?

cat /etc/resolv.conf
lsb_release -d

Do you have any settings in Wicd related to DNS? Can you ping by number?

ping -c3 192.168.1.1 <--or whatever your Homehub address is
ping -c3 173.194.73.99

What kind of (Intel) wireless card is in your netbook?

lspci -nn | grep 0280

Thanks.

[iclestu]

Hey there,

Thank you very much for replying. Here is the additional info:

resolve.conf:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001.4860::8888

lsb_release -d:

Description:    Ubuntu 12.04 LTS

Pings:

PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.

--- 192.168.1.254 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2009ms

PING 173.194.73.99 (173.194.73.99) 56(84) bytes of data.
From 192.168.1.66 icmp_seq=1 Destination Host Unreachable
From 192.168.1.66 icmp_seq=2 Destination Host Unreachable
From 192.168.1.66 icmp_seq=3 Destination Host Unreachable

--- 173.194.73.99 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms
pipe 3

network card:

02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8192E/RTL8192SE Wireless LAN Controller [10ec:8192] (rev 01)

I am aware of lots of issues with the driver for this card but believe that it has been resolved from 12.04 onwards? (I had previously found instructions for installing the manufacturers one on the internet). Either way I do not think this is the same issue as I have no problems connecting to public wifi nor do I have problems connecting to my girlfriends (protected) wifi.

I removed Wicd and went back to the default network manager after I found it hadnt helped. Can happily reinstall and check for DNS settings if needs be?

Thanks again for taking an interest.

[chili555]

I'm not sure you're actually connected! Let's see:

iwconfig
dmesg | grep wlan
route -n

I removed Wicd and went back to the default network manager after I found it hadnt helped.

Are there any manually added settings in there? Normally, none are needed.

[iclestu]

I'm not sure you're actually connected! Let's see:

iwconfig
dmesg | grep wlan
route -n

Are there any manually added settings in there? Normally, none are needed.

No, none. I have deleted and recreated the connection loads of times.

iwconfig:

pan1      no wireless extensions.

lo        no wireless extensions.

wlan0     802.11bgn  ESSID:"BTHub3-W4J6"  Nickname:"rtl8192E"
          Mode:Managed  Frequency=2.462 GHz  Access Point: CC:96:A0:2C:9D:BE   
          Bit Rate=19.5 Mb/s   
          Retry:on   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=94/100  Signal level=-54 dBm  Noise level=-117 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

dmesg:

[   20.523976] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.526260] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   23.960940] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   31.032617] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   73.308289] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   84.080050] wlan0: no IPv6 routers present
[  312.615974] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  314.231093] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  315.770369] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  316.900652] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  317.102101] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  323.307218] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  325.000657] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  326.625169] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  327.971383] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  328.945949] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  336.665280] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  347.376052] wlan0: no IPv6 routers present

ooo - that looks promising? IPv6 routers? should I change settings to IPv4 only? (im sure I have tried that before though?)

route:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 wlan0
10.168.157.0    0.0.0.0         255.255.255.0   U     0      0        0 pan1
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 wlan0

I should perhaps just let you know that I am plugging and unpluging a network cable each time to let me get online to respond (just in case its affecting any of the above?). Each time I make sure that i show as connected to the wireless netword but disconnected from the wired to generate the output then go online to paste it here...

[chili555]

ooo - that looks promising? IPv6 routers? should I change settings to IPv4 only? (im sure I have tried that before though?)

It's trivial. It just means the system doesn't see any IPv6 capable routers out there so it isn't going to bother going through the motions of asking for and waiting for an IPv6 address. You can speed things up by, oh maybe 1/100th of a second if you set IPv6 to ignore in Network Manager.

Please detach the ethernet cable and so we have a clean slate, reboot. Then run:

dmesg | grep -e 819 -e wlan
sudo cat /var/log/syslog | grep etwork | tail -n20
cat /etc/resolvconf/resolv.conf.d/original

Post them here. I love a mystery!

[iclestu]

Post them here. I love a mystery!

Ha Ha - I am very grateful that you are taking an interest!

Here goes (Rebooted as you said).

stewart@stewart-N130:~$ dmesg | grep -e 819 -e wlan
[    0.222408] pci 0000:02:00.0: [10ec:8192] type 0 class 0x000280
[    1.281891] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
[   17.603574] r8192e_pci: module is from the staging directory, the quality is unknown, you have been warned.
[   17.673774] Linux kernel driver for RTL8192E WLAN cards
[   17.673872] rtl819xE 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   17.673890] rtl819xE 0000:02:00.0: setting latency timer to 64
[   20.128498] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.130968] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   23.470985] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   34.022405] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  141.938815] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  152.720055] wlan0: no IPv6 routers present

May 23 14:43:44 stewart-N130 NetworkManager[637]: <info> (wlan0): supplicant interface state: associating -> associated
May 23 14:43:44 stewart-N130 NetworkManager[637]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'BTHub3-W4J6'.
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May 23 14:43:45 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> DNS: starting dnsmasq...
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> Policy set 'BTHub3-W4J6' (wlan0) as default for IPv4 routing and DNS.
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) successful, device activated.
May 23 14:43:46 stewart-N130 NetworkManager[637]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
May 23 14:43:50 stewart-N130 blueman-mechanism: loading Network 
May 23 14:43:51 stewart-N130 NetworkManager[637]: <warn> /sys/devices/virtual/net/pan1: couldn't determine device driver; ignoring...
May 23 14:43:51 stewart-N130 NetworkManager[637]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan1, iface: pan1)
May 23 14:43:51 stewart-N130 NetworkManager[637]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan1, iface: pan1): no ifupdown configuration found.

# Generated by NetworkManager
nameserver 192.168.1.254