Subj : Synchronet 3.21e upgrade To : hax0r From : Digital Man Date : Sat Apr 25 2026 02:43 pm Re: Synchronet 3.21e upgrade By: hax0r to MRO on Sat Apr 25 2026 09:43 am > Re: Synchronet 3.21e upgrade > By: MRO to hax0r on Fri Apr 24 2026 09:37 pm > > MR> i sent you a msg to vert. i'm not sure if you have the same email > MR> anymore. i can answer any questions you might have an i have some > MR> scripts that can help fix and convert your stuff so it works ok. > > I got the invite and will join up. e-mail address is still valid. I did > manage to track down what the problem is with the current QWK config. It > seems like at some point in tim the Synchronet FTP server stopped support > for PASV ftp connections. No, the Synchronet FTP server (and Vertrauen) still support passive FTP: $ ftp dove.synchro.net Trying 71.95.196.36:21 ... Connected to dove.synchro.net. Synchronet files are located in /Synchronet Synchronet files are mirrored on ftp.synchro.net (faster). .... ftp> dir 229 Entering Extended Passive Mode (|||1025|) 150 Opening ASCII mode data connection for /bin/ls. -r--r--r-- 1 VERT VERT 512 Apr 25 14:42 00index -r--r--r-- 1 VERT VERT 10240 Apr 25 14:42 VERT.qwk > One of the things that my vert.ftp file does is > issue a PASV command, to which it gets an "Invalid Command" response. The > system is behind a 1:1 NAT so active FTP will not work. > > Also, I think i have found out the culprit of my "blocked" connections. I > noticed that the Synchronet Control Panel services log did not have > anyactivity in it since 4/24 10:52:24p. All nodes reported "Waiting for > Connection". Performing a Test-Netconnetion on port 22 and 23 returned true, > however attempting to connect via Telent or SSH just hung. A socket > connection was established, but there was not output. Turns out there were 4 > CMD sessions on the host all stuck in the callout to vert for QWK in with: > > ftp> pasv > Invalid command. That's the Windows FTP client (ftp.exe), nothing to do with Synchronet: >ftp ftp> pasv Invalid command. It appears Windows' ftp.exe has never supported passive mode: https://learn.microsoft.com/en-us/answers/questions/1821850/ftp-exe-and-passive-mode Maybe you were using a different ftp.exe (not from Microsoft) at some point? > ftp> put c:\sbbs\data\vert.rep vert.rep > 504 Bad port number. > 150 Opening ASCII mode data connection for /bin/ls. > > Once I killed one of these sessions the telent/ssh sessions started working > again. Its pecurliar that there were 4 hung callouts and i have 4 nodes and > non ofthem were able to respond. > > I will look into the newer QWK config, but if it is dependent on FTP i may > have an issue. Should work fine because both the script (qnet-ftp.js) and the sever still support passive FTP mode. And event active (the original) FTP mode can work behind a 1:1 NAT if you have an FTP-ALG, but that's no matter: passive FTP works fine. -- digital man (rob) This Is Spinal Tap quote #32: Derek Smalls: [A jog?] We don't have time for that. Norco, CA WX: 68.2øF, 50.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.37-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) .