Hey all... re-visiting trying to get my Fidonet config running. I believe I've followed all directions in the wiki, and also referenced http://time.synchro.net:81/fidonet.ssjs, although that's a bit outdated with the synchronet version. From the looks of it, my netmail to Rob "looks" like it made it out, but any comms with my hub (like the latest %LIST attempt to areafix@1/266:512) just seems to sit there. The connection to the hub host is established, but it just seems to disconnect.

Last time I checked with my hub, I got this:

"You are connecting fine without any password errors. I haven't seen any packets as of yet."


Here's an except from the sbbsecho.log file:

2024-07-08 15:39:59 SBBSecho 3.14-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928 (PID 3768) invoked with options: -ni
2024-07-08 15:39:59 Configured: 7 archivers, 1 linked-nodes, 0 echolists 2024-07-08 15:39:59 NetMail directory: c:\sbbs\fido\netmail\
2024-07-08 15:39:59 Secure Inbound directory: C:\sbbs\fido\inbound\
2024-07-08 15:39:59 Non-secure Inbound directory: C:\sbbs\fido\nonsecure\ 2024-07-08 15:39:59 Outbound (BSO root) directory: C:\sbbs\fido\outbound 2024-07-08 15:39:59 Read 200 areas from ../data/areas.bbs
2024-07-08 15:39:59 Read 0 areas from ../data/badareas.lst
2024-07-08 15:39:59 Read 0 echo statistics from ../data/echostats.ini 2024-07-08 15:39:59 Exporting NetMail message #73 from Rob Olsen to areafix (1:266/512)
2024-07-08 15:39:59 Created NetMail (3.msg) from Rob Olsen (1:266/200) to areafix (1:266/512), attr: 0183, subject: f5gn&B5h
2024-07-08 15:39:59 Exporting NetMail message #74 from Rob Olsen to sysop (1:103/705)
2024-07-08 15:39:59 Created NetMail (4.msg) from Rob Olsen (1:266/200) to sysop (1:103/705), attr: 0183, subject: testing netmail
2024-07-08 15:39:59 Packing NetMail (3.msg) from Rob Olsen (1:266/200) to areafix (1:266/512), attr: 0183, subject: f5gn&B5h
2024-07-08 15:39:59 Node (1:266/512) successfully locked via: ../fido/outbound\010a0200.bsy
2024-07-08 15:39:59 Adding NetMail (3.msg) to new packet for 1:266/512: ../fido/outbound\010a0200.cut
2024-07-08 15:39:59 Deleting c:\sbbs\fido\netmail\3.msg (from line 5320) 2024-07-08 15:39:59 Packing NetMail (4.msg) from Rob Olsen (1:266/200) to sysop (1:103/705), attr: 0183, subject: testing netmail
2024-07-08 15:39:59 Node (1:103/705) successfully locked via: ../fido/outbound\006702c1.bsy
2024-07-08 15:39:59 Adding NetMail (4.msg) to new packet for 1:103/705: ../fido/outbound\006702c1.cut
2024-07-08 15:39:59 Deleting c:\sbbs\fido\netmail\4.msg (from line 5320) 2024-07-08 15:39:59 Touching outgoing semfile: ../data/binkout.now
2024-07-08 15:39:59 Writing 0 areas to ../data/badareas.lst
2024-07-08 15:39:59 Deleting ../fido/outbound\006702c1.bsy (from line 2957) 2024-07-08 15:39:59 Deleting ../fido/outbound\010a0200.bsy (from line 2957) 2024-07-08 15:39:59 Deleting C:\sbbs\ctrl\sbbsecho.bsy (from line 2963) 2024-07-08 15:39:59 SBBSecho (PID 3768) exiting with error level 0, NetMail(0 imported, 2 exported, 2 packed)


Here's the Events log from the synchronet control panel:

7/8 03:39:24p BINKPOLL Running timed event: BINKPOLL
7/8 03:39:24p BINKPOLL BinkIT/2.41 invoked with options: -p
7/8 03:39:24p BINKPOLL Attempting poll for node 1:266/512@fidonet
7/8 03:39:24p BINKPOLL JSBinkP/4 callout to 1:266/512@fidonet started
7/8 03:39:24p BINKPOLL Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/8 03:39:28p BINKPOLL Peer version: Internet Rex 2.29 Win32
7/8 03:39:28p BINKPOLL Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/8 03:39:28p BINKPOLL Authentication successful:
7/8 03:39:28p BINKPOLL Timed event: BINKPOLL returned 0
7/8 03:39:59p BBS Events Semaphore signaled for Timed Event: FIDOOUT
7/8 03:39:59p FIDOOUT Running native timed event: FIDOOUT
7/8 03:39:59p FIDOOUT Timed event: FIDOOUT returned 0
7/8 03:40:04p BBS Events Semaphore signaled for Timed Event: BINKOUT
7/8 03:40:04p BINKOUT Running timed event: BINKOUT
7/8 03:40:05p BINKOUT BinkIT/2.41 invoked with options:
7/8 03:40:05p BINKOUT Attempting callout for 1:103/705@fidonet, file: C:\sbbs\fido\outbound\006702c1.cut
7/8 03:40:05p BINKOUT JSBinkP/4 callout to 1:103/705@fidonet started
7/8 03:40:05p BINKOUT Connecting to 1:103/705@fidonet at f705.n103.z1.binkp.net:24554
7/8 03:40:08p BINKOUT Peer version: BinkIT/2.41,JSBinkP/4,sbbs3.20a/Win32
7/8 03:40:08p BINKOUT Authentication successful: non-secure
7/8 03:40:08p BINKOUT Sending file: C:\sbbs\fido\outbound\006702c1.cut (0.5KB)
7/8 03:40:08p BINKOUT Sent file: C:\sbbs\fido\outbound\006702c1.cut (0.5KB)
7/8 03:40:08p BINKOUT Deleted file: C:\sbbs\fido\outbound\006702c1.cut
7/8 03:40:08p BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut
7/8 03:40:08p BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/8 03:40:08p BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/8 03:40:09p BINKOUT Peer version: Internet Rex 2.29 Win32
7/8 03:40:09p BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/8 03:40:09p BINKOUT Authentication successful:
7/8 03:40:09p BINKOUT Timed event: BINKOUT returned 0

Checking in the c:\sbbs\fido\outbound folder, I still have a .cut file present. All the other fido subfolders (inbound, netmail, and nonsecure are empty)

Anyone have any suggestions as to where to look next? I appreciate any assistance!

--rob

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anything
By: smooth0401 to All on Mon Jul 08 2024 01:18 pm

Hey all... re-visiting trying to get my Fidonet config running. I believe I've followed all directions in the wiki, and also referenced http://time.synchro.net:81/fidonet.ssjs, although that's a bit outdated with the synchronet version.

Ugh. Yeah, you shouldn't follow those directions. Did you use the init-fidonet.js script as directed at https://wiki.synchro.net/howto:fidonet ?
That automates much of what any other directions have you do manually.

From the looks of it, my netmail to Rob "looks"
like it made it out

I got it and replied.

, but any comms with my hub (like the latest %LIST
attempt to areafix@1/266:512) just seems to sit there. The connection to the hub host is established, but it just seems to disconnect.

The log output (from your BinkP service) will tell you why it disconnects.

Last time I checked with my hub, I got this:

"You are connecting fine without any password errors. I haven't seen any packets as of yet."

Here's an except from the sbbsecho.log file:

You'd better change your areafix password now. You pasted it as part of your log output here.

2024-07-08 15:39:59 Adding NetMail (3.msg) to new packet for 1:266/512: ../fido/outbound\010a0200.cut

Looks good.

Here's the Events log from the synchronet control panel:

7/8 03:39:24p BINKPOLL Running timed event: BINKPOLL
7/8 03:39:24p BINKPOLL BinkIT/2.41 invoked with options: -p
7/8 03:39:24p BINKPOLL Attempting poll for node 1:266/512@fidonet
7/8 03:39:24p BINKPOLL JSBinkP/4 callout to 1:266/512@fidonet started
7/8 03:39:24p BINKPOLL Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/8 03:39:28p BINKPOLL Peer version: Internet Rex 2.29 Win32
7/8 03:39:28p BINKPOLL Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/8 03:39:28p BINKPOLL Authentication successful:
7/8 03:39:28p BINKPOLL Timed event: BINKPOLL returned 0

