Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] howto mark packets
Date: Mon, 24 Nov 2003 17:02:33 +0000	[thread overview]
Message-ID: <marc-lartc-106975009700588@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106968743300801@msgid-missing>

hi cezar,

why not use the TOS mark -- it is carried in the packet's tcp header ...
you can only have 8 types/marks however ...

cheers

charles





On Mon, 2003-11-24 at 17:03, Cezar Atanasiu wrote:
> On Mon, 24 Nov 2003 16:43:40 +0100
> Eric Leblond <eric@regit.org> wrote:
> 
> > Le lun 24/11/2003 à 16:16, Cezar Atanasiu a écrit :
> > >   Hi folks,
> > >   The questions : 
> > > 
> > >   1. can that be done ?
> > 
> > not that way, fw mark are lost when you leave the computer
> 
>  I know, that is why I asked.
> 
> > 
> > >   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.
> 
>  Hmm, that would become too complicated. There is no other way ? 
> 
> > 
> > BR,
> > -- 
> > Eric Leblond
> > NuFW, Now User Filtering Works (http://www.nufw.org)
> > 
> 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-11-24 17:02 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 [this message]
2003-11-24 21:52 ` Dick Shorter

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-106975009700588@msgid-missing \
    --to=lartc@manchotnetworks.net \
    --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