From: Wim Ceulemans <wim.ceulemans@able.be>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: netfilter-devel@lists.netfilter.org, pieter@able.be
Subject: Re: Routing decision?
Date: Mon, 15 Sep 2003 17:29:16 +0200 [thread overview]
Message-ID: <3F65DACC.8020706@able.be> (raw)
In-Reply-To: <Pine.LNX.4.44.0309151632240.16959-100000@filer.marasystems.com>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
Henrik
Thanks for your answer.
If I understand correct, if the local endpoint of the socket is not
bound, then:
1. The routing decision is taken, and the source IP address is assigned
to the IP address of the interface
through which the packet would leave the firewall.
2. The packet travels through the OUTPUT chain and does not pass the
routing decision anymore, because
the routing decision was already taken before going to the OUTPUT
chain.
Is there any specific reason why the packet doesn't pass the routing
decision the second time?
Regards
Wim
Henrik Nordstrom wrote:
>On Mon, 15 Sep 2003, Wim Ceulemans wrote:
>
>
>
>>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.
>>
>>
>
>Yes.
>
>
>
>>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?
>>
>>
>
>Both, depending on the situation.
>
>if the local endpoint of the socket sending the packet is bound then
>routing occurs after OUTPUT.
>
>If the local endpoint of the socket is NOT bound then routing occurs
>before OUTPUT to assign the source address.
>
>Regards
>Henrik
>
>
>
>
--
Wim Ceulemans
R&D Engineer
Secure Internet Communication with aXs Guard
Able NV
Leuvensesteenweg 282 - B-3190 Boortmeerbeek - Belgium
Phone: + 32 15 50.44.00 - Fax: + 32 15 50.44.09
E-mail: wim.ceulemans@able.be
--
Security check on this e-mail has been done by aXs GUARD
(http://www.axsguard.com)
next prev parent reply other threads:[~2003-09-15 15:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 13:16 Routing decision? Wim Ceulemans
2003-09-15 14:34 ` Henrik Nordstrom
2003-09-15 15:29 ` Wim Ceulemans [this message]
2003-09-15 16:06 ` Henrik Nordstrom
2003-09-15 16:25 ` Wim Ceulemans
2003-09-15 16:59 ` Cedric Blancher
2003-09-15 19:48 ` Henrik Nordstrom
2003-09-18 7:37 ` Wim Ceulemans
2003-09-18 11:22 ` Henrik Nordstrom
2003-09-18 11:54 ` Wim Ceulemans
2003-09-18 13:10 ` Henrik Nordstrom
2003-09-18 13:39 ` Wim Ceulemans
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 20:10 Daniel Chemko
2003-09-15 22:32 ` Henrik Nordstrom
2003-09-15 8:49 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
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=3F65DACC.8020706@able.be \
--to=wim.ceulemans@able.be \
--cc=hno@marasystems.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pieter@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 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.