All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter@lists.netfilter.org
Subject: Re: Logging source mac address
Date: Mon, 04 Oct 2004 10:16:01 -0500	[thread overview]
Message-ID: <41616931.7060207@pbl.ca> (raw)
In-Reply-To: <1096812880.4477.1.camel@porky>

Eric Leblond wrote:
> To log source address you need to able to know it. This is not the case
> if you are not directly connected to computer that drop via ethernet.
> Thus this is the case for almost all internet IPs....

Logging the MAC address of the router can also be usefull.  For example, 
if there are two routers on the network (each connected to different 
ISP), it would show from which router packets are arriving (usefull for 
debugging).  It could also show if a station on the local network is 
trying to inject packets into an existing connection (OK, this is really 
a task for IDS tool, but anyhow).

With that in mind, I'd say that logging MAC address for all packtes has 
a value (as long as user is aware of couple of basic principles of 
networking).

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


  reply	other threads:[~2004-10-04 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <415D19210004E96A@vsmtp1.tin.it>
2004-10-03 14:14 ` Logging source mac address Eric Leblond
2004-10-04 15:16   ` Aleksandar Milivojevic [this message]
     [not found] <414B19D30064B70D@vsmtp12.tin.it>
2004-10-03  5:26 ` Alistair Tonner
2004-10-02 21:24 mlist
  -- strict thread matches above, loose matches on Subject: below --
2004-10-01 21:45 Marco Reale

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=41616931.7060207@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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.