22 Jan
2013
22 Jan
'13
11:47 a.m.
Don, Marius, and All:
Marius, RIP44 is a TCP connection, in the most simple terms, there MUST
be communication BOTH ways (ACK, SYN ACK, the password, EST) via
Encapsulation from your station to 44.0.0.1. It is safe to say that the
encap route for 44.0.0.1 is operational if you seeded your router with a
route to 44.0.0.1 OR with default; and are receiving announcements. Just
because a host does not ping telnet, etc doesn’t mean it's not
operational (more below about how Don and I troubleshooted the issue).
Thanks to Don for his assistance. With his help, it was determined that
the reason I was not able to connect to stations originally was because
some had not yet updated their encap.
That problem slowly worked itself out; but other stations are unable to
connect to me. A number of reasons were found:
- all stations are not using JNOS as their Network OS; operators simply
(and understandingly) assume identical services and commands were
available (telnet, SMTP, etc.), and then noted I was down because I did
not have those same services available
- (thanks to Don for pointing this out) in my setup, the DNS entry for
my station ('kb3vwg.ampr.org') was not intended for my JNOS device (as I
do not use JNOS at this time); I understand now that in JNOS, to connect
to a station, you simply enter the callsign and the domain is appended -
this built-in scheme and command set is based in an assumption that the
remote station is running JNOS and has DNS configured for such - if this
is common on AMPR (which I assume), we definitely need to add this to
the Wiki
- some stations were testing me using telnet (I understand this services
comes enabled for APRS/Convers/etc.), but I am not running those
services at this time
~Lynwood
KB3VWG