All of lore.kernel.org
 help / color / mirror / Atom feed
From: JC <bikkit@gmail.com>
To: "Carl Holtje ,021,vcsg6," <cwh0803@cs.rit.edu>
Cc: netfilter@lists.netfilter.org
Subject: Re: Questions regarding routing in the stack
Date: Thu, 21 Jul 2005 10:18:26 -0700	[thread overview]
Message-ID: <a60102c305072110181bb1a491@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0507211222530.20075@newavalon.cs.rit.edu>

The diagram is helpfull, thank you. I'll give it a thorough look...

> > 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.
>
> Why does this sound like NAT, where you take data from one interface and
> spit it out on another (receive is done the same way)?

It is a kind of NATing, just changing the IP/interface. The thing is
the rules are not static, they can change at a high rate. Definitely
not confident changing the rules with a script rewritting/reloading
the ruleset will not break it at some point. I am currently thinking
of writting a netfilter module of some sort that will handle this out.


  reply	other threads:[~2005-07-21 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 14:30 Questions regarding routing in the stack JC
2005-07-21 16:24 ` Carl Holtje ;021;vcsg6;
2005-07-21 17:18   ` JC [this message]
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=a60102c305072110181bb1a491@mail.gmail.com \
    --to=bikkit@gmail.com \
    --cc=cwh0803@cs.rit.edu \
    --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.