Contents
Why is conntrack not working on iptables with TFTP?
Its the rule you are using for tftp initial connection that is to specific (at least I’d believe). Try to split it up. One for new connections one for related and one for established. Your rule only works with destination port 69 but the data connection is not on port 69 so this rule does not match.
How to solve passive FTP not working problem?
An ftp connection also needs a data transfer channel using active or passive session. Make sure firewall is not blocking your FTP session. If ports are open make sure IPtables is allowing passive ftp. To solve this problem add ip_conntrack_ftp module. Type the following command to load this module:
What are the rules for passive FTP in Linux?
Iptables passive ftp rules Category List of Unix and Linux commands File Management cat • ncdu Firewall Alpine Awall • CentOS 8 • OpenSUSE • RHE Network Utilities NetHogs • dig • host • ip • nmap OpenVPN CentOS 7 • CentOS 8 • Debian 10 • Debian
What to do if firewall is blocking your FTP session?
Make sure firewall is not blocking your FTP session. If ports are open make sure IPtables is allowing passive ftp. To solve this problem add ip_conntrack_ftp module. Type the following command to load this module: # modprobe ip_conntrack_ftp.
What should I do if my conntrack is not working?
Technicaly your totaly right, but I’d say in case of the conntrack helper we can bump UDP up to a statefull protocol. Its the rule you are using for tftp initial connection that is to specific (at least I’d believe). Try to split it up. One for new connections one for related and one for established.
Why is my sepcial accept rule not working with TFTP?
Your rule only works with destination port 69 but the data connection is not on port 69 so this rule does not match. You might also need a sepcial accept rule for the tftp_con_track module.