-
Notifications
You must be signed in to change notification settings - Fork 881
New issue
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
Connecting IPv4 network to container with IPv6 network resets IPv6 Gateway #1443
Comments
Forgot to add:
|
You are correct, that is the issue along with #1141 (comment) As a workaround, instead of connecting your container to the default |
The problem is that as far as I know, there is no way to disable IPv4, so my pure IPv6 So what I need is that it takes IPv4 subnet+gateway from one network and IPv6 subnet+gateway from the other. Then, there no way to name these so that both of these hold. However, if it simply checked if the IPv6 subnet+gateway are not set for current network, it should simply ignore it, then my current setup should work:
|
True, there is no way at the moment. |
But is it possible to at least ignore IPv6 subnet+gateway of My suggestion is to continue setting subnet+gateway the way you described it in #1141, but also include an exception if the gateway+subnet is not actually set. That is, If this is evaluated individually for IPv4 and IPV6, then it is possible to have different subnet+gateway for IPv4 and IPv6 by having the IPv4 network be lexically first and not specifying any IPv6 values on it. |
Any chance this will be fixed soon? The network setup does all of the connecting correctly, but performs an unnecessary overwrite:
|
I'm trying to connect containers on different hosts with each other and the outside world using the
macvlan
driver over IPv6. Additionally, the containers need to reach some IPv4 services, so I connected them through docker's defaultbridge
network. The issue is the IPv4 network resets the IPv6 gateway. The two networks are:Each of them works correctly individually, but adding both through
docker network connect
always resets the IPv6 gateway. for example:After this, the IPv4 network works correctly, but the IPv6 is unreachable because no gateway is set. Simply running
sudo route -A inet6 add default gw w:x:y:z::1 eth1
will fix the macvlan net as well.
Is this related to #1141/#1142 or is the
IPv6Gateway
set to "" becausebridge
IPv6Gateway
is not set andbridge
comes beforemacvlan
lexicographically? The expected outcome was that it should assumemacvlan
's IPv6 default gateway since it is the only IPv6 gateway that is actually set.The text was updated successfully, but these errors were encountered: