From: John Lister <john.lister@kickstone.com>
To: Edwin van den Oosterkamp <edwin@vandenoosterkamp.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Outbound traffic over two interfaces by port number
Date: Mon, 21 Jun 2010 14:45:24 +0100 [thread overview]
Message-ID: <4C1F6CF4.8080706@kickstone.com> (raw)
In-Reply-To: <7628f5b45c96214fccdfcf03e8440ed2.squirrel@edders.homeip.net>
You might try looking at connection/packet marking.
You can use the MARK target and --set-mark to tag packets as they come
in depending on other iptable rules (you might need to use CONNMARK to
tag the associated conntrack tables with the mark for subsequent
packets). Then create routing tables for each of the interfaces which
have the correct routing information (including gateways, etc) for each
interface. Finally set up routing rules using ip rule to check for the
mark using the mark, (eg ip rule fwmark 1 table 1).
Hope that helps
John
Edwin van den Oosterkamp wrote:
> Hello All,
>
> The requirement I have is bit unusual and unfortunately I have not found
> any answers searching the archives and the Internet in general. I hope
> that if it is actually possible this knowledge will be with this list. I'm
> a programmer with quite a bit of experience on Linux kernel based systems,
> but fairly new to netfilter specifics.
>
> My system has two NICs (eth0 and eth1) and both are connected to different
> networks. One network is for handling data streams, the other solely for
> controlling. Both networks may have gateways, both networks may have
> overlapping IP address ranges. Luckily, there is only a handful of ports
> in use, which allows me to filter all the incoming packets and drop the
> wrong type of packet (data/control traffic) from the wrong type of
> interface (data/control interface). The system is not allowed to route
> between the two networks.
>
> The issue I'm having is that for outbound packets the kernel can select
> the "wrong" interface - e.g. control traffic will then go out on the
> data-only network (due to overlapping IP ranges or having two gateways for
> example). Can I use netfilter to force/redirect these packets so that they
> still go out on the "correct" interface, which in this case would be the
> control-network? I can see from the port number on which interface (data
> or control) the packet was supposed to go out and would like to use that
> information to ensure that the packet does go out on the correct network.
>
> I hope that I have been clear, if not then please let me know and will be
> more than happy to elaborate.
>
> Best regards,
>
> Edwin.
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-06-21 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 12:58 Outbound traffic over two interfaces by port number Edwin van den Oosterkamp
2010-06-21 13:45 ` John Lister [this message]
2010-06-21 15:03 ` Edwin van den Oosterkamp
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=4C1F6CF4.8080706@kickstone.com \
--to=john.lister@kickstone.com \
--cc=edwin@vandenoosterkamp.com \
--cc=netfilter@vger.kernel.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.