You are here

Setting up Contact Servers in RMS EXPRESS

5 posts / 0 new
Last post
k1ky
k1ky's picture
Setting up Contact Servers in RMS EXPRESS

RMS EXPRESS will work over the MESH network as well as any LAN and the Internet for Post Office and Peer-To-Peer message delivery.
There are two modes of interest to us for MESH: 
1. Telnet Post Office: For Store and Retrieve messages
2. Telnet P2P: For Point-To-Point message transfer between two RMS EXPRESS systems (attended and unattended)

Each has a separate address book for the server identities. P2P uses port 8774 and Post Office uses port 8772.

Now for the fun part.  Since you can send messages to a Post Office or P2P via Telnet on a LAN or MESH, you can also send them direct via the Internet if the receiving station has a fixed IP and port 8772 and 8774 forwarded to the computer where RMS Express or RMS RELAY reside.  You can keep the routing straight by using station identifiers designating the route of delivery.  NOIP address names work also, i.e.   callsign.ddns.net if set up.
.
Example:  For MESH Post Offices I enter a name something like K1KY-MESH-LAVERGNE (as much or little as the field will hold) and for Post Offices over the Internet, simply K1KY-I

The receiving Post Office or Station doesn't care what you have named the entry so long as the IP address and Port number is correct.

That's my helpful tip of the day folks.  Any questions, drop them off to me via Winlink to K1KY or look up my Post Office on the MESH:
WINLINK Post Office KD4F 10.200.133.11 or Internet Post Office k1ky.ddns.net addressed to K1KY.

73,  T.D.
 

K5DLQ
K5DLQ's picture
Great info Tom.  Thx

Great info Tom.  Thx

KL5T
Telnet Peer-To-Peer Hangs with "Autoconnect"

Telnet Peer-To-Peer is great, but I'm seeing a consistent problem across a number of locations.  When I set up a Peer-To-Peer connection, and set an Autoconnect frequency (like 1 minute), the Winlink sessions HANG at the same point every time.  Here's an example:

This is from the initiating station end:

*** Connecting P2P Telnet to TUTTLE at 10.0.138.54 port 8774
*** Connected to TUTTLE at 10.0.138.54 port 8774 at 2019/01/17 08:34:12
   ;FW: KL5T
   [RMS Express-1.5.18.0-B2FHM$]
   TUTTLE DE KL5T >
;FW: KL7AA TUTTLE
[RMS Express-1.5.18.0-B2FHM$]
KL5T DE KL7AA >
----this is where it hangs ----


This is from the target station end:
*** Received incoming connection from 10.0.55.147 at 2019-01-17 08:34:22 UTC
*** Logon by KL5T
   ;FW: KL7AA TUTTLE
   [RMS Express-1.5.18.0-B2FHM$]
   KL5T DE KL7AA >
;FW: KL5T
[RMS Express-1.5.18.0-B2FHM$]
TUTTLE DE KL5T >
----this is where it hangs ----

It seems to work perfectly if manually initiated.

Anybody else see this?  Any ideas for a solution?

Thanks much,

Kent, KL5T
Anchorage, Alaska
 

ke7xo
suggestion ...

this is a RMS Express issue 

I suggest posting your question on the Winlink programs forum..        https://www.winlink.org/content/winlink_programs_group

Richard    ke7xo

AA7AU
AA7AU's picture
Use Ping/Traceroute tools?

Just to hazard a guess - looks like it *might* be packet loss along your route which fails on longer packet strings. When I'm using Windoze, here's the free version of one of the tools which works well for me:  http://www.pingplotter.com/products/free.html

Of course, this doesn't really explain why it works manually - but still worth checking to rule it out first.

HTH,
- Don - AA7AU    (who remembers Anchorage in January)

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer