It blocks the traffic from containers which it doesn't suppose to

[aliaksandrb]

Hi, nice app, helps a lot!

I've noticed recently, that when this tool is activated, my network inside Docker containers gets blocked too.
And it could be restored only after the whole Docker environment restart (not just container, even recreation doesn't help).

For example, within container normally:

$ curl -v google.com
*   Trying 17.253.144.10:80...
* Connected to google.com (17.253.144.10) port 80 (#0)
> GET / HTTP/1.1
> Host: google.com
> User-Agent: curl/7.76.1
> Accept: */*

After the tool is activated:

$ curl -v google.com
*   Trying 17.253.144.10:80...
*   Trying 2620:149:af0::10:80...
* Immediate connect fail for 2620:149:af0::10: Cannot assign requested address

It's quite annoying and I don't recall such behavior on my previous laptop, but after moving to Apple M1 Pro / Ventura macOS it is reproducible.
Sadly it makes it quite hard to use on that machine, and I have to move to browser based solution instead :/

Hope it's useful. Thank you!