From: Dimitri Yioulos <dyioulos@onpointfc.com>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Dual WAN set-up
Date: Fri, 13 Jan 2012 06:47:54 -0500 [thread overview]
Message-ID: <201201130647.54303.dyioulos@onpointfc.com> (raw)
In-Reply-To: <1326439545.2182.17.camel@andrew-desktop>
On Friday 13 January 2012 2:25:45 am Andrew Beverley wrote:
> Thanks for the comprehensive answer Lloyd. A couple of minor
points:
> > 2. You would set up a custom routing table for the special
> > DMZ traffic. Use the info in the above link to do that.
> > Suppose it is called "DMZSPECIAL". You will set up routing
> > to the new DMZ interface using the MYDMZ table, something
> > like this:
> >
> > ip route add 10.x.x.x/8 dev ${DMZinterface} src ${wan} table
> > DMZSPECIAL ip route add default via ${gateway} dev
> > ${interface} table DMZSPECIAL
>
> [...]
>
> > 3. You would NEW mark all packets from the special DMZ hosts
> > with fwmark 1, like this (repeat for each source IP or subnet
> > to use the new interface):
>
> Using marks is one way to do this, and provides plenty of
> flexibility. However, if all the traffic is coming from the
> same IP address / interface, then you should be able to use
> straight iproute2 rules to match those aspects, without even
> touching iptables (see ip rule).
>
> > iptables -t mangle -A PREROUTING -m state --state NEW
> > -s 10.x.x.x -j CONNMARK1
>
> Also, if you do decide to use netfilter marks (which is
> certainly no bad thing IMHO), then you probably don't need to
> mark connections and then restore them. Instead just mark a
> packet straight away:
>
> iptables -t mangle -A PREROUTING -s 10.x.x.x -j MARK --set-mark
> 1
>
> Andy
>
>
> --
> 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
Thanks to you both. I'll go over your suggestions, and try to
implement this asap. Please stand by as I may need additional
hand-holding :-) .
Dimitri
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2012-01-13 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 21:51 Dual WAN set-up Dimitri Yioulos
2012-01-12 22:28 ` Andrew Beverley
2012-01-12 22:48 ` Dimitri Yioulos
2012-01-13 7:18 ` Andrew Beverley
2012-01-12 23:08 ` Lloyd Standish
2012-01-12 23:12 ` Lloyd Standish
2012-01-12 23:22 ` Dimitri Yioulos
2012-01-12 23:19 ` Dimitri Yioulos
2012-01-13 0:52 ` Lloyd Standish
2012-01-13 7:25 ` Andrew Beverley
2012-01-13 11:47 ` Dimitri Yioulos [this message]
2012-01-13 14:17 ` Lloyd Standish
2012-01-13 15:17 ` Dimitri Yioulos
2012-01-13 15:22 ` Dimitri Yioulos
2012-01-14 2:27 ` Lloyd Standish
[not found] ` <201201160956.23955.dyioulos@onpointfc.com>
2012-01-16 20:28 ` Lloyd Standish
2012-01-13 20:00 ` Lloyd Standish
2012-01-13 20:04 ` Dimitri Yioulos
-- strict thread matches above, loose matches on Subject: below --
2012-01-16 21:43 Dimitri Yioulos
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=201201130647.54303.dyioulos@onpointfc.com \
--to=dyioulos@onpointfc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox