From: "Ana Carolina Alonso de Armiño" <aalonso@uncoma.edu.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help Diffserv
Date: Mon, 17 Mar 2003 13:17:04 +0000 [thread overview]
Message-ID: <marc-lartc-104790694524337@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104790563022966@msgid-missing>
Hello, I'm new too . I haven't routers but I use Linux router ... only you
need a pc, install Linux, compile the kernel with QoS and then configure
wdisc, classes and filters... I will begin now with this task.
I don't know how to mark the DSCP field traffic ....
I know the mgen (gen traffic) but I beleave that it couldn't mark the DSCP,
is it right?
Sorry my english
Thanks
Ana
At 12:52 p.m. 17/03/03 +0000, sun reflex4 wrote:
>Hi all,
>I am new to the world of Diffserv, and I have read many articles about it.
>However, I find only papers describing the architecture of Diffserv, and
>how it works, but nothing about how this can be realized.
>
>*)What do I need to build a Diffserv capable network (with Linux and
>Windows clients) but without buying routers, just with PCs?
>*)How to mark DSCP field of packets going out of a Windows XP PC?
>
>Thanx alot.
>
>
>
>
>_________________________________________________________________
>MSN 8 with e-mail virus protection service: 2 months FREE*
>http://join.msn.com/?pageþatures/virus
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-17 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 12:52 [LARTC] Help Diffserv sun reflex4
2003-03-17 13:17 ` Ana Carolina Alonso de Armiño [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-104790694524337@msgid-missing \
--to=aalonso@uncoma.edu.ar \
--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.