From: "Dick Shorter" <DickS@jetsoft.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] howto mark packets
Date: Mon, 24 Nov 2003 21:52:46 +0000 [thread overview]
Message-ID: <marc-lartc-106971090401744@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106968743300801@msgid-missing>
In answer to CA's question and EL's response,
Along the same lines, if you encapsulated the marked packet (IP in IP) and set (mangled) the TOS bits in the envelope packet, they could carry the mark without modifying the original packet. Would be a completely non-standard usage of the TOS bits (unless they happened to correspond to the reasons that you are marking packets,;>), but - since they wouldn't get out of your area of responsibility, it might provide an easy-to-setup-and-manage alternative. You would only need one "tunnel" that way, not one for each type of mark...
Of course, you could always filter the packet in user-land, encapsulating in an envelope with the mark data, and re-filter again at the second router (again in user-land), to de-cap and re-mark. No kernel patches needed...
Dick Shorter
dicks@jetsoft.com
-----Original Message <editted> -----
Subject: Re: [LARTC] howto mark packets
> 2. if the answer to the first q. is yes, can that be done w/o patching
> the kernel on the first router w/ experimental patches ?
you can do that in a "capillotracté" way (such an idea) by using tunnels
(gre or ipip) and doing some iproute2 an A do push packet in a tunnel
corresponding to their mark and have B route by interface.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-24 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 15:16 [LARTC] howto mark packets Cezar Atanasiu
2003-11-24 15:43 ` Eric Leblond
2003-11-24 16:03 ` Cezar Atanasiu
2003-11-24 17:02 ` lartc
2003-11-24 21:52 ` Dick Shorter [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-106971090401744@msgid-missing \
--to=dicks@jetsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox