How do I use ip6 static address with CNI? #13173

Folaht · 2022-02-09T00:37:15Z

Folaht
Feb 9, 2022

I've got two machines on which I want to run the same app.
Since the app can only run on IPv4 or IPv6 exclusively, I want to run one with IPv4 and one running Ipv6.

I've succeeded to run the IPv4 like so:

$ sudo podman run \ 
--name root_node \ 
--restart unless-stopped \ 
--publish [192.168.x.x]:12000-12015:12000-12015/udp \
--env CON_IP=[10.88.1.3] \
--env CON_PORT=12000 \
--env PUB_IP=[glo.bal.ip.v4] \
--env PUB_PORT=12000 \
--ip 10.88.1.3 \
--mount type=bind,source=/home/folaht/.local/share/safe/rf_cli,destination=/root/.safe/cli -d [ghcr.io/safenetwork-community/rf-rootnode-ipv4:latest](http://ghcr.io/safenetwork-community/rf-rootnode-ipv4:latest)

Now I wonder how to do the equivalent in ipv6.
I've tried the following:

$ sudo podman run \
--name root_node \
--restart unless-stopped \
--publish [glo.bal.ip.v6]:12000-12015:12000-12015/udp \
--env CON_IP=[::ffff:a58:103] \
--env CON_PORT=12000 \
--env PUB_IP=[glo.bal.ip.v6] \
--env PUB_PORT=12000 \
--ip6 ::ffff:a58:103 \
--mount type=bind,source=/home/folaht/.local/share/safe/rf_cli,destination=/root/.safe/cli -d ghcr.io/safenetwork-community/rf-rootnode-ipv6:latest-dev

But this results into:

Error: requested static ip 10.88.1.3 not in any subnet on network podman

I understand the network IPs should be equal to the conflist?
What I did was simply convert the IPv4 addresses into IPv6 and crossed my fingers.

 cat /etc/cni/net.d/87-podman.conflist
{
  "cniVersion": "0.4.0",
  "name": "podman",
  "plugins": [
    {
      "type": "bridge",
      "bridge": "cni-podman0",
      "isGateway": true,
      "ipMasq": true,
      "hairpinMode": true,
      "ipam": {
        "type": "host-local",
        "routes": [{ "dst": "::ffff:0:0/0" }],
        "ranges": [
          [
            {
              "subnet": "::ffff:a58:0/64",
              "gateway": "::ffff:a58:1"
            }
          ]
        ]
      }
    },
    {
      "type": "portmap",
      "capabilities": {
        "portMappings": true
      }
    },
    {
      "type": "firewall"
    },
    {
      "type": "tuning"
    }
  ]
}

Answered by Luap99

Feb 14, 2022

Your ipv6 addresses do not look valid. Right now you use a converted ipv4, this is not correct. Go will still parse this as ipv4.

You have to create a proper ipv6 subnet, see https://simpledns.plus/private-ipv6 for example.

View full answer

Luap99 · 2022-02-14T13:14:32Z

Luap99
Feb 14, 2022
Maintainer

Your ipv6 addresses do not look valid. Right now you use a converted ipv4, this is not correct. Go will still parse this as ipv4.

You have to create a proper ipv6 subnet, see https://simpledns.plus/private-ipv6 for example.

2 replies

Luap99 Feb 14, 2022
Maintainer

You can also create a dual stack network with podman v4.0 and podman network create --ipv6 and then manually remove the ipv4 subnet from the config file.

Folaht Feb 28, 2022
Author

That last advice ultimately allowed me to start my ip6 static address container app.
I'll file an issue though for I think the default network should work as well.

Folaht · 2022-02-15T13:28:04Z

Folaht
Feb 15, 2022
Author

Okay, so for example I have Combined/CID: | fdc4:5c83:002d:3eed

And I've changed /etc/cni/net.d/87-podman.conflist accordingly.

{
  "cniVersion": "0.4.0",
  "name": "podman",
  "plugins": [
    {
      "type": "bridge",
      "bridge": "cni-podman0",
      "isGateway": true,
      "ipMasq": true,
      "hairpinMode": true,
      "ipam": {
        "type": "host-local",
        "routes": [{ "dst": "fdc4:5c83:002d:3eed:0000:0000:0000:0000/0" }],
        "ranges": [
          [
            {
              "subnet": "fdc4:5c83:002d:3eed::/64",
              "gateway": "fdc4:5c83:002d:3eed:0000:0000:0000:0001"
            }
          ]
        ]
      }
    },
    {
      "type": "portmap",
      "capabilities": {
        "portMappings": true
      }
    },
    {
      "type": "firewall"
    },
    {
      "type": "tuning"
    }
  ]
}

Then reran podman

$ sudo podman run \
--name root_node \
--restart unless-stopped \
--publish [glo.bal.ip.v6]:12000-12015:12000-12015/udp \
--env CON_IP=[fdc4:5c83:002d:3eed:0000:0000:0000:0001] \
--env CON_PORT=12000 \
--env PUB_IP=[glo.bal.ip.v6] \
--env PUB_PORT=12000 \
--ip6 fdc4:5c83:002d:3eed:0000:0000:0000:0001 \
--mount type=bind,source=/home/folaht/.local/share/safe/rf_cli,destination=/root/.safe/cli -d ghcr.io/safenetwork-community/rf-rootnode-ipv6:latest-dev

I'm receiving this error.

WARN[0002] Failed to load cached network config: network podman not found in CNI cache, falling back to loading network podman from disk
WARN[0002] 1 error occurred:
	* plugin type="bridge" failed (delete): cni plugin bridge failed: running [/usr/bin/ip6tables -t nat -D POSTROUTING -s fdc4:5c83:002d:3eed ::1 -j CNI-cc14d1fe72264f4269a985e7 -m comment --comment name: "podman" id: "7d5e8f2aec8a3942806ef2a406b68cdc40463abdc2173398df4a1500d462e156" --wait]: exit status 2: ip6tables v1.8.7 (legacy): Couldn't load target `CNI-cc14d1fe72264f4269a985e7':No such file or directory

Try `ip6tables -h' or 'ip6tables --help' for more information.


Error: plugin type="bridge" failed (add): cni plugin bridge failed: failed to add route '{::fdc4:5c83:002d:3eed 00000000000000000000000000000000} via fdc4:5c83:002d:3eed::1 dev eth0': no route to host

What am I doing wrong?

1 reply

Luap99 Feb 16, 2022
Maintainer

You have to add ::/0 as route instead of fdc4:5c83:002d:3eed:0000:0000:0000:0000/0

Folaht · 2022-02-16T21:33:49Z

Folaht
Feb 16, 2022
Author

Same problem.

/etc/cni/net.d/87-podman.conflist

...
"routes": [{ "dst": "::/0" }],
...

...
Error: plugin type="bridge" failed (add): cni plugin bridge failed: failed to add route '{::fdc4:5c83:002d:3eed 00000000000000000000000000000000} via fdc4:5c83:002d:3eed::1 dev eth0': no route to host

1 reply

Luap99 Feb 17, 2022
Maintainer

I think you are setting the gateway as contianer ip this is wrong. You need to use another ipv6 from that subnet

Folaht · 2022-02-18T11:29:41Z

Folaht
Feb 18, 2022
Author

That sounds reasonable.
Unfortunately I yet again have the same issue.
I've also tried creating a ipv4/ipv6 new network and tried connecting via ipv6 there.
Same issue. Same error.

sudo podman run 
--name root_node 
--restart unless-stopped 
--publish [glo:bal:ip:v6]:12000-12015:12000-12015/udp 
--env CON_IP=[sub:net:ip:v6::2] 
--env CON_PORT=12000 
--env PUB_IP=[glo:bal:ip:v6] 
--env PUB_PORT=12000 
--ip6 sub:net:ip:v6:0000:0000:0000:0002 
--mount type=bind,source=/home/folaht/.local/share/safe/rf_cli,destination=/root/.safe/cli 
-d ghcr.io/safenetwork-community/rf-rootnode-ipv6:latest-dev

WARN[0001] Failed to load cached network config: network podman not found in CNI cache, 
falling back to loading network podman from disk
WARN[0001] 1 error occurred:
	* plugin type="bridge" failed (delete): cni plugin bridge failed: 
running [/usr/bin/ip6tables -t nat -D POSTROUTING -s sub:net:ip:v6::2 
-j CNI-57a545a1b0b178ced886949c -m comment --comment name: "podman" id:
 "cb585b5209f0431e14cf49e2a68457c5bcd70cbd4f77075d8c22b6ea021d4baf" --wait]: 
exit status 2: ip6tables v1.8.7 (legacy): Couldn't load target `CNI-57a545a1b0b178ced886949c':No such file or directory
Try `ip6tables -h' or 'ip6tables --help' for more information.
Error: plugin type="bridge" failed (add): cni plugin bridge failed: failed to add route 
'{:: 00000000000000000000000000000000} via sub:net:ip:v6::1 dev eth0': no route to host

/etc/cni/net.d/87-podman.conflist

...
"routes": [{ "dst": "::/0" }],
...              
"subnet": "sub:net:ip:v6::/64",
"gateway": "sub:net:ip:v6::1"
...

glo:bal:ip:v6 = IPv6 address in ip -6 -o addr show up primary scope global
sub:net:ip:v6 = Unique private randomly generated CID from https://simpledns.plus/private-ipv6 without ::/64

0 replies

Folaht · 2022-02-23T08:03:39Z

Folaht
Feb 23, 2022
Author

After rebooting, it works on the new network.
Well not work, but it launches and exits.

[update]

I have the issue again when attempting a podman commit for debugging purposes.

$ sudo podman commit safe_node debug/safe_node_1
$ sudo podman run -it --rm --entrypoint=/bin/bash --name debug_node_1 debug/safe_node_1

WARN[0002] Failed to load cached network config: network podman not found in CNI cache, falling back to loading network podman from disk
WARN[0002] 1 error occurred:
	* plugin type="bridge" failed (delete): cni plugin bridge failed: running [/usr/bin/ip6tables -t nat -D POSTROUTING -s  sub:net:ip:v6::4 -j CNI-caa74704887f9797adaca8c9 -m comment --comment name: "podman" id: "23a7110b8b183bd01dcef2b0ef7ee4e843bdc524c7a030eafba558f8b5bf5d35" --wait]: exit status 2: ip6tables v1.8.7 (legacy): Couldn't load target `CNI-caa74704887f9797adaca8c9':No such file or directory

Try `ip6tables -h' or 'ip6tables --help' for more information.


Error: unable to start container "23a7110b8b183bd01dcef2b0ef7ee4e843bdc524c7a030eafba558f8b5bf5d35": plugin type="bridge" failed (add): cni plugin bridge failed: failed to add route '{:: 00000000000000000000000000000000} via sub:net:ip:v6::1 dev eth0': no route to host

1 reply

Folaht Feb 28, 2022
Author

I've managed to not have this issue for a secondary network, but still have it for the default network.
I guess that solves the problem while having to file an issue.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How do I use ip6 static address with CNI? #13173

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

How do I use ip6 static address with CNI? #13173

Folaht Feb 9, 2022

Replies: 5 comments · 5 replies

Luap99 Feb 14, 2022 Maintainer

Luap99 Feb 14, 2022 Maintainer

Folaht Feb 28, 2022 Author

Folaht Feb 15, 2022 Author

Luap99 Feb 16, 2022 Maintainer

Folaht Feb 16, 2022 Author

Luap99 Feb 17, 2022 Maintainer

Folaht Feb 18, 2022 Author

Folaht Feb 23, 2022 Author

Folaht Feb 28, 2022 Author

Folaht
Feb 9, 2022

Replies: 5 comments 5 replies

Luap99
Feb 14, 2022
Maintainer

Luap99 Feb 14, 2022
Maintainer

Folaht Feb 28, 2022
Author

Folaht
Feb 15, 2022
Author

Luap99 Feb 16, 2022
Maintainer

Folaht
Feb 16, 2022
Author

Luap99 Feb 17, 2022
Maintainer

Folaht
Feb 18, 2022
Author

Folaht
Feb 23, 2022
Author

Folaht Feb 28, 2022
Author