From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.3] aaca5b: quagga: add config notes for redistribute kernel a...
Date: Sun, 08 Jul 2012 14:29:56 -0700 [thread overview]
Message-ID: <4ff9fbd4a84eb_1e0619bbae41112a9@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.3
Commit: aaca5b8799f38a4efc95a6e04a9a5ccab524d416
https://github.com/dtaht/ceropackages-3.3/commit/aaca5b8799f38a4efc95a6e04a9a5ccab524d416
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-07-08 (Sun, 08 Jul 2012)
Changed paths:
M net/quagga/files/babeld.conf
Log Message:
-----------
quagga: add config notes for redistribute kernel and rxcost
I use the rxcost parameter to give a mild bias to the 5.x
ghz radios. In the test deployment I found it necessary to bump up
rxcost in proportion to the radio's quality and intent.
so I ended up with rxcost of 1024 and 1023 for wndr3800s
rxcost of 768 for picostation 2HPs (used by users)
rxcost 256 for the directional nanostation M5 backbone
This gave the m5 radios preference and only in case of failure
do things fall back to the 2HPs and wndr3800s. Otherwise
the m5s would prefer a direct connection to a lousy radio
vs a 2 hop or more route that used good radios and ethernet.
I'm not saying this is correct, but it worked.
redistribute kernel works correctly for dhcpv4 inserted default
routes. It does not appear to work correctly for RA inserted
ipv6 routes, nor has it been tested for other forms of ipv6 routes
as yet. WIP.
reply other threads:[~2012-07-08 21:29 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=4ff9fbd4a84eb_1e0619bbae41112a9@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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