On 02 May 2022, claw was heard saying...

So I can only hope g00r00 can advise on this one. Unless anyone else
has experienced this. I added fsxNet to my BBS all went well until
the nodelist got pulled in. They have me set to connect to 21:1/100
with agency.bbs.nz however the node list shows that address pointing
to net1.fsxnet.nz. Avon assures me they are both the same computer
however authorization fails. If I remove the node list and turn the
node back to active it works again. But it I allow it to pull the
node list I just end up in a loop of the same issue.

would like to have the nodelist working, but for now leaving it
disabled. Any advise.

I'm going to reply and change the subject line for this as the original subject line is vague and we're not having any nodelist issues with
ArakNet. If anyone is carrying FSXnet and is having Nodelist issues with
the latest build of Mystic (claw: You are running the latest version of Mystic? Right?).


--
|11// |03Smooth |07+o |05{|12{|08.|15DESPAiR BBS|08.|12}|05} |14

--- Mystic BBS/NNTP v1.12 A48 2022/04/26 (Windows/64)
* Origin: DESPAiR BBS // sys:Smooth // Covina, CA (10:103/11.1)

with the latest build of Mystic (claw: You are running the latest
version of Mystic? Right?).

I am. Everything is up to date. Even keep up with the US updates which is Xubuntu. I wanted a very light graphical interface for easy SMB access to the network share to back up the BBS and pull files I find on other stations.

What might fix it is if there can be an option in the ini to not set the node to inactive after it imports the list. This way if the nodelist has conflicting information it doesn't cause this issue. Not sure if thats an easy
thing to add or not. Unless anyone else has any ideas how to prevent this. I
would like the netmail to be usable.

Thank you everyone for your support. Sorry for making it so confusing.

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

On 05 May 2022, Smooth said the following...

ArakNet. If anyone is carrying FSXnet and is having Nodelist issues
with the latest build of Mystic (claw: You are running the latest
version of Mystic? Right?).

I just setup the fsx nodelist in mutil the other night and everything seems to be fine. I'm on A48, Linux 64-bit, running on Ubuntu.

-zr

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
* Origin: Alcoholiday // alco.bbs.io (10:101/5)

I just setup the fsx nodelist in mutil the other night and everything seems to be fine. I'm on A48, Linux 64-bit, running on Ubuntu.

-zr

What node do you connect to? does it make the node inactive in the settings?

wondering if its something I'm doing wrong then?

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07!

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

On 06 May 2022, claw said the following...

What node do you connect to? does it make the node inactive in the settings?

I'm connecting to 21:4/100. The node says it's active in settings.

-zr

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
* Origin: Alcoholiday // alco.bbs.io (10:101/5)

fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!!

You gotta change that brown. Ick.

... If you're trying to drive me crazy, you're too late.

--- Renegade v1.30r3/Exp
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (10:103/23)

You gotta change that brown. Ick.

Makes it stand out though ;D

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |22|01fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07!

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

I connect to node 21:1/100 listed as agency.bbs.nz but the node list says that
its net1.fsxnet.nz. So I believe thats why. Its starts trying to connect to that internet address instead of the one assigned. I'm guessing that until it is updated to the correct internet address Mystic is trying to keep it updated in its own way. I see why you would wants this incase the Network admin changes addresses on you, you keep connected

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |20|10fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07!

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

On 09 May 2022, claw was ranting the following...

I connect to node 21:1/100 listed as agency.bbs.nz but the node list
says that its net1.fsxnet.nz. So I believe thats why. Its starts
trying to connect to that internet address instead of the one assigned. I'm guessing that until it is updated to the correct internet address Mystic is trying to keep it updated in its own way. I see why you would wants this incase the Network admin changes addresses on you, you keep connected

You've got your BINKP Hostname setup on Mystic as agency.bbs.nz, huh? That's why your getting an authentication issue. It's not matching with the system your connecting too on port 24554. Do you have a recent nodelist? The old nodelist still has the WHQ listed as agency.bbs.nz

If you check the FSXnet website the WHQ is listed as net1.fsxnet.nz. You should change your binkp hostname for 21:1/100 to agency.fsxnet.nz.

https://fsxnet.nz/about/#technical-details

|11// |03Smooth |07+o |05{|12{|08.|15DESPAiR BBS|08.|12}|05} |14

... Electricity is really just organized lightning.

