Hi g00r00,

I have a couple of nodes setup that I only need to send a file to every now & then, along with a point who polls me to pickup mail.

Would it be possible to add a "Poll: YES|NO" option to the node's binkp settings that would skip it from being included in "./mis poll forced"?

I mean, it doesn't hurt anything that I poll them once an hour (in the case of the point I just get "No BINKP hostname defined for 1:2/3.4" even though the node is set to Export Type: Hold). But it would be more efficient if it were possible to exclude nodes I know I'll never receive anything from.

Thanks for all you do!


Jay

... Everyone has his day, and some days last longer than others.

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

On 13 Sep 2021 at 02:54p, Jay Harris pondered and said...

I have a couple of nodes setup that I only need to send a file to every now & then, along with a point who polls me to pickup mail.
Would it be possible to add a "Poll: YES|NO" option to the node's binkp settings that would skip it from being included in "./mis poll forced"?
I mean, it doesn't hurt anything that I poll them once an hour (in the case of the point I just get "No BINKP hostname defined for 1:2/3.4"
even though the node is set to Export Type: Hold). But it would be more efficient if it were possible to exclude nodes I know I'll never receive anything from.

You could perhaps just set up a different event in Mystic to poll the nodes
you want in the shell line vs asking Mystic to poll all regardless of if
there is mail etc. to exchange with them or not.

I tend to do this so have an event for specific nodes

./mis poll 3:770/1|./mis poll x:xxx/x etc.. on the shell line

You can also run ./mis poll send so that when you export something out Mystic is only going to poll nodes that it has mail for to deliver (so long as the echomail node is not set to HOLD, in which case it would not poll it)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 15 Sep 2021, Paul Hayton said the following...

I tend to do this so have an event for specific nodes
./mis poll 3:770/1|./mis poll x:xxx/x etc.. on the shell line

I thought about doing it this way, but I have too many othernets to poll, so they won't all fit in the shell line. In that case I have to resort to a bash script:

=== Start poll.sh ===
#!/bin/bash
export mysticbbs=/home/pi/mystic
cd /home/pi/mystic
./mis poll 1:229/426
./mis poll 21:3/100
./mis poll 618:500/1
./mis poll 25:25/0
./mis poll 3:770/1
./mis poll 2:221/6
./mis poll 21:1/10
./mis poll 80:774/1
./mis poll 77:3/1
./mis poll 954:895/1
./mis poll send
./mutil mailin.ini
=== End poll.sh ===

But then we also loose any of the efficiency of ./mis poll forced where it would poll all nodes at the same time. Not a big deal I suppose, it's not like FTN networks need to be super high speed. :)

I guess another "nice to have" would be to allow more than one address on ./mis poll line like:

./mis poll 1:2/3 21:1/100 3:770/1

And it would/could poll all three nodes at the same time.

Maybe you would know off the top of your head. Deon = 21:3/100 & 77:3/1, if I poll his fsxNet node would I also get any mail from him for SciNet since I connect to him for both?


Jay

... Old fishermen never die, they just smell that way.

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

Would it be possible to add a "Poll: YES|NO" option to the node's binkp settings that would skip it from being included in "./mis poll forced"?

Yes we could probably make some sort of option for this. I'd have to think it through a little more since the forced command is designed to force a poll of every active node you've configured.

Maybe I can add a new command like "./mis poll uplink" and then have an "Uplink" flag that can be set to Yes which would make Mystic contact every system with that flag enabled.

You can also consider using ./mis poll send" instead which would send mail to nodes that have mail wanting to be sent and ignore the others, then configure your main uplinks to connect via "./mis poll <address>". Those would all work but it isn't exactly what you're asking for.

I'll add this uplink command to the TODO list. I am barely able to touch Mystic at the moment and it'll probably be like that for some time since I am moving and have a lot of things going outside of BBSes, but I can try to get that in sometime.

... Old computers make great boat anchors

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Re: Re: Skip Poll?
By: Jay Harris to Paul Hayton on Wed Sep 15 2021 10:47 am

