From: Luca Dionisi <luca.dionisi@gmail.com>
To: bufferbloat list <bloat@lists.bufferbloat.net>
Subject: [Bloat] new network deploy
Date: Mon, 31 Jan 2011 10:52:12 +0100 [thread overview]
Message-ID: <AANLkTi=mEsBTeWbmD6VaCX3Fg1_+J1rgoReUDLfbWo5t@mail.gmail.com> (raw)
Hi all
I am starting to deploy a local TCP/IP network in order to test a new
routing protocol.
Info on the routing protocol: www.netsukuku.org
Info on the network being deployed: pyntk.blogspot.com
It is separated from the Internet at the moment.
I ask for advices on how to make it as free as possible from the
bufferbloat problem.
I would also make some tests on this network and report here what I
find out about bufferbloat.
Further information:
* every node active on the network will be a modern linux host.
* all of the links between nodes will be on wifi or on cables owned
by the users. That is, no VPN links over the Internet.
* if it is needed I can list the actual chipset of ethernet cards
and radio devices.
* most of the wifi links will be managed by radio chipset installed
in linux hosts (mostly ad-hoc, no strange do-it-all out-of-control
embedded-router-bridge-repeater devices)
There is also a particular case. Two linux nodes are connected via a
VPN at layer 2 (I use tinc) over another network with static addresses
and routing. This network is formed by the 2 linux hosts and 2
embedded radio devices, from Ubiquity, which run AirOS, a derived of
OpenWRT.
In this particular case, where do I have to look for possible buffers?
Is it enough to look the tx-queue of the virtual nic or do I have to
check also the settings of the Ubiquity devices?
--Luca
next reply other threads:[~2011-01-31 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:52 Luca Dionisi [this message]
2011-01-31 13:55 ` Jim Gettys
2011-01-31 14:53 ` Dave Täht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=mEsBTeWbmD6VaCX3Fg1_+J1rgoReUDLfbWo5t@mail.gmail.com' \
--to=luca.dionisi@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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