title: Device Managers on Machines with external 10GigE devices causing problems
body: <p>The issue I am having is when I go to start a device manager on a remote PC and I have an external hardware device with 10GigE ports connected the registerDevice message from the device manager registers the IP address of the 10GigE interface used by the external device connected to the device manager PC instead of the device manager machines actual IP address.</p>
  
  <p>Network Setup:</p>
  
  <pre>
  PC1
    Domain Manager:192.168.5.10
    Device Manager A(GPP):192.168.5.10 (on same machine as the domain manager)
  </pre>
  
  <pre>
  PC2
    Device Manager B(GPP):192.168.5.11 
    Device Interface: 192.168.100.10 (connected to external hardware)
  </pre>
  
  <p>If I run my scenario without the external device connected to PC2, the device manager on that machine registers with IP address: 192.168.5.11. If I connect the external hardware to PC2 and the 10GigE interface comes online, the device manager registers with IP address: 192.168.100.10 and the entire REDHAWK domain hangs.</p>
  
  <p>I verified this issue by going through wireshark logs on both PC1 and PC2. We have not had this problem when connecting UHD devices other than the UHD devices with 10GigE ports. It is important to note that no devices or device managers for them are actually being used at this point. The devices are just powered on and a node with only the GPP is started. In the UHD and external hardware case, both 10GigE ports are custom and implement a limited 10GigE interface. When connected to another PC with 10GigE instead of a device with a limited 10GigE implementation, the device manager works. </p>
  
  <p>If I connect the 10GigE device after the node is active, the FE 2.0 devices work perfectly fine. This scenario, however, will not work for us as physically walking over and powering on the device is not valid for our use case. In addition, running with the devices on a domain started on the same computer does not exhibit these issues. This problem only occurs when the domain is on a remote PC.</p>
  
  <p>We are currently working with the following REDHAWK versions and it has the same problem on both.</p>
  
  <p>CentOS 6.6 with REDHAWK 2.0.3 and OmniORB 4.1<br>
  Fedora 24 with REDHAWK 2.0.3 and OmniORB 4.2</p>
  
  <p>Has anyone else had this problem and is there anything I can do about it? </p>