From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Wim Ceulemans <wim.ceulemans@able.be>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>, pieter@able.be
Subject: Re: Routing decision?
Date: 15 Sep 2003 15:09:59 +0200 [thread overview]
Message-ID: <1063631398.31092.91.camel@raylinux.internal> (raw)
In-Reply-To: <3F65B63E.7030203@able.be>
[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]
On Mon, 2003-09-15 at 14:53, Wim Ceulemans wrote:
> Ray
>
> Do you mean that if I masquerade all my packets behind the firewall,
> that they are
> considered as locally generated because due to the masquerading their
> source IP is changed?
>
> This would mean that these packets would travel through the FORWARD
> chain and then through
> the OUTPUT chain. And then the 'Kernel packet travelling diagram' would
> be completely wrong,
> because packets come only in the OUTPUT chain if they originate from a
> local process.
No, it was a question ... I don't think they are locally generated.
I think that the aliases on the interface have something to do with it.
I have had to add input and output rules in some situations to get DNAT
to work the way it is supposed to (redirect to a different destination).
It is strange.
>
> Regards
> Wim
>
> Ray Leach wrote:
>
> >On Mon, 2003-09-15 at 12:44, Wim Ceulemans wrote:
> >
> >
> >>Hi Ray
> >>
> >>In my opinion 'locally generated packets' can only be generated by a
> >>local process.
> >>So in the diagram where it says 'local process', that's where the
> >>'locally generated packets' start
> >>their way through the kernel. Where's the difference?
> >>
> >>
> >>
> >What about packets that get SNATed?
> >Where are they generated?
> >
> >
> >
> >>Regards
> >>Wim
> >>
> >>Ray Leach wrote:
> >>
> >>
> >>
> >>>On Mon, 2003-09-15 at 10:49, Wim Ceulemans wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>Hi
> >>>>
> >>>>In paragraph 6.2 of the iptables-tutorial the following is said:
> >>>>"The OUTPUT chain is used for altering locally generated packets (i.e.,
> >>>>on the firewall) before they get to the routing decision.
> >>>>
> >>>>But in paragraph 3.1, the "Traversing of tables and chains" diagram, we
> >>>>see the "Routing decision" is listed after the "Local process" and
> >>>>BEFORE! the packet goes to the output chain.
> >>>>
> >>>>So which one is right? Does the routing decision take place after or
> >>>>before the packet travels through the output chain?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>Are you not getting confused with 'locally generated' and 'local
> >>>process'. They are not the same thing.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>Regards
> >>>>
> >>>>
> >>>>
> >>>>
--
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-09-15 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 8:49 Routing decision? Wim Ceulemans
2003-09-15 9:08 ` Ray Leach
2003-09-15 10:44 ` Wim Ceulemans
2003-09-15 12:14 ` Ray Leach
2003-09-15 12:53 ` Wim Ceulemans
2003-09-15 13:09 ` Ray Leach [this message]
2003-09-15 13:31 ` Cedric Blancher
2003-09-15 13:46 ` Ray Leach
2003-09-15 14:00 ` Cedric Blancher
2003-09-15 15:03 ` Ray Leach
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=1063631398.31092.91.camel@raylinux.internal \
--to=raymondl@knowledgefactory.co.za \
--cc=netfilter@lists.netfilter.org \
--cc=pieter@able.be \
--cc=wim.ceulemans@able.be \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox