[SOLVED] Wireless gets IP, but cannot ping, wired works fine

analogrival · 11-02-2011, 07:23 PM

Greetings!

First time poster, and I've got a fun one

Currently using Arch Linux with my netbook set up as a test LAMP server.

Everything was working fine for a while, but apparently after a series of network changes and updates my connection crapped out.

I figured the easiest solution was to start "fresh".

I re-did all the wireless network configuration on my netbook, but it won't work.
Other wireless devices before a router change continued to work with no changes needed, used same SSID and password.

It gets an IP, get's a nameserver, I can even use "arp -n" and see a few machines on my network.
But that's it.

If I plug in a cable, and do "dhcpcd eth0" it springs to life and I connect just fine.

I'm no guru so I'll post whatever is asked, I checked for anything obvious (well, to me anyway) in /var/log/messages and saw nothing.

FWIW: using an Asus eeePC 1000H with a RALink 2860 wireless card

SecretCode · 11-09-2011, 06:39 AM

What do you get from route -n?

What do you get from nslookup www.linuxquestions.org? ... Although you are getting a nameserver, I suspect you are not actually getting names served.

All the above with the wifi on but without ethernet, obviously

analogrival · 11-09-2011, 08:01 AM

Quote:

Originally Posted by SecretCode

What do you get from route -n?

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    303    0        0 wlan0
10.8.0.0        10.8.0.2        255.255.255.0   UG    0      0        0 tun0
10.8.0.2        0.0.0.0         255.255.255.255 UH    0      0        0 tun0
192.168.1.0     0.0.0.0         255.255.255.0   U     303    0        0 wlan0

Quote:

Originally Posted by SecretCode

What do you get from nslookup www.linuxquestions.org? ... Although you are getting a nameserver, I suspect you are not actually getting names served.

Code:

;; connection timed out; no servers could be reached

Quote:

Originally Posted by SecretCode

All the above with the wifi on but without ethernet, obviously

I'm aware of the multiple routes, I'm running an OpenVPN server, which worked just fine until this happened.
Taking that into account, I've already tried troubleshooting with it disabled, and yet hardwired works fine with it on.

I'm also unable to ping 192.168.1.1 via wireless, but wired works fine.

SecretCode · 11-09-2011, 09:45 AM

Do you need a special driver for your RALink 2860 wireless card? In some notebook installs I've had to install first via ethernet, then get hold of proprietary drivers (or at least updated drivers) before the wireless works.

analogrival · 11-09-2011, 09:54 AM

Quote:

Originally Posted by SecretCode

Do you need a special driver for your RALink 2860 wireless card? In some notebook installs I've had to install first via ethernet, then get hold of proprietary drivers (or at least updated drivers) before the wireless works.

No, they were integrated into the kernel a while ago. I think during the 3.0 kernel release.

The staging drivers are pretty aged nowadays

SecretCode · 11-09-2011, 10:11 AM

Hmm

Code:

lspci | grep -i net

Code:

ifconfig -a

Code:

grep -i dhc /var/log/syslog

analogrival · 11-09-2011, 12:15 PM

[QUOTE=SecretCode;4519770]Hmm

Quote:

Originally Posted by SecretCode

Code:

lspci | grep -i net

Code:

01:00.0 Network controller: Ralink corp. RT2860
03:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)

Quote:

Originally Posted by SecretCode

Code:

ifconfig -a

Code:

eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500  metric 1
        ether 00:24:8c:10:cc:23  txqueuelen 1000  (Ethernet)
        RX packets 3203  bytes 4215143 (4.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1646  bytes 113819 (111.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 3  collisions 0
        device interrupt 43  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436  metric 1
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 44  bytes 2200 (2.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 44  bytes 2200 (2.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500  metric 1
        inet 10.8.0.1  netmask 255.255.255.255  destination 10.8.0.2
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet 192.168.1.251  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 00:22:43:60:ad:32  txqueuelen 1000  (Ethernet)
        RX packets 46985  bytes 6929718 (6.6 MiB)
        RX errors 0  dropped 19309  overruns 0  frame 0
        TX packets 542  bytes 72228 (70.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Quote:

Originally Posted by SecretCode

Code:

grep -i dhc /var/log/syslog

Returns nothing

SecretCode · 11-09-2011, 12:39 PM

Might be worth trying

Code:

dhclient -r

(may need root)

But the high number of RX dropped packets looks suspicious. I have 0 dropped on my wifi interface.

analogrival · 11-09-2011, 01:17 PM

Quote:

Originally Posted by SecretCode

Might be worth trying

Code:

dhclient -r

(may need root)

But the high number of RX dropped packets looks suspicious. I have 0 dropped on my wifi interface.

I'm using dhcpcd, dhclient isn't installed.

I noticed that too, about the packets.
Maybe a packet sniffer would be wise? Except I don't know how to read them.

SecretCode · 11-09-2011, 01:36 PM

Do you have any firewall rules? I don't know whether a packet dropped by an iptables rule would show as dropped in the interface stats.

analogrival · 11-09-2011, 01:37 PM

Quote:

Originally Posted by SecretCode

Do you have any firewall rules? I don't know whether a packet dropped by an iptables rule would show as dropped in the interface stats.

iptables isn't installed either

SecretCode · 11-09-2011, 01:52 PM

No further ideas at this point ... maybe someone else can suggest something?

analogrival · 11-09-2011, 02:16 PM

I greatly appreciate the troubleshooting help SecretCode.

I'm really trying to avoid re-installing my system since I spent so much time getting it set up just the way I like it.

repo · 11-09-2011, 02:23 PM

Some things to verify:
Try to use a fixes ip instead of dhcp.
Disable wep or wpa.
Verify the settings from the router (mac blocking,firewall....)
Try to use a live cd and see if wireless works.

Kind regards

analogrival · 11-09-2011, 09:12 PM

Meh, turns out the card is shot.

Explains all the dropped packets.

Oh well, have an external adapter I can use for now til I can get a new internal card.

Thank you all for the help, I learned a lot from this experience!