All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk mfedyk@matchmail.com
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Can't use two links on a linux box - correction/addition
Date: Fri, 10 Nov 2000 18:33:54 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216912@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216911@msgid-missing>

<PRE>Arthur van Leeuwen wrote:
&gt;<i> 
</I>&gt;<i> On Thu, 9 Nov 2000, Mike Fedyk wrote:
</I>&gt;<i> 
</I>&gt;<i> &gt; I've just subscribed to this list, and found this article.
</I>&gt;<i> &gt; It solved my problem perfectly, but he described the solution
</I>&gt;<i> &gt; I was trying as possible, which I've found is not.
</I>&gt;<i> 
</I>&gt;<i> That is interesting... I can't see much difference from the setup you've made
</I>&gt;<i> with what I've described, but for the ordering of the route setup commands
</I>&gt;<i> (which, unfortunately, *is* significant, a detail I forgot when composing
</I>&gt;<i> the e-mail).
</I>
The setup you described is exactly what worked in the end.

&quot;The specific tables (100 and 200) are not 
strictly necessary, but they provide you with the option to do a static
choice of the uplink route to take for certain traffic.&quot;

This is what my reply was for, you really do *need* the extra tables and ip rule
settings.

&gt;<i> &gt; I was reading some old docs that policy routing didn't work on packets from
</I>&gt;<i> &gt; local processes.  I'm sure glad it was wrong. :)
</I>&gt;<i> 
</I>&gt;<i> I've never seen those docs, fortunately. If I had, I probably wouldn't have
</I>&gt;<i> tried this... ;)
</I>&gt;<i> 
</I>
<A HREF="http://www.linuxdoc.org/HOWTO/Net-HOWTO/c1431.html">http://www.linuxdoc.org/HOWTO/Net-HOWTO/c1431.html</A>
There is a link to <A HREF="http://www.compendium.com.ar/policy-routing.txt">http://www.compendium.com.ar/policy-routing.txt</A>

Which was made when 2.1.xx was current.

&gt;<i> Yes. TCP only handles multipath traffic if the addresses stay the same on
</I>&gt;<i> all the paths. But it's not really good for most UDP based protocols either.
</I>&gt;<i> 
</I>
The only test that worked was icmp ping. ;P

&gt;<i> The name's Arthur. `van Leeuwen' is my surname. Yes, it's a silly European
</I>&gt;<i> thing. Note quite unlike `van Beethoven' in `Ludwig van Beethoven'.
</I>&gt;<i> 
</I>Ok, np.  That was what was in the From: in the archive, so I used that.  Maybe
you should add Arthur to your name in the From: field. &quot;Arthur van Leeuwen&quot;?

I hope this discussion will help others when it goes into the archive.  It
certainly helped me.  If they actually take the time to check the archive... but
that's another issue.

HTH
-- 

Mike Fedyk                   &quot;They that can give up essential liberty
Information Systems           to obtain a little temporary safety
Match Mail Productions Inc.   deserve neither liberty nor safety.&quot;
<A HREF="mailto:mfedyk@matchmail.com">mfedyk@matchmail.com</A>                                   Ben Franklin


</PRE>

      reply	other threads:[~2000-11-10 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 10:47 [LARTC] Re: Can't use two links on a linux box - correction/addition Arthur
2000-11-10 18:33 ` Mike [this message]

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-98373938216912@msgid-missing \
    --to=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.