From: Cathryn Mataga <cathryn@junglevision.com>
To: Thomas Osterried <thomas@x-berg.in-berlin.de>
Cc: Brian Rogers <n1uro@n1uro.ampr.org>,
linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Netrom
Date: Tue, 09 Jul 2013 19:13:11 -0700 [thread overview]
Message-ID: <51DCC337.9030204@junglevision.com> (raw)
In-Reply-To: <51DCC209.8080006@junglevision.com>
On 7/9/13 7:08 PM, Cathryn Mataga wrote:
> On 7/9/13 3:34 PM, Thomas Osterried wrote:
>> ((255*255)+128)/256 = 254 => It does decrease on the next hop and
>> behind.
>
>
>
> Oops, you're right. So what about this situation.
>
> A -- B -- C
> \ /
> D
>
>
> If A sends a broadcast to B. The link from B back to A should
> decrease the 'obsolete' value with each broadcasts. But can the
> listing loop around from C to D back to B?
>
> But the loop of death should eventually run out of gas when the
> quality hits 0. So, how are all those nodes sticking around for years
> and years. Even if misconfigured, can Netrom do this all by itself.
> Hmm.
> --
Err, if A sends a broadast to B and then disconnects.
next prev parent reply other threads:[~2013-07-10 2:13 UTC|newest]
Thread overview: 21+ 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 ` Netrom on kernel version 3.9.6-200 Cathryn Mataga
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 ` Cathryn Mataga [this message]
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
2004-02-20 18:32 netrom Tom Vavra
2004-02-20 19:12 ` netrom Tomi Manninen
-- strict thread matches above, loose matches on Subject: below --
2002-04-14 5:58 netrom Shane Deering
2002-04-14 7:25 ` netrom Arno Verhoeven
2002-04-14 8:24 ` netrom Shane Deering
2002-04-14 10:11 ` netrom Richard Adams
2002-04-14 12:45 ` netrom Shane Deering
2002-04-14 22:06 ` netrom M Taylor
2002-04-14 22:55 ` netrom Riley Williams
2002-04-15 0:23 ` netrom Walter R Fletcher
2002-04-15 17:55 ` netrom Riley Williams
2002-04-15 19:25 ` netrom Richard Adams
2002-04-15 1:16 ` netrom Shane Deering
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=51DCC337.9030204@junglevision.com \
--to=cathryn@junglevision.com \
--cc=linux-hams@vger.kernel.org \
--cc=n1uro@n1uro.ampr.org \
--cc=thomas@x-berg.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.