So "1:266/512@fidonet" is not necessarily the same node as "1:266/512". Which node do you have configured in echocfg->Linked Nodes?
--
digital man (rob)

Synchronet "Real Fact" #42:
Rob Swindell was laughed out of a FidoNet Net103 (OC, Calif.) meeting in 1992 Norco, CA WX: 86.1°F, 50.0% humidity, 11 mph WNW wind, 0.00 inches rain/24hrs

Hey Rob,

Sorry, yes, I initially ran through the external door fidonet config first.

For the Linked Node config:

Address: 1:266/512
Domain: fidonet
Name: my hub's name
comment: hub comment
archive type: ZIP
Packet type: 2+
Packet password: (not used as per hub)
Session password: xxxxxxxxx
Tic File Password: (not used as per hub)
AreaFix Support: Yes
AreaFix Password: xxxxxxxxx
EchoList Keys: blank
Status: Normal
Direct: Yes
Passive: No
Send Notify List: No
Uplink for Message Groups: FidoNet
Local Address (AKA): Best Match
Route to: Disabled
Inbox Directory: none
Outbox Directory: none

BinkP Settings ->
Host: cfbbs.no-ip.com
Port: 24554
Poll: Yes
Authentication: Plain Only
Encryption: Unsupported
Implicit TLS: No
Source Address: none

For your statement, "The log output (from your BinkP service) will tell you why it disconnects."... isn't that what I pasted with the BINKPOLL stuff? I copied that out of the events tab in the lower left corner of the Synchronet Control Panel... I searched around for another log file and didn't see anything...

Here's the last attempt... so it is 'seeing' the .cut file, just not sending it. The odd thing is now it seems to be connecting twice per callout:

7/9 12:00:00a BINKOUT Running timed event: BINKOUT
7/9 12:00:00a BINKOUT BinkIT/2.41 invoked with options:
7/9 12:00:00a BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut
7/9 12:00:00a BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/9 12:00:00a BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/9 12:00:04a BINKOUT Peer version: Internet Rex 2.29 Win32
7/9 12:00:04a BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/9 12:00:04a BINKOUT Authentication successful:
7/9 12:00:04a BINKOUT Attempting callout for 1:266/512@fidonet, outbox files: ../fido/outbound\010a0200.cut
7/9 12:00:04a BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/9 12:00:04a BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/9 12:00:06a BINKOUT Peer version: Internet Rex 2.29 Win32
7/9 12:00:06a BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/9 12:00:06a BINKOUT Authentication successful:
7/9 12:00:06a BINKOUT Timed event: BINKOUT returned 0


I'm wondering if it might be worth clearing out any existing configs and the sbbsecho.ini file and just starting that fresh... maybe there's some weird left over thing in there from when I was trying different things.

Actually just found this post: https://www.pbmystic.rdfig.net/?page=001-forum.s sjs&sub=dove-syncdisc&thread=292

He was connecting to the same hub I am with the same issue with the .cut file not being sent out... I'm going to double check my ini for any @fidonet.org settings and stuff as well...

To be continued!

--rob

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anythin
By: smooth0401 to Digital Man on Mon Jul 08 2024 09:08 pm

Hey Rob,

Sorry, yes, I initially ran through the external door fidonet config first.

For the Linked Node config:

Address: 1:266/512
Domain: fidonet
Name: my hub's name
comment: hub comment
archive type: ZIP
Packet type: 2+
Packet password: (not used as per hub)
Session password: xxxxxxxxx
Tic File Password: (not used as per hub)
AreaFix Support: Yes
AreaFix Password: xxxxxxxxx
EchoList Keys: blank
Status: Normal
Direct: Yes
Passive: No
Send Notify List: No
Uplink for Message Groups: FidoNet
Local Address (AKA): Best Match
Route to: Disabled
Inbox Directory: none
Outbox Directory: none

BinkP Settings ->
Host: cfbbs.no-ip.com
Port: 24554
Poll: Yes
Authentication: Plain Only
Encryption: Unsupported
Implicit TLS: No
Source Address: none

