Hi Kusankar,

thank you for your reply.

The problem it's a bit different that what I reported you first.

The ftp don't stop to work, only the "quit" command does.

It seems that it stops to receive the flag "F", when the command "quit" it's issued by the client. The ftp client need to kill the process, to the ftp connection be closed.Or we have to take off the "inspect ftp".

The problem it's that we have machines with ftp scripts configured, and then the machines stay full of ftp connections and processes running.

I will add some logs later. Can I use tcp time-out as workaround?

Thank you.

Best regards,

Does this break after the FWSM module has been up for more than 50 days?

CSCsi27512 You may be running into this issue.

Resolved in 004.000(000.037)          003.002(005.001)          003.001(010)          003.001(009.005)

Does the issue get resolved if you failover?

That makes sense...

The FWSM it's up at almost 1 year.

I didn't try the failover, cause the client need to schedule an intervention to do this.

In the client I didn't saw all this sequence after the quit:

221-  You have transferred 0 bytes in 0 files.

221-  Total traffic for this session was 2551 bytes in 1 transfers.

221-  Thank you for using the FTP service on orbi.

221-  Goodbye

I only see:

You have transferred 0 bytes in 0 files.

I will try to disable the 221 multiline and disable the TCP normalizer, and I let you know the results.

Thank you!

Best regards,