cannot ping WLan access point

Hello, All,

I cannot ping my access point, although my laptop can see the AP MAC
address:

eth1 IEEE 802.11b/g ESSID:"VibrostopWLan" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point:
00:0D:54:A0:1C:4A
Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Link Quality:187/0 Signal level:-40 dBm Noise level:-226
dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Am I missing something?

Cryptography is WPA,and the passwordphrase was entered in the YaST
setup dialog.

Thanks for your time!
-Gian

On 3 Mar 2005 23:46:20 -0800, Gian <(E-Mail Removed)> wrote:
> Hello, All,
>
> I cannot ping my access point, although my laptop can see the AP MAC
> address:
>
> eth1 IEEE 802.11b/g ESSID:"VibrostopWLan" Nickname:"linux"
> Mode:Managed Frequency:2.462 GHz Access Point:
> 00:0D:54:A0:1C:4A
> Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
> Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
> Link Quality:187/0 Signal level:-40 dBm Noise level:-226
> dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Am I missing something?
>
> Cryptography is WPA,and the passwordphrase was entered in the YaST
> setup dialog.

What was the error message?
Without output of ifconfig and route -n, and IP of AP we do not even know
if you have an IP or route to AP.

David,

thank for your kind reply.

My WLan card is set with 192.168.1.121, while the AP is 192.168.1.250.

gian@linux:~> /usr/sbin/iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"VibrostopWLan" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point:
00:0D:54:A0:1C:4A
Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Link Quality:185/0 Signal level:-41 dBm Noise level:-237
dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


linux:/home/gian # /sbin/ifconfig
eth1 Link encap:Ethernet HWaddr 00:0D:54:9D:07:A6
inet addr:192.168.1.121 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::20d:54ff:fe9d:7a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3408 (3.3 Kb) TX bytes:1000 (1000.0 b)
Interrupt:10

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:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)

linux:/home/gian # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0
eth1

gian@linux:~> ping 192.168.1.250
PING 192.168.1.250 (192.168.1.250) 56(84) bytes of data.
>From 192.168.1.121: icmp_seq=2 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=3 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=4 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=6 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=7 Destination Host Unreachable
>From 192.168.1.121 icmp_seq=8 Destination Host Unreachable

--- 192.168.1.250 ping statistics ---
9 packets transmitted, 0 received, +7 errors, 100% packet loss, time
8003ms, pipe 3

On 4 Mar 2005 01:29:00 -0800, Gian <(E-Mail Removed)> wrote:
> David,
>
> thank for your kind reply.
>
> My WLan card is set with 192.168.1.121, while the AP is 192.168.1.250.
>
> gian@linux:~> /usr/sbin/iwconfig eth1
> eth1 IEEE 802.11b/g ESSID:"VibrostopWLan" Nickname:"linux"
> Mode:Managed Frequency:2.462 GHz Access Point:
> 00:0D:54:A0:1C:4A
> Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
> Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
> Link Quality:185/0 Signal level:-41 dBm Noise level:-237
> dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> linux:/home/gian # /sbin/ifconfig
> eth1 Link encap:Ethernet HWaddr 00:0D:54:9D:07:A6
> inet addr:192.168.1.121 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::20d:54ff:fe9d:7a6/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3408 (3.3 Kb) TX bytes:1000 (1000.0 b)
> Interrupt:10
>
> 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:40 errors:0 dropped:0 overruns:0 frame:0
> TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
>
> linux:/home/gian # /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth1
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> lo
> 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0
> eth1
>
> gian@linux:~> ping 192.168.1.250
> PING 192.168.1.250 (192.168.1.250) 56(84) bytes of data.
>>From 192.168.1.121: icmp_seq=2 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=2 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=3 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=4 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=6 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=7 Destination Host Unreachable
>>From 192.168.1.121 icmp_seq=8 Destination Host Unreachable
>
> --- 192.168.1.250 ping statistics ---
> 9 packets transmitted, 0 received, +7 errors, 100% packet loss, time
> 8003ms, pipe 3

Everything there appears to be in order (assuming you have no other
conflicting interface like eth0), iwconfig shows no crypt errors, ifconfig
shows TX & RX packets with no errors. I am not familiar with kernel
wireless support (I use wlan-ng for wlan0 interface with WEP).

