--- On Tue, 12/2/08, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote:
> From: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx>
> Subject: Re: ath5k: can't browse at all.
> To: "Irwan Siajadi" <dev.bahamot@xxxxxxxxx>
> Cc: "Luis Rodriguez" <Luis.Rodriguez@xxxxxxxxxxx>, "Pavel Roskin" <proski@xxxxxxx>, "linux-wireless@xxxxxxxxxxxxxxx" <linux-wireless@xxxxxxxxxxxxxxx>
> Date: Tuesday, December 2, 2008, 8:00 AM
> On Mon, Dec 1, 2008 at 11:27 PM, Irwan Siajadi
> <dev.bahamot@xxxxxxxxx> 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:
wireshark_netcat_rx_tx_redo
Description: Binary data
Attachment:
wireshark_smb
Description: Binary data
