From: Cathryn Mataga <cathryn@junglevision.com>
To: n1uro@n1uro.ampr.org, linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Netrom on kernel version 3.9.6-200
Date: Mon, 08 Jul 2013 21:37:23 -0700 [thread overview]
Message-ID: <51DB9383.1050304@junglevision.com> (raw)
In-Reply-To: <1373314487.13641.19.camel@n1uro.ampr.org>
>One thing that X1J/TheNet does that I would like to see linux do is
NOT rebroadcast nodes received on a particular >interface back out on
that same interface.
Hmm, interesting that this would be an issue. The Linux code does
ignore a node if its best neighbor is one's self. I wonder if there's
a degenerate case, if 3 nodes all have their default_quality set to 255,
where the 'neighbor' can all be the third station in the pair, and then
the node broadcast just goes around and around for all eternity because
the quality never decreases at all.
In this equation,
= ((quality * best_quality) + 128) /256;
Could it be that 128 is a mistake, in a world with so many ip based
systems that set default quality at a high value. Without the 128 then a
default_quality of 255 turn a 255 quality node into 254, so the infinite
loop would end eventually. If we don't want to touch the code, maybe
we should discourage anyone from ever setting a def_qual=255. That this
just seems likely to cause problems to me.
next parent reply other threads:[~2013-07-09 4:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130708115635.A4B233700A5@n1uro.ampr.org>
[not found] ` <51DABEDA.8020905@junglevision.com>
[not found] ` <1373314487.13641.19.camel@n1uro.ampr.org>
2013-07-09 4:37 ` Cathryn Mataga [this message]
2013-07-09 12:05 ` Netrom Brian Rogers
2013-07-09 22:34 ` Netrom Thomas Osterried
2013-07-10 2:08 ` Netrom Cathryn Mataga
2013-07-10 2:13 ` Netrom Cathryn Mataga
2013-07-10 3:17 ` Netrom Nate Bargmann
2013-07-10 4:51 ` Netrom Brian Rogers
[not found] ` <1373415104.26592.32.camel@n1uro.ampr.org>
[not found] ` <EB9D8B55-6554-46D8-B0D4-D83F0A1499CC@osterried.de>
[not found] ` <1373460041.4524.33.camel@n1uro.ampr.org>
[not found] ` <6389184E-68DE-4B2D-B955-75E69726E08A@osterried.de>
[not found] ` <1373489422.1842.24.camel@n1uro.ampr.org>
[not found] ` <AE263F20-4B10-465A-BBAE-DB62498DB3CF@osterried.de>
2013-07-17 6:54 ` utf8-patch Cathryn Mataga
2013-07-06 4:19 Netrom on kernel version 3.9.6-200 Cathryn Mataga
2013-07-06 4:43 ` Cathryn Mataga
2013-07-06 5:33 ` Cathryn Mataga
2013-07-06 5:42 ` Cathryn Mataga
2013-07-06 17:24 ` David Ranch
2013-07-06 18:32 ` Cathryn Mataga
2013-07-06 20:28 ` Thomas Osterried
2013-07-07 5:49 ` Cathryn Mataga
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=51DB9383.1050304@junglevision.com \
--to=cathryn@junglevision.com \
--cc=linux-hams@vger.kernel.org \
--cc=n1uro@n1uro.ampr.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