wireless ping WRT54G under XP, not Linux

As the title says...

I have a Windows XP Home SP2 laptop that works wirelessly, perfectly, with a
Linksys WRT54G - I can ping the router on 192.168.1.1,access the router's
config pages, and ping other PCs on the network: both wired and wirelessly.

Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only do
the above when wired to the router.

Any ideas?

__spc__ wrote:
> As the title says...
>
> I have a Windows XP Home SP2 laptop that works wirelessly, perfectly, with a
> Linksys WRT54G - I can ping the router on 192.168.1.1,access the router's
> config pages, and ping other PCs on the network: both wired and wirelessly.
>
> Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only do
> the above when wired to the router.
>
> Any ideas?
>
>
Hi,
If your wireless card is not Linux friendly, it's different story.
Is your card properly configured with Linux? Google for what you need.

Tony Hwang wrote:
> __spc__ wrote:
>> As the title says...
>>
>> I have a Windows XP Home SP2 laptop that works wirelessly, perfectly,
>> with a Linksys WRT54G - I can ping the router on 192.168.1.1,access
>> the router's config pages, and ping other PCs on the network: both
>> wired and wirelessly.
>>
>> Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only
>> do the above when wired to the router.
>>
>> Any ideas?
>>
> Hi,
> If your wireless card is not Linux friendly, it's different story.
> Is your card properly configured with Linux? Google for what you need.
SOunds like the lap top wireless nic is not working under nix , what chp
set is it ?

__spc__ wrote:

> As the title says...
>
> I have a Windows XP Home SP2 laptop that works wirelessly, perfectly, with
> a Linksys WRT54G - I can ping the router on 192.168.1.1,access the
> router's config pages, and ping other PCs on the network: both wired and
> wirelessly.
>
> Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only do
> the above when wired to the router.

Odd that you told us what OSes, and what hardware you're connecting _to_ but
didn't tell us what hardware you're trying to connect _with_, which is the
really important bit. Only a few wireless NICs have native linux drivers.
If yours doesn't, you can try ndiswrapper, but there's no guarantees.

Rule #1, when buying hardware for a linux system: make sure that everything
you intend to use is supported _first_.
--
derek

[snip]

>> I have a Windows XP Home SP2 laptop that works wirelessly, perfectly,
>> with
>> a Linksys WRT54G - I can ping the router on 192.168.1.1,access the
>> router's config pages, and ping other PCs on the network: both wired and
>> wirelessly.
>>
>> Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only do
>> the above when wired to the router.
>
> Odd that you told us what OSes, and what hardware you're connecting _to_
> but
> didn't tell us what hardware you're trying to connect _with_, which is the
> really important bit. Only a few wireless NICs have native linux drivers.
> If yours doesn't, you can try ndiswrapper, but there's no guarantees.

[snip]

Sorry all.

I have my wireless NICs working perfectly fine under Linux for my laptop
(onboard BroadCom chipset) and my desktop (a generic 54Mbps PCI card,
Marvell chipset) - both machines using NDISwrapper.

So, what might be stopping my laptop (and dedesktop) from pinging the
router, and each other?

"__spc__" <s p a m t i m e @ n t l w o r l d . c o m> wrote in message
news:KXrTf.6683$(E-Mail Removed)...
> As the title says...
>
> I have a Windows XP Home SP2 laptop that works wirelessly, perfectly, with
> a Linksys WRT54G - I can ping the router on 192.168.1.1,access the
> router's config pages, and ping other PCs on the network: both wired and
> wirelessly.
>
> Under Linux Slackware 10.2, kernel 2.6.15.6, the same machine can only do
> the above when wired to the router.
>
> Any ideas?

Something to do with the route command showing two default interfaces -
localnet * 255.255.255.0 U 0 0 0 eth0
localnet * 255.255.255.0 U 0 0 0 eth1
localnet * 255.255.255.0 U 0 0 0 wlan0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 1 0 0 eth0

And here is the ping error:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.106 icmp_seq=1 Destination Host Unreachable
From 192.168.1.106 icmp_seq=2 Destination Host Unreachable
From 192.168.1.106 icmp_seq=3 Destination Host Unreachable
From 192.168.1.106 icmp_seq=5 Destination Host Unreachable
From 192.168.1.106 icmp_seq=6 Destination Host Unreachable
From 192.168.1.106 icmp_seq=7 Destination Host Unreachable

..102 is the address of wlan0, the WiFi NIC, while .106 is the address of
eth0, my first ethernet NIC.

Even though I am connected via .102, Linux is adopting .106 as the default
route for ping.

Any ideas how to change this?