Arch Linux

dextro_

Member

Registered: 2009-09-07

Posts: 24

Wireless problems

Here it is step by step

I threw a couple new WiFi cards in my Arch box
I installed wireless tools via `pacman -S wireless_tools`
I ran `iwconfig wlan0 essid "MyEssid" key 1234567890 && dhcpcp wlan0` and obtained an IP. (http://wiki.archlinux.org/index.php/Wireless_Setup)
The Internet didn't work so I ran `ping 192.168.1.254 -I wlan0` and it just hangs on "PING 192.168.1.254 (192.168.1.254) from 192.168.1.70 wlan0: 56(84) bytes of data." indefinitely.
I can't even ping the AP I just got an IP from! wtf?!

Any ideas what is going on? I can ping the AP from other devices that I have on it, and the Internet works fine on them also.

I should probably note I did all of the above on wlan1 with a different (also working) AP and got same results.

Also wlan0 and wlan1 are different cards/drivers.

01:06.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
        Subsystem: Atheros Communications Inc. TRENDnet TEW-443PI Wireless PCI Adapter
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at df000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
        Kernel driver in use: ath5k
        Kernel modules: ath5k

01:07.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
        Subsystem: Linksys WMP54G 2.0 PCI Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at df010000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: rt2500pci
        Kernel modules: rt2500pci

Summary:

[root@gw ~]# dhcpcd wlan0
dhcpcd: version 5.0.6 starting
dhcpcd: wlan0: rebinding lease of 192.168.1.70
dhcpcd: wlan0: acknowledged 192.168.1.70 from 192.168.1.254
dhcpcd: wlan0: checking for 192.168.1.70
dhcpcd: wlan0: leased 192.168.1.70 for 86400 seconds
dhcpcd: forking to background
[root@gw ~]# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:16:B6:56:6B:38
          inet addr:192.168.1.70  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::216:b6ff:fe56:6b38/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69619 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9978 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3729642 (3.5 Mb)  TX bytes:664118 (648.5 Kb)

[root@gw ~]# iwconfig wlan0
wlan0     IEEE 802.11bg  ESSID:"2WIRE764"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:18:3F:55:2F:89
          Bit Rate=54 Mb/s   Tx-Power=26 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Encryption key:4549-9763-0895-8146-8568-4430-99   Security mode:open
          Power Management:off
          Link Quality=41/70  Signal level=-69 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[root@gw ~]# ping 192.168.1.254 -I wlan0
PING 192.168.1.254 (192.168.1.254) from 192.168.1.70 wlan0: 56(84) bytes of data.
**** Hangs here until I ^c ***

EDIT:

After a little chat in #archlinux on freenode I tried a few things, like taking eth0 and wlan1 down via `dhcpcd -k $IF && ifconfig $IF down` then the only default route was wlan0, still could not even ping AP just be be sure I was pining the AP with a laptop and it was working fine.

I am going to take the cards out and try them in a Kubuntu machine I am building to test run the Ubuntu's as I have never used any of them. I still have to download the Kubuntu iso and install it so that may be a while, if I even do it before bed.

Last edited by dextro_ (2009-09-08 08:44:08)

dextro_

Member

Registered: 2009-09-07

Posts: 24

Re: Wireless problems

Nothing?

dextro_

Member

Registered: 2009-09-07

Posts: 24

Re: Wireless problems

No one? :'(

Dogs1985

Member

Registered: 2008-03-01

Posts: 201

Re: Wireless problems

i remember if wifi access point is using wpa password, need wpa_supplicant to connect. are you using wep password in your access point?

dextro_

Member

Registered: 2009-09-07

Posts: 24

Re: Wireless problems

WEP, correct.

Boris Bolgradov

Member

From: Bulgaria

Registered: 2008-07-27

Posts: 185

Re: Wireless problems

Could the routers be blocking the ping requests? Can you ping an internet server like google.com?

edit: oops, I didn't read your post to the end... sorry

I was pining the AP with a laptop and it was working fine

Last edited by Boris Bolgradov (2009-09-12 17:57:14)