[hpsdr] Metis/Hermes with multiple NICs in SDR host PC

[Duane - N9DG]

Today I discovered that my machine with two NICs in it will only connect to the Metis if the other NIC that is not directly connect to the Metis is unplugged. The NIC that is directly connected to the Metis is first in the NIC binding order, so NIC binding order I don't believe has any bearing on what I'm seeing. So the machine is currently setup like this:

Mobo NIC 192.168.1.x network > to a switch with other machines on it. 
PCIe NIC 192.168.2.x network > directly connected to Metis.

I don't think this was an issue of the Metis port being dormant before boot up because a reboot of the W7x64 box after I first encountering this (and while leaving the Metis powered up) did not change the behavior. It wasn't until I unplugged the cable from the mobo NIC that PSDR would find the Metis/Mercury. Even PSDR couldn't connect to the Metis I could ping it. I have a static IP assigned to the Metis. Is there a PSDR (1.19.3.4 BaseSVN 3444) design limitation that can account for what I discovered?

My ultimate goal is to be able to drive two Hermes from one machine and have a NIC configuration as follows:

Mobo NIC 192.168.1.x network > to a switch with other machines on it. 

PCIe NIC #1 192.168.2.11 network > directly connected to Hermes #1.
PCIe NIC #2 192.168.2.12 network > directly connected to Hermes #2.

Will there be provisions in future code to accommodate the above scenario? Specifically running multiple NICs and multiple instances of PSDR (or other flavors of SDR SW) on one machine? I don't have a second Metis/Mercury on hand to try this myself..

If someday there is raw PC horsepower enough, I could even see wanting to go beyond having just two instances of SDR SW on one machine someday. 

73,
Duane
N9DG

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20110724/4958a5af/attachment-0002.htm>