I've updated the A36 pre-releases with today's code.

In this one, I have switched FIDOPOLL over to use the BINKP from MIS2 so it needs testing. This is the first step to enabling IPV6 in FidoPoll as MIS2 BINKP uses the newer socket engine that is capable of SSL and IPV6.

www.mysticbbs.com/downloads/prealpha

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/29/17, g00r00 pondered and said...

I've updated the A36 pre-releases with today's code.

In this one, I have switched FIDOPOLL over to use the BINKP from MIS2 so it needs testing. This is the first step to enabling IPV6 in FidoPoll
as MIS2 BINKP uses the newer socket engine that is capable of SSL and IPV6.

Cool :) Looks like I know what I'll be doing tonight when I get home :)

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/29/17, g00r00 pondered and said...

www.mysticbbs.com/downloads/prealpha

--- Mystic BBS v1.12 A36 (Windows/32)

I wonder if you should not add some minor ver number to these releases so
when we use them it's clear which one is which... if they all say A36 then we do risk getting things muddled if someone reports something amiss with a version of A36 that may be 2-3 builds ago.

Maybe these should have been A35.1, A35.2 etc?

The way I know is that you update the whatsnew.txt each time and I always
copy those docs into my working system when I update the exe files etc. at
the same time.

It's probably not a biggy right now as the number involved in providing this iterative feedback is quite small and we're all experienced enough to know
not to bollocks it up :)

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/29/17, g00r00 said the following...

In this one, I have switched FIDOPOLL over to use the BINKP from MIS2 so it needs testing. This is the first step to enabling IPV6 in FidoPoll
as MIS2 BINKP uses the newer socket engine that is capable of SSL and IPV6.

Alright. I just installed the new pre-release, and polled my game server system, which also handles my newsgroups coming in. It is running Mystic 1.12A32.

It was showing quite a few 'Socket Write error 25', and 'Socket read error
25' messages...

snip <=-

Oct 29 17:41:15 FIDOPOLL Version 1.12 A36
Oct 29 17:41:15 Scanning 195:195/1
Oct 29 17:41:15 Queued 0 files (0 bytes) to 195:195/1
Oct 29 17:41:15 Polling BINKP node 195:195/1
Oct 29 17:41:15 Connecting to castlerockbbs.com:24555
Oct 29 17:41:15 Connected
Oct 29 17:41:15 Authorization State: 1 HH:0 NH:1
Oct 29 17:41:15 Socket Write error 25
Oct 29 17:41:15 Sent: NUL SYS Castle Rock BBS
Oct 29 17:41:15 Socket Write error 25
Oct 29 17:41:15 Sent: NUL ZYZ Black Panther
Oct 29 17:41:15 Socket Write error 25
Oct 29 17:41:15 Sent: NUL VER Mystic/1.12A36 binkp/1.0
Oct 29 17:41:15 Sent: ADR 1:317/3@fidonet 21:1/186@fsxNET 24:150/1@sportnet 24:150/2@sportnet 44:505/0@dorenet 46:1/181@agoranet 80:505/0@retronet 195:1/101@castlnet 432:1/118@vkradio 316:36/17@whispnet 9:91/27@survnet 24:150/0@sportnet 42:31/0@sfnet 42:31/1@sfnet 195:1/100@castlnet 700:100/7@spooknet
Oct 29 17:41:15 Authorization State: 2 HH:0 NH:1
Oct 29 17:41:16 Socket read error 25
Oct 29 17:41:16 Recv: NUL OPT CRAM-MD5-915291a19ceee3827bdc8f03c373b2d6
Oct 29 17:41:16 Authorization State: 2 HH:1 NH:0
Oct 29 17:41:16 Received challenge (915291a19ceee3827bdc8f03c373b2d6)
Oct 29 17:41:16 Recv: NUL SYS CRBBS Linux Game Server
Oct 29 17:41:16 System: CRBBS Linux Game Server
Oct 29 17:41:16 Recv: NUL ZYZ Black Panther
Oct 29 17:41:16 Info: ZYZ Black Panther
Oct 29 17:41:16 Recv: NUL VER Mystic/1.12A32 binkp/1.0
Oct 29 17:41:16 Recv: ADR 316:36/19@whispnet 195:195/1@castlnet 24:150/5@sportnet 21:1/186.2@fsxnet 1:317/3.1@fidonet
Oct 29 17:41:16 Socket Write error 25
Oct 29 17:41:16 Sent: PWD CRAM-MD5-88d6e0a100a48375fd07d141c0d0d6ce
Oct 29 17:41:16 Authorization State: 5 HH:0 NH:1
Oct 29 17:41:16 Socket read error 25
Oct 29 17:41:16 Recv: OK secure
Oct 29 17:41:16 Authorization State: 5 HH:1 NH:0
Oct 29 17:41:17 State RxS:WaitFile TxS:NextFile HH:0 NH:1
Oct 29 17:41:17 Socket Write error 25
Oct 29 17:41:17 Sent: EOB
Oct 29 17:41:17 Socket read error 25
Oct 29 17:41:17 Recv: FILE 11aa364b.pkt 281 1509298642 0
Oct 29 17:41:17 State RxS:WaitFile TxS:Done HH:1 NH:0
Oct 29 17:41:17 Receiving: 11aa364b.pkt (281 bytes)
Oct 29 17:41:17 State RxS:GetData TxS:Done HH:0 NH:1
Oct 29 17:41:17 Socket read error 25
Oct 29 17:41:17 State RxS:GetData TxS:Done HH:1 NH:0
Oct 29 17:41:17 Received: 281 of 281
Oct 29 17:41:17 Socket Write error 25
Oct 29 17:41:17 Sent: GOT 11aa364b.pkt 281 1509298642
Oct 29 17:41:17 State RxS:WaitFile TxS:Done HH:0 NH:1
Oct 29 17:41:17 Socket read error 25
Oct 29 17:41:17 Recv: EOB
Oct 29 17:41:17 State RxS:WaitFile TxS:Done HH:1 NH:0
Oct 29 17:41:17 Session complete (0 sent, 1 rcvd, 0 skip)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A36 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I wonder if you should not add some minor ver number to these releases so when we use them it's clear which one is which... if they all say A36
then we do risk getting things muddled if someone reports something
amiss with a version of A36 that may be 2-3 builds ago.

