System is PPPoE
He ran tdpdump in passive ftp mode . Dachstein showns the mss at differnt stages of the ftp as 1460 and 1412 In Bering the tcpdump log shows that mss is 1452 and 1460. Bering has CLAMPMSS = Yes
The internal ftp passive mode client log shows the port that it will send the ftp file.
The tcpdump shows that in Dachstien that port is used and the ftp is successful.
In Bering the port used by the client shows in the tcpdump file AS ONE PORT LOWER THAN THE REQUESTED PORT.
Why would ip_conntrack_ftp assign a passive client one port lower than the agreed upon port for transfer.
******
if the ftp log shows that the tcp port for sending the file is supposed to be 13780
tcpdump on the Bering firewall shows the packet is sent on port 13779 and the ftp fails.
******
Is this a bug in ip_conntrack_ftp that only shows up when a client sends a file?
Passive clients probably usually recieve files instead of sending them.
Anyone else seen this problem? My friend's weather station will not send ftp files through the Bering box. It will send files through the Dactsein box. All hardware, application program , remote ftp server and ISP are the same.
-- Victor McAllister
------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
