Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] tables and mapping marked packets to realms
Date: Tue, 27 Feb 2001 12:30:57 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417058@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940417057@msgid-missing>

<PRE>On Tue, 27 Feb 2001, Gregory OSINAIKE wrote:

&gt;<i> Looking at the HOWTO for iproute2 isee examples where they create a rule
</I>&gt;<i> and make a look up table (the John example). I have installed iproute2
</I>&gt;<i> but don't seem to have a:
</I>&gt;<i>
</I>&gt;<i> /etc/rt_tables/ path.
</I>&gt;<i>
</I>&gt;<i> Why?
</I>
Because you didn't make the directory and didn't put the example files
there. That's all there is to making one.

&gt;<i> I want to map marked packets(using iptables) to realms and all packets
</I>&gt;<i> within a realm to have the same route regardless of destination.
</I>&gt;<i>
</I>&gt;<i> What if two marked packets have the same destination ?
</I>
You can select policy rules based solely on marks, thereby disregarding
destination until a certain routing policy has been chosen. Two differently
marked packets with the same destination can still be routed differently.

Doei, Arthur.

-- 
  /\    / |      <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A>      | Work like you don't need the money
 /__\  /  | A friend is someone with whom | Love like you have never been hurt
/    \/__ | you can dare to be yourself   | Dance like there's nobody watching



</PRE>

      reply	other threads:[~2001-02-27 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 12:25 [LARTC] tables and mapping marked packets to realms Gregory
2001-02-27 12:30 ` Arthur [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-98373940417058@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox