I recently did the 3.17b update and since have had FTP problems: I nmap'd myself:

PORT STATE SERVICE VERSION
21/tcp open ftp?
| ftp-anon: Anonymous FTP login allowed (FTP code 230)
|_Can't get directory listing: TIMEOUT
|_ftp-bounce: server forbids bouncing to low ports <1025

I set PasvIpAddress in sbbs.ini, checked ports are open, etc but still no bueno unless I connect using 192.x.x.x internal ip ... any ideas

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTP Problem
By: Mortifis to All on Sun Jan 06 2019 11:49 am

I recently did the 3.17b update and since have had FTP problems: I nmap'd myself:

PORT STATE SERVICE VERSION
21/tcp open ftp?
| ftp-anon: Anonymous FTP login allowed (FTP code 230)
|_Can't get directory listing: TIMEOUT
|_ftp-bounce: server forbids bouncing to low ports <1025

I set PasvIpAddress in sbbs.ini, checked ports are open, etc but still no bueno unless I connect using 192.x.x.x internal ip ... any ideas

Was it working fine before the update? If so, what version did you update from?

There's a big difference between active and passive FTP connections - both have their issues, but generally passive is more NAT/firewall friendly. The client controls which mode to use, so to have a real working FTP server, you have to test and make sure both modes are working. I don't know what FTP mode 'nmap' is trying to use. But if you use a command-line 'ftp' client, they generally allow you (the client) to switch between passive and active modes. Web browsers mostly just use passive FTP mode.

The "PasvIpAddress" setting only affects passive FTP mode. If you're having a problem with active FTP mode, then that setting will make no difference.

Read this FAQ carefully:
http://wiki.synchro.net/faq:tcpip#ftp_nat

digital man

Synchronet "Real Fact" #28:
Rob Swindell's first computer was a Commodore VIC-20 (1980).
Norco, CA WX: 56.8oF, 60.0% humidity, 2 mph NNW wind, 0.21 inches rain/24hrs --- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTP Problem
By: Mortifis to All on Sun Jan 06 2019

11:49 am

I recently did the 3.17b update and

since have had FTP problems: I nmap'd

myself:

PORT STATE SERVICE VERSION
21/tcp open ftp?
| ftp-anon: Anonymous FTP login allowed

(FTP code 230)

|_Can't get directory listing: TIMEOUT
|_ftp-bounce: server forbids bouncing

to low ports <1025

I set PasvIpAddress in sbbs.ini,

checked ports are open, etc but still

no bueno unless I connect using

192.x.x.x internal ip ... any ideas

Was it working fine before the update? If

so, what version did you update

from?

I updated from 3.17a last built from source
on Decemver 18th or so ... yes it wss working
before the update.

There's a big difference between active

and passive FTP connections - both

have their issues, but generally passive

is more NAT/firewall friendly. The

client controls which mode to use, so to

have a real working FTP server, you

have to test and make sure both modes are

working. I don't know what FTP

mode 'nmap' is trying to use. But if you

use a command-line 'ftp' client,

they generally allow you (the client) to

switch between passive and active

modes. Web browsers mostly just use

passive FTP mode.

The "PasvIpAddress" setting only affects

passive FTP mode. If you're having

a problem with active FTP mode, then that

setting will make no difference.

Read this FAQ carefully:
http://wiki.synchro.net/faq:tcpip#ftp_nat

Thank you, read the wiki before I posted. I
almost have it working. I opened port 1024 on
my router, seems to have helped a bit but
still is prone to time outs ...using
sbbs/web->File Libraries or web browser
ftp://blah blah blah returns 425 Error 2 type
error.

Hoping it is a config error in /sbbs/web

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTP Problem
By: Mortifis to All on Sun Jan 06 2019 11:49 am

I recently did the 3.17b update and since have had FTP problems: I nmap'd myself:

PORT STATE SERVICE VERSION
21/tcp open ftp?
| ftp-anon: Anonymous FTP login allowed (FTP code 230)
|_Can't get directory listing: TIMEOUT
|_ftp-bounce: server forbids bouncing to low ports <1025

I set PasvIpAddress in sbbs.ini, checked ports are open, etc but still no bueno unless I connect using 192.x.x.x internal ip ... any ideas

Was it working fine before the update? If so, what version did you update from?

There's a big difference between active and passive FTP connections - both have their issues, but generally passive is more NAT/firewall friendly. The client controls which mode to use, so to have a real working FTP server, you have to test and make sure both modes are working. I don't know what FTP mode 'nmap' is trying to use. But if you use a command-line 'ftp' client, they generally allow you (the client) to switch between passive and active modes. Web browsers mostly just use passive FTP mode.

The "PasvIpAddress" setting only affects passive FTP mode. If you're having a problem with active FTP mode, then that setting will make no difference.

I have never had an issue with SBBS FTP, just started with the lastest cvs update following the cvs update instructions. seems the main issue, even using a console or gui client in either mode or especially the web interface is 425 Error 2 selecting socket for connection ... ocassionally it grabs a socket but mostly times out with that error

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTP Problem
By: Mortifis to Digital Man on Sun Jan 06 2019 08:07 pm

I updated from 3.17a last built from source
on Decemver 18th or so ... yes it wss working
before the update.

So you think something changed in the update which is causing your FTP server to stop working?

There's a big difference between active

and passive FTP connections - both

have their issues, but generally passive

is more NAT/firewall friendly. The

client controls which mode to use, so to

have a real working FTP server, you

have to test and make sure both modes are

working. I don't know what FTP

mode 'nmap' is trying to use. But if you

use a command-line 'ftp' client,

they generally allow you (the client) to

switch between passive and active

modes. Web browsers mostly just use

passive FTP mode.

The "PasvIpAddress" setting only affects

passive FTP mode. If you're having

a problem with active FTP mode, then that

setting will make no difference.

Read this FAQ carefully:
http://wiki.synchro.net/faq:tcpip#ftp_nat

Thank you, read the wiki before I posted. I
almost have it working. I opened port 1024 on
my router, seems to have helped a bit but
still is prone to time outs

Helped with what?

...using
sbbs/web->File Libraries or web browser
ftp://blah blah blah returns 425 Error 2 type
error.

Please provide the full/exact error message.

Hoping it is a config error in /sbbs/web

No, nothing in sbbs/web has anything to do with the FTP server. Are you sure you read that FAQ?

digital man

Synchronet/BBS Terminology Definition #2:
ARS = Access Requirement Strings
Norco, CA WX: 49.3oF, 80.0% humidity, 0 mph S wind, 0.20 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTP Problem
By: Mortifis to Digital Man on Sun Jan 06 2019 08:37 pm

The "PasvIpAddress" setting only affects passive FTP mode. If you're having a problem with active FTP mode, then that setting will make no difference.

I have never had an issue with SBBS FTP, just started with the lastest cvs update following the cvs update instructions. seems the main issue, even using a console or gui client in either mode or especially the web interface is 425 Error 2 selecting socket for connection ... ocassionally it grabs a socket but mostly times out with that error

That error can only happen in passive FTP mode. It means that the server basically times-out waiting for the client to connect on the FTP data port. That means that you have something misconfigured between your FTP server and your firewall.

But you haven't really provided much in the way of details, so I can't really help you unless you provide things like log snippets, configuration settings, etc.

digital man

Synchronet/BBS Terminology Definition #5:
BBS = Bulletin Board System
Norco, CA WX: 49.3oF, 80.0% humidity, 0 mph S wind, 0.20 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

interface is 425 Error 2 selecting socket for connection ... ocassionally it grabs a socket but mostly times out with that error

That error can only happen in passive FTP mode. It means that the server basically times-out waiting for the client to connect on the FTP data port. That means that you have something misconfigured between your FTP server and your firewall.

I haven't made any changes to my firewall or router virtual servers

But you haven't really provided much in the way of details, so I can't really help you unless you provide things like log snippets, configuration settings, etc.

config:
[FTP] FTP Server
AutoStart=true
Port=21
MaxClients=10
MaxInactivity=300
QwkTimeout=600
MinFileSize=0
MaxFileSize=0
Interface=

