When M17Gateway is left idle, it eventually drops off the network. The exact cause hasn't been determined (whether network interruption or some other cause), but the symptoms are:
Condition: M17Gateway is configured with a startup reflector.
M17Gateway connects on startup as expected and remains connected. However after some time (~ a few to several days), M17Client is no longer connected to its target reflector. At this point, using the DEST field on a RF client does not result in a connection to the destination reflector/module as expected. The actual destination of this connection attempt doesn't matter, the connection won't be established. The ECHO destination does still work when M17Gateway is in this fault condition.
Untested: I haven't yet tested an explicit UNLINK and subsequent attempt to link to a reflector. Won't be able to test until the fault reappears.
When M17Gateway is left idle, it eventually drops off the network. The exact cause hasn't been determined (whether network interruption or some other cause), but the symptoms are:
Condition: M17Gateway is configured with a startup reflector.
M17Gateway connects on startup as expected and remains connected. However after some time (~ a few to several days), M17Client is no longer connected to its target reflector. At this point, using the DEST field on a RF client does not result in a connection to the destination reflector/module as expected. The actual destination of this connection attempt doesn't matter, the connection won't be established. The ECHO destination does still work when M17Gateway is in this fault condition.
Untested: I haven't yet tested an explicit UNLINK and subsequent attempt to link to a reflector. Won't be able to test until the fault reappears.