All of lore.kernel.org
 help / color / mirror / Atom feed
From: JC <bikkit@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Questions regarding routing in the stack
Date: Thu, 21 Jul 2005 07:30:48 -0700	[thread overview]
Message-ID: <a60102c3050721073024051dd2@mail.gmail.com> (raw)

I was hoping someone could possibly shed some light into this or at
least point me to the right direction...

I am trying to develop a kernel module level solution for dynamic host
multihoming. This requires that I mangle packets from specific
applications running on the system right in the stack and basically
change the interface the packets are sent from (at least two
interfaces).

I understand that I need to register my mangling function with one of
the 5 netfilter hooks (the ROUTING one?), grab the interesting packets
and change..... something in the skbuff.

What really evades me is where/when does routing *exactly* happen. If
I know at which point it happens, I should tap right after it and
change the interface to the one I want. Or this whole idea could be
bad and I end up breaking something in the
packet and it gets dropped...

Of course, that needs to happen for both locally generated traffic and
incoming traffic, so that I link the incoming packets to the right
applications.

regards,
JC


             reply	other threads:[~2005-07-21 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 14:30 JC [this message]
2005-07-21 16:24 ` Questions regarding routing in the stack Carl Holtje ;021;vcsg6;
2005-07-21 17:18   ` JC
2005-07-21 17:42   ` Jan Engelhardt
2005-07-22 22:45     ` Donald Murray
2005-07-23  0:26       ` R. DuFresne
2005-07-23 11:11         ` Jan Engelhardt
2005-07-23 22:25           ` R. DuFresne
2005-07-24  7:33             ` Jan Engelhardt
2005-07-24 11:18               ` R. DuFresne

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=a60102c3050721073024051dd2@mail.gmail.com \
    --to=bikkit@gmail.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.