I guess another "nice to have" would be to allow more than one address on ./mis poll line like:
./mis poll 1:2/3 21:1/100 3:770/1
Maybe you would know off the top of your head. Deon = 21:3/100 & 77:3/1, if I poll his fsxNet node would I also get any mail from him for SciNet since I connect to him for both?

So when I send to you - if you present me all your addresses (which you do), I'll send *all* mail to you.

Here is an example from this morning:

+ 16 Sep 06:31:29 [26524] call to 21:3/110@fsxnet
16 Sep 06:31:29 [26524] trying bbs.nrbbs.net [xxxx:xxxx:xxxx:babe::1002]...
16 Sep 06:31:30 [26524] connected
...
+ 16 Sep 06:31:31 [26524] Remote requests MD mode
- 16 Sep 06:31:31 [26524] SYS Northern Realms
- 16 Sep 06:31:31 [26524] LOC Binbrook, Ontario, Canada
- 16 Sep 06:31:31 [26524] ZYZ Warpslide
- 16 Sep 06:31:31 [26524] TIME Wed, 15 Sep 2021 16:31:32 -0400
- 16 Sep 06:31:31 [26524] VER Mystic/1.12A47 binkp/1.0
- 16 Sep 06:31:31 [26524] BUILD 2021/09/07 03:47:32 Raspberry Pi/32
+ 16 Sep 06:31:31 [26524] addr: 21:3/110@fsxnet
+ 16 Sep 06:31:31 [26524] addr: 77:1/156@scinet
+ 16 Sep 06:31:32 [26524] pwd protected session (MD5)
+ 16 Sep 06:31:32 [26524] sending /fido/mailer/out.04d/42584506.th0 as 42584506.th0 (604)
+ 16 Sep 06:31:32 [26524] sending /fido/mailer/out.015/42584501.th0 as 42584501.th0 (785)
- 16 Sep 06:31:32 [26524] QSIZE 0 files 0 bytes
+ 16 Sep 06:31:32 [26524] sent: /fido/mailer/out.04d/42584506.th0 (604, 604.00 CPS, 77:1/156@scinet)
+ 16 Sep 06:31:32 [26524] sent: /fido/mailer/out.015/42584501.th0 (785, 785.00 CPS, 21:3/110@fsxnet)
+ 16 Sep 06:31:32 [26524] done (to 21:3/110@fsxnet, OK, S/R: 2/0 (1389/0 bytes))
16 Sep 06:31:32 [26524] session closed, quitting...
16 Sep 06:31:32 [26] rc(26524)=0

You'll see I sent you zone 21 (015) and 77 (04d) mail in the same session.

However, when you are polling me, you only present the single address that you are polling for, and thus I'll only send you mail for that address.

If you can present all your addresses, then you can poll me once :)


...δεσ∩
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

On 16 Sep 2021, deon said the following...

So when I send to you - if you present me all your addresses (which you do), I'll send *all* mail to you.
You'll see I sent you zone 21 and 77 mail in the same session.

However, when you are polling me, you only present the single address
that you are polling for, and thus I'll only send you mail for that address.

If you can present all your addresses, then you can poll me once :)

Ah ha! So Mystic has this option to "Hide AKAs" in a node's binkp settings which I had set for some reason. I've turned that off and #'ed out the ./mis poll 77:3/1 line. So now I should be able to poll mail from you in one go.

Imagine all of the bandwidth we'll save! ;)

+ 16 Sep 06:31:29 [26524] call to 21:3/110@fsxnet
16 Sep 06:31:29 [26524] trying bbs.nrbbs.net [xxxx:xxxx:xxxx:babe::1002]... 16 Sep 06:31:30 [26524] connected

Good to see that IPv6 tunnel is working. The native IPv6 I have with my ISP changes the prefix so often that it made it hard to use w/ my DNS provider who doesn't (yet) support dynamic IPV6. I'm now using this OpenVPN tunnel through 6project.org which gives me one static IPV6 address (they could have given me a /80, but I only need the one address).


