<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Duane,<br>
<br>
My hardware config is similar to yours: <br>
<br>
a) MOBO Ethernet used for general networking, internet connection,
via DHCP, currently 192.168.1.6<br>
<br>
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.<br>
<br>
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.<br>
<br>
Pete, N3EVL<br>
<br>
<br>
On 7/24/2011 11:15 AM, Duane - N9DG wrote:
<blockquote
cite="mid:1311520545.54794.YahooMailClassic@web161502.mail.bf1.yahoo.com"
type="cite">
<pre wrap="">***** High Performance Software Defined Radio Discussion List *****
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top"><br>
After an off list response and then also downloading V1.2
of the Metis documentation, I find this on page 9:<br>
<br>
"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."<br>
<br>
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.<br>
<br>
Duane<br>
N9DG<br>
<br>
--- On <b>Sun, 7/24/11, Duane - N9DG <i><a class="moz-txt-link-rfc2396E" href="mailto:n9dg@yahoo.com"><n9dg@yahoo.com></a></i></b>
wrote:<br>
<blockquote style="border-left: 2px solid rgb(16, 16,
255); margin-left: 5px; padding-left: 5px;"><br>
From: Duane - N9DG <a class="moz-txt-link-rfc2396E" href="mailto:n9dg@yahoo.com"><n9dg@yahoo.com></a><br>
Subject: [hpsdr] Metis/Hermes with multiple NICs in SDR
host PC<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a><br>
Date: Sunday, July 24, 2011, 9:03 AM<br>
<br>
<div class="plainMail">***** High Performance Software
Defined Radio Discussion List *****<br>
<br>
</div>
<div id="yiv568201664">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top"><br>
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:<br>
<br>
Mobo NIC 192.168.1.x network > to a switch
with other machines on it. <br>
PCIe NIC 192.168.2.x network > directly
connected to Metis.<br>
<br>
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?<br>
<br>
My ultimate goal is to be able to drive two
Hermes from one machine and have a NIC
configuration as follows:<br>
<br>
Mobo NIC 192.168.1.x network > to a switch
with other machines on it. <br>
PCIe NIC #1 192.168.2.11 network > directly
connected to Hermes #1.<br>
PCIe NIC #2 192.168.2.12 network > directly
connected to Hermes #2.<br>
<br>
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..<br>
<br>
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. <br>
<br>
73,<br>
Duane<br>
N9DG<br>
<br>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</blockquote>
</td>
</tr>
</tbody>
</table>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
HPSDR Discussion List
To post msg: <a class="moz-txt-link-abbreviated" href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a>
Subscription help: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a>
HPSDR web page: <a class="moz-txt-link-freetext" href="http://openhpsdr.org">http://openhpsdr.org</a>
Archives: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<p class="avgcert" color="#000000" align="left">No virus found in
this message.<br>
Checked by AVG - <a moz-do-not-send="true"
href="http://www.avg.com">www.avg.com</a><br>
Version: 10.0.1390 / Virus Database: 1518/3785 - Release Date:
07/24/11</p>
</blockquote>
<br>
</body>
</html>