From: john connolly on
Hi,
I'm new to things wifi and am using a laptop
that has both windows7 and slack13 installed. In
several locations I find that windows7 will connect
to available (unsecured) sources but slack, using
wicd will not. Wicd finds the sources all right but
it times out when trying to connect. I have the feeling
that windows attempts to reconnect until it succeeds
but I don't know how to verify that.
I'm only interested to get slack13 to do the job
so if you have any suggestions I would appreciate
it.
jwc36
From: Sidney Lambe on
On alt.os.linux.slackware, john connolly <jwc1936(a)kc.rr.com>
wrote:

> Hi, I'm new to things wifi and am using a laptop that has both
> windows7 and slack13 installed. In several locations I find
> that windows7 will connect to available (unsecured) sources but
> slack, using wicd will not. Wicd finds the sources all right
> but it times out when trying to connect. I have the feeling
> that windows attempts to reconnect until it succeeds but I
> don't know how to verify that. I'm only interested to get
> slack13 to do the job so if you have any suggestions I would
> appreciate it. jwc36


Running a packet logger on the interface can be a big help in
situations like this. I prefer the console app tethereal,
which has a graphical version called ethereal, too.

You can watch the packets in real time or log them for
later examination.


Sid
From: john connolly on
Sidney Lambe wrote:
> On alt.os.linux.slackware, john connolly <jwc1936(a)kc.rr.com>
> wrote:
>
>> Hi, I'm new to things wifi and am using a laptop that has both
>> windows7 and slack13 installed. In several locations I find
>> that windows7 will connect to available (unsecured) sources but
>> slack, using wicd will not. Wicd finds the sources all right
>> but it times out when trying to connect. I have the feeling
>> that windows attempts to reconnect until it succeeds but I
>> don't know how to verify that. I'm only interested to get
>> slack13 to do the job so if you have any suggestions I would
>> appreciate it. jwc36
>
>
> Running a packet logger on the interface can be a big help in
> situations like this. I prefer the console app tethereal,
> which has a graphical version called ethereal, too.
>
> You can watch the packets in real time or log them for
> later examination.
>
>
> Sid
I used tcpdump to monitor the packets and I see
a bunch of ARP request who has ... messages
while I am connected and trying to access a url.
From: Sidney Lambe on
On alt.os.linux.slackware, john connolly <jwc1936(a)kc.rr.com> wrote:
> Sidney Lambe wrote:
>> On alt.os.linux.slackware, john connolly <jwc1936(a)kc.rr.com>
>> wrote:
>>
>>> Hi, I'm new to things wifi and am using a laptop that has both
>>> windows7 and slack13 installed. In several locations I find
>>> that windows7 will connect to available (unsecured) sources but
>>> slack, using wicd will not. Wicd finds the sources all right
>>> but it times out when trying to connect. I have the feeling
>>> that windows attempts to reconnect until it succeeds but I
>>> don't know how to verify that. I'm only interested to get
>>> slack13 to do the job so if you have any suggestions I would
>>> appreciate it. jwc36
>>
>>
>> Running a packet logger on the interface can be a big help in
>> situations like this. I prefer the console app tethereal,
>> which has a graphical version called ethereal, too.
>>
>> You can watch the packets in real time or log them for
>> later examination.
>>
>>
>> Sid
> I used tcpdump to monitor the packets and I see
> a bunch of ARP request who has ... messages
> while I am connected and trying to access a url.

Sounds right. Those are used on LANs of all kinds.

Sorry I don't know more about wifi. Try comp.os.linux.networking.


Sid