All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing for split multiple uplinks/providers with port
Date: Wed, 12 Nov 2003 08:32:07 +0000	[thread overview]
Message-ID: <marc-lartc-106862765407852@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106770352107516@msgid-missing>


Ian! D. Allen wrote:
> I suspect the fix is somehow to mark the port forwarded packets with
> a flag indicating on which interface they arrived at the Linux router,
> and then preserve this flag into the answer packets on the web server.
> On the Linux router I can then make sure that appropriately flagged
> answer packets go out the correct interface.
> Am I on the right track here?
Is the same track I went along a week or so ago and seems to work fine.
Mark them as they come in, then make the PREROUTING table direct them to the 
appropriate routing table to get back out.

regards

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer  email:     damion@snapgear.com
SnapGear ---                           ph:         +61 7 3435 2809
  | Custom Embedded Solutions          fax:         +61 7 3891 3630
  | and Security Appliances            web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ---  Free Embedded Linux Distro at   http://www.snapgear.org  ---

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-11-12  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01 15:50 [LARTC] routing for split multiple uplinks/providers with port forwarding Ian! D. Allen
2003-11-12  7:42 ` Ian! D. Allen
2003-11-12  8:32 ` Damion de Soto [this message]
2003-11-14  4:42 ` [LARTC] routing for split multiple uplinks/providers with port Martin A. Brown

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=marc-lartc-106862765407852@msgid-missing \
    --to=damion@snapgear.com \
    --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.