• Help with FidoNet setup

    From Xofraq@VERT/MICROBUR to All on Thursday, October 03, 2024 20:44:22
    Hello all,

    Not sure if this is enough information to get some direction on my Fido setup issue i am having. This is what I see when I try to send areafix netmail.

    BINKOUT Running native timed event: BINKOUT
    10/3 20:30:50 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/3 20:30:50 evnt BINKOUT Attempting callout for 1:3634/59@fidonet, file: /home/pi/sbbs/fido/outbound/0e32003b.out
    10/3 20:30:50 evnt BINKOUT JSBinkP/4 callout to 1:3634/59@fidonet started
    10/3 20:30:50 evnt BINKOUT Connecting to 1:3634/59@fidonet at f59.n3634.z1.binkp.net:24554
    10/3 20:30:50 evnt BINKOUT Connection to f59.n3634.z1.binkp.net:24554 failed (Error: Name or service not known).
    10/3 20:30:50 evnt BINKOUT Timed event: BINKOUT returned 0

    I can't seem to find what I have configured wrong. Thanks in advance for any direction. Xofraq

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Digital Man@VERT to Xofraq on Thursday, October 03, 2024 21:32:29
    Re: Help with FidoNet setup
    By: Xofraq to All on Thu Oct 03 2024 08:44 pm

    Hello all,

    Not sure if this is enough information to get some direction on my Fido setup issue i am having. This is what I see when I try to send areafix netmail.

    BINKOUT Running native timed event: BINKOUT
    10/3 20:30:50 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/3 20:30:50 evnt BINKOUT Attempting callout for 1:3634/59@fidonet, file: /home/pi/sbbs/fido/outbound/0e32003b.out
    10/3 20:30:50 evnt BINKOUT JSBinkP/4 callout to 1:3634/59@fidonet started 10/3 20:30:50 evnt BINKOUT Connecting to 1:3634/59@fidonet at f59.n3634.z1.binkp.net:24554
    10/3 20:30:50 evnt BINKOUT Connection to f59.n3634.z1.binkp.net:24554 failed (Error: Name or service not known).
    10/3 20:30:50 evnt BINKOUT Timed event: BINKOUT returned 0

    I can't seem to find what I have configured wrong. Thanks in advance for any direction. Xofraq

    That hostname seems to resolve for me:
    $ host f59.n3634.z1.binkp.net
    f59.n3634.z1.binkp.net is an alias for microbur.synchro.net. microbur.synchro.net has address 108.233.175.10

    But... it's resolving to *your* BBS? You're trying to send an areafix netmail to yourself?
    --
    digital man (rob)

    Rush quote #81:
    Catch the witness, catch the wit, catch the spirit, catch the spit
    Norco, CA WX: 71.3øF, 72.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs
    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Dennis Slagers@VERT to Xofraq on Friday, October 04, 2024 11:32:14
    Hello Xofraq!

    03 Oct 24 20:44, you wrote to all:


    BINKOUT Running native timed event: BINKOUT
    10/3 20:30:50 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/3 20:30:50 evnt BINKOUT Attempting callout for 1:3634/59@fidonet,
    file: /home/pi/sbbs/fido/outbound/0e32003b.out 10/3 20:30:50 evnt
    BINKOUT JSBinkP/4 callout to 1:3634/59@fidonet started 10/3 20:30:50
    evnt BINKOUT Connecting to 1:3634/59@fidonet at f59.n3634.z1.binkp.net:24554 10/3 20:30:50 evnt BINKOUT Connection to f59.n3634.z1.binkp.net:24554 failed (Error: Name or service not
    known). 10/3 20:30:50 evnt BINKOUT Timed event: BINKOUT returned 0

    tried it

    Parsing nodelist file /var/spool/ftn/nodelist/NODELIST.277
    Nodelist for Thursday, October 3, 2024 -- Day number 277 parsed, 945 IP-nodes pr ocessed (0.012 sec)
    Calling '1:3634/59'. Call time: '0000-2400' UTC.
    Now is: 0931 UTC.
    microbur.synchro.net, 24554
    Calling 1:3634/59 (108.233.175.10:24554)
    OPT CRAM-MD5-176a8ea27fe0739462cabd35d24e8929
    SYS MicroBurst II BBS
    ZYZ stacy caudle
    LOC Gastonia, NC
    NDL 115200,TCP,BINKP
    TIME Fri Oct 04 2024 05:31:42 GMT-0400 (EDT)
    VER BinkIT/2.41,JSBinkP/4,sbbs3.20a/Linux binkp/1.1
    address: 1:3634/59@fidonet
    address: 1337:3/202@tqwnet
    address: 954:895/73@hobbynet
    108.233.175.10 - Ok.
    Session with 1:3634/59 done.

    the only thing I can think of is that the binkp.net domain is causing you troubles.



    Dennis


    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Gamgee@VERT/PALANTIR to Xofraq on Friday, October 04, 2024 07:39:00
    Xofraq wrote to All <=-

    Not sure if this is enough information to get some direction on my Fido setup issue i am having. This is what I see when I try to send areafix netmail.

    BINKOUT Running native timed event: BINKOUT
    10/3 20:30:50 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/3 20:30:50 evnt BINKOUT Attempting callout for 1:3634/59@fidonet,
    file: /home/pi/sbbs/fido/outbound/0e32003b.out 10/3 20:30:50 evnt
    BINKOUT JSBinkP/4 callout to 1:3634/59@fidonet started 10/3 20:30:50
    evnt BINKOUT Connecting to 1:3634/59@fidonet at f59.n3634.z1.binkp.net:24554 10/3 20:30:50 evnt BINKOUT Connection to f59.n3634.z1.binkp.net:24554 failed (Error: Name or service not known). 10/3 20:30:50 evnt BINKOUT Timed event: BINKOUT returned 0

    I can't seem to find what I have configured wrong. Thanks in advance
    for any direction. Xofraq

    There have been issues lately with the binkp.net resolving fidonet-style addresses to an IP address.

    You can avoid that by defining the location of a nodelist file on your
    BBS machine, in the [domain] section for Fidonet, in your sbbsecho.ini
    file.

    It's documented here: https://wiki.synchro.net/config:sbbsecho.ini#domain_sections

    That way, the calling system can just use the normal domain name for the
    called system as defined by the "INA:" part of the nodelist entry.



    ... Gone crazy, be back later, please leave message.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
  • From Gamgee@VERT/PALANTIR to Digital Man on Friday, October 04, 2024 07:40:00
    Digital Man wrote to Xofraq <=-

    BINKOUT Running native timed event: BINKOUT
    10/3 20:30:50 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/3 20:30:50 evnt BINKOUT Attempting callout for 1:3634/59@fidonet, file: /home/pi/sbbs/fido/outbound/0e32003b.out
    10/3 20:30:50 evnt BINKOUT JSBinkP/4 callout to 1:3634/59@fidonet started 10/3 20:30:50 evnt BINKOUT Connecting to 1:3634/59@fidonet at f59.n3634.z1.binkp.net:24554
    10/3 20:30:50 evnt BINKOUT Connection to f59.n3634.z1.binkp.net:24554 failed (Error: Name or service not known).
    10/3 20:30:50 evnt BINKOUT Timed event: BINKOUT returned 0

    I can't seem to find what I have configured wrong. Thanks in advance for any direction. Xofraq

    That hostname seems to resolve for me:
    $ host f59.n3634.z1.binkp.net
    f59.n3634.z1.binkp.net is an alias for microbur.synchro.net. microbur.synchro.net has address 108.233.175.10

    But... it's resolving to *your* BBS? You're trying to send an areafix netmail to yourself?

    I think he mentioned a little while back that he was trying to set up a
    point off of his main system.



    ... Gone crazy, be back later, please leave message.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
  • From Xofraq@VERT/MICROBUR to Dennis Slagers on Friday, October 04, 2024 08:00:00
    Re: Help with FidoNet setup
    By: Dennis Slagers to Xofraq on Fri Oct 04 2024 11:32 am

    the only thing I can think of is that the binkp.net domain is causing you troubles.

    I made some changes and now getting this:

    10/4 07:54:03 evnt BBS Events Semaphore signaled for Timed Event: BINKOUT
    10/4 07:54:03 evnt BINKOUT Running native timed event: BINKOUT
    10/4 07:54:03 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/4 07:54:03 evnt BINKOUT Attempting callout for 1:3634/12@fidonet, file: /home/pi/sbbs/fido/outbound/0e32000c.out
    10/4 07:54:03 evnt BINKOUT JSBinkP/4 callout to 1:3634/12@fidonet started
    10/4 07:54:03 evnt BINKOUT Connecting to 1:3634/12@fidonet at fido-z1.darkrealms.ca:24554
    10/4 07:54:03 evnt BINKOUT Authentication successful: non-secure
    10/4 07:54:03 evnt BINKOUT Timed event: BINKOUT returned 0

    Looks promising, but lets if I get a reply. TY!

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Xofraq@VERT/MICROBUR to Digital Man on Friday, October 04, 2024 08:02:04
    Re: Help with FidoNet setup
    By: Digital Man to Xofraq on Thu Oct 03 2024 09:32 pm

    But... it's resolving to *your* BBS? You're trying to send an areafix netmail to yourself?

    Sounds like someting I would do! (-:

    I made some changes and now I get this:

    10/4 07:54:03 evnt BBS Events Semaphore signaled for Timed Event: BINKOUT
    10/4 07:54:03 evnt BINKOUT Running native timed event: BINKOUT
    10/4 07:54:03 evnt BINKOUT BinkIT/2.41 invoked with options:
    10/4 07:54:03 evnt BINKOUT Attempting callout for 1:3634/12@fidonet, file: /home/pi/sbbs/fido/outbound/0e32000c.out
    10/4 07:54:03 evnt BINKOUT JSBinkP/4 callout to 1:3634/12@fidonet started
    10/4 07:54:03 evnt BINKOUT Connecting to 1:3634/12@fidonet at fido-z1.darkrealms.ca:24554
    10/4 07:54:03 evnt BINKOUT Authentication successful: non-secure
    10/4 07:54:03 evnt BINKOUT Timed event: BINKOUT returned 0

    I will wait for a reply. Thanks!

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Xofraq@VERT/MICROBUR to Gamgee on Friday, October 04, 2024 16:15:09
    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:39 am

    You can avoid that by defining the location of a nodelist file on your
    BBS machine, in the [domain] section for Fidonet, in your sbbsecho.ini
    file.

    I did update to point to the nodelist file. I am not getting the error any more, but I never get a response.

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Gamgee@VERT/PALANTIR to Xofraq on Friday, October 04, 2024 19:07:00
    Xofraq wrote to Gamgee <=-

    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:39 am

    You can avoid that by defining the location of a nodelist file on your
    BBS machine, in the [domain] section for Fidonet, in your sbbsecho.ini
    file.

    I did update to point to the nodelist file. I am not getting the error
    any more, but I never get a response.

    Well, the answer to that probably lies in your log(s). On my system,
    which may not be configured the same as yours, it's in 'sbbs.log'. It
    is VERY likely to be a password mismatch between you and your FidoNet
    hub. Check the log and see what it says when you try to send the
    Areafix netmail. If it is indeed a password issue you'll have to work
    that out with your uplink (hub).



    ... Backup not found: (A)bort (R)etry (P)anic
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
  • From Dumas Walker@VERT/CAPCITY2 to XOFRAQ on Saturday, October 05, 2024 08:05:00
    I did update to point to the nodelist file. I am not getting the error any more, but I never get a response.

    The binkit log info you posted didn't show any mail coming into, or
    leaving, your system.

    Now that you have binkit sorted you may need to send the message(s) again.


    * SLMR 2.1a * And Adam asked, "What's a Headache?"
    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Xofraq@VERT/MICROBUR to Gamgee on Saturday, October 05, 2024 11:45:09
    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:07 pm

    Well, the answer to that probably lies in your log(s). On my system, which may not be configured the same as yours, it's in 'sbbs.log'. It is VERY likely to be a password mismatch between you and your FidoNet hub.

    Will check it out! Thanks for the input.

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Xofraq@VERT/MICROBUR to Gamgee on Sunday, October 06, 2024 18:49:27
    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:07 pm

    which may not be configured the same as yours, it's in 'sbbs.log'. It is VERY likely to be a password mismatch between you and your FidoNet hub. Check the log and see what it says when you try to send the Areafix netmail. If it is indeed a password issue you'll have to work that out with your uplink (hub).

    I have been working with my uplink, and still having the issues. My passwords are correct but seems that my NetMail is not being packed and is being sent out as .out files?

    I have been over my setup 100 times, hope to figure it out soon. I need to step away from it for a few hours (days), lol.

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Gamgee@VERT/PALANTIR to Xofraq on Monday, October 07, 2024 07:55:00
    Xofraq wrote to Gamgee <=-

    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:07 pm

    which may not be configured the same as yours, it's in 'sbbs.log'. It is VERY likely to be a password mismatch between you and your FidoNet hub. Check the log and see what it says when you try to send the Areafix netmail. If it is indeed a password issue you'll have to work that out with your uplink (hub).

    I have been working with my uplink, and still having the issues. My passwords are correct but seems that my NetMail is not being packed and
    is being sent out as .out files?

    I have been over my setup 100 times, hope to figure it out soon. I need
    to step away from it for a few hours (days), lol.

    I have the same uplink. Below is the node definition for that node,
    snipped from my /sbbs/ctrl/sbbsecho.ini file. Obviously the passwords
    have been redacted, but this works fine for me. Put in your own
    passwords on this config and see what happens.

    [node:1:3634/12]
    Name = Mark Lewis
    Comment = Southeast Star
    Archive = None
    PacketType = 2+
    PacketPwd = xxxxxxxx
    AreaFix = true
    AreaFixPwd = xxxxxxxx
    SessionPwd = xxxxxxxx
    TicFilePwd = xxxxxxxx
    Inbox =
    Outbox =
    Passive = false
    Direct = true
    Notify = false
    Keys =
    Status = Normal
    BinkpHost = sestar.synchro.net
    BinkpPort = 24554
    BinkpPoll = true
    BinkpPlainAuthOnly = false
    BinkpAllowPlainAuth = false
    BinkpAllowPlainText = true
    BinkpTLS = false


    ... All the easy problems have been solved.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
  • From Xofraq@VERT/MICROBUR to Gamgee on Monday, October 07, 2024 12:43:40
    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Mon Oct 07 2024 07:55 am

    Xofraq wrote to Gamgee <=-

    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:07 pm

    which may not be configured the same as yours, it's in 'sbbs.log'. It
    VERY likely to be a password mismatch between you and your
    FidoNet hub. > Ga> Check the log and see what it says when you try to send the Areafix
    netmail. If it is indeed a password issue you'll have to work that out
    with your uplink (hub).

    I have been working with my uplink, and still having the issues. My passwords are correct but seems that my NetMail is not being packed and
    is being sent out as .out files?

    I have been over my setup 100 times, hope to figure it out soon. I need
    to step away from it for a few hours (days), lol.

    I have the same uplink. Below is the node definition for that node,
    snipped from my /sbbs/ctrl/sbbsecho.ini file. Obviously the passwords
    have been redacted, but this works fine for me. Put in your own
    passwords on this config and see what happens.

    [node:1:3634/12]
    Name = Mark Lewis
    Comment = Southeast Star
    Archive = None
    PacketType = 2+
    PacketPwd = xxxxxxxx
    AreaFix = true
    AreaFixPwd = xxxxxxxx
    SessionPwd = xxxxxxxx
    TicFilePwd = xxxxxxxx
    Inbox =
    Outbox =
    Passive = false
    Direct = true
    Notify = false
    Keys =
    Status = Normal
    BinkpHost = sestar.synchro.net
    BinkpPort = 24554
    BinkpPoll = true
    BinkpPlainAuthOnly = false
    BinkpAllowPlainAuth = false
    BinkpAllowPlainText = true
    BinkpTLS = false


    ... All the easy problems have been solved.

    Just updarted some fields that were diffrent. Let's see what happens. (-:

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!
  • From Xofraq@VERT/MICROBUR to Gamgee on Monday, October 07, 2024 16:11:21
    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Mon Oct 07 2024 07:55 am

    Xofraq wrote to Gamgee <=-

    Re: Re: Help with FidoNet setup
    By: Gamgee to Xofraq on Fri Oct 04 2024 07:07 pm

    which may not be configured the same as yours, it's in 'sbbs.log'. It
    VERY likely to be a password mismatch between you and your
    FidoNet hub. > Ga> Check the log and see what it says when you try to send the Areafix
    netmail. If it is indeed a password issue you'll have to work that out
    with your uplink (hub).

    I have been working with my uplink, and still having the issues. My passwords are correct but seems that my NetMail is not being packed and
    is being sent out as .out files?

    I have been over my setup 100 times, hope to figure it out soon. I need
    to step away from it for a few hours (days), lol.

    I have the same uplink. Below is the node definition for that node,
    snipped from my /sbbs/ctrl/sbbsecho.ini file. Obviously the passwords
    have been redacted, but this works fine for me. Put in your own
    passwords on this config and see what happens.

    [node:1:3634/12]
    Name = Mark Lewis
    Comment = Southeast Star
    Archive = None
    PacketType = 2+
    PacketPwd = xxxxxxxx
    AreaFix = true
    AreaFixPwd = xxxxxxxx
    SessionPwd = xxxxxxxx
    TicFilePwd = xxxxxxxx
    Inbox =
    Outbox =
    Passive = false
    Direct = true
    Notify = false
    Keys =
    Status = Normal
    BinkpHost = sestar.synchro.net
    BinkpPort = 24554
    BinkpPoll = true
    BinkpPlainAuthOnly = false
    BinkpAllowPlainAuth = false
    BinkpAllowPlainText = true
    BinkpTLS = false


    ... All the easy problems have been solved.

    Looks like I am in business! Made these changes, password update and reated a new directory seemed to work. Thanks for the input!

    ---
    þ Synchronet þ MicroBurst II BBS - 30 Years Later!