Hello everybody!
is it possible to change mystic's default routing?? I want to turn off routing for my hub (uplink) I want/need mystic to send mail from any of my points directly to the node's the nodes boss (ie 123/900) node .. all points should only have to poll their boss node (in my case 340/201) instead of 340/201's uplink

so can it be done??

Micheal

... Mountains should be seen and felt.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

Re: routed netmail
By: Micheal Pierce to All on Sat May 02 2020 20:09:17

all points should only have to poll their boss node (in my case
340/201) instead of 340/201's uplink

this is true... what software is 340/201's uplink running?
if it is what i think it is, 340/201's uplink needs to update to the latest version of their software as soon as possible... if they are running what i think they are running, there were two defects that were fixed in the last week or so that lead this problem...

so two things need to be done and then things will start working properly...

1. 340/201's uplink needs to update their software first.

2. 340/201's points need to poll that uplink system at
least once more after that system updates its software
to gather their netmail that is stuck there.

once those two steps are done, proper netmail routing should just happen...

FWIW: this is true for ALL systems running that BBS software... the defect has been in place for a while and only just discovered, reported, and fixed... i'm specifically not naming the software in question but i'm running it here... that should be the only clue needed ;)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark!

03 May 20 08:50, you wrote to me:

Re: routed netmail
By: Micheal Pierce to All on Sat May 02 2020 20:09:17

all points should only have to poll their boss node (in my case
340/201) instead of 340/201's uplink

this is true... what software is 340/201's uplink running?
if it is what i think it is, 340/201's uplink needs to update to the latest version of their software as soon as possible... if they are running what i think they are running, there were two defects that
were fixed in the last week or so that lead this problem...

so two things need to be done and then things will start working properly...

1. 340/201's uplink needs to update their software first.

2. 340/201's points need to poll that uplink system at
least once more after that system updates its software
to gather their netmail that is stuck there.

once those two steps are done, proper netmail routing should just happen...

FWIW: this is true for ALL systems running that BBS software... the
defect has been in place for a while and only just discovered,
reported, and fixed... i'm specifically not naming the software in question but i'm running it here... that should be the only clue
needed ;)

do you know if the *_run.tgz & *_src.tgz files have been updated?? our uplink just updated approx 2 days ago???

Micheal

... Got my tie caught in the fax... Suddenly I was in L.A.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Other Point - Portland, OR - mansion.dynv6.net: (1:340/201.2)

Re: routed netmail
By: Micheal Pierce to mark lewis on Sun May 03 2020 07:02:26

FWIW: this is true for ALL systems running that BBS software... the
defect has been in place for a while and only just discovered,
reported, and fixed... i'm specifically not naming the software in
question but i'm running it here... that should be the only clue
needed ;)

do you know if the *_run.tgz & *_src.tgz files have been updated??
our uplink just updated approx 2 days ago???

they should have been updated, yes... there was a minor fix posted on 2020 May 02 at 16:04 UTC-0800... there were other more necessary ones posted during the week before that one, though...

aside from those important updates, the only other thing would be if the uplink's routing table is correct... shouldn't need a specific y:our/node.ALL entry but it is possible...

we should probably also move this over to a more appropraite area, too, since it is not directly related to mystic... find me by this name or one of my alts, rampage or wkitty42 ;)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

is it possible to change mystic's default routing?? I want to turn off routing for my hub (uplink) I want/need mystic to send mail from any of
my points directly to the node's the nodes boss (ie 123/900) node .. all points should only have to poll their boss node (in my case 340/201) instead of 340/201's uplink

Yes you can have echo and netmail sent where ever you want them to be sent.

Every entry in Networking > Echomail Nodes has a Route Info field where
routing can be defined. If you're having a specific problem getting it
routed please post more details.

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Sector 7 (1:129/215)

Hello g00r00!

03 May 20 14:15, you wrote to me:

is it possible to change mystic's default routing?? I want to
turn off routing for my hub (uplink) I want/need mystic to send
mail from any of my points directly to the node's the nodes boss
(ie 123/900) node .. all points should only have to poll their
boss node (in my case 340/201) instead of 340/201's uplink

Yes you can have echo and netmail sent where ever you want them to be sent.

Every entry in Networking > Echomail Nodes has a Route Info field
where routing can be defined. If you're having a specific problem
getting it routed please post more details.

problem - mail to other systems points going out via my uplink/hub
340/400 (sbbs). everyrything goes out to 340/400 - want to turn that off so that netmail for zone 1 goes direct to the boss node (ie if I enter a netmail to 1:1.1 mystic would send it 1:1/1)

I think I finally have it setup so that it *should* work

Route 1:340/400 to 1:340/400
Route 21:2/100 to 21:2/100
Route 80:774/1 to 80:774/1
Route 80:774/86.2 to 80:774/86.2
Route 21:2/145.2 to 21:2/145.2
Route 1:340/201.2 to 1:340/201.2
Route 1:340/201.1 to 1:340/201.1
Route 21:1/10 to 21:1/10
Route 21:1/101 to 21:1/101
Route 2:* 3:* 4:* 5:* 6:* 7:* to 1:340/400
Route 21:2/145 21:* to 21:2/100
Route 80:774/86 80:* to 80:774/1

Micheal

... Mountains should be seen and felt.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

problem - mail to other systems points going out via my uplink/hub
340/400 (sbbs). everyrything goes out to 340/400 - want to turn that off so that netmail for zone 1 goes direct to the boss node (ie if I enter a netmail to 1:1.1 mystic would send it 1:1/1)

I am a little confused by the addressing there. I will give you an example:

If you have a point system 123:456/1.1 and you want it to send all Netmail directly to 123:1/1 then you'd go into your Echomail Nodes on your 123:456/1.1 system and create an entry for 123:1/1 (where you want to send your mail) and then set "Route Info: 123:*".

This will tell your point node (123:456/1.1) to send all Netmail for zone 123 through 123:1/1. It will bypass 123:456/1 entirely which I think is what you want to do.

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Sector 7 (1:129/215)

problem - mail to other systems points going out via my
uplink/hub 340/400 (sbbs). everyrything goes out to 340/400 -
want to turn that off so that netmail for zone 1 goes direct to
the boss node (ie if I enter a netmail to 1:1.1 mystic would send
it 1:1/1)

I am a little confused by the addressing there. I will give you an example:

If you have a point system 123:456/1.1 and you want it to send all
Netmail directly to 123:1/1 then you'd go into your Echomail Nodes on
your 123:456/1.1 system and create an entry for 123:1/1 (where you
want to send your mail) and then set "Route Info: 123:*".

This will tell your point node (123:456/1.1) to send all Netmail for
zone 123 through 123:1/1. It will bypass 123:456/1 entirely which I
think is what you want to do.

that is the end results, but what I do not want to do is route the netmail, I want netmail to be direct to in this example 123:1/1 or 124:1/45 or where ever

what your example says, a point system, using binkp.net would have to create an entry each destination.





Micheal


... Mountains should be seen and felt.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

that is the end results, but what I do not want to do is route the netmail, I want netmail to be direct to in this example 123:1/1 or 124:1/45 or where ever

I see what you're saying now. I will look into it when I can, but this is a busy week for me. Sorry I don't have a better answer for you at the moment.

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Sector 7 (1:129/215)

that is the end results, but what I do not want to do is route
the netmail, I want netmail to be direct to in this example
123:1/1 or
124:1/45 or where ever

I see what you're saying now. I will look into it when I can, but
this is a busy week for me. Sorry I don't have a better answer for
you at the moment.

Thank you.
Micheal


... Drive A: format failed, formatting C: instead.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)