It really hasn't been too much of an issue, but I have just made some changes to include the compile date in the tear lines, and also printed to the screen when you run "mystic -ver".

You should see it in this message!

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/29/17, g00r00 pondered and said...

It really hasn't been too much of an issue, but I have just made some changes to include the compile date in the tear lines, and also printed
to the screen when you run "mystic -ver".

You should see it in this message!

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)

I do :) Thanks... call me a worrying old women if like ;-P I just wanted to ensure we're all using the same ver :)

Will do some updating shortly.

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/29/17, g00r00 pondered and said...

I've updated the A36 pre-releases with today's code.

In this one, I have switched FIDOPOLL over to use the BINKP from MIS2 so it needs testing. This is the first step to enabling IPV6 in FidoPoll
as MIS2 BINKP uses the newer socket engine that is capable of SSL and IPV6.

I updated and found fidopoll was unreliable. It would poll 2-4 nodes then
pause after a session ended with a node. I had to ctrl-c to close it, remove the semaphore and start it again. It would run 4-8 nodes and then stop.

So this is with fidopoll running on win7 32 with binkP running on MIS for
IPv4 and MIS2 running BinkP on IPv6 only.

I had to drop the last version of Fidopoll back in to the HUB as it was too unreliable but have left the rest of the updated binaries in place.

I also updated Agency BBS and have not pulled the fidopoll there as yet, just keeping an eye on things.

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/29/17, g00r00 pondered and said...

You should see it in this message!

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)

When are you rolling this out to the pre A36 builds? The one I pulled down tonight does not seem to have it.

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/30/17, Avon said the following...

www.mysticbbs.com/downloads/prealpha
--- Mystic BBS v1.12 A36 (Windows/32)

then we do risk getting things muddled if someone reports something
amiss with a version of A36 that may be 2-3 builds ago.
Maybe these should have been A35.1, A35.2 etc?
The way I know is that you update the whatsnew.txt each time and I always copy those docs into my working system when I update the exe files etc.
at the same time.

when i was a renegade alpha they had 98-203-xx cant remember the other part perhaps a 17.day of the year.10?

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A36 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 10/30/17, dream master pondered and said...

when i was a renegade alpha they had 98-203-xx cant remember the other part perhaps a 17.day of the year.10?

OK :) I would have enjoyed doing that back then also... sadly never got to do it then :( But grateful to all those who helped to contribute to the project.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

It was showing quite a few 'Socket Write error 25', and 'Socket read
error 25' messages...

Yes, there are a million other messages too its all part of debug logs :)

Oct 29 17:41:15 Connected
Oct 29 17:41:17 Receiving: 11aa364b.pkt (281 bytes)
Oct 29 17:41:17 Session complete (0 sent, 1 rcvd, 0 skip)

This completed successfully according to the logs you're showing. Are you saying it didn't?

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/31/17, g00r00 said the following...

It was showing quite a few 'Socket Write error 25', and 'Socket read error 25' messages...

Yes, there are a million other messages too its all part of debug logs :)

Ok. When I first posted this message, I noticed the entries and got a bit worried. :)

Oct 29 17:41:15 Connected
Oct 29 17:41:17 Receiving: 11aa364b.pkt (281 bytes)
Oct 29 17:41:17 Session complete (0 sent, 1 rcvd, 0 skip)

This completed successfully according to the logs you're showing. Are
you saying it didn't?

Most of them were completing successfully. I have had some polls that had failed. I have limited logs to post, but here is a snippet from what I have
of a failed transfer:

Oct 31 11:10:36 Recv: GET 00cbfd42.mo0 431690 1509383994 0
Oct 31 11:10:36 State RxS:WaitFile TxS:SendData HH:1 NH:0
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: FILE 00cbfd42.mo0 431690 1509383994 0
Oct 31 11:10:36 State RxS:WaitFile TxS:SendData HH:0 NH:1
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Sent: Data 32,768
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:10:36 Socket Write error 25
Oct 31 11:13:15 Socket Write error 25
Oct 31 11:13:15 Sent: Data 32,768
Oct 31 11:13:15 Socket read error 25
Oct 31 11:13:15 Socket read error 25
Oct 31 11:13:15 Socket read error 25
Oct 31 11:13:15 Error receiving data (size=252 msg=Socket read buffer error
25)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A36 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Most of them were completing successfully. I have had some polls that had failed. I have limited logs to post, but here is a snippet from what I have of a failed transfer:

Okay thank you I will do some testing and see what I can find.

--- Mystic BBS v1.12 A36 2017/11/01 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)