All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2 gateway on linux
Date: Tue, 06 May 2003 16:09:22 +0000	[thread overview]
Message-ID: <marc-lartc-105223746626285@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105221603102461@msgid-missing>

--On Tuesday, May 06, 2003 09:06:55 AM -0500 "Martin A. Brown" 
<mabrown-lartc@securepipe.com> wrote:

> There are two different types of solutions.  If you can describe which
> type of traffic you wish to send to which ISP, you can use multiple
> uplinks without load sharing [1].

This sounds like the problem I posted earlier this week. I've got most of 
my traffic going out eth2 (T1) and a little going out eth1 (ADSL). eth2 is 
the default gateway, and a few selected netblocks and hosts are statically 
routed to eth1.

Now I find that I can't traceroute or ping to eth2 from a host routed to 
eth1. The failing ping seems to be because the ICMP replies have a source 
address of eth2 but are going out eth1, and I suspect the ISP is 
egress-filtering these. I'm guessing this happens to all my replies. Is 
there any way around this? The ISP for eth1, which is on a /29, is PacBell. 
Should I bother to ask them to put in an exception in their egress filter?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-05-06 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 10:18 [LARTC] 2 gateway on linux Zealous
2003-05-06 14:06 ` Martin A. Brown
2003-05-06 16:09 ` Kenneth Porter [this message]
2003-05-09 12:21 ` Martin A. Brown
2003-05-10  4:23 ` Zealous

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-105223746626285@msgid-missing \
    --to=shiva@sewingwitch.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.