Hi All,

So, I finally have everything set up and running utilizing BinkD, HPT and Docker for Net 4.

Please let me know if you run into any issues.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 26 Oct 2020 at 05:00p, Black Panther pondered and said...

So, I finally have everything set up and running utilizing BinkD, HPT and Docker for Net 4.

Please let me know if you run into any issues.

12:06:12 Poll BINKP node via address lookup: 21:4/100
12:06:12 Queued 1 files (1,722 bytes) for 21:4/100
12:06:12 1-Polling 21:4/100 on slot 1 via BINKP
12:06:12 1-Connecting to net4.fsxnet.nz on port 24553
12:06:13 1-Using address 184.155.113.241
12:06:19 1-Unable to connect
12:06:20 Polled 1 systems

Do I need to change something at my end? Drop 24553 SSL?

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

On 27 Oct 2020, 12:07p, Avon said the following...

12:06:12 1-Connecting to net4.fsxnet.nz on port 24553
12:06:13 1-Using address 184.155.113.241
12:06:19 1-Unable to connect

Do I need to change something at my end? Drop 24553 SSL?

For now I think we'll have to use 24560 only. I'm not sure if BinkD will do SSL.

I'm also shutting it down on and off as I adjust config files...


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 26 Oct 2020 at 05:28p, Black Panther pondered and said...

For now I think we'll have to use 24560 only. I'm not sure if BinkD will do SSL.
I'm also shutting it down on and off as I adjust config files...

OK all set, yep looks 'down' at the mo.

13:18:12 Poll BINKP node via address lookup: 21:4/100
13:18:12 Queued 1 files (1,636 bytes) for 21:4/100
13:18:12 1-Polling 21:4/100 on slot 1 via BINKP
13:18:12 1-Connecting to net4.fsxnet.nz on port 24560
13:18:13 1-Using address 184.155.113.241
13:18:19 1-Unable to connect
13:18:20 Polled 1 systems

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

On 27 Oct 2020, 01:21p, Avon said the following...

13:18:12 Poll BINKP node via address lookup: 21:4/100
13:18:12 Queued 1 files (1,636 bytes) for 21:4/100
13:18:12 1-Polling 21:4/100 on slot 1 via BINKP
13:18:12 1-Connecting to net4.fsxnet.nz on port 24560
13:18:13 1-Using address 184.155.113.241
13:18:19 1-Unable to connect
13:18:20 Polled 1 systems

Yup, I have it down right now. Can you take a look and make sure there is no packet password set? I've gotten three message archives from 1/100, and all three were flagged as 'Security Violation'.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 26 Oct 2020 at 06:32p, Black Panther pondered and said...

Yup, I have it down right now. Can you take a look and make sure there
is no packet password set? I've gotten three message archives from
1/100, and all three were flagged as 'Security Violation'.

will take this over to FSX_NET :)

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

Re: Re: Hub Change
By: Black Panther to Avon on Mon Oct 26 2020 05:28 pm

Hey BP,

For now I think we'll have to use 24560 only. I'm not sure if BinkD will do SSL.
I'm also shutting it down on and off as I adjust config files...

You're still using my container image?

If so, you can do SSL - just map a port to 24553 and it should work.

...ëîåï

... Old? The only thing that kept it standing was the woodworm holding hands. --- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 26 Oct 2020, 05:00p, Black Panther said the following...

So, I finally have everything set up and running utilizing BinkD, HPT and Docker for Net 4.

Please let me know if you run into any issues.

I did have some issues on this end for a bit. I know that someone was trying to send an areafix message, and was getting 'area not found'. If that was you, please resend it. Keep in mind the areafix and filefix are now a bit different, so you may want to send a %help first.

I think everything is flowing nicely now. Just let me know if you don't get this message. ;)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Black wrote:

On 26 Oct 2020, 05:00p, Black Panther said the following...

So, I finally have everything set up and running utilizing BinkD, HPT and
Docker for Net 4.

Please let me know if you run into any issues.

I did have some issues on this end for a bit. I know that someone was trying to send an areafix message, and was getting 'area not found'. If that was you, please resend it. Keep in mind the areafix and filefix are now a bit different, so you may want to send a %help first.

I think everything is flowing nicely now. Just let me know if you don't get this message. ;)

It's a bug in Mystic areafix handler than can't deal with more than one %COMMAND in a message. You want the 4 new areas, send 4 separate messages.
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

On 27 Oct 2020, 12:41a, Nigel Reed said the following...

I did have some issues on this end for a bit. I know that someone was tr to send an areafix message, and was getting 'area not found'. If that wa you, please resend it. Keep in mind the areafix and filefix are now a bi different, so you may want to send a %help first.

