All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jørn Andre" <jornandr@stud.ntnu.no>
To: netfilter-devel@lists.netfilter.org
Subject: Olsr and Netfilter
Date: Mon, 14 Mar 2005 21:57:54 +0100	[thread overview]
Message-ID: <4235FAD2.9090009@stud.ntnu.no> (raw)

Hi!

I'm a newbie on kernel programming and on NETFILTER and in the middle of
making a netfilter-hook into PREROUTING and INPUT that simply changes 
the destination
of a packet. From the source-code I've read from Rusty Russel
and Harald Welte guide I can not see any difficulties with doing this, 
but in case
I'm wrong and before I try to break my kernel open....is it not 
possibly  to hook
in and change the destination of a packet  and then push it on without 
further notice?

I'm making a plugin for the Unik Olsrd implementation which is supposed 
to eliminate
the gateway-problem it has. By changing the destination in INPUT  at the 
source-host and then
change it back to the original in PREROUTING at the gateway I can 
preserve the route
and avoid a reset when the protocol changes default gateway because of 
topology changes.

Jørn Andre

                 reply	other threads:[~2005-03-14 20:57 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=4235FAD2.9090009@stud.ntnu.no \
    --to=jornandr@stud.ntnu.no \
    --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 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.