From: Irwan Siajadi <dev.bahamot@yahoo.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Pavel Roskin <proski@gnu.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath5k: can't browse at all.
Date: Tue, 2 Dec 2008 05:04:55 -0800 (PST) [thread overview]
Message-ID: <252364.38659.qm@web59613.mail.ac4.yahoo.com> (raw)
In-Reply-To: <43e72e890812020000h4fc52fb5u19f4ebcae847cdaf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
--- On Tue, 12/2/08, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: ath5k: can't browse at all.
> To: "Irwan Siajadi" <dev.bahamot@yahoo.com>
> Cc: "Luis Rodriguez" <Luis.Rodriguez@atheros.com>, "Pavel Roskin" <proski@gnu.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
> Date: Tuesday, December 2, 2008, 8:00 AM
> On Mon, Dec 1, 2008 at 11:27 PM, Irwan Siajadi
> <dev.bahamot@yahoo.com> wrote:
>
> > PS: the attachment is without hexdump packet data,
> please let me know if
> > you require the one with hexdump packet data.
>
> Raw tcpdump data is preferred (so I can parse it myself).
I didn't save the raw log, but I redid the test and saved the raw log.
It's not exactly the same one as this time I send/recieve "netcat: testing
ath5k" while previously I sent a source code from Intel2200BG to ath5k.
Note that I also added raw log while trying to browse/discover the ath5k
from intel2200BG using SMB.
Oh yes, I tried netcat with port 80 and it behaved exactly the same as port 3333.
>
> Luis
[-- Attachment #2: wireshark_netcat_rx_tx_redo --]
[-- Type: application/octet-stream, Size: 7022 bytes --]
[-- Attachment #3: wireshark_smb --]
[-- Type: application/octet-stream, Size: 11881 bytes --]
next prev parent reply other threads:[~2008-12-02 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 3:11 ath5k: can't browse at all Irwan Siajadi
2008-12-01 21:36 ` Luis R. Rodriguez
2008-12-02 7:27 ` Irwan Siajadi
2008-12-02 8:00 ` Luis R. Rodriguez
2008-12-02 13:04 ` Irwan Siajadi [this message]
2008-12-07 19:39 ` Irwan Siajadi
-- strict thread matches above, loose matches on Subject: below --
2008-11-24 17:41 Irwan Siajadi
2008-11-24 18:53 ` Pavel Roskin
2008-11-25 2:36 ` Irwan Siajadi
2008-11-25 17:24 ` Irwan Siajadi
2008-11-25 20:02 ` Pavel Roskin
2008-11-30 16:53 ` Irwan Siajadi
2008-12-01 17:11 ` Luis R. Rodriguez
2008-11-24 18:54 ` Dan Williams
2008-11-25 2:30 ` Irwan Siajadi
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=252364.38659.qm@web59613.mail.ac4.yahoo.com \
--to=dev.bahamot@yahoo.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.