From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>, netfilter@vger.kernel.org
Subject: Re: Bridges
Date: Mon, 23 Aug 2010 21:18:50 +0100 [thread overview]
Message-ID: <4C72D7AA.1090206@abpni.co.uk> (raw)
In-Reply-To: <4C722FAF.5030203@plouf.fr.eu.org>
On 23/08/10 09:22, Pascal Hambourg wrote:
> Jonathan Tripathy a écrit :
>
>>> "IP routing" may have different meanings. It can be a synonym for "IP
>>> forwarding", like in "IP routers do IP routing". But in the context of
>>> the Linux IP stack, it rather means the handling of an IP packet
>>> according to the routing table. In short :
>>> - for an incoming packet, determine whether it is for local delivery or
>>> to be forwarded ;
>>> - for an outgoing or forwarded packet, determine the output interface
>>> and gateway.
>>>
>> I definitely still want link to do that though, with my bridge traffic...
>>
> Do what ? I don't understand, sorry.
>
Sorry, I'm not wording my questions very well. Let me start from the
top. Thanks everyone for the fantastic help by the way :)
Ok, so as I understand Linux, and please correct me if I'm wrong, when a
packet comes into a physical interface on a Linux machine, regardless of
the status of the net.ipv4.conf.<interface>.forwarding, Linux will
always put the packet onto a "chain". This will either be the INPUT
chain or the FORWARD chain. Is that correct?
Next, if the packet it destined for an IP of one of the local
interfaces, it puts it onto the INPUT chain, correct?
However if the packet it destined for a non-local host, it puts it onto
the FORWARD chain, correct?
Then, when the packet is on the forward chain, it depends on if the
incoming interface is connected to a bridge or not. If it is connected
to a bridge, the packet will transverse the FORWARD chain and go out the
interface which must be part of the same bridge, correct?
If, however, the incoming interface is not connected to a bridge, Linux
will fordward the packet out of another interface which is thinks is
correct (as defined by the routing table), but it will only do this if
net.ipv4.conf.<interface>.forwarding is set to 1, correct?
Before I go on with my next set of question, I'd just like someone to
correct the above if it is wrong
Many Thanks
next prev parent reply other threads:[~2010-08-23 20:18 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 22:44 Bridges Jonathan Tripathy
2010-08-17 22:56 ` Bridges Jan Engelhardt
2010-08-17 23:34 ` Bridges Stephen Hemminger
2010-08-18 11:27 ` Bridges Thomas Jacob
2010-08-18 19:51 ` Bridges Jonathan Tripathy
2010-08-18 21:51 ` Bridges Grant Taylor
2010-08-18 21:57 ` Bridges Jonathan Tripathy
2010-08-18 22:08 ` Bridges Grant Taylor
2010-08-18 22:15 ` Bridges Jonathan Tripathy
2010-08-18 22:26 ` Bridges Jan Engelhardt
2010-08-18 22:51 ` Bridges Jonathan Tripathy
2010-08-18 23:05 ` Bridges Pascal Hambourg
2010-08-18 23:07 ` Bridges Jonathan Tripathy
2010-08-18 23:21 ` Bridges Pascal Hambourg
2010-08-18 23:23 ` Bridges Jonathan Tripathy
2010-08-18 23:45 ` Bridges Jonathan Tripathy
2010-08-19 7:26 ` Bridges Pascal Hambourg
2010-08-19 18:47 ` Bridges Jonathan Tripathy
2010-08-19 19:26 ` Bridges Pascal Hambourg
2010-08-19 19:37 ` Bridges Jonathan Tripathy
2010-08-19 20:00 ` Bridges Jan Engelhardt
2010-08-19 20:11 ` Bridges Jonathan Tripathy
2010-08-19 21:14 ` Bridges Pascal Hambourg
2010-08-19 21:24 ` Bridges Jonathan Tripathy
2010-08-19 22:04 ` Bridges Pascal Hambourg
2010-08-19 22:53 ` Bridges Jonathan Tripathy
2010-08-20 8:53 ` Bridges Pascal Hambourg
2010-08-21 21:46 ` Bridges Jonathan Tripathy
2010-08-21 23:25 ` Bridges Jan Engelhardt
[not found] ` <4C70E853.6050107@abpni.co .uk>
2010-08-22 9:05 ` Bridges Jonathan Tripathy
2010-08-22 9:09 ` Bridges Jan Engelhardt
[not found] ` <4C70E 9A2.3040907@abpni.co.uk>
2010-08-22 9:10 ` Bridges Jonathan Tripathy
2010-08-22 21:02 ` Bridges Pascal Hambourg
[not found] ` <4C7194 D3.7070803@abpni.co.uk>
2010-08-22 21:21 ` Bridges Jonathan Tripathy
2010-08-23 8:22 ` Bridges Pascal Hambourg
2010-08-23 20:18 ` Jonathan Tripathy [this message]
2010-08-24 8:57 ` Bridges Karel Rericha
2010-08-24 14:44 ` Bridges Pascal Hambourg
2010-08-24 17:37 ` Bridges Jonathan Tripathy
2010-08-24 18:07 ` Bridges Pascal Hambourg
2010-08-24 18:34 ` Bridges Jonathan Tripathy
2010-08-24 22:20 ` Bridges Pascal Hambourg
2010-08-20 8:38 ` Bridges Jan Engelhardt
2010-08-20 9:05 ` Bridges Pascal Hambourg
2010-08-20 9:09 ` Bridges Jan Engelhardt
2010-08-20 10:26 ` Bridges Pascal Hambourg
2010-08-20 16:02 ` Bridges Grant Taylor
2010-08-20 16:18 ` Bridges Jan Engelhardt
2010-08-20 16:25 ` Bridges Grant Taylor
2010-08-20 16:32 ` Bridges Jan Engelhardt
2010-08-21 12:48 ` Bridges Pascal Hambourg
2010-08-21 21:44 ` Bridges Grant Taylor
2010-08-19 19:28 ` Bridges Jan Engelhardt
2010-08-18 22:59 ` Bridges Pascal Hambourg
2010-08-18 23:00 ` Bridges Jonathan Tripathy
2010-08-18 23:11 ` Bridges Pascal Hambourg
2010-08-19 8:29 ` Bridges Jan Engelhardt
2010-08-19 9:16 ` Bridges Pascal Hambourg
2010-08-19 3:52 ` Bridges Grant Taylor
2010-08-19 7:33 ` Bridges Pascal Hambourg
2010-08-19 14:51 ` Bridges Grant Taylor
2010-08-19 14:56 ` Bridges Jan Engelhardt
2010-08-19 15:49 ` Bridges Grant Taylor
2010-08-19 16:21 ` Bridges Jan Engelhardt
2010-08-19 16:41 ` Bridges Grant Taylor
2010-08-19 17:10 ` Bridges Jan Engelhardt
2010-08-19 18:36 ` Bridges Grant Taylor
2010-08-19 17:10 ` Bridges Rick Jones
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=4C72D7AA.1090206@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--cc=netfilter@vger.kernel.org \
--cc=pascal.mail@plouf.fr.eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox