Connecting two TAP interfaces on different containers in same network

So basically I defined container A and container B and put them in same network, after starting both containers I bring down their default interfaces and bring up TAP interfaces on a same IP and gateway.
The problem is that two virtual interfaces can not communicate with each other, when I try to ping container B from Container A the TAP interface on container A get a ARP broadcast request packet for container B IP and it is written back to the TAP file descriptor but container B TAP interface never receives this ARP packet and vice versa.

I burned ChatGPT a lot on this topic and it is not helping much, things that I did understand was that Docker on mac basically runs on its own virtual machine and that machine maintains the network stack of its own which communicate with the host network.

Any insight on how to troubleshoot this issue would be helpful, or if anyone have any idea how to maybe ssh into the docker VM OS and manipulate network stack from within ?

TAP interfaces that are running on a containers are custom made and they basically read the incoming packets from the TAP FD and write them as is to the TAP FD

Best regards,
Tom.

If you are using Docker Desktop for Mac, how do you

?

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.