Does Containerlab support the creation of topologies with multiple subnets? #2718
Unanswered
stephane-klein
asked this question in
Q&A
Replies: 2 comments
-
You will need to use bridges as a layer 2 network to which you connect Linux nodes with their non Management interfaces https://containerlab.dev/manual/kinds/bridge/ |
Beta Was this translation helpful? Give feedback.
0 replies
-
You should overall be looking at the links section of the topology definition. Thats how you define traffic carrying interfaces other then the once connected to the docker mgmt network. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I tried using Containerlab to improve my understanding and practical mastery of IPv6.
I wanted to create two IPv6 networks connected by a router.
I tried this topology:
(My source code playground: https://github.com/stephane-klein/containerlab-playground/tree/main )
Problem: At the moment, I don't understand how to create two separate networks with Containerlab.
I don't know how to define the ipv6 prefix length of the
eth0
interfaces of the different nodes.For the moment, all the nodes belong to the same subnet
2001:db8:a::0/48
, whereas I'd like to separate them into two networks:2001:db8:a:1
2001:db8:a:2
Containerlab may not be suitable for this need.
It might be wise to explore the other alternatives mentioned in https://brianlinkletter.com/2024/02/open-source-network-simulation-roundup-2024/
Alternatively, this issue could potentially address my objective in the future: #2513
Question: Does Containerlab support the creation of topologies with multiple subnets?
See also: #2475
Beta Was this translation helpful? Give feedback.
All reactions