netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Fisher <brad@info-link.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Kevin Spiteri <kspiteri@hobsoft.com.mt>
Subject: Re: libnetfilter_queue man page
Date: Wed, 08 Feb 2006 12:18:38 -0600	[thread overview]
Message-ID: <43EA35FE.6000000@info-link.net> (raw)
In-Reply-To: <43EA2683.3030606@info-link.net>

Brad Fisher wrote:
> One small thing I should mention - possibly a bug:  I tried playing 
> around with nfq_get_packet_hw() yesterday and the hw_addrlen returned 
> seemed to be much too large...  For an ethernet packet I'd expect it 
> to be 6 (ethernet MAC address is 6 octets), but it was something like 
> 1520 or so.  Needless to say, much larger than expected.  Perhaps I'm 
> interpreting it wrong.  I haven't had a chance to look too deeply into 
> it yet.
I've determined that this is not a bug.  The hw address length is 
returned in network byte order, and thus the confusion.  The value of 
1536 I was seeing on an Athlon system is actually 6 in network order.  A 
simple ntohs() fixed it.  Sorry if this confused anyone...  Sure 
confused me for a bit :)

-Brad

  reply	other threads:[~2006-02-08 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1139235549.30902.3.camel@localhost.localdomain>
2006-02-08 14:19 ` libnetfilter_queue man page Harald Welte
2006-02-08 17:12   ` Brad Fisher
2006-02-08 18:18     ` Brad Fisher [this message]
2006-02-21 17:03     ` Gregor Maier
2006-02-21 18:10       ` Brad Fisher
2007-02-27  8:05 Julien DHERSIN
2007-02-28 12:43 ` Pablo Neira Ayuso
2007-03-02 13:15   ` Julien DHERSIN
  -- strict thread matches above, loose matches on Subject: below --
2007-03-01 21:00 Jay Manni

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=43EA35FE.6000000@info-link.net \
    --to=brad@info-link.net \
    --cc=kspiteri@hobsoft.com.mt \
    --cc=netfilter-devel@lists.netfilter.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).