Comment on page
SDN: Software Defined Networking
Dividing your Antsle's environment into isolated networks and creating trunk ports
SDN is only available in edgeLinux 2.0.0 and later
Creating a VLAN and adding antlets to it is an easy way to isolate different antlets into their own network environment within your Antsle server.
A common reason for doing this is when you are doing things with those antlets that could adversely affect the others or their networking.
To get started, head over to the SDN tab on the left menu and hit create.
Give your VLAN a name and a vLAN ID (We'll discuss ID when creating a trunk). Do not connect it to an interface.
Add some antlets, and then connect them. Voila. That's all.
This adds a new virtual NIC to those antlets. You will want to log into your antlets and give them a static IP that allows them to communicate in their isolated network.
Your antlets are all created -- by default -- with a virtual NIC and connected to an internal natted network. This is what allows you to SSH into them from your Antsle's console, and allows them to communicate with each other.
Your default NIC, bblv, will still be active (and your antlet not truly isolated) unless you delete it.
To truly isolate your antlets, you will need to remove the default, bblv NIC under the network tab. This means you will only be able to access that antlet via the VNC console. You can restore the default vNIC at any time.
This is how you connect your vLAN (and the antlets in them) to "outside" networks, integrating it into virtual networks that may span many nodes (devices, servers, etc.).
Creating a trunk happens automatically when you connect a vLAN to an interface (see image below).
Once you connect it to an interface (aka NIC or port) on your server, it becomes a trunk port. Creating a trunk port means that it will now send information about what vLAN the traffic is associated with and direct incoming traffic to the appropriate vLAN.
If you are connected your vLAN to an external network you will want to give it the same vLAN ID (aka "tag") as the external network you are connecting it to.
Follow the process of adding antlets and you're done.
If you have a monitoring tool that you want to keep separate from a vLAN but still have it able to see all the internal traffic, just mirror one vLAN (the one with the traffic) to the other vLAN (the one with your monitoring tool).
Last modified 3yr ago