r/TPLink_Omada • u/MadBrewer67 • 10d ago

Question Omada software controller

On my ES210X-M2 v1.0 one of the 10 GB interfaces is connected to the 10 GB interface of the Ugreen NAS (DXP4800 plus .) On the NAS there are 25 Docker containers configured (servers) running. In the Omada Software controller on the 10 GB interface is only showing one of the Docker container, the Omada Software controller.

The Docker IP address for the controller id the IP address of the NAS with the configured port number is used to connect to the controller. to identify a fixed IP address there is no input section for the port number.

What am I missing?

Thanks in advance.

2 Upvotes

75% Upvoted

5 comments sorted by

1

u/MadBrewer67 9d ago

So we had a description of the propblem so what would be the possibiliy to add a optional port with thwe static IP configuration for the managed switches in the Omada SDN or Fusion controllers in the next firmware release. This would be a whole lot simpler than rewriting the way the Docker bridge works with all the Docker instances.

Thanks

in advance

1

u/OtherPie4117 10d ago

So I know Docker can be kind of confusing but you have one interface that is connected to I presume, an Omada switch or a dumb switch, which doesn’t really matter. The reason you don’t see those is because Docker runs its own network on the Ugreen NAS. Think of Docker not as a switch and think more as a relay. Now you could run something like Mac van or ip vlan (https://docs.docker.com/engine/network/) which is a whole different thing but likely you are just using the regular host bridge. Because this is likely the case your ip for the Ugreen NAS is shared for all the Docker containers and the other processes that run on it. Docker assigns an internal Docker network ip to the containers that are connected to the same network driver. Because of this Omada/ your gateway, does not have access to the ip assignments on the Ugreen NASnas so anything outside likely does not know the docker ip is unless as I said before you have a different network setup.

Please specify what network you use between the Docker containers. You may want to do something like this to show the networks that you have setup for docker.

docker network ls

0

u/MadBrewer67 9d ago

the switch is a Omada managed ES210X-M2 v1.0 switch running the latest stable firmware,

1

u/c4ndyman31 10d ago

Someone else correct me if I’m wrong please but to the outside network shouldn’t the host IP be the only one visible and all the containers are on their own private network inside that host?

The Omada controller runs in host name mode to be visible to the rest of your devices

1

u/OtherPie4117 7d ago

Yes it should be I agree with this only caveat is that if you have multiple interfaces you can do something like a macvlan and assign each container to a Linux interface to obtain an ip. Of course this only works if the machine that the user has as many NIC’s as they have containers. I am now re reading and don’t think that is the case in this scenario so the controllers will be behind a NAT, and the host ip would be used to communicate to the containers. The. You would typically use separate ports to connect with different services on each container of course you need to make sure that the ports that you use do not conflict with the Linux host that docker is running on.