--- Mystic BBS v1.12 A48 2022/04/26 (Windows/64)
* Origin: DESPAiR BBS // sys:Smooth // Covina, CA (10:103/11.1)

on 10 May 2022, Smooth said...

You've got your BINKP Hostname setup on Mystic as agency.bbs.nz, huh? That's why your getting an authentication issue. It's not matching with the system your connecting too on port 24554. Do you have a recent nodelist? The old nodelist still has the WHQ listed as agency.bbs.nz

If you check the FSXnet website the WHQ is listed as net1.fsxnet.nz. You should change your binkp hostname for 21:1/100 to agency.fsxnet.nz.

https://fsxnet.nz/about/#technical-details

// Smooth +o {{.DESPAiR BBS.}}

I will give it a shot after work today and see if I can get it all going. Thank you for reaching out to help!

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |20|10fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07!

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

On 05 May 2022, Smooth said the following...

I'm going to reply and change the subject line for this as the original subject line is vague and we're not having any nodelist issues with ArakNet. If anyone is carrying FSXnet and is having Nodelist issues
with the latest build of Mystic (claw: You are running the latest
version of Mystic? Right?).

Um, I haven't had a nodelist for ArakNet since July 2020 :'(

I also still have issues with sporadic data coming from my uplink... can that be looked into please?

I don't have any issues with any other network (except Retronet which appears to have entirely disappeared).

I am still on A47 tho, and I'm really hesitant this time round to upgrade due to the bugs I hear that are still circulating with the latest version.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (10:104/2)

I am still on A47 tho, and I'm really hesitant this time round to
upgrade due to the bugs I hear that are still circulating with the
latest version.

Can you tell me what those are? I have zero open issues that I can think of right now.

... Evil triumphs when good people do nothing. - Einstein

--- Mystic BBS v1.12 A48 2022/04/26 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (10:101/30)

Can you tell me what those are? I have zero open issues that I can
think of right now.

I could use a little more cowbell on the track

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

I am still on A47 tho, and I'm really hesitant this time round to
upgrade due to the bugs I hear that are still circulating with the
latest version.

Well, I dont find any bugs yet... but theres something weird about ibol or InterBBS oneliners.... after migrated to A48, ibol "v" command doesnt work anymore. Thats the only issue I ve had so far. I am writing it here so maybe
we could find a solution together hehehe <it seems like a python apis trouble

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/64)
* Origin: The Vault BBS (10:103/12)

Can you tell me what those are? I have zero open issues that I can think of right now.

I could use a little more cowbell on the track

Added to TODO.

... If you can't make it good, make it LOOK good. -Bill Gates.

--- Mystic BBS v1.12 A48 2022/04/26 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (10:101/30)

On 26 May 2022, g00r00 said the following...

Can you tell me what those are? I have zero open issues that I can
think of right now.

The main ones I hear about are the python2 and python3 issues. If you get p2 working, python3 borks, and if you get p3 working, python2 borks.

I'm on leave for work next week so I could spend a little time cloning my bbs vm and giving it a try and see if it works ok or borks, then report what borks if it does if that helps?

I'm currently running;
Mystic BBS v1.12 A47 compiled 2021/12/13 09:19:46

This has been super stable for me hence why I'm reluctant to upgrade.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (10:104/2)

The main ones I hear about are the python2 and python3 issues. If you
get p2 working, python3 borks, and if you get p3 working, python2 borks.

I think the smartest thing to do is rip the bandaid off and force everyone to migrate to python 3. We can help one another fix each others' mods, as a community. Then we won't have to worry about this wonky hybrid thing and g00r00
won't have to continue supporting it :)

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)

on 06 Jun 2022, esc said...

I think the smartest thing to do is rip the bandaid off and force
everyone to migrate to python 3. We can help one another fix each
others' mods, as a community. Then we won't have to worry about this
wonky hybrid thing and g00r00 won't have to continue supporting it :)

Completely agree. Its only a matter of time before 2 just isn't supported properly anymore. Better to do it before vulnerabilities come up.

One thing to note when I experimented with this myself I didn't have the issue in the newest raspberry pi OS or in a VM with xubuntu. Haven't tested in arch because I havn't had a reason to use python2 in it it.

|23|04Dr|16|12Claw |16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04) |10Standard Ports for SSH/Telnet Web/|01HTTP://|14Noverdu.com:808 |20|15fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07!

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (10:102/7)