From: Dave Taht <dave.taht@gmail.com>
To: Andrew Hammond <andrew.george.hammond@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] getting started with mesh networking
Date: Mon, 28 Nov 2011 04:28:49 +0100 [thread overview]
Message-ID: <CAA93jw5MuHWVXmztHADzv0HL5eZRD81pif_a=DBxehtgHPG27A@mail.gmail.com> (raw)
In-Reply-To: <CAAC-ZNXJSuuVY3it8yw-JB_0=B93D45JaT4TLVDcFbH_5bZvdg@mail.gmail.com>
On Sun, Nov 27, 2011 at 9:43 PM, Andrew Hammond
<andrew.george.hammond@gmail.com> wrote:
> I have been trying to follow the directions at
> http://www.bufferbloat.net/projects/cerowrt/wiki/Mesh
> however they assume a lot of prior knowledge. I'd like to set up mesh
> networking where I simply add routers to extend the mesh. I have my primary
> / uplink router configured and working. I have enabled AHCP on it and
> applied the changes to /etc/config/network as described (except I left
> txqueuelen at 37 since it bumped my laptops off the network when I tried it
> at 4).
Very cool.
1) I spent some time this morning cleaning up and I hope vastly
improved the document
http://www.bufferbloat.net/projects/cerowrt/wiki/Mesh
Let me know if that helps.
2) Some changes in openwrt in late october in the startup scripts and
lua broke startup for AHCP. :(
if the AHCPD process is not running after you configure it, then I
have to come up with a fix, but it can be made to go with a one liner
in /etc/rc.local and generating the 3 line ahcp.conf file
I'll fix it for rc8
3) I discovered that txqueuelen 40 was less buggy than 37, and of late
I've been working with some QFQ and SFQ based scripts
that make much longer txqueuelens feasible, and even desirable.
4) Getting the first two nodes to work is hard. Getting a third much
less so. It's really all the backward compatability cruft (DHCP,
firewalling, nat notably) that's the real source of the problem...
I can help on irc, but not til tuesday. There is also a ##babeld on irc
> I have the first of the secondary mesh nodes flashed and ready to go. I
> would like to stick to the default IPs. I'm not clear about what I should do
> next to get this working.
> Andrew
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
next prev parent reply other threads:[~2011-11-28 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 20:43 Andrew Hammond
2011-11-28 3:28 ` Dave Taht [this message]
2011-11-28 3:37 ` Dave Taht
2011-12-12 15:55 ` Juliusz Chroboczek
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='CAA93jw5MuHWVXmztHADzv0HL5eZRD81pif_a=DBxehtgHPG27A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=andrew.george.hammond@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