All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wim Ceulemans <wim.ceulemans@able.be>
To: Ray Leach <raymondl@knowledgefactory.co.za>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>, pieter@able.be
Subject: Re: Routing decision?
Date: Mon, 15 Sep 2003 14:53:18 +0200	[thread overview]
Message-ID: <3F65B63E.7030203@able.be> (raw)
In-Reply-To: <1063628083.31092.82.camel@raylinux.internal>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

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.

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
>>>>   
>>>>
>>>>        
>>>>


-- 
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)


  reply	other threads:[~2003-09-15 12:53 UTC|newest]

Thread overview: 24+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15 13:16 Wim Ceulemans
2003-09-15 14:34 ` Henrik Nordstrom
2003-09-15 15:29   ` Wim Ceulemans
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
2003-09-15 20:10 Daniel Chemko
2003-09-15 22:32 ` Henrik Nordstrom

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=3F65B63E.7030203@able.be \
    --to=wim.ceulemans@able.be \
    --cc=netfilter@lists.netfilter.org \
    --cc=pieter@able.be \
    --cc=raymondl@knowledgefactory.co.za \
    /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.