Tag Info

New answers tagged

1

The problem is, that iptables-persistent calls iptables-restore during bootup before the network is initialised. Therefore you cannot do dns-lookups at this point. You either have to use the ip-address instead of a domain name or load the domain-related rules at a later time e.g. via rc.local.


0

What iptables-persistent does is it saves the rules to /etc/iptables/rules.v4 or /etc/iptables/rules.v6 at install time, and by using webwin to remove the rules, it saved a ruleset that had no rules. Note that ip6tables uses /etc/iptables/rules.v6, while iptables uses /etc/iptables/rules.v4`. Add your rules to the iptables and ip6tables firewalls. Then, ...


0

ufw is not capable of doing this because it is outside of its scope. Typical iptables rules need to be implemented instead.


0

This simple one liner run as root will quickly find all the names and run them through a for look that runs the 'iptables -X' on the name of the chain. for ufw in `iptables -L |grep ufw|awk '{ print $2 }'`; do iptables -X $ufw; done


0

Test this: Open a terminal. Run it: sudo -i mv /etc/rc2.d/rc.firewall /etc/init.d/ chmod 755 /etc/init.d/rc.firewall update-rc.d rc.firewall defaults


0

The problem has been solved by adding those strings: • -A INPUT -p udp -m udp --dport 1024:65535 --sport 53 -j ACCEPT • -A INPUT -p tcp -m tcp --dport 1024:65535 --sport 53 -j ACCEPT • -A INPUT -i lo -j ACCEPT



Top 50 recent answers are included