10.10 and wireless question.

Hi everyone I've been using 10.10 since it came out but have recently ran into an odd issue. Regardless of if the computer has been restarted or has been sleeping/standby mode the wireless, while still connected, will not work. At first I thought it was my home network not working, but I am typing this on one of my other computers attached to the same network. I'm sorta at a loss as to why this is happening so any suggestions will be great.

If it helps the machine I've got 10.10 installed on is a hp pavillion dv6000 and I'm currently up to date according to the update manager. Thanks in advance.

 

Do you see a wifi symbol in the tray? Also when you do an ifconfig what info does it give for your wireless nic?

 

Yeah I do see the symbol for wifi and it shows that I am connected but when the issue crops up it still shows Im connected to our network. Sorry but I'm not the best with linux but i did run the ifconfig in terminal but don't know what I'm looking for aside from the wlan info.

 

Yeah exactly, post the output of sudo ifconfig and sudo iwconfig

It would be good to know what kind of wireless card you have too, so post the output of lspci

Further: can you ping your router? can you ping your ISP's default gateway?

 

You're looking for a proper ip being issued by your dhcp server. If that is correct and you can ping your gateway there maybe a setting on your router inhibiting the local ip from accessing outside the lan. When you issue ifconfig in the terminal you should see a series of numbers looking like this : 192.168.X.X (the X is a variable as some routers issue different addressing schemes). Ill post and example when I get to my computer.

 

Using:

Code:

ifconfig

This is my output:

Code:

andrew@sphinx:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:24:7e:6a:0a:31 
          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:20 Memory:fc000000-fc020000

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:480 (480.0 B)  TX bytes:480 (480.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:22:fa:db:d4:76 
          [B]inet addr:192.168.1.8[/B]  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:faff:fedb:d476/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10416 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7943 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13142223 (13.1 MB)  TX bytes:1488420 (1.4 MB)

The bold text is the important stuff as it shows whether or not you have an address or dhcp error. A 192.168.X.X address is a DHCP server issued address scheme. If you see a 169.X.X.X address that means there are DCHP issues. Now here is the command to ping my router/gateway:

Code:

ping 192.168.1.1

As you can see the third set in the series of numbers is the same as mine above (bold text) that denotes it is on the same network as mine (as well as the subnet mask). For most home and office setups the 1 in the last set of the series is the first and logical address to use as a gateway. Examples:

your address = 192.168.1.10 your default gateway = 192.168.1.1
your address = 192.168.0.10 your default gateway = 192.168.0.1

If you do not get a reply back from the gateway then the connection is broken between the computer and router/gateway. This could be a DHCP server malfunction, a MAC address filter on the router, or even a NIC malfunction(hardware or software). Now if you can ping your gateway fine then you at least have a local connection. Now ping the google server using this command:

Code:

ping www.google.com

Now if you cannot get a reply from google.com then there is something going on with one or more of the following settings: NAT, DNS server, firewall settings, MAC filter settings, or the internet could be down.

Now if you can ping google.com fine then you should have internet theoretically. The only things I can foresee causing any issues now are website filters on the router, possible DNS updates, or port issues.

 

Since it's an HP it's a broadcom card.

 

To see your network hardware, run this:

lshw -c net

install lshw if needed.