New answers tagged ufw
You can use apparmor to deny network traffic for some application. First you must install apparmor and apparmor-utils .. sudo apt-get install apparmor* After that you can generate profile to you application ... sudo aa-genprof /usr/bin/google-chrome Next step is to change Networking part in profile to: sudo nano ...
The Fix Update /etc/default/ufw so that IPV6 is equal to no. Notes No ufw disable and ufw enable is required before you can successfully use ufw allow 22. Note that I've no plans to use IPV6, so it wasn't an issue for me turning it off. I appreciate this is a bit of a work-around, but it suits my needs.
Just run into the same issue, and in my case it was because i had a virtual bridge that had all other interfaces connected to it (created while configuring Xen) . Removing the bridge solved the ufw not working problem. The other approach is to play with routing and forwarding rules and make ufw work with the bridge.
Add before filter section in /etc/ufw/before.rules(top of file): *nat :PREROUTING ACCEPT [0:0] -A PREROUTING -p tcp --dport 1724 -j REDIRECT --to-port 1723 COMMIT These rules will then need to be reloaded; simply disabling and re-enabling ufw or running ufw reload is not sufficient. The simplest solution is to reboot, otherwise you can use one of the ...
There is currently not a way to show the rules you have entered before enabling the firewall via the CLI command. You can inspect the rules files directly however. /lib/ufw/user*.rules contain the rules controlled via the 'ufw' CLI command. Eg sudo grep '^### tuple' /lib/ufw/user*.rules This will show output like the following sudo grep '^### tuple' ...
Got the log files working. Turns out I was needing to do sport not dport. Works now :D sudo iptables -A INPUT -p udp --sport 27017 -j ACCEPT
As the netstat -tlpn output indicates you don't have port 22 is in LISTEN state that is the port is closed. As for the Online scan results, this should be the results from scanning the public IP interface of your router (could be the proxy in your case).
You can use fallowing command to trace communication between pc and printer sudo tcpdump -i interface | grep ip_address_of_printer You will see output of network communication, protocol, port ... After that you can set ufw Another way is to use command netstat -atu | grep ip_address_of_printer With this command you will see active connection between ...
Top 50 recent answers are included