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

[n3evl]

Duane,

My hardware config is similar to yours:

a) MOBO Ethernet used for general networking, internet connection, via 
DHCP, currently 192.168.1.6

b) Second Gb Ethernet card dedicated to HPSDR; uses 10.0.0.100 for the 
card and 10.0.0.101 for Metis; I also have the default gateway for this 
connection set to 10.0.0.101; the subnet mask is 255.255.255.0; no DNS 
specified.

HPSDR seems to work fine with this configuration both for firmware 
updates via HPSDRProgrammer and regular operation of the radio.  This is 
on 32-bit Windows XP/SP3.

Pete, N3EVL


On 7/24/2011 11:15 AM, Duane - N9DG wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
>
>
>
> After an off list response and then also downloading V1.2 of the Metis 
> documentation, I find this on page 9:
>
> "If a static IP address is assigned and Metis is connected to a second 
> Ethernet port on a PC then the address assigned must be on a different 
> sub net. For example if the first port on the PC is using 192.168.x.x 
> then use 10.x.x.x for the Mets and the second port."
>
> So should in theory my 192.168.1.x and 192.168.2.x networks each setup 
> with subnet masks of 255.255.255.0 meet the requirement/definition of 
> being different sub nets? At least that is what I though I was 
> achieving with my NIC configurations.
>
> Duane
> N9DG
>
> --- On *Sun, 7/24/11, Duane - N9DG /<n9dg at yahoo.com>/* wrote:
>
>
>     From: Duane - N9DG <n9dg at yahoo.com>
>     Subject: [hpsdr] Metis/Hermes with multiple NICs in SDR host PC
>     To: hpsdr at openhpsdr.org
>     Date: Sunday, July 24, 2011, 9:03 AM
>
>     ***** High Performance Software Defined Radio Discussion List *****
>
>
>     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
>
>
>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 10.0.1390 / Virus Database: 1518/3785 - Release Date: 07/24/11
>

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