All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Eric Leblond <eric@inl.fr>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Martijn Lievaart <m@rtij.nl>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: ip_conntrack_tuple and marks
Date: Tue, 26 Sep 2006 00:02:05 +0200	[thread overview]
Message-ID: <451851DD.7060609@gmx.net> (raw)
In-Reply-To: <1159221370.18152.7.camel@localhost.localdomain>

Eric Leblond wrote:
> Hi,
> 
> Le lundi 25 septembre 2006 à 20:42 +0200, Martijn Lievaart a écrit :
>> Carl-Daniel Hailfinger wrote:
>>
>>> No, they are not. Let me explain:
>>> The box in question has two pairs of interfaces.
>>> eth0: 10.0.0.254/24   eth1: 10.0.1.254/24
>>> eth2: 10.0.0.254/24   eth3: 10.0.1.254/24
>>> I want to do routing and firewalling between eth0 and eth1. That's
>>> simple. However, I also want to do routing and filtering between
>>> eth2 and eth3. Although eth0 and eth2 have the same subnet, they
>>> are NOT the same network, they just happen to have identical
>>> configurations. Same goes for eth1 and eth3.
> 
> It is more an on iproute problem.
> You could do that by using two dedicated routing tables and by setting
> carefully routing table :
> [...]

Yes, routing has been running here for a while and works perfectly
(with a similar iproute2 setup as you suggested).
Only connection tracking is giving me problems.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

  reply	other threads:[~2006-09-25 22:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 20:33 ip_conntrack_tuple and marks Carl-Daniel Hailfinger
2006-09-24  3:14 ` Pablo Neira Ayuso
2006-09-24 17:57   ` Carl-Daniel Hailfinger
2006-09-24 22:03     ` Martijn Lievaart
2006-09-25 14:04       ` Carl-Daniel Hailfinger
2006-09-25 18:42         ` Martijn Lievaart
2006-09-25 20:52           ` [Proposal] ip_conntrack_tuple extension for advanced matching Carl-Daniel Hailfinger
2006-09-25 23:48             ` Pablo Neira Ayuso
2006-09-26 10:00               ` Patrick McHardy
2006-09-26 13:45                 ` Martijn Lievaart
     [not found]                 ` <60318.2001:888:19e1::53.1159278334.squirrel@dexter>
2006-09-26 13:54                   ` Carl-Daniel Hailfinger
2006-09-26 13:59                     ` Patrick McHardy
2006-09-26 14:45                       ` Carl-Daniel Hailfinger
2006-09-25 21:56           ` ip_conntrack_tuple and marks Eric Leblond
2006-09-25 22:02             ` Carl-Daniel Hailfinger [this message]
2006-09-25 22:08             ` Eric Leblond
2006-09-25 22:23               ` Carl-Daniel Hailfinger

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=451851DD.7060609@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=eric@inl.fr \
    --cc=m@rtij.nl \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.