It's a bug in Mystic areafix handler than can't deal with more than one

Nope, Hub 4 is now running BinkD and Husky, in a Docker container. Someone had sent an areafix message as I was getting things set up and it didn't process correctly.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

Black wrote:

On 27 Oct 2020, 12:41a, Nigel Reed said the following...

I did have some issues on this end for a bit. I know that someone was tr
to send an areafix message, and was getting 'area not found'. If that wa
you, please resend it. Keep in mind the areafix and filefix are now a bi
different, so you may want to send a %help first.

It's a bug in Mystic areafix handler than can't deal with more than one

Nope, Hub 4 is now running BinkD and Husky, in a Docker container. Someone had sent an areafix message as I was getting things set up and it didn't process correctly.

Still a bug. Mystic won't accept a \r\n terminated string unless someone can point to a spec that says only \r should be accepted?
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Nigel wrote (2020-10-27):

It's a bug in Mystic areafix handler than can't deal with more
than one

Nope, Hub 4 is now running BinkD and Husky, in a Docker container.
Someone had sent an areafix message as I was getting things set up and
it didn't process correctly.

Still a bug. Mystic won't accept a \r\n terminated string unless someone can point to a spec that says only \r should be accepted?

You mean \r\n terminated line/paragraph? (the string is the whole text body and is \0 terminated)

In Fidonet paragraphs are separated by \r. \r\n is just wrong because it strictly parsed as:

AREA1\r
\nAREA2\r
\nAREA3\r
\n

(or is there some FTS that says \n should be ignored?)

---
* Origin: (21:3/102)

I did have some issues on this end for a bit. I know that someone was trying tosend an areafix message, and was getting 'area not found'. If that was you,please resend it. Keep in mind the areafix and filefix are now a bit different,so you may want to send a %help first.

That was me :) I'll send the help request. Thanks!

Robbie

|07Ú[|08..|15Alpha|08.....................|07]¿
|07Ã[|08..|11The Drunken Gamer BBS|08.....|07]´ |07À[|08..|03TheDrunkenGamer.com:8888|08..|07]Ù

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: The Drunken Gamer BBS (21:4/158)

Re: Hub Change
By: Oli to Nigel Reed on Tue Oct 27 2020 12:34 pm

Nigel wrote (2020-10-27):

It's a bug in Mystic areafix handler than can't deal with more
than one

Nope, Hub 4 is now running BinkD and Husky, in a Docker container.
Someone had sent an areafix message as I was getting things set up and
it didn't process correctly.

Still a bug. Mystic won't accept a \r\n terminated string unless someone can point to a spec that says only \r should be accepted?

You mean \r\n terminated line/paragraph? (the string is the whole text body and is \0 terminated)

In Fidonet paragraphs are separated by \r. \r\n is just wrong because it strictly parsed as:

AREA1\r
\nAREA2\r
\nAREA3\r
\n

(or is there some FTS that says \n should be ignored?)

From FTS-1 (http://ftsc.org/docs/fts-0001.016):
"All linefeeds, 0AH, should be ignored."
--
digital man

Sling Blade quote #22:
Karl: I don't reckon you have to go with women to be a good father to a boy. Norco, CA WX: 66.0øF, 69.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Digital wrote (2020-11-05):

Nigel wrote (2020-10-27):

Still a bug. Mystic won't accept a \r\n terminated string unless
someone can point to a spec that says only \r should be
accepted?

You mean \r\n terminated line/paragraph? (the string is the whole
text body and is \0 terminated)

In Fidonet paragraphs are separated by \r. \r\n is just wrong because
it strictly parsed as:

AREA1\r
\nAREA2\r
\nAREA3\r
\n

(or is there some FTS that says \n should be ignored?)

From FTS-1 (http://ftsc.org/docs/fts-0001.016):
"All linefeeds, 0AH, should be ignored."

I should have written '... _must_ be ignored?'. "Should" means "should", so it's still not a hard bug in Mystic. The real bug (specification wise) is in the fido software that creates the mails to areafix and puts \r\n as line endings instead of \r. There is not really an excuse or need to create such mails.

But just silently ignoring lines without any warning/errors is not very user friendly.

---
* Origin: (21:3/102)

On 11/08/2020 2:02 am Black Panther said...

Someone had sent an areafix message as I was getting things set up and it didn't process correctly.

Hmm, I wonder if that's why my areafix messages were on the fritz? :)

.o(I guess I should have checked first before I started sending those out)

Take Care,
Beanzilla

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
* Origin: BZ&BZ BBS (21:4/110)