Chai Feng

Yes, I think there is. Do you think the following commands meet your needs? ufw-docker allow from project_name:service_name to host_server_ip port ufw-docker deny from host_server_ip to project_name:service_name service_port

Sorry, I haven't tried IPv6 in Docker. This weekend I tried to set up a local IPv6 network by using VirtualBox, but not successful. I checked our servers and found...

@Fazel94 No, currently it doesn't support IPv6. But the method is similar. For the following code, you need to replace `10.0.0.0/8`/`172.16.0.0/12`/`192.168.0.0/16` with your internal IPv6 addresses. Then adding the changed...

Yes, it's a known issue. Except for the confusing output, everything should be ok, right?

Since ufw-docker has inserted the rule ufw-user-forward in front of all Docker related rules. So you could try using `ufw route` command to allow all connections from within the Tailscale...

Hi @vitalyrepin Thanks for your pull request. I'm sorry for the late response. I've considered using `ufw-before-forward` instead of `ufw-user-forward`. Because the first rule of `ufw-before-forward` is jumping to `ufw-user-forward`....

No, this feature hasn't been implemented. I'll do it later. Thanks for reporting!

I found that the script doesn't clean up the previous rule for current service. So you can allow the two ports separately for now.

We should choose UDP ports less than 32767 which are blocked and managed by the firewall. If we change the firewall rules that block more UDP ports, we may meet...

> Yes, just remove the three lines of code about `192.168.0.0/16` if you don't trust this network.