1. Forum
  2. Fidonet
  3. SYNC SYSOPS

  • QWK Network

    From Sys64738@1:103/705 to All on Fri Jan 7 09:12:57 2022
    I'm setting up a QWK network, but I keep running into an error.

    1/7 08:53:47a QNET FTP Session with 160.2.36.126 failed: Error: Invalid port 1/7 08:53:47a QNET Call-out to: BOGUSNET returned 1

    Below is how I have the "Call-out Command Line" set up for the network hub.

    *qnet-ftp %s 160.2.36.126 98 Password01!

    "98" is the port I'm trying to direct the traffic to because the hub is set up to receive traffic on that port

    I'm thinking that I have a syntax issue in the Call-out Command Line. I've tried adding the port as "160.2.36.126:98", "160.2.36.126/98", "160.2.36.126\98" and as you see above "160.2.36.126 98".

    Anyone have any idea of where I've gone wrong?

    SYS64738

    ---
    þ Synchronet þ TEXNet
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Trikester@1:103/705 to Sys64738 on Fri Jan 7 10:28:48 2022
    Re: QWK Network
    By: Sys64738 to All on Fri Jan 07 2022 09:12 am

    *qnet-ftp %s 160.2.36.126 98 Password01!
    "98" is the port I'm trying to direct the traffic to because the hub is set up to receive traffic on that port

    If I'm reading the code correctly, the port argument comes after the password.

    var addr = options.address || argv[1];
    var password = options.password || argv[2];
    var port = options.port || argv[3] || 21;

    Hope that works.

    ---
    þ Synchronet þ ... The Basement ... Not really open yet.
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Trikester on Fri Jan 7 12:40:07 2022
    Re: QWK Network
    By: Trikester to Sys64738 on Fri Jan 07 2022 10:28 am

    Re: QWK Network
    By: Sys64738 to All on Fri Jan 07 2022 09:12 am

    *qnet-ftp %s 160.2.36.126 98 Password01!
    "98" is the port I'm trying to direct the traffic to because the hub is set up to receive traffic on that port

    If I'm reading the code correctly, the port argument comes after the password.

    var addr = options.address || argv[1];
    var password = options.password || argv[2];
    var port = options.port || argv[3] || 21;

    Hope that works.

    Correct, the port, if specified, comes last on the command-line.
    --
    digital man (rob)

    Synchronet "Real Fact" #44:
    Synchronet added JavaScript suppport with v3.10a (2001).
    Norco, CA WX: 63.2øF, 61.0% humidity, 2 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Sys64738@1:103/705 to Trikester on Fri Jan 7 14:53:12 2022
    Re: QWK Network
    By: Trikester to Sys64738 on Fri Jan 07 2022 10:28:48

    *qnet-ftp %s 160.2.36.126 98 Password01!
    "98" is the port I'm trying to direct the traffic to because the hub is set up to receive traffic on that port

    If I'm reading the code correctly, the port argument comes after the password.

    var addr = options.address || argv[1];
    var password = options.password || argv[2];
    var port = options.port || argv[3] || 21;

    Hope that works.

    I think that did it. At the very least, I'm not getting that "invalid port" error any more. :)

    SYS64738

    ---
    þ Synchronet þ TEXNet
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Gamgee@1:103/705 to Sys64738 on Fri Jan 7 14:24:00 2022
    Sys64738 wrote to All <=-

    I'm setting up a QWK network, but I keep running into an error.

    1/7 08:53:47a QNET FTP Session with 160.2.36.126 failed: Error:
    Invalid port 1/7 08:53:47a QNET Call-out to: BOGUSNET returned
    1

    Below is how I have the "Call-out Command Line" set up for the
    network hub.

    *qnet-ftp %s 160.2.36.126 98 Password01!

    "98" is the port I'm trying to direct the traffic to because the
    hub is set up to receive traffic on that port

    I'm thinking that I have a syntax issue in the Call-out Command
    Line. I've tried adding the port as "160.2.36.126:98",
    "160.2.36.126/98", "160.2.36.126\98" and as you see above
    "160.2.36.126 98".

    Anyone have any idea of where I've gone wrong?

    It uses FTP for the transfers, you may not have the FTP server enabled
    in ../ctrl/sbbs.ini. I don't think you can specify a port like '98'
    because the FTP is using port 21.



    ... A woman drove me to drink, and I never had the courtesy to thank her.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mike Powell@1:103/705 to SYS64738 on Fri Jan 7 17:53:00 2022
    "98" is the port I'm trying to direct the traffic to because the hub is set up
    to receive traffic on that port

    I'm thinking that I have a syntax issue in the Call-out Command Line. I've tr
    d adding the port as "160.2.36.126:98", "160.2.36.126/98", "160.2.36.126\98" a
    as you see above "160.2.36.126 98".

    Anyone have any idea of where I've gone wrong?

    Is the hub set up to receive *FTP* traffic on that port? If that is their telnet port, that is not the port you want for QWK networking.

    I am not sure of the syntax as I have never tried QWK networking to a
    server running a non-standard ftp port.


    * SLMR 2.1a * This message protected by DALETECH!!

    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)