From: nick@nhthomas.freeserve.co.uk
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath6kl_usb - ping problems when compiled for sh4.
Date: Thu, 21 Mar 2013 15:09:46 +0100 (CET) [thread overview]
Message-ID: <17341425.1561363874986481.JavaMail.www@wwinf3717> (raw)
In-Reply-To: <3255301.1161363872896882.JavaMail.www@wwinf3715>
Hi Mohammed,
I've added some debug at the top of ath6kl_wmi_dix_2_dot3 function.
Just after:
eth_hdr = (struct ethhdr *) skb->data;
type = eth_hdr->h_proto;
I added some debug to print all the values of eth_hdr->h_dest and eth_hdr->h_source .
And, all look correct at that point.
Regards
Nick
> Message Received: Mar 21 2013, 01:35 PM
> From: nick@nhthomas.freeserve.co.uk
> To: "Mohammed Shafi"
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: ath6kl_usb - ping problems when compiled for sh4.
>
> Hi Mohammed,
>
> What do you need to me to do on this?
> I see that function in the wmi.c file.
>
> Do you want me to add some debug printk's in there somewhere?
>
> Regards
>
> Nick
>
> > Message Received: Mar 21 2013, 11:42 AM
> > From: "Mohammed Shafi"
> > To: nick@nhthomas.freeserve.co.uk
> > Cc: linux-wireless@vger.kernel.org
> > Subject: Re: ath6kl_usb - ping problems when compiled for sh4.
> >
> > On Wed, Mar 20, 2013 at 10:33 PM, wrote:
> > >
> > > Here is another example, taken from Wireshark.
> > > It's an ARP response, effectively saying IP address 192.168.0.107 is at 00:03:7f:20:50:59
> > >
> > > This is a message coming out of the wifi adaptor, and the above numbers are the IP address, and MAC address of the wifi device.
> > >
> > > 7f 20 50 59 00 24 00 03 7f 20 50 59 08 06 00 01
> > > 08 00 06 04 00 02 00 03 7f 20 50 59 c0 a8 00 07
> > > 20 cf 30 94 83 7b c0 a8 00 65
> > >
> > > What we see here is the Destination MAC address is 7f:20:50:59:00:24 (first 6 bytes).
> > > But that's wrong. It should be 20:cf:30:94:83:7b .
> > >
> > > The other parts look right though:
> > > 00:03:7f:20:50:59 is the MAC of the wifi device.
> > > c0 a8 00 65 is 192.168.0.101 which is the IP address of the destination.
> > > c0 a8 00 07 is the IP address of the wifi adaptor itself.
> >
> > let us check in ath6kl_wmi_dix_2_dot3, that should give us some clue.
> >
> > >
> > > So, where in the code is the first 6 bytes generated ?
> > >
> > >
> > > Regards
> > >
> > > Nick
> >
> >
> >
> > --
> > thanks,
> > shafi
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-21 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 15:22 ath6kl_usb - ping problems when compiled for sh4 nick
2013-03-20 15:34 ` Mohammed Shafi
2013-03-20 16:06 ` nick
2013-03-20 17:03 ` nick
2013-03-21 11:41 ` Mohammed Shafi
2013-03-21 13:34 ` nick
2013-03-21 14:09 ` nick [this message]
2013-03-21 14:25 ` nick
2013-03-22 5:28 ` Mohammed Shafi
2013-03-22 7:10 ` nick
2013-03-22 7:15 ` nick
2013-04-15 10:20 ` nick
2013-04-19 16:02 ` nick
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=17341425.1561363874986481.JavaMail.www@wwinf3717 \
--to=nick@nhthomas.freeserve.co.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.com \
/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).