All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Castelhano" <CastelhanoD@emigrant.com>
To: netfilter@lists.netfilter.org
Subject: weird mac address format
Date: Wed, 13 Jun 2007 14:11:58 -0400	[thread overview]
Message-ID: <466FFB2D.6422.0055.0@emigrant.com> (raw)

Hi,
 
Does anyone know why iptables would log a mac address in this fashion:
 
Jun 12 22:00:42 servername kernel: FW filter INPUT Chain:IN=ext OUT= MAC=02:00:00:00:00:09:00:06:2a:73:f0:70:08:00:45:00:00:28:94:7b:40:00:35:06:db:02:9c:37:85:
58:44:a3:70:1f:01:bb:da:e1:87:0f:30:c4:00:00:00:00:50:04:c2:10:83:0d:00:00:00:00:00:00:00:00:87:61:75:e8:92:64:cd:6e:f6:ce:91:bc:ed:ee:37:6e:b3:db:64:8b:18:59
 SRC=<some source ip> DST=<some destination ip> LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=38011 DF PROTO=TCP SPT=443 DPT=56033 WINDOW=49680 RES=0x00 RST URGP=0

Its been determined the mac= portion is a combined string for:
2:00:00:00:00:09:00:06:2a:73:f0:70: --> SMAC and DMAC address combined
08:00:  --> type IP
45:00:00:2c: --> IP v4 header, TOS and Length fields
a2:d7:00:00: --> ID, flags and frag offset
f2:06:50:c1: --> TTL, protocol (TCP) and checksum 
d0:4e:50:22:44:a3:70:1f: --> SrcIP and DstIP
00:50:e3:99: --> SrcPort (HTTP) and DestPort
 
We are running iptables 1.2.9. Only packets from the filter input chain get logged in this fashion and we don't know why. Such a long mac address makes it hard to analyze the logs and figure out what's going on. 
 
Why does the mac get logged this way? And is there anyway to prevent it from logging in this manner?

Thanks,
Dan

_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.



                 reply	other threads:[~2007-06-13 18:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=466FFB2D.6422.0055.0@emigrant.com \
    --to=castelhanod@emigrant.com \
    --cc=netfilter@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 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.