|
Hi,
Sorry that I forgot to mention that don't install ip masq application modules
(such as ip_masq_ftp.o) for PCC scheduling. Since the ip masq application
modules are used to handle connections from inside to access Internet service
through IP masquerading box, those modules will keep PCC scheduling
from working, because the LinuxDirector box work in the reverse direction
(from outside to inside for virtual service).
If you have already install ip_masq_ftp.o,
rm /lib/modules/2.2.10/ipv4/ip_masq_ftp.o
reboot your system and see what happens.
Wensong
Ted Pavlic wrote:
> Actually, active FTP was broken before you spoke of the PCC scheduling. I
> tried the PCC scheduling and now active works, but passive is still broken.
>
> Should passive work as well? I heard that there was an issue in
> net/ipv4/ip_masq_ftp.c that kept passive ftp from working...
>
> An excerpt from a message from Eddie E. Shi (eshi@xxxxxxxxxxxxxxxxx):
> =====
> I've checked the source code and found out that the module
> ~net/ipv4/ip_masq_ftp.c is supposed to handle the situation by adding an
> masq entry for 216,69,192,197,4,25 which xlate to 216.69.192.197:1049 so
> that the ftp client will be able to connect to LVS and be scheduled to the
> ftp server.
>
> Unfortunately , ip_masq_ftp.c has a bug which prevent this from happening.
> =====
>
> So I think that might be the trouble with passive ftp.
>
> All the best --
> Ted
>
|
