From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ipt_LOG: MAC address output
Date: Fri, 7 May 2010 10:02:49 +0200 [thread overview]
Message-ID: <201005071002.49899.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1005031741100.938@obet.zrqbmnf.qr>
On Monday, 3. May 2010 17:41:47 Jan Engelhardt wrote:
> >The MAC address really looks strange if you take
> >the original data into consideration:
> >
> >
> >- Output "08:00" garbage at the end.
>
> No garbage.
>
> It's not the MAC address, it's the (entire) MAC header that's printed.
Thanks, Jan. So would it make sense to output a human readable
MACSRC= and MACDST=? We also don't print the raw IP header...
Cheers,
Thomas
next prev parent reply other threads:[~2010-05-07 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 13:58 ipt_LOG: MAC address output Thomas Jarosch
2010-05-03 15:41 ` Jan Engelhardt
2010-05-07 8:02 ` Thomas Jarosch [this message]
2010-05-07 9:31 ` Jan Engelhardt
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=201005071002.49899.thomas.jarosch@intra2net.com \
--to=thomas.jarosch@intra2net.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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).