Does not bind/listen to ports with 1.3.7b about proftpd-mod_autohost

[clmerriman]

It does resolve the issue. All ports are answering.

Thanks again.

[Castaglia]

It's a bit of sticky issue, due to changes in the core Bindings API (which, in turn, are related to SNI/HOST support); the specific loss of functionality impacted the AutohostPorts directively specifically.

I may have to rethink how that directive works. How do you use it, specifically? Put another way, why do you use AutohostPort, rather than using a Port directive in each of the config files?

[clmerriman]

i currently use port-specific autohost config files. This allows a one virtualhost to handle ports 21 and 990, while another handles just port 22. (The unsupported ports are configrued with a <LIMIT LOGIN>DenyAll</LIMIT>.)

As I understand it, AutoHostPorts tells proftpd which ports to listen on. The actual config file is not read until a connection is made. I'm not sure how a Port directive in the autohost config would have any impact.

What am I missing? Is there an alternative setup?

[Castaglia]

Argh. I found the offending commit -- specifically this bit:

# src/bindings.c
static int init_standalone_bindings(void) {
  int res = 0;
  server_rec *serv = NULL;
  unsigned char *default_server = NULL, is_default = FALSE;

+  memset(ipbind_table, 0, sizeof(ipbind_table));

By clearing the ipbind_table here, the ProFTPD 1.3.7b code is effectively erasing all of the bindings that mod_autohost sets up. Which means that this cannot be easily fixed by mod_autohost -- it's more a bug in the core ProFTPD engine. I'll see what I can do to get that fixed; will need to re-remember why I thought that ipbind_table clearing was needed in the first place.

[Castaglia]

@clmerriman Would you be able to build ProFTPD with proftpd/proftpd#1311, and verify that it fixes the mod_autohost behavior for you? It does seem to fix things for my local testing...