; Passive transfer settings to work-around broken/stupid firewall/NAT devices
; see docs/tcpip_faq.html for details
; the LOOKUP_PASV_IP option can be useful for dynamic IPs
PasvIpAddress=24.138.28.115
PasvPortLow=1024
PasvPortHigh=65535

; Dynamically generated index files
IndexFileName=00index
HtmlIndexFile=00index.html
HtmlIndexScript=ftp-html.js
Options=INDEX_FILE | HTML_INDEX_FILE | ALLOW_QWK | DEBUG_DATA | LOOKUP_PASV_IP

There is nothing in the logs to indicate an error, just times out. If I use a web browser it give the 425 (no way to put any browsers I have in to active mode (PORT) just uses the default PASV). If I use a gui-ftp client in PORT mode it works, or console ftp 'passive off' it works as expected. I have never had to mess with PASV for FTP to work out of the box, since like 2001, just port forward 21 to my ftp server system. If nothing has changed in the update and I haven't changed any router settings or config settings then I am at a loss. I will try to do a fresh install instead of cvs update and see if that instance works :-/

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTP Problem
By: Mortifis to Digital Man on Mon Jan 07 2019 11:16 am

interface is 425 Error 2 selecting socket for connection ... ocassionally it grabs a socket but mostly times out with that error

That error can only happen in passive FTP mode. It means that the server basically times-out waiting for the client to connect on the FTP data port. That means that you have something misconfigured between your FTP server and your firewall.

I haven't made any changes to my firewall or router virtual servers

But you haven't really provided much in the way of details, so I can't really help you unless you provide things like log snippets, configuration settings, etc.

config:
[FTP] FTP Server
AutoStart=true
Port=21
MaxClients=10
MaxInactivity=300
QwkTimeout=600
MinFileSize=0
MaxFileSize=0
Interface=

; Passive transfer settings to work-around broken/stupid firewall/NAT devices
; see docs/tcpip_faq.html for details
; the LOOKUP_PASV_IP option can be useful for dynamic IPs
PasvIpAddress=24.138.28.115
PasvPortLow=1024
PasvPortHigh=65535

For those settings to work, you would have to configure your firewall/gateway to forward all 64,000+ ports between 1024 and 65535 to your BBS's private IP address. Did you do that? A more reasonable number of passive ports would be something like 10 ports (e.g. PasvPortLow=1024, PasvPortHigh=1033).

; Dynamically generated index files
IndexFileName=00index
HtmlIndexFile=00index.html
HtmlIndexScript=ftp-html.js
Options=INDEX_FILE | HTML_INDEX_FILE | ALLOW_QWK | DEBUG_DATA | LOOKUP_PASV_IP

There is nothing in the logs to indicate an error, just times out.

A time-out is an error.

If I use
a web browser it give the 425 (no way to put any browsers I have in to active mode (PORT) just uses the default PASV). If I use a gui-ftp client in PORT mode it works, or console ftp 'passive off' it works as expected.

Okay, so you're only have problems with passive mode. It sounds like active mode is working fine.

I
have never had to mess with PASV for FTP to work out of the box, since like 2001, just port forward 21 to my ftp server system. If nothing has changed in the update and I haven't changed any router settings or config settings then I am at a loss. I will try to do a fresh install instead of cvs update and see if that instance works :-/

No, that's unnecessary. The changes you need to make are in ctrl/sbbs.ini and your firewall/gateway setup. That's it.


digital man

This Is Spinal Tap quote #34:
We'd love to stand around and chat, but we've gotta sit down in the lobby Norco, CA WX: 60.5oF, 64.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

For those settings to work, you would have to configure your firewall/gateway to forward all 64,000+ ports between 1024 and 65535 to your BBS's private IP address. Did you do that? A more reasonable number of passive ports would be something like 10 ports (e.g. PasvPortLow=1024, PasvPortHigh=1033).

I was fiddling with my router earlier to forward 1024 - 1050 but got a invalid range error. Though I have never had to set any of those before and Files Libraries from the web interface worked :-/ oh, well, I will manually forward 10 ports instead of a range and see what happens :)

