On 29 Feb 2020 at 03:20p, g00r00 pondered and said...

fidopoll 1:123/1234 -> mis poll 1:123/1234

I wonder if there should also be an option to force an IPv4 or IPv6 poll?

I did a test poll to Al just now which used the nodelist lookup to find his details as I don't have him defined as an echomail node.

I have both IPv4 and IPv6 connectivity here and the polling defaulted to an IPv6 outgoing connection

mis poll 21:4/106

┌─ Status
────────────────────────────────────────────────────────────────────┐
│ 21:35:11 Poll BINKP node via address lookup: 21:4/106
│
│ 21:35:11 1-Polling 21:4/106 on slot 1 via BINKP
│
│ 21:35:11 1-Connecting to trmb.ca on port 24554
│
│ 21:35:12 1-Connected by IPV6 to 2600:3C04::F03C:92FF:FE69:8DB0
│
│ 21:35:12 1-System The Rusty MailBox
│
│ 21:35:12 1-SysOp Alan Ianson
│
│ 21:35:12 1-Location Penticton, BC Canada
│
│ 21:35:12 1-Info NDL 115200,CM,XW,IBN
│
│ 21:35:12 1-Info TIME Sun, 1 Mar 2020 00:35:13 -0800
│
│ 21:35:12 1-Mailer binkd/1.1a-101/Linux binkp/1.1
│
│ 21:35:13 1-Info TRF 0 0
│
│ 21:35:13 1-Session ended (0 sent, 0 rcvd, 0 skip)
│
│ 21:35:13 Polled 1 systems
│ └─────────────────────────────────────────────────────────────────────────────┘

perhaps

mis poll [node] -4

mis poll [node] -6

or some setting somewhere in MIS config to enable IPV4+IPV6 etc.. like we
have for servers?

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I did a test poll to Al just now which used the nodelist lookup to find his details as I don't have him defined as an echomail node.

I have both IPv4 and IPv6 connectivity here and the polling defaulted to an IPv6 outgoing connection

When doing a nodelist lookup it will automatically figure out IP options are available for the remote system. It will default to IPV6 when available for the connection.

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 29 Feb 2020, g00r00 said the following...

I plan to keep the original fidopoll in there for a while but initial reports have been very positive so far and the only issue I knew about
was a display issue that I cleaned up today! Who knows maybe it will go earlier than expected if this new version proves to be as stable as it seems already.

Did you mention something about either removing or having less need for the event editor? I'm fairly certain that's about the only place I'd have to
really change these commands.

Accession

--- Mystic BBS v1.12 A46 2020/02/29 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)