1. Forum
  2. DOVE-Net
  3. Synchronet Baja

  • qnet-ftp and non-standard ports

    From Nightfox@DIGDIST to Digital Man on Sunday, November 01, 2009 21:17:26
    Hi -

    In the process of using the qnet-ftp script to set up my BBS with a QWK hub with a non-standard FTP port, I seem to have spotted a bug in the qnet-ftp script.

    I've updated my sbbs\exec directory from the CVS repository and noticed that
    a couple years ago, the qnet-ftp script had been updated to take a port number as the last argument. However, it seems to be setting the port number to only the last digit of the port number specified on the command line. For example, I'm specifying port 2121 on the qnet-ftp command-line; I added a line of debugging in the qnet-ftp script during its command-line processing, under the "case 3" (where it's setting the port variable) to output the port that it gets. It seems to be iterating over each digit in the port argument. This is the output I see in my Synchronet events window (with my line of debug output) when my BBS does the network call-out (my password has been hidden with asterisks): 11/1 09:10:26p QNET-FTP: KELLYS kellys.synchro.net ******** 2121
    11/1 09:10:26p *** Passed port: 2
    11/1 09:10:26p *** Passed port: 1
    11/1 09:10:26p *** Passed port: 2
    11/1 09:10:26p *** Passed port: 1
    11/1 09:10:26p QNET-FTP: Connecting to kellys.synchro.net:1 ...

    Would this be easily fixable?

    Nightfox

    ---
    ■ Synchronet ■ Digital Distortion BBS: digdist.bbsindex.com
  • From Digital Man to Nightfox on Sunday, November 01, 2009 22:26:22
    Re: qnet-ftp and non-standard ports
    By: Nightfox to Digital Man on Sun Nov 01 2009 09:17 pm

    Hi -

    In the process of using the qnet-ftp script to set up my BBS with a QWK hub with a non-standard FTP port, I seem to have spotted a bug in the qnet-ftp script.

    I've updated my sbbs\exec directory from the CVS repository and noticed
    that a couple years ago, the qnet-ftp script had been updated to take a
    port number as the last argument. However, it seems to be setting the port number to only the last digit of the port number specified on the command line. For example, I'm specifying port 2121 on the qnet-ftp command-line;
    I added a line of debugging in the qnet-ftp script during its command-line processing, under the "case 3" (where it's setting the port variable) to output the port that it gets. It seems to be iterating over each digit in the port argument. This is the output I see in my Synchronet events window (with my line of debug output) when my BBS does the network call-out (my password has been hidden with asterisks): 11/1 09:10:26p QNET-FTP: KELLYS kellys.synchro.net ******** 2121
    11/1 09:10:26p *** Passed port: 2
    11/1 09:10:26p *** Passed port: 1
    11/1 09:10:26p *** Passed port: 2
    11/1 09:10:26p *** Passed port: 1
    11/1 09:10:26p QNET-FTP: Connecting to kellys.synchro.net:1 ...

    Would this be easily fixable?

    Try this:

    http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/exec/qnet-ftp.src

    That should fix it.

    digital man

    Snapple "Real Fact" #27:
    A ball of glass will bounce higher then a ball of rubber.
  • From Nightfox@DIGDIST to Digital Man on Sunday, November 01, 2009 23:02:10
    Re: qnet-ftp and non-standard ports
    By: Digital Man to Nightfox on Sun Nov 01 2009 22:26:22

    Try this:

    http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/exec/qnet-ftp.src

    That should fix it.

    That works.. Thanks.

    Nightfox

    ---
    ■ Synchronet ■ Digital Distortion BBS: digdist.bbsindex.com