All of lore.kernel.org
 help / color / mirror / Atom feed
From: "anish_46628" <anish_46628@rediffmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Requset regarding packet marking.
Date: Thu, 05 Sep 2002 16:57:53 +0000	[thread overview]
Message-ID: <marc-lartc-103124517825350@msgid-missing> (raw)

Hello Sir,

I want some help from you. I have my configuration like this. I 
have three machines. PC1,PC2,PC3.

            hub                        hub
PC1--------------------PC2-----------------------PC3
eth0                eth0,eth1                    eth0



I want to work my configuration like diffserv. I am generating 
traffic from PC3 and sending it to PC1 via PC2(as a router)and 
 from PC2 to PC1 also. So i have two kinds of traffic. I want to 
do these things:

1. Mark the packets going out from PC3 towards PC1 via PC2.

2. I have my rules and filters with tc in PC2. Means i want to 
contol the traffic from PC2. Based on the mark which i put on the 
traffic going out     from   PC3 i want to put the traffic in 
different-differnt classes. Means i want to filter the traffic 
based on the mark on traffic. It would be helpful if i am  able to 
mark the TOS bits so that i can see it in tcdump or ethereal.

3. Traffic going out from PC2 and generated by PC2 itself should 
have different differnt mark so that the traffic can be filtered 
based on the mark.

Please suggest sthing related to this.

Waiting for your reply.

Anish Mehta.
ENST-Bretagne.



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

             reply	other threads:[~2002-09-05 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 16:57 anish_46628 [this message]
2002-09-06 20:31 ` [LARTC] Requset regarding packet marking Jose Luis Domingo Lopez

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-103124517825350@msgid-missing \
    --to=anish_46628@rediffmail.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 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.