Jay

... Anything can be made to work if you fiddle with it long enough!

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

Re: Re: Skip Poll?
By: Jay Harris to deon on Wed Sep 15 2021 10:05 pm

Ah ha! So Mystic has this option to "Hide AKAs" in a node's binkp settings which I had set for some reason. I've turned that off and #'ed out the ./mis poll 77:3/1 line. So now I should be able to poll mail from you in one go.

Imagine all of the bandwidth we'll save! ;)

:)

You can (if you want), also change your polling to once or twice a day, which in the normal role should not pick up anything! I have you set to crash, so my hub will keep trying to send stuff to you (and increase the delay between retries if I recall). But in the case that I mess with something, your inbound poll should pick up everything waiting for you. Also, when you write a messages (and have me set up as crash), that also will pick up any mail that I have queued for you.

Good to see that IPv6 tunnel is working. The native IPv6 I have with my ISP changes the prefix so often that it made it hard to use w/ my DNS provider who doesn't (yet) support dynamic IPV6. I'm now using this OpenVPN tunnel through 6project.org
which
gives me one static IPV6 address (they could have given me a /80, but I only need the one address).

I sometimes see you come in over TLS as well - not sure why it toggles between the two - but yes, glad to see the IPv6 connection. I would love to get rid of the IPv4 connection - its just another thing that I have to debug when something doesnt work (which is me tinkering normally :)


...δεσ∩
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

So when I send to you - if you present me all your addresses (which you do), I'll send *all* mail to you.

If you can present all your addresses, then you can poll me once :)

Just to add to what Deon said here, Mystic will present all of your addresses if you ensure that "hide AKAs" is set to No in Mystic's echonode settings for
Deon's system.

It might be more ideal to have Deon set you up to crash and then you can just use "mis poll send" as Mystic generates the send semaphores. Maybe just toss in a single poll once per day for good measure?

Even so, I'll still probably either make one of the following changes in Mystic's setup (open to opinions on which would be best if anyone has them):

A: Uplink flag that you can set Yes/No" and then a "poll uplink" option
B: Change it so that "Hold" export types will not poll in "poll forced" mode

... A SQL query walks into a bar and sees two tables. Asks: 'Can I join you?'

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 16 Sep 2021, g00r00 said the following...

Even so, I'll still probably either make one of the following changes in Mystic's setup (open to opinions on which would be best if anyone has them):

A: Uplink flag that you can set Yes/No" and then a "poll uplink" option
B: Change it so that "Hold" export types will not poll in "poll forced" mode

I would vote for A and/or be able to specify more than address on the command line with ./mis poll, e.g:

./mis poll (address 1) (address 2) (address 3) etc

And when called like that it would poll any specified addresses simultaneity.


Jay

... To remove dust from the eye, pull the eye down over the nose.

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

On 16 Sep 2021, g00r00 said the following...

Just to add to what Deon said here, Mystic will present all of your addresses if you ensure that "hide AKAs" is set to No in Mystic's
echonode settings for Deon's system.

It might be more ideal to have Deon set you up to crash and then you can just use "mis poll send" as Mystic generates the send semaphores. Maybe just toss in a single poll once per day for good measure?

Ok, removed the hourly poll from 21:3/100 & 77:3/1 and will do one just poll per day at ~1am during nightly maintenance just for good measure.

I followed Paul's videos so I have a semaphore setup to do a "./mutil mailout.ini|./mis poll send" when I post a message so those should still go out near real-time.


Jay

... The worst thing about censorship is ██████████.

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

Hello g00r00!

On 16 Sep 2021, g00r00 said the following...

Even so, I'll still probably either make one of the following changes in Mystic's setup (open to opinions on which would be best if anyone has them):

A: Uplink flag that you can set Yes/No" and then a "poll uplink" option
B: Change it so that "Hold" export types will not poll in "poll forced" mode

I'd vote for A, as a forced poll might be because one wants to deliver/clear all mail waiting for a node for some reason.

I know ifcico (as an example) offers "Hold" (really hold) and "NoHold" (send held packets if we initiated the session). Not sure how binkd handles things like this.

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

On 16 Sep 2021 at 12:25p, g00r00 pondered and said...

A: Uplink flag that you can set Yes/No" and then a "poll uplink" option

I'd go with this option. Good to still have an option for force poll
everything

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 16 Sep 2021 at 01:28p, Jay Harris pondered and said...

I would vote for A and/or be able to specify more than address on the command line with ./mis poll, e.g:

./mis poll (address 1) (address 2) (address 3) etc

Perhaps a way forward if g00r00 opts to look at this would be to be able to create a special ini or txt file that contains the list of nodes and or syntax in it that is read by mis poll and then executed as a poll?

Ideally it could use some wildcard notation or certain keywords (like FastEcho does in it's routing file) to simplify which systems are polled when the txt file is read my mis poll.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I know ifcico (as an example) offers "Hold" (really hold) and "NoHold" (send held packets if we initiated the session). Not sure how binkd handles things like this.

Yeah it am thinking it may just be that Mystic should not be polling any node marked as "Export type: Hold" even when forced is used, unless the address itself is supplied on the command line "mis poll 1:1/1"

I did like someone's suggestion about being able to supply multiple addresses on the poll command like "mis poll 1:1/1 10:1/1" etc so I might look into doing that as well.

It seems the few responses have suggested either option A or this command line change. Maybe both would be good!? I'll have to look at the code when I can get some time and see how easy it'd be to do this.

... Error, no Keyboard - Press F1 to Continue.

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

A: Uplink flag that you can set Yes/No" and then a "poll uplink" opti

I'd go with this option. Good to still have an option for force poll everything

Thanks! This seems like the way the community wants it to go, so it shall
have to be!

... One tequila, two tequila, three tequila, floor.

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

./mis poll (address 1) (address 2) (address 3) etc

Perhaps a way forward if g00r00 opts to look at this would be to be able to create a special ini or txt file that contains the list of nodes and
or syntax in it that is read by mis poll and then executed as a poll?

Ideally it could use some wildcard notation or certain keywords (like FastEcho does in it's routing file) to simplify which systems are polled when the txt file is read my mis poll.

Maybe a fusion of both those ideas.

The POLL command could accept multiple addresses but also accept wildcards too or something. Like "mis poll 1:*/1 21:*" or something along those lines. Although maybe this is overkill?

... No one knows what's next, but everybody does it.

--- Mystic BBS v1.12 A47 2021/08/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 20 Sep 2021, g00r00 said the following...

It seems the few responses have suggested either option A or this
command line change. Maybe both would be good!? I'll have to look at the code when I can get some time and see how easy it'd be to do this.

Both sound like good additions, I think!

This would make it easy to poll uplinks, and for those who want to poll multiple systems, it can be done in one go (which adds to the "parallelism concept" of mis poll).

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

On 20 Sep 2021 at 01:00p, g00r00 pondered and said...

Maybe a fusion of both those ideas.
The POLL command could accept multiple addresses but also accept
wildcards too or something. Like "mis poll 1:*/1 21:*" or something
along those lines. Although maybe this is overkill?

It may be but I was thinking along those lines too... being able to use the same notation as the route info line in echomail node config... but that said it could be dangerous as someone could launch quite a massive polling effort
in error if they were not careful.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 22 Sep 2021, Paul Hayton said the following...

It may be but I was thinking along those lines too... being able to use the same notation as the route info line in echomail node config... but that said it could be dangerous as someone could launch quite a massive polling effort in error if they were not careful.

I was thinking the same thing, you just know someone out there would be polling 1:* 2:* 3:* 4:* hourly. Some sanity checking would need to be built in for sure.

Maybe limit wildcards to the node level only? (e.g 21:3/*)


Jay

... Don`t force it, get a larger hammer.

--- Mystic BBS v1.12 A47 2021/09/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)