From: Dave Taht <dave.taht@gmail.com>
To: Nick Feamster <feamster@cc.gatech.edu>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] about ready to do another build
Date: Fri, 20 May 2011 17:27:36 -0600 [thread overview]
Message-ID: <BANLkTi=JbiNePr+9hcLRBM7B5xGeHyySug@mail.gmail.com> (raw)
In-Reply-To: <3D4FDD73-CD02-4B57-BF46-3AAD7EBB75A2@cc.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 3903 bytes --]
On Fri, May 20, 2011 at 5:22 PM, Nick Feamster <feamster@cc.gatech.edu>wrote:
> We actually have a test exactly like this in bismark active. I'll give it
> a try.
>
> Remember: people have data caps here. Another complication. :-)
>
Well, yea, but I wanted a good number to bake into the build which I'm
hovering over the build button for...
>
> Two questions:
> 1. What do you want lab.projectbismark.net pointing to? I'll update the
> dreaded godaddy until DNS lands.
>
A problem is that the routers register themselves in DNS (or will), and we
need bind9 for that.
I hope to have real dns after meeting with netops monday.
2. How do you run the babel multihop stuff? Can I run it in this build?
> I'm in a fairly big house with *zero* wireless connectivity downstairs and
> would like to try it out.
> I would like Host <----wireless----> WNDR Relay <---wireless-->WNDR Relay
> <---wired ---> Modem
> Not sure how to set up the relays.
>
Yes, you can do that. I'm tickled you're willing to try it...
There are a couple ways, but I'd prefer to get you through it in irc?
>
> Thanks,
> -Nick
>
> On May 21, 2011, at 12:47 AM, Dave Taht wrote:
>
> > A much longer test would be to download this
> >
> > wget -4
> http://gw.lab.bufferbloat.net/capetown/capetown-wndr3700v2/OpenWrt-ImageBuilder-ar71xx-for-Linux-x86_64.tar.bz2
> >
> > while pinging somewhere fairly close by.
> >
> > Over your wired and wireless connection(s)...
> >
> > Over multiple downloads, too...
> >
> > Sorry to make you work so hard. I am SO OVERJOYED to get some data on
> this problem, however.....
> >
> > (yes, I'll change it to lab.bismarkproject.net as soon as DNS lands)
> >
> > On Fri, May 20, 2011 at 4:42 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> >
> > On Fri, May 20, 2011 at 4:35 PM, Nick Feamster <feamster@cc.gatech.edu>
> wrote:
> >
> > On May 21, 2011, at 12:28 AM, Dave Taht wrote:
> >
> > >
> > > And btw, what are the results of a speedtest from your location without
> QoS on?
> > >
> >
> > Have run it 2x now.
> >
> > I see about 850 kbps down and 400 kbps up.
> >
> > The default upload setting is abusive.
> >
> > Sorry. Nicaragua typically had 64k-128k up. Took my best guess.
> >
> >
> > > With QoS on, set to up/dl values within a few percentage points of that
> (and the overhead calculation disabled)
> > >
> >
> > And with QoS set to say 840/380, with the overhead calculation disabled?
> Should be about 15% below that for a long bulk transfer. Can get closer...
> >
> > Please note that setting these values on the basis of one datapoint in a
> majorish city will result in bad values deeper in the country....
> >
> > Helps to also ping somewhere at the same time of the test to see your
> latencies start to go to heck as you get closer to the "edge". You'll see it
> start to jitter... then go wildly late... and at extreme values, tcp/ip will
> start to malfunction as per the bufferbloat diagrams...
> >
> > I'd LOVE for a few tcpdumps of stuff like this, from where you are.....
> >
> > > I can bake a better default into the next build, but I was figuring
> you'd be lucky to be gettting 1000 down....
> > >
> > > I want to note that according to your previous study, the first 30
> seconds of data need to be discarded in order for a speedtest to be valid,
> and speedtest.net doesn't do that...
> >
> > Yep yep... though I don't think PowerBoost is enabled over here.
> Although, we'll find out. :-)
> >
> > -Nick
> >
> >
> >
> > --
> > Dave Täht
> > SKYPE: davetaht
> > US Tel: 1-239-829-5608
> > http://the-edge.blogspot.com
> >
> >
> >
> > --
> > Dave Täht
> > SKYPE: davetaht
> > US Tel: 1-239-829-5608
> > http://the-edge.blogspot.com
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 5878 bytes --]
next prev parent reply other threads:[~2011-05-20 23:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:27 Dave Taht
2011-05-20 21:40 ` Nick Feamster
2011-05-20 21:41 ` Nick Feamster
2011-05-20 22:11 ` Dave Taht
2011-05-20 22:12 ` Nick Feamster
2011-05-20 22:15 ` Dave Taht
2011-05-20 22:16 ` Nick Feamster
2011-05-20 22:28 ` Dave Taht
2011-05-20 22:35 ` Nick Feamster
2011-05-20 22:42 ` Dave Taht
2011-05-20 22:47 ` Dave Taht
2011-05-20 23:22 ` Nick Feamster
2011-05-20 23:27 ` Dave Taht [this message]
2011-05-20 23:29 ` Nick Feamster
2011-05-20 23:27 ` Nick Feamster
2011-05-21 8:12 ` Srikanth Sundaresan
2011-05-21 12:09 ` Nick Feamster
[not found] ` <BANLkTikzEnRk8D0D4yR-4smqPiMYW0OH4A@mail.gmail.com>
2011-05-21 15:48 ` Srikanth Sundaresan
2011-05-21 16:08 ` Dave Taht
2011-05-21 16:33 ` Srikanth Sundaresan
2011-05-21 16:49 ` Dave Taht
2011-05-21 16:53 ` Nick Feamster
2011-05-21 17:07 ` Srikanth Sundaresan
2011-05-23 13:20 ` Jim Gettys
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='BANLkTi=JbiNePr+9hcLRBM7B5xGeHyySug@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=feamster@cc.gatech.edu \
/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