Hello Sébastien, is there a way to transfer dicom files (query/retrieve) between multiple IP network Addresses???
E.G. In software aplications Osirix/Horos, the configuration recognize if are various network adapters in the computer (wifi, and/or multiple ethernets for servers), in fact, I have a G5 MAC server with two Ethernet adapters, one with Static IP “192.168.1.X” that is the address wich receive Dicom files from modalities (US, MR, CT, CR, etc) and the second Ethernet adapter have an static IP “172.16.1.X”, that sends studies to M.D. Stations that retrieve the studies with Radiant and Osirix/Horos
So, is possible to use multiple network adapters with different IP Addresses at same time to transfer DICOM files in Orthanc?
Regards, Ricardo Martínez
Hello,
Orthanc can be used to send its local images across different networks if several network adapters are available. In fact, the routing to multiple networks is an OS-level feature (i.e. implemented by the operating system through the IP routing tables), so Orthanc transparently benefits from this feature.
Sébastien-
Just figured out that you might be talking about the “server” part of Orthanc.
As of Orthanc 1.9.1, you cannot tell Orthanc to bind its HTTP server or its DICOM server to only one specific network interface (as specified by one IP address): Orthanc will listen on all the network interfaces of the computer.
Regarding the HTTP server, it could be possible to listen only to one network interface by adapting the “listening_ports” configuration option of civetweb (the embedded Web server used by Orthanc):
https://github.com/civetweb/civetweb/blob/master/docs/UserManual.md#listening_ports-8080
Regarding the DICOM server, DCMTK 3.6.6 doesn’t offer the possibility to restrict the network interface. This topic has been discussed at the following place, and I see no change in the source of DCMTK on that aspect since 2006 (there is a patch from 2009 that has not been integrated in DCMTK as far as I can tell):
https://forum.dcmtk.org/viewtopic.php?t=989
On the other hand, this is certainly the kind of stuff that can be controlled at a lower level through your firewall (e.g. iptables on Linux). Quoting the last link: “Restricting a service on a multi-homed host to a certain interface seems to be a rather rare wish.”
Sébastien-