For your statement, "The log output (from your BinkP service) will tell you why it disconnects."... isn't that what I pasted with the BINKPOLL stuff?

Yes, but at that point in the message there was only log output from sbbsecho.

copied that out of the events tab in the lower left corner of the Synchronet Control Panel... I searched around for another log file and didn't see anything...

You pasted the right/useful log output.

Here's the last attempt... so it is 'seeing' the .cut file, just not sending it. The odd thing is now it seems to be connecting twice per callout:

7/9 12:00:00a BINKOUT Running timed event: BINKOUT
7/9 12:00:00a BINKOUT BinkIT/2.41 invoked with options:
7/9 12:00:00a BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut
7/9 12:00:00a BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/9 12:00:00a BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/9 12:00:04a BINKOUT Peer version: Internet Rex 2.29 Win32
7/9 12:00:04a BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/9 12:00:04a BINKOUT Authentication successful:
7/9 12:00:04a BINKOUT Attempting callout for 1:266/512@fidonet, outbox files: ../fido/outbound\010a0200.cut
7/9 12:00:04a BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/9 12:00:04a BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/9 12:00:06a BINKOUT Peer version: Internet Rex 2.29 Win32
7/9 12:00:06a BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/9 12:00:06a BINKOUT Authentication successful:
7/9 12:00:06a BINKOUT Timed event: BINKOUT returned 0

I'm wondering if it might be worth clearing out any existing configs and the sbbsecho.ini file and just starting that fresh... maybe there's some weird left over thing in there from when I was trying different things.

Actually just found this post: https://www.pbmystic.rdfig.net/?page=001-forum.s sjs&sub=dove-syncdisc&thread=292

He was connecting to the same hub I am with the same issue with the .cut file not being sent out... I'm going to double check my ini for any @fidonet.org settings and stuff as well...

To be continued!

Good luck!
--
digital man (rob)

Breaking Bad quote #35:
You ever smoke anything else, Wendy? Sausages don't count - ha ha - Hank Norco, CA WX: 65.6°F, 87.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs

So ran into something interesting... I basically grabbed a fresh sbbsecho.ini from a new install and tried to remove any reference to Fido I could within the different sections of the echocfg and the bbs config utility. I logged in and went through the door to do the initial Fidonet install, re-downloaded backbone.na, imported the message areas, etc etc.. I logged off, recycled, and ran echocfg. I didn't see anything in there about the hub or my config.

For kicks, I shut down the bbs, went out into dos and ran the 'jsexec init-fidonet.js' command. I went through the process and was greeted with this:

Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)? y
!Error 13 opening sbbsecho.ini
Using JavaScript exit_code: 1
C:\sbbs\exec\init-fidonet.js executed in 137.64 seconds
!Module (init-fidonet.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

Returning error code: 1

Is this an indicator of an issue? or should I just ignore it and go back and manually fill it out again via echocfg?

--rob

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anythin
By: smooth0401 to Digital Man on Tue Jul 09 2024 06:00 am

Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)? y
!Error 13 opening sbbsecho.ini

"Error 13" is permission denied.

