squromiv

Results 43 comments of squromiv

docker-compose.yml with "network_mode: host"

> Can you try to delete that line with `disable_ipv6`. Of course, I did it. The result is unpromising. Take a look at [screenshot](http://s01.geekpic.net/di-ESYB8G.jpeg), please.

docker-compose.yml with "network_mode: host"

> Looks like port 53 is already in use on your host machine. Perfectly. I`ve found out, that [it is used](https://www.linuxuprising.com/2020/07/ubuntu-how-to-free-up-port-53-used-by.html) by "systemd-resolved". So we need to free it up....

No access to internet with "Routed" mode on pure IPv6 clients

![screen_2021 03 31 002](https://user-images.githubusercontent.com/15985877/113104279-04556b80-9209-11eb-9fc5-4fca2ec2b505.png)

No access to internet with "Routed" mode on pure IPv6 clients

![screen_2021 03 31 003](https://user-images.githubusercontent.com/15985877/113106530-8b0b4800-920b-11eb-8ced-a20787273f5a.png)

No access to internet with "Routed" mode on pure IPv6 clients

Yes. ![screen_2021 03 31 006](https://user-images.githubusercontent.com/15985877/113108693-ef2f0b80-920d-11eb-894b-c8bf515e9326.png)

No access to internet with "Routed" mode on pure IPv6 clients

The fix from [here](https://github.com/b-m-f/WirtBot/issues/183#issuecomment-809560175) still works.

No access to internet with "Routed" mode on pure IPv6 clients

@b-m-f Most likely it is very interesting for technically skilled persons, but I am not like that. :) So what should I do until the best solution will appear? To...

No access to internet with "Routed" mode on pure IPv6 clients

> looks like you are using a hybrid setup Hi, Maximilian. I do not know how to name it, but I use standard WirtBot docker container with added commands, proposed...

No access to internet with "Routed" mode on pure IPv6 clients

> that your issue will be resolved in **v2.6.5** It looks like working. Very quick fix. Thanks. I will continue testing.

Duplicate images

Could you open it again?Or should i create a new one?