Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Gregory OSINAIKE gregory.osinaike@elec.qmw.ac.uk
To: lartc@vger.kernel.org
Subject: [LARTC] tables and mapping marked packets to realms
Date: Tue, 27 Feb 2001 12:25:29 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417057@msgid-missing> (raw)

<PRE>Looking at the HOWTO for iproute2 isee examples where they create a rule
and make a look up table (the John example). I have installed iproute2
but don't seem to have a:

/etc/rt_tables/ path.

Why?

I want to map marked packets(using iptables) to realms and all packets
within a realm to have the same route regardless of destination. 

What if two marked packets have the same destination ?

Thanks for any help

Greg.
-- 
----------------------
Gregory OSINAIKE (<A HREF="mailto:ee9829@elec.qmw.ac.uk">ee9829@elec.qmw.ac.uk</A>)
Electronic Engineering Department
Queen Mary and Westfield College


</PRE>

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 12:25 Gregory [this message]
2001-02-27 12:30 ` [LARTC] tables and mapping marked packets to realms Arthur

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-98373940417057@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