Using JavaScript exit_code: 1
C:\sbbs\exec\init-fidonet.js executed in 137.64 seconds
!Module (init-fidonet.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

Returning error code: 1

Is this an indicator of an issue? or should I just ignore it and go back and manually fill it out again via echocfg?

Double-check the sbbsecho.ini file's ownership and permissions.
--
digital man (rob)

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: 81.5°F, 62.0% humidity, 2 mph W wind, 0.00 inches rain/24hrs

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anythin
By: Digital Man to smooth0401 on Tue Jul 09 2024 10:59 am

Another thing that would help debug your BinkP issues would be to enable debug-level logging (LogLeve = debug in ctrl/sbbs.ini).
--
digital man (rob)

Rush quote #43:
Summers going fast nights growing colder children growing up old friends, older Norco, CA WX: 83.0°F, 59.0% humidity, 7 mph SW wind, 0.00 inches rain/24hrs

Here's the latest attempt with debug logging:

7/9 03:47:36p BBS Events constructor using socket -1 (settings=8212)
7/9 03:47:36p BBS Events temporary file directory: C:\sbbs\temp\event\
7/9 03:47:36p BBS Events BBS Events thread started
7/9 03:47:36p BBS Events JavaScript: Creating event runtime: 167772160 bytes
7/9 03:48:02p BBS Events Semaphore signaled for Timed Event: BINKOUT
7/9 03:48:02p BINKOUT Running timed event: BINKOUT
7/9 03:48:02p BINKOUT Executing external: ?binkit
7/9 03:48:02p BINKOUT BinkIT/2.41 invoked with options:
7/9 03:48:02p BINKOUT Running outbound
7/9 03:48:02p BINKOUT Outbound roots: ["../fido/outbound","../fido/outbound ","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound"," ../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../ fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fid o/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/o utbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outb ound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outboun d","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound", "../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound",".. /fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fi do/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/ outbound"]
7/9 03:48:02p BINKOUT Outbound dirs: ["C:\\sbbs\\fido\\outbound\\"]
7/9 03:48:02p BINKOUT Running outbound dir C:\sbbs\fido\outbound\
7/9 03:48:02p BINKOUT Locking C:\sbbs\fido\outbound\010a0200.bsy
7/9 03:48:02p BINKOUT Lock successful.
7/9 03:48:02p BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut
7/9 03:48:02p BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/9 03:48:02p BINKOUT connecting to 1:266/512@fidonet at cfbbs.no-ip.com
7/9 03:48:02p BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/9 03:48:05p BINKOUT Connection to cfbbs.no-ip.com:24554 successful
7/9 03:48:05p BINKOUT Sending M_NUL command args: SYS Rise n' Shine
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_NUL command args: ZYZ Rob Olsen
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_NUL command args: LOC New Providence, NJ
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_NUL command args: NDL CM,IBN
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_NUL command args: TIME Tue Jul 09 2024 15:48:05 GMT-0400 (Eastern Daylight Time)
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_NUL command args: VER BinkIT/2.41,JSBinkP/4,sbbs3.19b/Win32 binkp/1.1
7/9 03:48:05p BINKOUT Sent M_NUL command
7/9 03:48:05p BINKOUT Sending M_ADR command args: 1:266/200@fidonet
7/9 03:48:05p BINKOUT Sent M_ADR command
7/9 03:48:05p BINKOUT Got M_NUL command args: OPT MB CRAM-MD5-xxxxxxxxxxxxxxxxxxxxxxxxxx
7/9 03:48:05p BINKOUT Got M_NUL command args: SYS Christian Fellowship
7/9 03:48:05p BINKOUT Got M_NUL command args: ZYZ Michael Luko
7/9 03:48:05p BINKOUT Got M_NUL command args: LOC Mt. Ephraim, NJ
7/9 03:48:05p BINKOUT Got M_NUL command args: NDL CM,INA:cfbbs.no-ip.com,IBN,ITN,IFT
7/9 03:48:05p BINKOUT Got M_NUL command args: TIME 2024/07/09 15:45:51 -5:00
7/9 03:48:05p BINKOUT Got M_NUL command args: VER Internet Rex 2.29 Win32 (binkp/1.1)
7/9 03:48:05p BINKOUT Peer version: Internet Rex 2.29 Win32
7/9 03:48:05p BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/9 03:48:05p BINKOUT Parsed BinkP version: 1.1
7/9 03:48:05p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org 1:13/0.0@fidonet.org 1:13/3.0@fidonet.org 1:129/0.0@fidonet.org 1:266/0.0@fidonet.org 454:1/1.0@ilink.org
7/9 03:48:05p BINKOUT Sending M_PWD command args: xxxxxxxx
7/9 03:48:05p BINKOUT Sent M_PWD command
7/9 03:48:05p BINKOUT Got M_OK command args:
7/9 03:48:05p BINKOUT Authentication successful:
7/9 03:48:05p BINKOUT Unconfigured address 1:266/512@fidonet.
7/9 03:48:05p BINKOUT Unconfigured address 1:13/0@fidonet.
7/9 03:48:05p BINKOUT Unconfigured address 1:13/3@fidonet.
7/9 03:48:05p BINKOUT Unconfigured address 1:129/0@fidonet.
7/9 03:48:05p BINKOUT Unconfigured address 1:266/0@fidonet.
7/9 03:48:05p BINKOUT Unconfigured address 454:1/1@ilink.or
7/9 03:48:05p BINKOUT Sending M_EOB command args:
7/9 03:48:05p BINKOUT Sent M_EOB command
7/9 03:48:05p BINKOUT Got M_EOB command args:
7/9 03:48:05p BINKOUT Sending M_EOB command args:
7/9 03:48:05p BINKOUT Sent M_EOB command
7/9 03:48:05p BINKOUT Remote host closed socket
7/9 03:48:05p BINKOUT Unlocking C:\sbbs\fido\outbound\010a0200.bsy.
7/9 03:48:05p BINKOUT No flow files to be processed.
7/9 03:48:05p BINKOUT Done checking in C:\sbbs\fido\outbound\.
7/9 03:48:05p BINKOUT Timed event: BINKOUT returned 0

The .cut file is still in the C:\SBBS\FIDO\OUTBOUND folder as well. (010a0200.cut)

--rob

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anythin
By: smooth0401 to Digital Man on Tue Jul 09 2024 12:57 pm

Here's the latest attempt with debug logging:

7/9 03:48:02p BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut

7/9 03:48:05p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org 1:13/0.0@fidonet.org 1:13/3.0@fidonet.org 1:129/0.0@fidonet.org 1:266/0.0@fidonet.org 454:1/1.0@ilink.org

Okay, you're attemping to a callout to 1:266/512[.0]@fidonet, yet, the link is advertising 1:266/512[.0]@fidonet.org as its "matching" address. It doesn't match. "fidonet" is not "fidonet.org". Your uplink you should fix that. The proper FidoNet domain in a 5D address is "fidonet", not "fidonet.org".
--
digital man (rob)

Breaking Bad quote #51:
I did it for me. I liked it. I was good at it. And.. I was really.. I was alive Norco, CA WX: 90.7°F, 48.0% humidity, 9 mph WNW wind, 0.00 inches rain/24hrs

I guess that makes sense... that was what the other user was experiencing with this same hub a while back. (he was the one that got binkd to work because of the aliases where binkit can't do that?)

I'll reach out to Michael and see what he can do. If not, maybe I can try to get the binkd method working if you think that might be worth trying.

Thanks for all the info!
--rob

Re: Fidonet - sbbsecho looks good... binkit timed events don't do anythin
By: smooth0401 to Digital Man on Tue Jul 09 2024 01:22 pm

I guess that makes sense... that was what the other user was experiencing with this same hub a while back. (he was the one that got binkd to work because of the aliases where binkit can't do that?)

I'll reach out to Michael and see what he can do. If not, maybe I can try to get the binkd method working if you think that might be worth trying.

Thanks for all the info!

FTN domains are by definition a maximum of 8 characters in length, so "fidonet.org" clearly is an invalid FTN domain. And it's just wrong anyway. The hub should fix that.
--
digital man (rob)

Sling Blade quote #26:
Karl: kaiser blade, ax handle with long blade on it shaped kinda like a banana. Norco, CA WX: 94.2°F, 41.0% humidity, 12 mph W wind, 0.00 inches rain/24hrs

Hi Digital,

On 2024-07-09 15:35:13, you wrote to smooth0401:

I guess that makes sense... that was what the other user was
experiencing
with this same hub a while back. (he was the one that got binkd to work
because of the aliases where binkit can't do that?)

I'll reach out to Michael and see what he can do. If not, maybe I can try
to get the binkd method working if you think that might be worth trying.

Thanks for all the info!

FTN domains are by definition a maximum of 8 characters in length, so "fidonet.org" clearly is an invalid FTN domain. And it's just wrong anyway.
The hub should fix that.

You're probably right. ;-)

But in the default configuration for binkd there is this section:

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet domain")
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet

So if binkit can do something similar, you can still make connections work when others make mistakes.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Re: Re: Fidonet - sbbsecho looks good... binkit timed events don't do anyth
By: Wilfred van Velzen to Digital Man on Wed Jul 10 2024 12:23 pm

FTN domains are by definition a maximum of 8 characters in length, so "fidonet.org" clearly is an invalid FTN domain. And it's just wrong anyway.
The hub should fix that.

You're probably right. ;-)

But in the default configuration for binkd there is this section:

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet domain") domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet

So if binkit can do something similar, you can still make connections work when others make mistakes.

Sure, it would be possible for BinkIT to have some hacky work-around for misconfigured nodes, but if possible, it would preferable to just fix the configuration of the node in question.
--
digital man (rob)

Breaking Bad quote #42:
We have laws, detective. Have your kindergarten teacher read them to you. Norco, CA WX: 81.8°F, 60.0% humidity, 3 mph W wind, 0.00 inches rain/24hrs

So Michael was able to remove the .org and it seems to be getting further... it seems to be sending the packet, removing the .cut file from the outbound folder, but still not receiving any of the areafix responses (tried %LIST and %HELP) Here's the latest logs:

7/13 10:19:36a BBS Events Semaphore signaled for Timed Event: FIDOOUT
7/13 10:19:36a FIDOOUT Running native timed event: FIDOOUT
7/13 10:19:36a FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -ni
7/13 10:19:36a FIDOOUT Timed event: FIDOOUT returned 0
7/13 10:19:41a BBS Events Semaphore signaled for Timed Event: BINKOUT
7/13 10:19:41a BINKOUT Running timed event: BINKOUT
7/13 10:19:41a BINKOUT Executing external: ?binkit
7/13 10:19:42a BINKOUT BinkIT/2.41 invoked with options:
7/13 10:19:42a BINKOUT Running outbound
7/13 10:19:42a BINKOUT Outbound roots: ["../fido/outbound","../fido/outboun d","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound", "../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound",".. /fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fi do/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/ outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/out bound","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbou nd","../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound" ,"../fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound",". ./fido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../f ido/outbound","../fido/outbound","../fido/outbound","../fido/outbound","../fido /outbound"]
7/13 10:19:42a BINKOUT Outbound dirs: ["C:\\sbbs\\fido\\outbound\\"]
7/13 10:19:42a BINKOUT Running outbound dir C:\sbbs\fido\outbound\
7/13 10:19:42a BINKOUT Locking C:\sbbs\fido\outbound\010a0200.bsy
7/13 10:19:42a BINKOUT Lock successful.
7/13 10:19:42a BINKOUT Attempting callout for 1:266/512@fidonet, file: C:\sbbs\fido\outbound\010a0200.cut
7/13 10:19:42a BINKOUT JSBinkP/4 callout to 1:266/512@fidonet started
7/13 10:19:42a BINKOUT connecting to 1:266/512@fidonet at cfbbs.no-ip.com
7/13 10:19:42a BINKOUT Connecting to 1:266/512@fidonet at cfbbs.no-ip.com:24554
7/13 10:19:45a BINKOUT Connection to cfbbs.no-ip.com:24554 successful
7/13 10:19:45a BINKOUT Sending M_NUL command args: SYS Rise n' Shine
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_NUL command args: ZYZ Rob Olsen
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_NUL command args: LOC New Providence, NJ
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_NUL command args: NDL CM,IBN
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_NUL command args: TIME Sat Jul 13 2024 10:19:45 GMT-0400 (Eastern Daylight Time)
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_NUL command args: VER BinkIT/2.41,JSBinkP/4,sbbs3.19b/Win32 binkp/1.1
7/13 10:19:45a BINKOUT Sent M_NUL command
7/13 10:19:45a BINKOUT Sending M_ADR command args: 1:266/200@fidonet
7/13 10:19:45a BINKOUT Sent M_ADR command
7/13 10:19:45a BINKOUT Got M_NUL command args: OPT MB CRAM-MD5-xxxxxxxxxxxxxxxxxxxxx
7/13 10:19:45a BINKOUT Got M_NUL command args: SYS Christian Fellowship
7/13 10:19:45a BINKOUT Got M_NUL command args: ZYZ Michael Luko
7/13 10:19:45a BINKOUT Got M_NUL command args: LOC Mt. Ephraim, NJ
7/13 10:19:45a BINKOUT Got M_NUL command args: NDL CM,INA:cfbbs.no-ip.com,IBN,ITN,IFT
7/13 10:19:45a BINKOUT Got M_NUL command args: TIME 2024/07/13 10:20:31 -5:00
7/13 10:19:45a BINKOUT Got M_NUL command args: VER Internet Rex 2.29 Win32 (binkp/1.1)
7/13 10:19:45a BINKOUT Peer version: Internet Rex 2.29 Win32
7/13 10:19:45a BINKOUT Peer ended their VER with " (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp 1.1 anyway
7/13 10:19:45a BINKOUT Parsed BinkP version: 1.1
7/13 10:19:45a BINKOUT Got M_ADR command args: 1:266/512.0@fidonet 1:13/0.0@fidonet 1:13/3.0@fidonet 1:129/0.0@fidonet 1:266/0.0@fidonet 454:1/1.0@ilink
7/13 10:19:45a BINKOUT Sending M_PWD command args: xxxxxxxxxxxxxx
7/13 10:19:45a BINKOUT Sent M_PWD command
7/13 10:19:45a BINKOUT Got M_OK command args:
7/13 10:19:45a BINKOUT Authentication successful:
7/13 10:19:45a BINKOUT Unconfigured address 1:13/0@fidonet
7/13 10:19:45a BINKOUT Unconfigured address 1:13/3@fidonet
7/13 10:19:45a BINKOUT Unconfigured address 1:129/0@fidonet
7/13 10:19:45a BINKOUT Unconfigured address 1:266/0@fidonet
7/13 10:19:45a BINKOUT Unconfigured address 454:1/1@ilink
7/13 10:19:45a BINKOUT Adding outbound files for 1:266/512@fidonet (object)
7/13 10:19:45a BINKOUT Adding 'C:\sbbs\fido\outbound\010a0200.cut' as 'uu5a5l7e.pkt'
7/13 10:19:45a BINKOUT Sending file: C:\sbbs\fido\outbound\010a0200.cut (0.4KB)
7/13 10:19:45a BINKOUT Sending M_FILE command args: uu5a5l7e.pkt 432 1720880376 0
7/13 10:19:45a BINKOUT Sent M_FILE command
7/13 10:19:45a BINKOUT Sending 432 bytes of data
7/13 10:19:45a BINKOUT Sent file: C:\sbbs\fido\outbound\010a0200.cut (0.4KB)
7/13 10:19:45a BINKOUT Sending M_EOB command args:
7/13 10:19:45a BINKOUT Sent M_EOB command
7/13 10:19:45a BINKOUT Got M_EOB command args:
7/13 10:19:45a BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT
7/13 10:19:45a BINKOUT Sending M_EOB command args:
7/13 10:19:45a BINKOUT Sent M_EOB command
7/13 10:19:45a BINKOUT Got M_GOT command args: uu5a5l7e.pkt 432 1720880376
7/13 10:19:45a BINKOUT Got M_EOB command args:
7/13 10:19:45a BINKOUT Sending M_EOB command args:
7/13 10:19:45a BINKOUT Sent M_EOB command
7/13 10:19:45a BINKOUT Remote host closed socket
7/13 10:19:45a BINKOUT Deleted file: C:\sbbs\fido\outbound\010a0200.cut
7/13 10:19:45a BINKOUT Unlocking C:\sbbs\fido\outbound\010a0200.bsy.
7/13 10:19:45a BINKOUT No flow files to be processed.
7/13 10:19:45a BINKOUT Done checking in C:\sbbs\fido\outbound\.
7/13 10:19:45a BINKOUT Timed event: BINKOUT returned 0

--rob

Ù Preview lines 1-10 of 549 ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 2024-07-13 À List of areas available to you:
Selected Area name
-------- -------------------------------------------------------------------- No ALLFIX_HELP
No OTHERNETS
No Z1C
No Z1_SYSOP
No FN_SYSOP
No FTSC_PUBLIC

Just a quick update, I got the areafix mails!

Now I just have to subscribe to the echos and we'll see if I can pull the messages... thanks for all the help!

--rob