From: Johan Cimen <c99jcn@cs.umu.se>
To: lartc@vger.kernel.org
Subject: [LARTC] [tcng] link-quality
Date: Fri, 12 Dec 2003 09:34:38 +0000 [thread overview]
Message-ID: <marc-lartc-107122388704209@msgid-missing> (raw)
Hi!
This is my second post in this list with this problem and I need clearing.
Situation is this:
My host is a WLAN Access Point (AP) and I am using one network card. The
host is going to generate packets to stations and those links with good
uplink to the host are going to have priority in the downlink. Incomming
Information in the uplink are going to be stored and used at egress to
regulate downlink traffic.
Incomming packets are only information given and flow quality is within
the ttl-field.
----> ingress (Classifying, using information in ttl-field).
Packet generated from packet generator.
|
------>egress (regulating downlink traffic)
After some tests using tcng and reading [1], [2], [3], [4], I have
realised that:
* I cannot use DSMARK instead of ingress, sins I only have one wireless
network card (wlan0) in my host.
* Using u32 filter, I dont know how to store link quality after
classification in ingress.
Q: Can I store the link quality in a variable/structure in ingress after
classification and use this information at egress?
* Using tcindex: I have to use hash-table or set_tcindex and use this
information at egress.
* RSVP does not scale, so my choice will be to use tcindex, where I
classify flows into classes using tcindex.
Is tcindex and rsvp possible solutions to this problem using tcng [5]?
Or is there another better solution to this problem?
[1] Leonardo Balliache http://www.opalsoft.net/qos/DS-210.htm
[2] tcng Reference Manual http://linux-ip.net/gl/tcng/node165.html
[3] http://almesberger.net/cv/papers.html
[4] http://almesberger.net/cv/papers/dsid-01.ps.gz
[5] http://linux-ip.net/gl/tcng/node165.html
- Johan-
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-12-12 9:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-107122388704209@msgid-missing \
--to=c99jcn@cs.umu.se \
--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