John,
Jeremy,
- From any VM I can ftp the pureftpd VMs (persee1 & 2) without any
problem
- If I ftp the HAProxy VM Ip, I don't even get a ftp banner.
- Using tcpdump on the ftp vm, I can see that HAProxy sends a packet
to pureftpd, which responds, but
it doesn't seem to be forwarded.
Again, everything works with 1.4.15.
Does the HAProxy stats page show the server as up? It wouldn't
surprise me if you got into trouble with FTP data ports but I wouldn't
expect it to fail before banner / auth.
Is this the exact config that failed, or from your functional
configuration?
I kept the very same configuration across versions. The ftp server shows
as up in stats page.
The only thing that changes is the haproxy version.
mode tcp
timeout client 1h
bind publicip:21,publicip:990,publicip:50000-50400
default_backend pureftpd_backend
backend pureftpd_backend
mode tcp
timeout server 1h
server persee1 172.16.0.11 check port 21 inter 10s rise 1 fall 2
server persee2 172.16.0.12 check port 21 inter 10s backup
Once you get past the connection issue you'll also need to validate
that you've properly configured pureftpd. You should have limited it
to passive mode and specified the desired port range (50000-50400).
You may also need to use a setting that tells it to falsify it's IP
address and present the public IP instead.
Still doesn't explain why it isn't working up to the banner though.
-JohnF
Yep, this is set correctly; had a fun time searching informations and
configuring everything,
but everything has worked perfectly with haproxy 1.4.15 for months now;
however I am no tcp guru.
This is not critical for me ATM, but it may be to some.
Given directions, I can produce traces however if it can help.
Jérémy Longo
