Hot answers tagged

3

Allow first your local connection and your RELATED, ESTABLISHED connections protocols. $ sudo iptables -A INPUT -p tcp -s 127.0.0.1 -j ACCEPT $ sudo iptables -A INPUT -p tcp -m state --state RELATED,ESTABLISHED -j ACCEPT $ sudo iptables -A INPUT -p udp -m state --state RELATED,ESTABLISHED -j ACCEPT $ sudo iptables -A INPUT -p icmp -m state --state ...


3

Use iptables rule to block outbound traffic for a specific user: http://www.cyberciti.biz/tips/block-outgoing-network-access-for-a-single-user-from-my-server-using-iptables.html This way you even have full control over ranges of ips that get through (for instance, only allow LAN address block). It's probably useful also to block only specific ports. ...


2

On 23/11/12 12:50, Gene Czarcinski wrote: Libvirt is in the process of changing for using bind-interface to using bind-dynamic to fix a security related issue where dnsmasq was responding to port 53 queries which did not occur on an address on the virtual network interface that instance of dnsmasq was supporting. Checking ps -ax|grep dnsmasq, ...


1

You need to allow incoming on the ports you opened, not just outgoing. Otherwise the destination server will not be able to send you a response. If you notice, your ssh works because you're allowing incoming and outgoing. GIT does not work because you're blocking the response from the remote server. DNS is probably broken as well. MySQL: by default your ...



Only top voted, non community-wiki answers of a minimum length are eligible