OK onto this lovely file next... I'm going to have to tackle a standalone
link file (or start it) after my dinner.

Do I need to explicitly state a route line for all defined links?

In an example I see

route normal noroute 2:280/1027
route normal noroute 2:280/5555

I'm picking they are known/defined links in HPT link file that need this kind of coverage?

Does the route file work top down? When does HPT decide it can satisfy the routing?

Assuming a few things I'm picking something like this?

route normal noroute 21:1/100
route normal noroute 21:2/100
route normal noroute 21:3/100
route normal noroute 21:4/100
route normal noroute 21:5/100

route normal 21:1/100 21:1/*
route normal 21:2/100 21:2/*
route normal 21:3/100 21:3/*
route normal 21:4/100 21:4/*
route normal 21:5/100 21:5/*


I'm also wondering about how best to handle routed netmail for point systems
on a known link?

e.g. incoming netmail for 21:1/101.5

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

OK onto this lovely file next... I'm going to have to tackle a
standalone link file (or start it) after my dinner.

Do I need to explicitly state a route line for all defined links?

Yes, if there is no route for a node netmail for them will be skipped
over and untouched. Each of your links should have a route line something like...

route <flavour> <next hop> <target> [target ...]

route crash 1:153/250 1:153/250.*

route normal noroute 2:280/1027
route normal noroute 2:280/5555

I'm picking they are known/defined links in HPT link file that need
this kind of coverage?

I have a few lines like the above for nodes not setup as links. Mail for
those nodes whether they originate here or not be packed in the outbound directly to the node.

Does the route file work top down? When does HPT decide it can
satisfy the routing?

That is what it looks like to me, and the way I have always used the
route file. I believe it will take the first route found for a node so
all of my catch all routes like 1:* 2:* 3:* 4:* etc are down below my
links.

Assuming a few things I'm picking something like this?

route normal noroute 21:1/100
route normal noroute 21:2/100
route normal noroute 21:3/100
route normal noroute 21:4/100
route normal noroute 21:5/100

route normal 21:1/100 21:1/*
route normal 21:2/100 21:2/*
route normal 21:3/100 21:3/*
route normal 21:4/100 21:4/*
route normal 21:5/100 21:5/*

Yes, I would do it that way. I think the first block (with noroute) is
undeeded since the second block will cover it. It won't hurt anything.

I'm also wondering about how best to handle routed netmail for
point systems on a known link?

e.g. incoming netmail for 21:1/101.5

If 21:1/101 is a link (I think it is as a matter of fact!) I would add .*
after the node number.

All of my links in net 153 look like this..

route crash 1:153/250 1:153/250.*

Those are all listed above routes for other nets/regions/zones

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Dec 2019, Avon said the following...

Do I need to explicitly state a route line for all defined links?

I would say yes, just to make sure the routing is correct.

Does the route file work top down? When does HPT decide it can satisfy
the routing?

It does work top down. What I have done in CRBBS, is set it up like:

route crash 80:505/3 80:505/3
route crash 80:505/6 80:505/6
route crash 80:505/7 80:505/7
route crash 80:774/1 80:*

That way, if a netmail message comes in for a node that I'm feeding, it will get sent to their node, otherwise, it will be sent to my uplink.

route normal noroute 21:1/100
route normal noroute 21:2/100
route normal noroute 21:3/100
route normal noroute 21:4/100
route normal noroute 21:5/100

This setup doesn't look familiar. I'll have to look into that a bit more.

route normal 21:1/100 21:1/*
route normal 21:2/100 21:2/*
route normal 21:3/100 21:3/*
route normal 21:4/100 21:4/*
route normal 21:5/100 21:5/*

This looks closer to what I've been using. What I was looking at doing here,
is set it up something like:

route crash 21:4/101 21:4/101
route crash 21:4/102 21:4/102
...etc...
route crash 21:1/100 21:1/*
route crash 21:2/100 21:2/*
route crash 21:3/100 21:3/*
route crash 21:5/100 21:5/*

I'm also wondering about how best to handle routed netmail for point systems on a known link?

e.g. incoming netmail for 21:1/101.5

That is also something I haven't worked with with HPT. I'll have to do some research...

I'm thinking the lines for each node could read:

route crash 21:4/101 21:4/101.*

That way, anything that came in for a point, or the main hub would still be sent to that node.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

OK onto this lovely file next... I'm going to have to tackle a
standalone link file (or start it) after my dinner.

I should also mention RouteFile..

I don't use this keyword but it is a "thing" that you may need at some
point for attached files depending on what goes on at your node.

It's got nothing to do with tic files.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 30 Nov 2019 at 09:45p, Black Panther pondered and said...

It does work top down. What I have done in CRBBS, is set it up like:

route crash 80:505/3 80:505/3
route crash 80:505/6 80:505/6
route crash 80:505/7 80:505/7
route crash 80:774/1 80:*

Thanks

route normal noroute 21:5/100

This setup doesn't look familiar. I'll have to look into that a bit more.

route normal 21:1/100 21:1/*

This looks closer to what I've been using. What I was looking at doing here, is set it up something like:

route crash 21:4/101 21:4/101
route crash 21:4/102 21:4/102

I think it seems a but nutty to have to say netmail for a known link needs to be routed to it. I have a hunch the noroute may be the better option. But the fact you need to state it at all for a known link seems a bit of a bummer to
me :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 30 Nov 2019 at 08:35p, Al pondered and said...

Do I need to explicitly state a route line for all defined links?

Yes, if there is no route for a node netmail for them will be skipped
over and untouched. Each of your links should have a route line something like...

route <flavour> <next hop> <target> [target ...]

route crash 1:153/250 1:153/250.*

ouch... ok thanks and good to know.

Yes, I would do it that way. I think the first block (with noroute) is undeeded since the second block will cover it. It won't hurt anything.

OK thanks Al. :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 30 Nov 2019 at 09:51p, Al pondered and said...

OK onto this lovely file next... I'm going to have to tackle a standalone link file (or start it) after my dinner.

I should also mention RouteFile..

Yep seen this also, thanks :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On Sat, 30 Nov 2019 20:35:30 -0800
"Al -> Avon" <0@106.4.21> wrote:

Do I need to explicitly state a route line for all defined
links?

Yes, if there is no route for a node netmail for them will be skipped
over and untouched. Each of your links should have a route line
something like...

route <flavour> <next hop> <target> [target ...]

route crash 1:153/250 1:153/250.*

Is there really no smarter way to do this?

---
* Origin: (21:1/151)

route <flavour> <next hop> <target> [target ...]

route crash 1:153/250 1:153/250.*

I often wonder about that when looking at the route config. There may
very well be a better way but I haven't found it yet.

When it comes to hpt in most cases you have to tell it what to do and
when to do it. I suppose that is good in some ways, but it sure involves
a lot of typing. Gives me lots of opportunities for typos.. ;)

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Sun, 1 Dec 2019 02:05:14 -0800
"Al -> Oli" <0@106.4.21> wrote:

route <flavour> <next hop> <target> [target ...]

route crash 1:153/250 1:153/250.*

I often wonder about that when looking at the route config. There may
very well be a better way but I haven't found it yet.

What about

route crash no-route 21:1/*

?

The documentation needs better examples.

---
* Origin: (21:1/151)

Hello, Oli.
On 12/1/19 6:23 AM you wrote:

On Sun, 1 Dec 2019 02:05:14 -0800 "Al -> Oli" <0@106.4.21> wrote:

route <flavour> <next hop> <target> [target ...] route crash
1:153/250 1:153/250.*

I often wonder about that when looking at the route config. There
may very well be a better way but I haven't found it yet.

I'm late to the game.. what is hpt?

What about route crash no-route 21:1/* ? The documentation needs
better examples. --- * Origin: (21:1/151)

--
Best regards!
Posted using Hotdoged on Android

--- Mystic BBS/NNTP v1.12 A43 2019/03/02 (Linux/64)
* Origin: The ByteXchange BBS | bbs.thebytexchange.com (21:1/107)

I often wonder about that when looking at the route config.
There may very well be a better way but I haven't found it yet.

What about

route crash no-route 21:1/*

That might work, it looks like it will.

My own habbit has been to add a rule for each link and I would have to
struggle with the devil at this point to get away from that.

For a hub with many links the above might be the way to go.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I'm late to the game.. what is hpt?

hpt is part of the husky project. A multi platform tosser. The project
includes htick to toss files and a number of related utilities.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I'm late to the game.. what is hpt?

Husky Potty Training :)

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: Scrawled in haste at The Lower Planes (21:3/101)

On 01 Dec 2019 at 12:42p, Al pondered and said...

What about
route crash no-route 21:1/*

That might work, it looks like it will.

My head is starting to hurt with these statements.

Wouldn't this impact on some of the route statements I was posting the other day?

e.g. route crash 21:1/100 21:1/*

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

My head is starting to hurt with these statements.

I understand!

Wouldn't this impact on some of the route statements I was posting
the other day?

e.g. route crash 21:1/100 21:1/*

That does look workable. 21:1/100 is the next hop and 21:1/* is the
target.

Keep in mind I am not a hub so I don't have a hubs perspective on things.
My brain tends to think smaller.

It is OK (and it's what I do) to write your route statements in a way
that works for you and is easy to follow.

It's also something that you can update as you go.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Dec 2019 at 03:25p, Al pondered and said...

I understand!

:)

Keep in mind I am not a hub so I don't have a hubs perspective on things. My brain tends to think smaller.

It is OK (and it's what I do) to write your route statements in a way
that works for you and is easy to follow.

It's also something that you can update as you go.

Yep, understood. It's lunchtime Monday here, I'll pick this up again tonight. Setting up the routing file is the least of my worries. The Links file is
going to take some time.

The way you and Dan approach it is quite different. I'd need to see a bit of Dans Links file to understand it completely. But he seems to define a link as
a network with a lot of settings in his general file, not sure how that name then relates to links, etc.

I'll figure it out in time.

This work to date has been helpful, I think I will try to set up HPT for 3:770/1 concurrently with my work on NET 1 in fsxNet.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Yep, understood. It's lunchtime Monday here, I'll pick this up
again tonight. Setting up the routing file is the least of my
worries. The Links file is going to take some time.

I tend to worry more about the routes. I find I add a new link and that's
all there is to that. It doesn't need any more from me, as long as I
avoid typos.. :)

The way you and Dan approach it is quite different. I'd need to see
a bit of Dans Links file to understand it completely. But he seems
to define a link as a network with a lot of settings in his general
file, not sure how that name then relates to links, etc.

Sounds interesting. I wouldn't mind seeing or reading more on what Dan
has done. I am always open to different ways of doing things have have
learned most of my own ways of doing what I do from others over the
years.

I'm going to post my configs in a bit here, excluding the areas file they
are 6 or 7 Kb, and I'll just post a snippit of my areas file since it's
just more of the same.

I'll do that in the FSX_BBS area.

I think if we put our heads together and see how others do things we may
be able to improve our own configs. Whenever I look at my config I always wonder if there are better ways..

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 02 Dec 2019, Avon said the following...

The way you and Dan approach it is quite different. I'd need to see a
bit of Dans Links file to understand it completely. But he seems to
define a link as a network with a lot of settings in his general file,
not sure how that name then relates to links, etc.

That's how I have it set up on CRBBS. Basically, it's due to each link being part of a different network.

The config that I've been working on for fsxNet Hub 4, is a lot different,
and also in one file. Each link consists of only 4 or 5 lines, and the rest
of the setting handled in the LinkDefaults section.

This work to date has been helpful, I think I will try to set up HPT for 3:770/1 concurrently with my work on NET 1 in fsxNet.

Once you have a working config, it's actually not too bad to create another
one for a different system/network. I've adopted and modified my original config file from a few years ago, from Windows, to Linux, and now back to Windows. :)


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 01 Dec 2019, Al said the following...

Sounds interesting. I wouldn't mind seeing or reading more on what Dan
has done. I am always open to different ways of doing things have have learned most of my own ways of doing what I do from others over the
years.

I'll actually post a copy of my config that I just about have ready for the
Hub 4 system. It's not as complicated as the one running on CRBBS. I feel it would help us all out as well.

I'm going to post my configs in a bit here, excluding the areas file they are 6 or 7 Kb, and I'll just post a snippit of my areas file since it's just more of the same.

I'll have this one ready in a day or so. Once it's in place I'll post it as well. This ones not too bad, as it's all in one file, and only 565 lines... :)


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Husky Potty Training :)

Lol, probably.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The ByteXchange BBS | bbs.thebytexchange.com (21:1/107)

Hi Paul

Having trouble with bre all fine till latest brenode i must have samething wrong with it so could you please put one in my inbound dir please

Ian S 2nd Choice Core Mystic Nz

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: 2nd Choice Core|New Zealand (21:1/152)

On 03 Dec 2019 at 09:32a, Sneaky pondered and said...

Hi Paul

Having trouble with bre all fine till latest brenode i must have samething wrong with it so could you please put one in my inbound dir please

Yep will do Ian. I did create a problem with the file I sent out but did send out another one. Will send this to you when I get home.

Thanks, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hi Paul

Yep will do Ian. I did create a problem with the file I sent outbut did send out another one. Will send this to you when I get home.

Okay, Thank you

Ian S 2nd Choice Core Mystic Nz
Mystic Web site Http://2ndchoicecore.nz:81

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: 2nd Choice Core|New Zealand (21:1/152)

On 03 Dec 2019 at 05:43p, Sneaky pondered and said...

Yep will do Ian. I did create a problem with the file I sent outbut d send out another one. Will send this to you when I get home.

Okay, Thank you

On it's way to you now good sir...

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hello nugax,

I often wonder about that when looking at the route config. There
may very well be a better way but I haven't found it yet.

I'm late to the game.. what is hpt?

Hpt stands for Highly Portable Tosser which is a full-featured FTN tosser.

HPT is part of a complete freeware group of Fidonet applications.

Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: FSXNET: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On Sun, 1 Dec 2019 13:35:58 -0600
"Jeff Smith -> nugax" <0@128.1.21> wrote:

Hpt stands for Highly Portable Tosser which is a full-featured FTN tosser.

HPT is part of a complete freeware group of Fidonet applications.

it is open source software, not freeware :)

---
* Origin: (21:1/151)

Avon Sn> Av> Yep will do Ian. I did create a problem with the file I sent outbut d

send out another one. Will send this to you when I get home.

Okay, Thank you

On it's way to you now good sir...

Got it thank you.

Ian S 2nd Choice Core Mystic Nz
www.2ndchoicecore.nz:81

--- MultiMail/Win v0.52

Hello Oli,

On Sun, 1 Dec 2019 13:35:58 -0600
"Jeff Smith -> nugax" <0@128.1.21> wrote:

Hpt stands for Highly Portable Tosser which is a full-featured FTN
tosser.
HPT is part of a complete freeware group of Fidonet applications.

it is open source software, not freeware :)

Open source software that I was not required to pay any monies to acquire, install, or use.

My understanding of "Freeware" is software that is available free of charge. Hence my use of the term "Freeware".

Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: FSXNET: The Ouija Board - bbs.ouijabrd.net (21:1/128)