On 08/24/2018 03:53 PM, ToddAndMargo wrote:
On 08/24/2018 03:40 PM, Samuel Sieb wrote:
> On 08/24/2018 03:23 PM, ToddAndMargo wrote:
>> # insmod nf_conntrack_ftp
>> insmod: ERROR: could not load module nf_conntrack_ftp: No such file
>> or directory
>
> That's because you didn't specify an actual file. Try passing the
> entire path to the module.
>
> But the proper way is to use "modprobe nf_conntrack_ftp".
>
> However, as several people have mentioned, there should not be any
> restrictions on using an ftp client. At the start of this thread, it
> would have been good if you had described the actual problem you are
> trying to solve. Please do that.
I just figured out I should be using modprobe and not insmod.
I have iptables-config set to
IPTABLES_MODULES=nf_conntrack_ftp nf_conntrack_tftp nf_nat_ftp nf_nat_tftp
I will reboot and try again.
The actual problem is
Aug 22 16:12:09 rn6 kernel: dsl-out Everything Else IN= OUT=eno2
SRC=192.168.xxx.yyy DST=208.106.xxx.yyy LEN=60 TOS=0x00 PREC=0x00 TTL=64
ID=25991 DF PROTO=TCP SPT=59698 DPT=21023 WINDOW=29200 RES=0x00 SYN URGP=0
Which is iptables not tracking the high ports ftp uses. And
that has not changed since I posted.
I will get back after the reboot. (with NVMe that is fast.)
-T
I modprobe'ed all four in.
They showed in `lsmod | grep ftp`
I ran a
systemctl restart iptables
No joy.
Then I rebooted. Now
`lsmod | grep ftp`
show nothing.
badwordbadwrodbadwordbadwrod
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~