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ã

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.ã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

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ã