[driverloader] Can reach WAP but no further . . . arrr

[Mike Reith]

Hi, and thank you,

I am new to Linux. Could you, (or someone else on the list) be so kind as to
tell me how to verify that my adapter is or is not associated with my AP. I
would also appreciate any clues as to how I might go about fixing that
through config files, etc. I realize that this may be more of a networking
than a driver issue and I greatly appreciate any help that can be provided.
----- Original Message -----
From: "Linuxant support" <support at linuxant.com>
To: "Mike Reith" <reith at bigfoot.com>
Cc: "support" <support at linuxant.com>
Sent: Friday, November 28, 2003 10:26 AM
Subject: Re: [driverloader] Can reach WAP but no further . . . arrr


Hi,

I noticed in the last "dumpdiag" that you sent that your adapter was not
associated with your AP. Make sure you verify that first.

Regards,

Jean-Simon Durand
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


On Friday 28 November 2003 12:57, you wrote:
> Hi, Jean-Simon,
>
> Thank you for your quick reply. I can understand that it would appear to
be
> a network configuration problem and not one with Driverloader. What
> perplexes me is that I was able to get version 1.35 to work flawlessly. I
> have tried a clean install and 1.35 again, and I cannot reach the
internet.
> It is also strange that the Windows wireless machine has no problem, with
> precisely the same network setup as the Linux machine. I did recall that
> when I first installed SuSE, and before I installed ver 1.35, I did an
> online update of SuSE. Two files were upgraded, and I cannot recall which.
> Now there are 9 or more on the online update feature and I cannot
> distinguish which were the frist 2, so I cannot replicate the exact
> conditions of ver 1.35 install. I will try what you suggest, and try the
> board as well. Thank you, as always.
>
>
> ----- Original Message -----
> From: "Linuxant support" <support at linuxant.com>
> To: "Mike Reith" <reith at bigfoot.com>
> Cc: "support" <support at linuxant.com>
> Sent: Friday, November 28, 2003 8:28 AM
> Subject: Re: [driverloader] Can reach WAP but no further . . . arrr
>
>
> Hi,
>
> we can't give much support for the network configuration, but I suggest
> that you verify your default gateway with the "ip route" command. If you
> use DHCP,
> then the default gateway is assigned by the DHCP server at the same time
as
> the IP address. You should then verify the DHCP server's configuration on
> your AP.
>
> Also make sure that the NAT options are setup properly on your AP. If you
> still need help, you might ask on the mailing list or consult your AP's
> documentation.
>
> Regards,
>
> Jean-Simon Durand
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
>
> On Thursday 27 November 2003 20:53, you wrote:
> > Thank you for your kind and prompt reply.
> >
> > Since your reply, I followed your advice:
> >
> > I installed the latest version of Driverloader (1.48)
> > I installed the latest drivers from Linksys (ver. 3.30)
> > I set the ESSID to "linksys"
> > I flashed the AP's latest firmware.
> > I resolved the problem of not reaching other computers on the
> > network---they were running WinXP's
> >     firewall. I can now reach other computers, can ping myself, the WAP,
> > and all other PC's including other
> >     wireless computers using my router.I still cannot reach the internet
> > however. If I attempt to ping a
> >     known site (e.g., www.msn.com at 207.68.171.245) there is an
> > instantaneous response of
> >    "network is unreachable".
> > If I attempt to browse to a web site, I receive an instantaneous
response
> > of "an error occured while loading www.msn.com   unknown host".
> > This very same notebook has no difficulty with the same network using
> > WinXP, so I must be missing something in the configuration within Linux.
> >
> > I did another dldrconfig --dump and have included the output below, if
it
> > will help you.
> > What should I try next?
> > Thank you for helping,
> > Mike Reith