1. Forum
  2. FidoNet
  3. SYNCHRONET

  • I broke telgate?

    From Vague@1:135/391 to All on Tuesday, July 08, 2025 19:32:57
    I'm not sure what I did, but I am unable to telgate now. Something I did is causing me to get this when I try:

    Connecting to remote host ...
    !ERROR -1 (49) binding to socket
    telgate.js: Failed to connect to remote host

    It was working fine for a long time, but something I changed recently must have broken it, and I have no idea what it could have been. It's not the receiving end. I can directly connect to it.

    Any insight would be very welcome.
    --- SBBSecho 3.23-Win32
    * Origin: Vague BBS - vague.ddns.net (1:135/391)
  • From Digital Man@1:103/705 to Vague on Tuesday, July 08, 2025 17:20:40
    Re: I broke telgate?
    By: Vague to All on Tue Jul 08 2025 07:32 pm

    I'm not sure what I did, but I am unable to telgate now. Something I did is causing me to get this when I try:

    Connecting to remote host ...
    !ERROR -1 (49) binding to socket
    telgate.js: Failed to connect to remote host

    It was working fine for a long time, but something I changed recently must have broken it, and I have no idea what it could have been. It's not the receiving end. I can directly connect to it.

    Any insight would be very welcome.

    $ grep 49 /usr/include/*/*errno.h
    /usr/include/asm-generic/errno.h:#define EUNATCH 49 /* Protocol driver not attached */

    Double-check the value of your [BBS] OutboundInterface setting in ctrl/sbbs.ini. If it's blank, maybe you're having a problem with IPv4 or IPv6 address binding in general. Try instead:
    - 0.0.0.0
    - ::
    - The IPv4 address of your primary network adapter
    --
    digital man (rob)

    Steven Wright quote #11:
    I almost had a psychic girlfriend, ..... But she left me before we met.
    Norco, CA WX: 89.2øF, 31.0% humidity, 10 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.28-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Vague@1:135/391 to Digital Man on Tuesday, July 08, 2025 20:53:22
    There we go!
    The OutboundInterface was set to 255.255.255.255. Removing that and leaving it blank fixed the issue. I don't remember changing that, but here we are.

    Thank you. For the help, for Synchronet, and for all your work. You rock!
    --- SBBSecho 3.23-Win32
    * Origin: Vague BBS - vague.ddns.net (1:135/391)
  • From MRO@1:103/705 to Vague on Wednesday, July 09, 2025 13:06:29
    Re: I broke telgate?
    By: Vague to All on Tue Jul 08 2025 07:32 pm

    I'm not sure what I did, but I am unable to telgate now.
    Something I did is causing me to get this when I try:

    Connecting to remote host ... !ERROR -1 (49) binding to socket
    telgate.js: Failed to connect to remote host

    It was working fine for a long time, but something I changed recently
    must have broken it, and I have no idea what it could have been.
    It's not the receiving end. I can directly connect to it.


    restore a backup
    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From MRO@1:103/705 to Vague on Wednesday, July 09, 2025 13:07:58
    Re: I broke telgate?
    By: Vague to Digital Man on Tue Jul 08 2025 08:53 pm

    There we go!
    The OutboundInterface was set to 255.255.255.255. Removing that and
    leaving it blank fixed the issue. I don't remember changing that,
    but here we are.

    Thank you. For the help, for Synchronet, and for all your work. You

    something went wonky with your network and synchronet updated it.
    i saw it happen before.
    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)