New answers tagged firewall
Alright, I've not gotten any good responses and it took trial and error, as well as monitoring to determine what works to achieve this. I found some things were said to be needed, so the example up above might not work on all systems because a full path should be used on the executables. Also, when specifying a range of ports, you need to add in --match ...
Maybe better than earlier answer; firewall-cmd --permanent --zone=trusted --change-interface=docker0 firewall-cmd --permanent --zone=trusted --add-port=4243/tcp firewall-cmd --reload
In my company we use watch -n 2 -d iptables -nvL, it shows changes between requests
quickest would be to start a netcat listener, e.g. nc -l 23 or ncat -l 23 on the server, then use echo foo | nc server 23 or such on clients to throw data at the server
The above iptables config will only let TCP and UDP packets get past the firewall (unless they came from loopback). The default rule of the INPUT chain has been set to DROP, meaning that every packet that isn't explicitly ACCEPTed will be discarded. There should be no weird packets from loopback, so only TCP/UDP packets are allowed in. There is one major ...
You should be able to re-compile it using something to the similar commands. make KERNEL_DIR=/usr/src/linux make install KERNEL_DIR=/usr/src/linux make dep make bzIamge make make install make modules Source: iptables: Table does not exist (do you need to insmod?)
The better solution may be to just disconnect the guest's NIC in Virtualbox's networking settings until you're ready to bring it online. If you still want to use iptables then on the guest run: sudo iptables -P INPUT DROP sudo iptables -P FORWARD DROP sudo iptables -P OUTPUT DROP This changes the default policy for the chains to DROP.
Top 50 recent answers are included