From: Alexandre Becholey <alexandre@shockfish.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [rt73usb] Master Mode almost done; problem with ARP
Date: Fri, 08 May 2009 16:17:00 +0200 [thread overview]
Message-ID: <4A043EDC.4000307@shockfish.com> (raw)
In-Reply-To: <1241774214.1567.34.camel@johannes.local>
Johannes Berg wrote:
> On Fri, 2009-05-08 at 11:08 +0200, Alexandre Becholey wrote:
>
>
>> And what I can't do:
>> - Computers on the LAN can't ping the stations (Destination Host
>> Unreachable)
>> - AP can't ping the stations
>>
>> I ran wireshark on a computer on the LAN, on the AP (here I used tcpdump
>> on all interfaces because I don't have the possibility to have X) and on
>> a stations. I would say that's a problem with ARP packets.
>>
>
> Here's a similar bug -- the debugging I did there you should do here.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=13237
>
> johannes
>
I said something wrong: from any stations, I can't ssh the AP (it works
only if from the station pings the AP during the ssh). I made a few
other observations:
I start a ping from a LAN computer to a futur associated station (all IP
are fix). When the station finished the association, the ping works for
20 sec (it seems to correspond to the time an entry stays in the ARP
table) and then Destination Host Unreachable.
As soon as I start a ping from the station to the LAN computer, the LAN
computer's ping receive the responses, but when I stop the ping from the
station, the LAN computer's ping don't receive the respond any more even
if I stop it before 20sec are elapsed... I think it's more than just a
problem with the ARP table.
I looked at the patch given in the bug you gave me, the ralink driver
seems do the things correctly.
Alexandre
prev parent reply other threads:[~2009-05-08 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 9:08 [rt73usb] Master Mode almost done; problem with ARP Alexandre Becholey
2009-05-08 9:16 ` Johannes Berg
2009-05-08 14:17 ` Alexandre Becholey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A043EDC.4000307@shockfish.com \
--to=alexandre@shockfish.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).