From: Peter Johnson <peter@thejohnsons.com.au>
To: Netfiler E-Mail List <netfilter@lists.netfilter.org>
Subject: Re: Strange setup
Date: 20 Jan 2003 09:31:50 +1100 [thread overview]
Message-ID: <1043015513.24583.16.camel@wizardslair> (raw)
In-Reply-To: <1648.10.35.120.83.1043012159.squirrel@mail.unixpimps.org>
If this traffic isn't LAN related then just do
ip rule add from $WAN_IP table $TABLE_NAME
ip route add default via $WAN_PEER_IP dev $WAN_IF table $TABLE_NAME
This will add a source based route so that traffic entering on the
$WAN_IF has its resonses exit on the $WAN_IF.
See the Advanced Routing HOWTO for more info.
Regards,
PJ
On Mon, 2003-01-20 at 08:35, Evan Borgstrom wrote:
> I've got sort of a strange setup that I'm looking to accomplish some
> strange async routing. I know how I want to accomplish it and am pretty
> sure that I can do it with netfilter but just can't seem to find the
> proper way.
>
> Here's the rundown on the network setup:
>
> [ LAN ] --
> [ DMZ ] -- [ Firewall/Router ] -- [ WAN ]
> |
> |
> [ WLAN ]
>
>
> The WLAN is between myself and a couple of other people in my building to
> provide redundant paths out of each of our networks and is working
> beautifully. We all advertise (via BGP) blocks close to us to each to
> provide the shortest path as well.
>
> Comming from the WAN I have a /29 routed to the DMZ which services a
> number of machines that provide different services.
>
> The firewall/router is a linux box that is running iptables.
>
>
> Now the problem:
> Because of the advertisments comming over the WLAN I now have about 40
> routes in the kernel routing table. Most of them are not very specific
> since we advertise our ISP's blocks to each other, so I have routes for
> /16's, /21's, etc... What happens is when someone that resides in one of
> these blocks that I'm getting advertisements for tries to access an
> address in my /29 their return path follows the advertisment over the
> WLAN.
>
> Using the iproute2 package I've created a second routing table with a
> single default route out my WAN default route. I'm hopping that there's a
> way to tag the connection in the conntrack table and then -j MARK it when
> a related,established packet comes back so that I use the iproute2 package
> to specify that the second routing table will be used.
>
> Anyone know of a way that I can accomplish this?
>
> Thanks in advance,
> Evan
>
> --
> Evan Borgstrom <evan@unixpimps.org>
> http://www.unixpimps.org - SIG:ILL
>
>
>
--
'Conformity is the jailer of freedom and the enemy of growth.' - John F.
Kennedy
next prev parent reply other threads:[~2003-01-19 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 21:35 Strange setup Evan Borgstrom
2003-01-19 22:00 ` Evan Borgstrom
2003-01-19 22:31 ` Peter Johnson [this message]
2003-01-20 0:45 ` Evan Borgstrom
2003-01-20 7:24 ` Peter Johnson
2003-01-20 7:50 ` Peter Johnson
2003-01-20 14:49 ` Evan Borgstrom
2003-01-20 15:01 ` ip_conntrack: table full, dropping packet hare ram
2003-01-20 15:13 ` Maciej Soltysiak
2003-01-24 2:50 ` Strange setup Evan Borgstrom
2003-01-20 20:42 ` Peter Johnson
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=1043015513.24583.16.camel@wizardslair \
--to=peter@thejohnsons.com.au \
--cc=netfilter@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox