dcm4chee
  1. dcm4chee
  2. DCMEE-1278

Ability to listen on more than one dicom port

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: dcm4chee-2.14.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I believe current version can listen to only one dicom port. I had an use case where DcmServer was needed to listen on more than one port. In this case dcm4chee should replace another pacs that had such ability and the surrounding dicom workstations/modalities were configured to use both.

        Activity

        Hide
        Gunter Zeilinger added a comment - - edited

        Will not be provided before update of the DICOM library used by dcm4chee from dcm4che-1.4.x to dcm4che-2.x.

        In the meantime you may deploy multiple DcmServer Service instances associated with their own Storage and QueryRetrieve SCP services (s.a. http://www.dcm4che.org/confluence/display/ee2/Deploying+multiple+archive+instances )

        Show
        Gunter Zeilinger added a comment - - edited Will not be provided before update of the DICOM library used by dcm4chee from dcm4che-1.4.x to dcm4che-2.x. In the meantime you may deploy multiple DcmServer Service instances associated with their own Storage and QueryRetrieve SCP services (s.a. http://www.dcm4che.org/confluence/display/ee2/Deploying+multiple+archive+instances )
        Hide
        Alexander Karaivanov added a comment -

        Thank you. I though about it today but discarded the idea immediately because it sounded I bit dangerous to me . Also I really needed same storage and q/r scp.

        What I did instead was just solution at network level adding a rule to iptables to do NAT so when one (remote) client connects to 104 it will be mapped to port 11112 instead:

        iptables -t nat -F
        iptables -t nat -X
        iptables -t nat -A PREROUTING -p tcp -d a.b.c.d --dport 104 -j DNAT --to a.b.c.d:11112

        I just thought this might be useful feature and that is why this feature request.

        Show
        Alexander Karaivanov added a comment - Thank you. I though about it today but discarded the idea immediately because it sounded I bit dangerous to me . Also I really needed same storage and q/r scp. What I did instead was just solution at network level adding a rule to iptables to do NAT so when one (remote) client connects to 104 it will be mapped to port 11112 instead: iptables -t nat -F iptables -t nat -X iptables -t nat -A PREROUTING -p tcp -d a.b.c.d --dport 104 -j DNAT --to a.b.c.d:11112 I just thought this might be useful feature and that is why this feature request.
        Hide
        Jordan K added a comment - - edited

        Just a note, the iptables statements that worked for me, and don't require specifying IP addresses:

        iptables -t nat -A PREROUTING -p tcp --dport 104 -j REDIRECT --to-ports 11112 (handles traffic from other systems)
        iptables -t nat -A OUTPUT -p tcp ! -o eth0+ -m tcp --dport 104 -j REDIRECT --to-ports 11112 (handles traffic from the system itself, if you want to be able to use the loopback)

        Show
        Jordan K added a comment - - edited Just a note, the iptables statements that worked for me, and don't require specifying IP addresses: iptables -t nat -A PREROUTING -p tcp --dport 104 -j REDIRECT --to-ports 11112 (handles traffic from other systems) iptables -t nat -A OUTPUT -p tcp ! -o eth0+ -m tcp --dport 104 -j REDIRECT --to-ports 11112 (handles traffic from the system itself, if you want to be able to use the loopback)

          People

          • Assignee:
            Gunter Zeilinger
            Reporter:
            Alexander Karaivanov
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development