You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two physical PCs, robot controller and dev pc connected via ethernet on something like 10.x.x.x
Running on dev pc, I have two docker containers (backend and frontend) connected on a custom internal Docker network (IP addresses on 192.168.0.x)
I want the front end container to be able run the drivers and to communicate with the robot controller. Because of the internal network between the two containers, I can't simply use the host network, so I need to explicitly open the ports I want to use in my compose file.
Now, I know EGM needs a UDP connection - it seems that that is normally port 6511 and/or 6510. This wasn't sufficient though.
On opening Wireshark, I saw the controller was also producing TCP traffic on port 57414 (forward from port 80, from memory).
Adding an entry to for this seemed to be enough for things to start to work.
A brief description of my network architecture:
robot controller
anddev pc
connected via ethernet on something like 10.x.x.xdev pc
, I have two docker containers (backend
andfrontend
) connected on a custom internal Docker network (IP addresses on 192.168.0.x)I want the front end container to be able run the drivers and to communicate with the robot controller. Because of the internal network between the two containers, I can't simply use the
host
network, so I need to explicitly open the ports I want to use in my compose file.Now, I know EGM needs a UDP connection - it seems that that is normally port 6511 and/or 6510. This wasn't sufficient though.
On opening Wireshark, I saw the controller was also producing TCP traffic on port 57414 (forward from port 80, from memory).
Adding an entry to for this seemed to be enough for things to start to work.
The relevant section of my compose file:
My questions:
I didn't keep the wireshark data; I'll try to recreate it when I have chance.
The text was updated successfully, but these errors were encountered: