Tag Info

New answers tagged

0

This is what I did to clean it up, if ufw is enabled, disable it. Then remove all of the ufw rules from iptables and ip6tables. #! /usr/bin/env bash set -e set -o pipefail iptables --flush rules=($(iptables --list | grep Chain | grep -Eo "ufw-[a-z-]+" | xargs echo)) for i in "${rules[@]}" do iptables --delete-chain $i done ip6tables --flush ...


-3

It's not exactly a solution, but you probably don't need to reboot you computer, just try to restart your networking service! Your software may be causing some exceptions to occur on your machine, that will later block the port! When that happens again try this! sudo service networking restart #sudo /etc/init.d/networking restart #the old fashioned way ...


0

Why not use iptables? It can differentiate per interface. Something like this: iptables -A INPUT -i ppp0 -p icmp --icmp-type echo-request -j REJECT That works like a champ for me.


1

Ok, I just checked, it appears to be enabled already - here's a copy of the .conf file: # /etc/ufw/ufw.conf # # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes # Please use the 'ufw' command to set the loglevel. Eg: 'ufw logging medium'. # ...


1

Edit your /etc/ufw/ufw.conf and make, ENABLED=yes


0

I would suggest you utilize the --link option to link the DB container into the containers that need it. That way you can just use the name given as the connection host... (--name the DB container and use the given name)



Top 50 recent answers are included