Hey all,
we use docker to manage and distribute our IOCs.
Assume the following:
I have two PCs connected via LAN.
On PC A I ran a docker container containing an IOC
ON PC B I try to access PVs of this IOC via caget/pvget
(locally installed).
If I start my docker container with the `--network host`
option (the
container uses the network of PC A), both caget and pvget
are working fine.
But if I use the Docker's default bridge network and map
the ports of
the container to the ports on PC A (`-p 5064:5064 -p
5064:5064/udp -p
5075:5075 -p 5076:5076/udp`) only caget works.
The ioc does not reply to any request on port 5076/udp
I also tried to use pvlist which returns nothing. But
`pvlist <IP of PC
A>` works.
I used wireshark to check. The only difference in these
two scenarios I
can see are broadcast messages send regularly by the ioc
to ports
5065/udp and 5076/udp.
This difference is to be expected, as network bridges do
not forward
broadcasts, so these are only visible in the 1st case.
Any idea why pvget/pvlist cannot connect with my ioc if I
use the `-p`
options when starting the docker container?
Best regards,
Florian
--
Ruhr-Universität Bochum
AG der Experimentalphysik I
Dr. Florian Feldbauer
NB 2/131 / Fach 125
Universitätsstr. 150
D-44801 Bochum
Office: NB 2/134
Phone: (+49)234 / 32-23563
Fax: (+49)234 / 32-14170
https://eur03.safelinks.protection.outlook.com/?url="">