Well ... you don't tell us very much, and I have to read a bit between the
lines here. So since this is based partly on guesses about what lies behind
veils like "as I would expect them to look", I may be off base. With that
disclaimer ...
... the problem appears to be specific to the wireless link, and it clearly
involves the router itself (not simply the other network) reaching that
network. So focus on that part first ... why can't the router itself ping
the wireless client? Several things suggest themselves to check.
First, *how* does the ping fail? I'm guessing silently (that is, it just
sits there until you interrupt it, then is displays a message that says,
more or less, "X packets transmitted, 0 packets recrived"). If the ping
fails immediately, though, tell us the error message you get, as that is
VERY informative.
Second, after you try and fail to ping the wireless client from the router,
has the TX packet count on the wireless interface increased? The RX packet
count?
Third, after you try and fail to ping the wireless client, is there an
entry in the router's arp table for the relevant IP address ("cat
/proc/net/arp", I think)?
Fourth, fifth, and sixth, what are the corresponding results when you ping
the router from the wireless client?
Fourth, do any of the logs contain any relevant information? If so, and if
you cannot interpret it yourself, post the relevant entries verbatim, please.
In addition to answering the above information, next time please include
the standard disgnostics, to wit ...
output of "ip addr show"
output of "netstat -nr"
output of "ipchains -nvL"
output of "lsmod" (this is not on the standard list)
... as well as equivalent information for the wireless Windows client.
This so we can see if *we* think "everything looks ok". And please read the
document referenced at the bottom of every list message, the one labeled
SR-FAQ ... it should give you some additional, general help with sending
informative posts.
At 10:08 AM 6/3/02 +1000, Klint Gore wrote:
>I'm stumped. I can't ping over the wireless even though everything
>looks ok.
>
>I've got a bering setup (finally) with pcmcia wavelan cards to ethernet.
>I'm just doing plain routing so my shorewall is set to wide open (as far
>as I can tell it is). ethernet is 192.168.1.x, wireless is 10.1.1.x.
>bering is .254 on both subnets and is set as the default gateway on both
>workstations. iwconfig lists the device (eth1) though there are no db
>figures. ip route lists both subnets as I would expect them to be.
>
> >From ethernet workstation 192.168.1.2 (win98 desktop), I can ping
>192.168.1.254 and 10.1.1.254, but not 10.1.1.1.
>
> >From wirless workstation 10.1.1.1 (win95 notebook), I can't ping
>anything. wavelan test indicates that the connection is fine (50db+
>SNR).
>
> >From the router, I can't ping 10.1.1.1, I can ping 192.168.1.2.
>
>The lights on the wireless cards look as I would expect them to look
>(I've had the setup running between the 2 workstations directly).
>
>What do I look at now?
--
-----------------------------------------------"Never tell me the
odds!"--------------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------------------
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
