From: Cathryn Mataga <cathryn@junglevision.com>
To: David Ranch <linux-hams@trinnet.net>
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 20:49:17 -0700 [thread overview]
Message-ID: <51DA36BD.7070209@junglevision.com> (raw)
In-Reply-To: <51DA34A9.5070108@trinnet.net>
On 7/7/2013 8:40 PM, David Ranch wrote:
>
> Maybe a way to fix this is with a new parameter, say:
>
> # ax25_name min_obs def_qual worst_heard_qual verbose worst_calced_qual
> 1 5 120 120 0 120
>
> --David
If we're up for new parameters. I suggest a worst_quality_to_send. This
is the issue as I see it. We're getting big lists from the internet,
and the internet partners can handle them, but if you have any RF links,
they'll be bombarded by a giant list of nodes in the broadcast. The
user connects to a 1200 baud TNC, types "NODES" and the table is filled
up with junk from far away. He falls asleep before the list finishes
printing.
We add a 'worst_quality_to_send' and then you can set a worst quality to
send to each specific connection. Set your RF links to 255 and your IP
connections to 1. That way the RF connections can get a tiny list of
only the absolute most important stuff, but internet partners can get
all the distant nodes. This is a pretty easy change to make. It's all
in netromd and doesn't require any mucking with the kernel.
next prev parent reply other threads:[~2013-07-08 3:49 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
2013-07-07 18:45 ` Cathryn Mataga
2013-07-08 3:40 ` David Ranch
2013-07-08 3:49 ` Cathryn Mataga [this message]
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=51DA36BD.7070209@junglevision.com \
--to=cathryn@junglevision.com \
--cc=linux-hams@trinnet.net \
--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 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.