<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I forgot to add the group to this reply. <br>
</p>
<p>Jim<br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellspacing="0"
cellpadding="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>Re: [hpsdr] How to configure a hermes IP connection?</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Fri, 27 Oct 2017 15:14:39 -0400</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Jim Lynch <a class="moz-txt-link-rfc2396E" href="mailto:jim@k4gvo.com"><jim@k4gvo.com></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td>Tom McDermott <a class="moz-txt-link-rfc2396E" href="mailto:tom.n5eg@gmail.com"><tom.n5eg@gmail.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>
On 10/27/2017 02:40 PM, Tom McDermott wrote:
> Hi Jim - using the version 3.1 (the 'old' protocol) on my Hermes it
> retrieves a DHCP address
> automatically. It used to be that switches and routers would not
> remember which
> devices used which addresses, meaning that any particular device on
> your home LAN
> could change IP addresses when power cycled. this was a real pain
> when opening
> firewall ports for example.
>
> However modern Ethernet switches and routers usually now have a
> 'reservations'
> table that auto populates. It remembers which MAC devices got which
> IP address
> in the past, and it makes sure to re-assign that exact same IP address
> to that same device
> in the future. So for most common cases I can think of, the use of
> static IP is really
> not needed anymore.
I understand and make use of that often or sometimes I set a static
address in the router configuration for a specific mac address just to
be sure. I stick a lot of different devices on my lan so I know once it
a while the leases get reused. It's just that the Hermes isn't looking
for a dhcp server as far as I can tell. I have looked in the device
table on my router and there's nothing there that I don't already know
what is.
>
> Ethernet added an MDI-X PHY type for 100Meg and 1Gig awhile ago. For
> devices made in
> the last few years, they will automatically auto-crossover if
> needed. The Ethernet
> interface in your computer may or may not have the capability, but I
> suspect that your
> Ethernet switch or router does. That's why when you hook Hermes to
> that more modern
> switch or router, it will detect the configuration and auto-crossover
> if it is needed.
I am assuming the Hermes doesn't do auto-crossover. I'm using a
USB-Ethernet dongle, so I'm not surprised it doesn't either. The laptop
is too new to have an Ethernet port.
>
> So if you connect two old computers at 100M you might need a crossover
> cable, but
> if they are recent or you have a switch or router in the path, it
> should automatically work.
> 1G Ethernet usually always does the MDI-X function. That's because 1GE
> uses all 4
> pairs in the cable at the same time. In fact all 4 pairs are
> operating full-duplex, 1GE sends
> lane identifier information down each pair so the receiver can figure
> out what's going on.
It worked in the past but only when I connected it directly to the
computer and knew what the address of the Hermes was and configured a
static address in my computer to be on the same network. However I've
forgotten what that network/static address was. I'm fairly certain that
the procedure at the beginning of time according to Hermes was to
connect directly from the Hermes to the computer, set a new ip address
in the Hermes that is on the LAN, then connect the Hermes to the LAN.
But then my memory is not what it used to be.
So I guess the question is how can I get this thing to play?
Thanks,
Jim
>
> -- Tom, N5EG
>
>
</pre>
</div>
</body>
</html>