Hi All

I've been trying to set up Fidonet for a week and I am starting to get really frustrated.

When running Binkout my events feed is saying:

BINKOUT Attempting callout for 6:633/280@fidonet, file ../fido/outbound .. etc BINKOUT JSBinkP/1.112 callout to 6:633/280@fidonet started
BINKOUT Connecting to f280.n633.z6.binkp.net:24554
BINKOUT Connection to f280.n633.z6.binkp.net:24554 failed.

I don't understand this for a number of reasons.

My Fidonet node has been set by the NC at 3:633/416 (So I don't know why it is coming up as callout to 6:633/280 when it is set as 3:633/280 in Echocfg)
The hub address to go out to is 3:633/280 and I am assuming the domain is Fidonet
The port is definitely 24554, I've checked that
The hub IP is 103.39.238.13 (the address is ftn633.vk3heg.net)

I've followed the youtube tutorial to get Fidonet working to the letter, and i've played with Echocfg endlessly.

Can someone just tell me what all my Echocfg fields should read based on the above addresses and info?

I love Synchronet and the board is ready to go live apart from this. Thanks all!

Randers

---
þ Synchronet þ Mind's Eye - mindseye.ddns.net - Melbourne Australia
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Trouble setting up Fidonet
By: Randers to All on Wed Mar 18 2020 08:34 pm

Hi All

I've been trying to set up Fidonet for a week and I am starting to get really frustrated.

When running Binkout my events feed is saying:

BINKOUT Attempting callout for 6:633/280@fidonet, file ../fido/outbound .. etc BINKOUT JSBinkP/1.112 callout to 6:633/280@fidonet started
BINKOUT Connecting to f280.n633.z6.binkp.net:24554
BINKOUT Connection to f280.n633.z6.binkp.net:24554 failed.

I don't understand this for a number of reasons.

My Fidonet node has been set by the NC at 3:633/416 (So I don't know why it is coming up as callout to 6:633/280 when it is set as 3:633/280 in

Echocfg)

You apparently have files for that zone 6 address in your fido/outbound. It doesn't necessarily have to be your hub.

The hub address to go out to is 3:633/280 and I am assuming the domain is Fidonet
The port is definitely 24554, I've checked that
The hub IP is 103.39.238.13 (the address is ftn633.vk3heg.net)

Okay. But for whatever reason you have some outbound files (likely mail packets) for that 6:633/280 address.

I've followed the youtube tutorial to get Fidonet working to the letter,

and

i've played with Echocfg endlessly.

Can someone just tell me what all my Echocfg fields should read based on

the

above addresses and info?

Look in your fido/outbound directory.
The key for the file names and directory naming of Binkley Style Outbound is here: http://wiki.synchro.net/ref:fidonet_files

digital man

Synchronet "Real Fact" #75:
Rob's alias "digital man" was inspired by a song on Rush's 1982 "Signals" album.
Norco, CA WX: 57.2øF, 53.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Trouble setting up Fidonet
By: Randers to All on Wed Mar 18 2020 08:34 pm

My Fidonet node has been set by the NC at 3:633/416 (So I don't know why it is coming up as callout to 6:633/280 when it is set as 3:633/280 in Echocfg) The hub address to go out to is 3:633/280 and I am assuming the domain is Fidonet
The port is definitely 24554, I've checked that
The hub IP is 103.39.238.13 (the address is ftn633.vk3heg.net)

I pickup fidonet from Vorlon, so it sounds like you have something amiss.

Can you poll 3:633/280 successfuly (as a starting point)?

jsexec binkit -l 3:633/280?
...deon


... Religions change; Beer and Wine remain.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 03-18-20 16:31, Digital Man wrote to Randers <=-

My Fidonet node has been set by the NC at 3:633/416 (So I don't know why it is coming up as callout to 6:633/280 when it is set as 3:633/280 in

Echocfg)

You apparently have files for that zone 6 address in your
fido/outbound. It doesn't necessarily have to be your hub.

Yes, sounds like it. I'd definitely fish around in the outbound tree for foles
destined for z6. But I'd also double check the configuration for typos and brain farts. Been there, done that! :D

The hub address to go out to is 3:633/280 and I am assuming the domain is Fidonet
The port is definitely 24554, I've checked that
The hub IP is 103.39.238.13 (the address is ftn633.vk3heg.net)

Yep, the hub information is correct (that's my Fidonet hub as well)

Okay. But for whatever reason you have some outbound files (likely mail packets) for that 6:633/280 address.

Yeah I think he has a typo somewhere in the configs. ;)


... "42? 7 and a half million years and all you can come up with is 42?!"
--- MultiMail/Win v0.51
þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.au
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 03-19-20 11:36, alterego wrote to Randers <=-

I pickup fidonet from Vorlon, so it sounds like you have something
amiss.

I few of us do, though I'm using binkd to do it.


... Federal Employment Principle: Confusion creates jobs.
--- MultiMail/Win v0.51
þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.au
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Trouble setting up Fidonet
By: Randers to All on Wed Mar 18 2020 20:34:52


Randers> When running Binkout my events feed is saying:

Randers> BINKOUT Attempting callout for 6:633/280@fidonet, file ../fido/outbound .. etc
Randers> BINKOUT JSBinkP/1.112 callout to 6:633/280@fidonet started
Randers> BINKOUT Connecting to f280.n633.z6.binkp.net:24554
Randers> BINKOUT Connection to f280.n633.z6.binkp.net:24554 failed.

Randers> I don't understand this for a number of reasons.

we've already covered this on discord but for others reading along, the key is the zone number in the above... the netmail was apparently misaddressed to 6:633/280 so sbbsecho properly created the .out file in outbound.006... however the proper destination is 3:633/280 so that sbbsecho will create the .out file in outbound.003... since the mailer was finding the one file in outbound.006, it was properly trying to send it to a non-existent address... the solution is to delete the .out file from outbound.006 and rewrite the netmail with the proper destination address...

NOTE: yeah, i was on discord with my other alias ;)


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)