From: Michael Davidson <michael@bbd.co.za>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Fwd: Inbound and outbound traffic problem
Date: Tue, 20 Dec 2005 18:37:02 +0000 [thread overview]
Message-ID: <43A84F4E.6040906@bbd.co.za> (raw)
In-Reply-To: <1b47fd660512200515x4d9fed51h5b9eb194d10dbf69@mail.gmail.com>
Hi,
There is another way to do this, but I doubt that it is anymore
elegant than what you have right now. I have just completed this same
task and I can say that if I could have used your method - overlaying
another subnet -I would have done so since it's a cleaner solution in my
view.
I used iptables to "mark" the packets of the flows that where generated
by the server ( WWW).
I created a second routing table with it's own default route.
I created an "ip rule" which looks for a "mark" on the packets and
directs those packets to the new routing table.
Keep in mind, for this to work correctly you need to be using NAT or
Masquerade on at least one of your ISP ports.
Regards Mike
Janis Daniel Bistevins wrote:
> sorry if I can't explain correctly what my problem is.
> What I need is to route traffic originated inside my lan by one ISP,
> and traffic coming from another ISP (mostly requests to machines
> inside the lan)back by the same ISP.
> The way I've found is by creating two diferent networks inside my lan.
> Those machines running services have two IP's on its NICs. That way I
> can route depending the source of the packets.
> I have a snapshot of my drawing, so you can figure this out.
>
> http://www.iglobal.com.ar/~janis/snap0000.xpm
> <http://www.iglobal.com.ar/%7Ejanis/snap0000.xpm>
>
>
> ---------- Forwarded message ----------
> From: Janis Daniel Bistevins < bistevins@gmail.com
> <mailto:bistevins@gmail.com>>
> Date: Dec 19, 2005 12:05 PM
> Subject: Inbound and outbound traffic problem
> To: lartc@mailman.ds9a.nl <mailto:lartc@mailman.ds9a.nl>
>
>
> +---------------+
> +----+ ISP A | |
> | |-----------------| |
> +----+ | |
> +------+
> | ROUTER | NET
> C | www |
> | LINUX
> |----------------| |
> | |
> NET D +-------+
> +----+ ISP B | |
> | |----------------| |
> +----+ | |
> +----------------+
>
>
> Hi!
> I need that requests to www arriving from net ISP A returns by the
> same route, but connections initiated from www go out by net ISP B.
>
> The only way I have discovered so far is creating two differents
> networks (NET C and NET D)
> So, www have a route to ISP A by NET C and a default route by NET D .
> On the Linux Router evereything coming from NET D is routed by NET B
> and everything coming from NET C is routed by NET A
> This is accomplished by creating logical interfaces on www and on the
> Linux Router.
>
> Is there another way to do this?
>
> Thanks in advance.
> Regards.
>
> --
> Janis Bistevins
> >Belief is 9/10 of YOUR reality<
>
>
> --
> Janis Bistevins
> >Belief is 9/10 of YOUR reality<
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
--
Regards Mike.
Michael Davidson
Barone Budge & Dominick
Email: michael@bbd.co.za
Office: +27 11 532 8380
BB&D : +27 11 532 8300
Fax: +27 11 532 8400
Mobile: +27 82 650 5707
Home: +27 11 452 4423
This e-mail is confidential and subject to the disclaimer published at
http://www.bbd.co.za
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-20 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 13:15 [LARTC] Fwd: Inbound and outbound traffic problem Janis Daniel Bistevins
2005-12-20 18:37 ` Michael Davidson [this message]
2005-12-21 11:56 ` Janis Daniel Bistevins
2005-12-21 15:22 ` Michael Davidson
2005-12-21 18:34 ` Jody Shumaker
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=43A84F4E.6040906@bbd.co.za \
--to=michael@bbd.co.za \
--cc=lartc@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.