Yes thanks Lonnie. I thought that was the case. Im pretty sure that it won’t be
a port range problem as its a standard application that is used on many sites
and they say that its only this site that is broken.
Interestingly the customer has two Astlinux boxes onsite (dual broadband
connections
Hi Michael,
OK, to make sure we are on the same page, the setup (as I read it) is as
follows...
Public FTP Server (PASV) -- AstLinux (edge router) -- Private FTP Client
correct ?
And yes, if correct, the "nf_nat_ftp" module is not used in this case since all
FTP connections are outbound by th
Thanks Lonnie
nf_nat_ftp 972 0
nf_nat 10076 3 ipt_MASQUERADE,nf_nat_ftp,iptable_nat
nf_conntrack_ftp3784 1 nf_nat_ftp
nf_conntrack 36939 8
ipt_MASQUERADE,nf_nat_ftp,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state,xt_conntrack,nf_conntrack_ftp
Loo
Replying to myself,
It seems AIF automatically modprobe's "nf_nat_ftp" if NAT is enabled. So first
try:
--
lsmod | grep nf_nat_ftp
--
to see if "nf_nat_ftp" is loaded already.
Of course if AstLinux is not the edge router then it is more complicated.
Lonnie
On Sep 11, 2014, at 8:03 PM, Lonni
Hi Michael,
On the AstLinux system try:
--
modprobe nf_nat_ftp
--
and then try again.
If that works, you can make it persistent by adding "nf_nat_ftp" into
/etc/rc.modules or "modprobe nf_nat_ftp" into /mnt/kd/rc.local, etc. .
Lonnie
On Sep 11, 2014, at 7:08 PM, Michael Knill
wrote:
> Hi G
Hi Group
I have an unusual one that Im not really sure where to start.
The customer has an application which FTP’s (not SFTP mind you) files from a
central site. Using PASSIVE FTP, when it tries to connect the data channel the
session times out. There are no entries in the log. It is using Astli
