BBS: TELESC.NET.BR Assunto: Synchronet 3.21e upgrade De: hax0r Data: Sat, 25 Apr 2026 09:43:05 -0700 ----------------------------------------------------------- hbRenb: hcSynchronet 3.21e upgrade bBynb: hcMRO bto chax0r bon cFri Apr 24 2026 09:37 pmn MR> i sent you a msg to vert. i'm not sure if you have the same email anymore. MR> i can answer any questions you might have an i have some scripts that can MR> 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. 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. 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. n --- mSynchronetn hgVertrauen n hHome of Synchronet n gh[vert/cvs/bbs].synchro.net ----------------------------------------------------------- [Voltar]