Thanks for the help, DM

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTP Problem
By: Mortifis to Digital Man on Mon Jan 07 2019 11:16 am

have never had to mess with PASV for FTP to work out of the box, since like 2001, just port forward 21 to my ftp server system. If nothing has changed in the update and I haven't changed any router settings or config settings then I am at a loss. I will try to do a fresh install instead of cvs update and see if that instance works :-/

No, that's unnecessary. The changes you need to make are in ctrl/sbbs.ini and your firewall/gateway setup. That's it.

All good now, I need a new router, had to add each port forward manually. I am not sure why I had to all of a sudden as it has always just worked without having to do that :-/

---
* Synchronet * The Empty Keg BBS emptykeg.synchro.net:82 Lake Echo NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTP Problem
By: Mortifis to Digital Man on Mon Jan 07 2019 05:56 pm

Re: Re: FTP Problem
By: Mortifis to Digital Man on Mon Jan 07 2019 11:16 am

have never had to mess with PASV for FTP to work out of the box, since like 2001, just port forward 21 to my ftp server system. If nothing has changed in the update and I haven't changed any router settings or config settings then I am at a loss. I will try to do a fresh install instead of cvs update and see if that instance works :-/

No, that's unnecessary. The changes you need to make are in ctrl/sbbs.ini and your firewall/gateway setup. That's it.

All good now, I need a new router, had to add each port forward manually. I am not sure why I had to all of a sudden as it has always just worked without having to do that :-/

Maybe your method of testing has changed?

digital man

Synchronet/BBS Terminology Definition #24:
DTE = Data Terminal Equipment
Norco, CA WX: 58.2oF, 76.0% humidity, 3 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2019 Jan 07 17:56:16, you wrote to Digital Man:

All good now, I need a new router, had to add each port forward
manually. I am not sure why I had to all of a sudden as it has always
just worked without having to do that :-/

are you running FTP on the standard ports 20&21? if not, that could explain it... i tried to explain some of it in irc the other day but i guess i failed or maybe didn't get that train on the track before it wandered off...

network modules... eg: nf_nat_ftp, nf_conntrack_ftp and similar... they know that ftp takes place on port 20 and 21 as well as possibly a range for passive... when a session starts, they mark that first packet... other packets related to that stream can be detected and automatically passed through the system... if you try to run your ftp server on non-standard ports, these tools cannot do their job and ftp breaks between the WAN and the LAN... it /might/ be
possible to add special command options to these modules in their load call but
that depends on the firewall as this is deep in the innards of the system and its startup... moving ftp is not as easy as it is moving telnet, web or similar...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... COOK: 1. Act of preparing food for consumption. 2. Mom's other name.
---
* Origin: (1:3634/12.73)

On 2019 Jan 07 17:56:16, you wrote to Digital Man:

All good now, I need a new router, had to add each port forward manually. I am not sure why I had to all of a sudden as it has always just worked without having to do that :-/

are you running FTP on the standard ports 20&21? if not, that could explain it... i tried to explain some of it in irc the other day but i guess i failed or maybe didn't get that train on the track before it wandered off...

network modules... eg: nf_nat_ftp, nf_conntrack_ftp and similar... they know that ftp takes place on port 20 and 21 as well as possibly a range for passive... when a session starts, they mark that first packet... other packets related to that stream can be detected and automatically passed through the system... if you try to run your ftp server on non-standard ports, these tools cannot do their job and ftp breaks between the WAN and the LAN... it /might/ be
possible to add special command options to these modules in their load call but
that depends on the firewall as this is deep in the innards of the system and its startup... moving ftp is not as easy as it is moving telnet, web or similar...

Turned out to be my router had an automagically applied firmware update, prior to the update the NAT handled the port 20/21 PASV on-demand, the firmware update required me to open and forward each subsequent port manually, along with a very limited and strict range. It was just a coincidence that it happened around the same time I did the 3.17b update. No worries, got it back working as usual.

---
* Synchronet * Twisted Truckers BBS alleycat.synchro.net:81 Dartmouth NS Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)