Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: Cathryn Mataga <cathryn@junglevision.com>
Cc: Thomas Osterried <thomas@x-berg.in-berlin.de>,
	linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Netrom:  Quality issue
Date: Sun, 07 Jul 2013 09:59:47 -0700	[thread overview]
Message-ID: <51D99E83.9000604@trinnet.net> (raw)
In-Reply-To: <51D905C2.1000301@junglevision.com>


I agree with Cathryn that this is a "as designed" issue though I'd argue 
we should CHANGE it.  Specifically, the Linux netromd man page says 
"RECEIVED from a routing broadcast" where as

Kantronics KPC3+ - 
http://www.kantronics.com/documents/kpc-3plus_manual_RevD.pdf
"
Page 137
. . .
When K-Net hears neighbor node (A) transmit a node broadcast, it
computes the quality to distant nodes (B, C, D, etc.) contained in that 
broadcast
by using the quality that is assigned to neighbor node (A). If the 
***resultant
computation*** is less than MINQUAL, the distant nodes (B, C, D, etc.) 
are not
added to the nodes table (see QUALITY command).
--


I also looked around for finding the default for the X1J TNC but 
couldn't find a clear citable URL but I believe the default there is 140.

--David




> Err, I don't think it's really a bug.  He's probably got a node coming 
> in at quality 120 and then it does (120 * 120 +128)/256 Maybe update 
> the man page to explain what's going on.
>
>               worstqual     this is the worst quality node received 
> from a routing broadcast that will be added
>                             to our routing table.
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2013-07-07 16:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2013-07-07  6:08           ` Netrom: Quality issue Cathryn Mataga
2013-07-07 16:59             ` David Ranch [this message]
2013-07-07 18:45               ` Cathryn Mataga
2013-07-08  3:40                 ` David Ranch
2013-07-08  3:49                   ` Cathryn Mataga
2013-07-08  7:48                     ` Thomas Osterried
2013-07-08 13:24                       ` Cathryn Mataga
  -- strict thread matches above, loose matches on Subject: below --
2013-07-07 18:36 Brian Rogers

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=51D99E83.9000604@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=cathryn@junglevision.com \
    --cc=linux-hams@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox