Why isn't mis poll not doing it's job? I read somewhere on here that it wouldn't work on bookworm pi but worked on bullseye pi. I find it hard to believe that everyone polling is using outdated os.

POLL v1.12 A48 2023/01/15 Fri, Oct 31 2025 (loglevel 2)
Polling all nodes of session type ALL
Queued 2 files (4,089 bytes) for 21:3/100
1-Polling 21:3/100 on slot 1 via BINKP
1-DEBUG ConnectMode=0
1-Connecting to n3.z21.bbs.dege.au on port 24554
Polled 1 systems

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: mis poll not polling
By: freq to All on Fri Oct 31 2025 12:46 pm

Howdy,

POLL v1.12 A48 2023/01/15 Fri, Oct 31 2025 (loglevel 2)
Polled 1 systems

Increase the log level, it should provide more useful information.


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Increase the log level, it should provide more useful information.

I ran the log level on 1, 2 and 3. they all gave same output

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: mis poll not polling
By: freq to deon on Sat Nov 01 2025 01:39 am

Howdy,

Increase the log level, it should provide more useful information.

I ran the log level on 1, 2 and 3. they all gave same output

So I didnt see the information that I expected with loglevel 3.

Here is an example of something that I played with about a month ago.

--------------------- POLL v1.12 A48 2023/01/15 Wed, Oct 01 2025 (loglevel 3) + 2025.10.01 22:37:16 Poll BINKP node via address lookup: 10:999/1
+ 2025.10.01 22:37:16 1-Polling 10:999/1 on slot 1 via BINKP
+ 2025.10.01 22:37:16 1-DEBUG ConnectMode=0
+ 2025.10.01 22:37:16 1-Connecting to 172.31.20.48 on port 24554
+ 2025.10.01 22:37:16 1-Using address 172.31.20.48
+ 2025.10.01 22:37:16 1-Connected by IPV4 to 172.31.20.48
+ 2025.10.01 22:37:16 1-S: NUL SYS New Mystic BBS
+ 2025.10.01 22:37:16 1-S: NUL ZYZ Sysop Name Here
+ 2025.10.01 22:37:16 1-S: NUL TIME Wed, 01 Oct 2025 22:37:16 0000
...
+ 2025.10.01 22:37:17 1-Mailer clrghouz/dev binkp/1.1
+ 2025.10.01 22:37:17 1-R: ADR 10:999/900.0@private 10:999/0.0@private
+ 2025.10.01 22:37:17 1-S: PWD
+ 2025.10.01 22:37:17 1-R: ERR You must support MD5 auth to talk to me
+ 2025.10.01 22:37:17 1-Authorization failed
+ 2025.10.01 22:37:18 Polled 1 systems

IE: Your log didnt show the "Using address...", nor the reason for the failed session.

If your loglevel 3 still shows the same output, then I would suggest your mystic is not resolving addresses (which is the next item in the log, that I see in my log, but not in yours).


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

If your loglevel 3 still shows the same output, then I would suggest your mystic is not resolving addresses (which is the next item in the log,
that I see in my log, but not in yours).

So how does one get mystic to resolve addresses?

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

If your loglevel 3 still shows the same output, then I would suggest mystic is not resolving addresses (which is the next item in the log, that I see in my log, but not in yours).

So how does one get mystic to resolve addresses?

I added cloudflare and google to DNS on bookworm OS. It didn't fix it. I tried pinging the hub and got no response.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: mis poll not polling
By: freq to deon on Sun Nov 02 2025 01:43 am

Howdy,

So how does one get mystic to resolve addresses?

Mystic (or apps in general), dont resolve addresses, the OS does.

So does host (or nslookup, or whatever the resolver client is), resolve n3.z21.bbs.dege.au? It should resolve to 139.99.135.199.

# host n3.z21.bbs.dege.au
n3.z21.bbs.dege.au is an alias for clrghouz.bbs.dege.au.
clrghouz.bbs.dege.au is an alias for ip4.bbs.dege.au.
ip4.bbs.dege.au has address 139.99.135.199
ip4.bbs.dege.au has IPv6 address 64:ff9b::8b63:87c7


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: mis poll not polling
By: freq to deon on Sun Nov 02 2025 02:32 am

Howdy,

I added cloudflare and google to DNS on bookworm OS. It didn't fix it. I tried pinging the hub and got no response.

The host that the hub runs on doesnt respond to pings - so dont think of that as the issue.

If that is all the logging shows you (at maximum log), and your OS is resolving the address correctly, then I'm not sure what your issue might be.

Could be a routing issue, but if your host can ping 1.1.1.1, then I dont think that would be the issue either.


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

So does host (or nslookup, or whatever the resolver client is), resolve n3.z21.bbs.dege.au? It should resolve to 139.99.135.199.

Yes, it resolves to 139.99.135.199 using nslookup and dig.
I can telnet to 139.99.135.199:24554 and connect.
I did a traceroute and it stops after about 15 hops at 72.251.0.8
I cannot ping 72.251.0.8.
I can get on my phone (different network) and ping 139.99.135.199 no problem. The BBS is on ethernet via static VPN cisco router.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

The host that the hub runs on doesnt respond to pings - so dont think of that as the issue.

As stated in last reply, I can ping the hub from my phone.

How can I copy and paste my traceroute results to here?
I can retype some of it i suppose...

snippet (notice the time jump in chicago)

9 66.110.15.38 89.724 ms 89.846 ms *
10 66.110.15.37 304.703 ms * *
11 216.6.52.18 290.708 ms 278.893 ms
12 * * *
13 * 64.86.26.36 302.380 ms
14 * * 64.86.26.39 302.334 ms
15 * * *
16 * 72.251.0.8 334.089 ms *
17 * * *
18 * * *
19 * * *

(all the way to 30 hops * * *)

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

The host that the hub runs on doesnt respond to pings - so dont think of that as the issue.

Yeah, you are right thought my net-analyzer app was pinging it, but then i tried ping app and it wouldn't ping.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: mis poll not polling
By: freq to deon on Sun Nov 02 2025 07:24 am

The host that the hub runs on doesnt respond to pings - so dont think of that as the issue.

As stated in last reply, I can ping the hub from my phone.

Unlikely, as the hub doesnt respond to pings.

But in your previous reply you stated that you could telnet to the hub's binkp port - so that validates you have network connectivity and your host is resolving addresses OK.

So I suggest you give a higher log level than 2, because the hub has many mystic nodes feeding from it, so there is something a miss here...

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.

"mis poll forced" from a command line will do it.

|11ogg
|11SysOp, Altair IV BBS
|11altairiv.ddns.net:2323

... They say there's always one weirdo on the bus, but I couldn't find them!

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (21:2/147)

So I suggest you give a higher log level than 2, because the hub has many mystic nodes feeding from it, so there is something a miss here...

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.

Been polling with mis poll forced, then tried mis poll send, also mis poll 21:3/100 and mis poll n3.z21.bbs.dege.au manually and have mis poll send setup hourly in events.

Here is a snippet from level 3 logs

--------------------- POLL v1.12 A48 2023/01/15 Sun, Nov 02 2025 (loglevel 3) + 2025.11.02 16:21:04 Poll BINKP node via address lookup: 21:3/100
+ 2025.11.02 16:21:04 Queued 2 files (4,089 bytes) for 21:3/100
+ 2025.11.02 16:21:04 1-Polling 21:3/100 on slot 1 via BINKP
+ 2025.11.02 16:21:04 1-DEBUG ConnectMode=0
+ 2025.11.02 16:21:04 1-Connecting to n3.z21.bbs.dege.au on port 24554
+ 2025.1101:12 Polled 1 systems

Shift-Ins in draw mode pastes - just figured that out.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)