Maybe a firewall (known or unknown) is blocking ping. Can you access web
interface of AP? Can you ping your default gw (192.168.1.254)? Does
/sbin/arp -a show anything for AP or gw IP after ping?

See if following from another terminal gives any clue (0 is zero):
tcpdump -i eth1 -n -s 0

David Efflandt wrote:
> On 4 Mar 2005 01:29:00 -0800, Gian <(E-Mail Removed)> wrote:
> > David,
> >
> > thank for your kind reply.
> >
> > My WLan card is set with 192.168.1.121, while the AP is
192.168.1.250.
> >
> > gian@linux:~> /usr/sbin/iwconfig eth1
> > eth1 IEEE 802.11b/g ESSID:"VibrostopWLan" Nickname:"linux"
> > Mode:Managed Frequency:2.462 GHz Access Point:
> > 00:0D:54:A0:1C:4A
> > Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
> > Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
> > Link Quality:185/0 Signal level:-41 dBm Noise
level:-237
> > dBm
> > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> >
> >
> > linux:/home/gian # /sbin/ifconfig
> > eth1 Link encap:Ethernet HWaddr 00:0D:54:9D:07:A6
> > inet addr:192.168.1.121 Bcast:192.168.1.255
> > Mask:255.255.255.0
> > inet6 addr: fe80::20d:54ff:fe9d:7a6/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:24 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:3408 (3.3 Kb) TX bytes:1000 (1000.0 b)
> > Interrupt:10
> >
> > 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:40 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)
> >
> > linux:/home/gian # /sbin/route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
Use
> > Iface
> > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0
0
> > eth1
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0
> > eth1
> > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0
> > lo
> > 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0
0
> > eth1
> >
> > gian@linux:~> ping 192.168.1.250
> > PING 192.168.1.250 (192.168.1.250) 56(84) bytes of data.
> >>From 192.168.1.121: icmp_seq=2 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=2 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=3 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=4 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=6 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=7 Destination Host Unreachable
> >>From 192.168.1.121 icmp_seq=8 Destination Host Unreachable
> >
> > --- 192.168.1.250 ping statistics ---
> > 9 packets transmitted, 0 received, +7 errors, 100% packet loss,
time
> > 8003ms, pipe 3
>
> Everything there appears to be in order (assuming you have no other
> conflicting interface like eth0), iwconfig shows no crypt errors,
ifconfig
> shows TX & RX packets with no errors. I am not familiar with kernel
> wireless support (I use wlan-ng for wlan0 interface with WEP).
>
> Maybe a firewall (known or unknown) is blocking ping. Can you access
web
> interface of AP? Can you ping your default gw (192.168.1.254)?

I can ping my gateway(same as dns server)


Does
> /sbin/arp -a show anything for AP or gw IP after ping?

but my cygwin did not recognize /sbin/arp -a
>
> See if following from another terminal gives any clue (0 is zero):
> tcpdump -i eth1 -n -s 0

cygwin also did not have tcpdump
at its experiment

how to make it route info from outside to me?

(E-Mail Removed) (David Efflandt) wrote in message news:<(E-Mail Removed)>...

> Everything there appears to be in order (assuming you have no other
> conflicting interface like eth0), iwconfig shows no crypt errors, ifconfig
> shows TX & RX packets with no errors. I am not familiar with kernel
> wireless support (I use wlan-ng for wlan0 interface with WEP).
>
> Maybe a firewall (known or unknown) is blocking ping. Can you access web
> interface of AP? Can you ping your default gw (192.168.1.254)? Does
> /sbin/arp -a show anything for AP or gw IP after ping?
>
> See if following from another terminal gives any clue (0 is zero):
> tcpdump -i eth1 -n -s 0

no, I cannot access the web interface of AP, and neither can ping GW.
I suspect WPA is not supported for my Prism54 card, a 3Com 3CRWE154G72
v.1.0. since iwconfig returns Encryption=off although I entered the
PSK in the YaST dialog.

I will search if someone has a working Prism54 WPA setup.
Thanks for your kind help,
ciao,
-Gian