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 Adding NetMail (3.msg) to new packet for 1:266/512: ../fido/outbound\010a0200.cut
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
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?
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!
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?
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
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!
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.
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.
Sysop: | Tandy |
---|---|
Location: | New York, USA |
Users: | 15 |
Nodes: | 13 (0 / 13) |
Uptime: | 12:41:25 |
Calls: | 324 |
Messages: | 105,766 |