| |
N9SEO > ROUTES 26.04.26 20:04l 44 Lines 1398 Bytes #10 (0) @ WW
BID : 52469_N9SEO
Read: GUEST
Subj: Re: RE^2: Node routes
Path: ED1ZAC<ED1ZAC<LU4ECL<K1AJD<GB7BED<GB7YEW<W9GM<N9PMO<N9SEO
Sent: 260426/1711Z 52469@N9SEO.#NAR.AR.USA.NOAM LinBPQ6.0.25
On Fri, 24 Apr 26 22:51:00 Z
KQ6UP wrote:
>
> BPQ should have a setting for the routes TTL, so that
> old routes are flushed after specified time. I could
> be wrong, but check the documentation. These are more
> likely static routes.
That is what node obsolescence settings could be used for. (OBSINIT and
OBSMIN)
It works with other things naturally like QUALITY, MINQUAL and
NODESINTERVAL to name a few. Those are all directly related to how
long NETROM nodes live in your system.
I would suggest you explore these settings and get a better
understanding of them. When you do, you might be able to think of a
way to control those peers you have routes with by static routes and
lower qualities or tuning the above.
Other things I like in other stacks like Xrouter is that we can set
QUALITY and MINQUAL per AXIP port. But I guess in BPQ you could
technically define another AXIP port for a peer and do that too. It is
just not a common practice. Everyone tends to lump all their AXIP
peers on one port in BPQ.
The above is more or less how I do it.
1) set the quality and minquality to allow only 2 hops by default
2) set static routes for peers that have larger (than i want) node
tables with a lower quality than the ports default quality.
3) naturally there may be a case to increase said quality for a peer,
such as your own neighboring network nodes.
73
Kayne
n9seo
Read previous mail | Read next mail
| |
