We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the following setup work after installing ufw-docker?:
The host is not on a private subnet, but on a public IP. That is why UFW is essential for this host.
After 'ufw disable', access from the container to the host is possible.
After 'ufw enable' I am getting the following lines in syslog when I try to connect from the container to the database on the host:
[UFW BLOCK] IN=docker0 OUT= PHYSIN=vethc149a32 MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx SRC=172.17.0.2 DST=yy.yy.yy.yy LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=58585 DF PROTO=TCP SPT=45360 DPT=5432 WINDOW=29200 RES=0x00 SYN URGP=0
yy.yy.yy.yy is the (public) IP of my host
I added the following ufw allow rules, but still cannot connect:
sudo ufw status Status: active To Action From -- ------ ---- Anywhere ALLOW 172.16.0.0/16 yy.yy.yy.yy ALLOW 172.16.0.0/16 5432 ALLOW 172.16.0.0/16 5432 ALLOW FWD 172.16.0.0/16 yy.yy.yy.yy ALLOW FWD 172.16.0.0/16
Is it possible to somehow prevent the [UFW BLOCK] (see log) from happening?
Thanks,
The text was updated successfully, but these errors were encountered:
I got the same issue.
I just removed the following rules temporarily, then everything all right.
-A ufw-docker-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW DOCKER BLOCK] " -A ufw-docker-logging-deny -j DROP
Sorry, something went wrong.
It's 172.16.0.0/12 not /16...
No branches or pull requests
Should the following setup work after installing ufw-docker?:
The host is not on a private subnet, but on a public IP. That is why UFW is essential for this host.
After 'ufw disable', access from the container to the host is possible.
After 'ufw enable' I am getting the following lines in syslog when I try to connect from the container to the database on the host:
yy.yy.yy.yy is the (public) IP of my host
I added the following ufw allow rules, but still cannot connect:
Is it possible to somehow prevent the [UFW BLOCK] (see log) from happening?
Thanks,
The text was updated successfully, but these errors were encountered: