All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Eliot, Wireless and Server Administrator,
	Great Lakes Internet" <support8@greatlakes.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: POSTROUTING hooks
Date: Thu, 08 Jun 2006 09:43:50 +0200	[thread overview]
Message-ID: <4487D536.1050702@trash.net> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25544B@xavier.staff.greatlakes.net>

Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
> Where in the kernel's packet delivery process does the POSTROUTING chain
> hook in? 
> 
> I'm trying to figure out how to write a module to allow matching on the
> destination MAC address. From what I have been able to figure out so
> far, it looks like the destination MAC is not actually set until right
> before the packet goes out of the interface. Now, I have not been able
> to find the code that would confirm this, so if anyone can point me to
> the exact position where the destination MAC address is set, that would
> be helpful. However, from what I have been able to observe with logging
> and some quick and dirty modifications to a couple of modules to print
> out some extra debugging info, this appears to be the case. 
> 
> What would it take to modify the Netfilter code to make the POSTROUTING
> chain hook in AFTER the destination MAC is set, but BEFORE it gets sent
> out the interface? 

Still doesn't help, ARP resolution happens after that.

  parent reply	other threads:[~2006-06-08  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 14:21 POSTROUTING hooks Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-05 16:01 ` Patrick Schaaf
2006-06-08  7:43 ` Patrick McHardy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-05 16:46 Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-05 17:25 ` Patrick Schaaf
2006-06-05 17:32 Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-06  6:37 ` Patrick Schaaf
2006-06-06  7:21   ` Philip Craig

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=4487D536.1050702@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=support8@greatlakes.net \
    /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.