[arm-allstar] Chasing Multiple Rpi Node Gremlins

John wb5nfc at gmail.com
Sat Aug 13 15:16:18 EST 2016

We've made considerable progress this week helping a friend set up a new
Rpi node, but a few gremlins remain.

#1: What might cause a node to require sending the "disconnect last node"
function (*10) twice? The first time the sequence is sent, it produces no
action. The second time, the node responds properly and disconnects the
last node. This happens every time. It occurs only when connected via a
radio link. The CLI shows that the digits are properly decoded both the
first and the second time. The command works the first time (evert tune) if
issued from the iaxRpt client.

#2: When connecting to the Echolink Echo Reflector, the node connect
announcement is received twice. Immediately after hearing the connect
message the first time, it repeats a secont time. Eannode=3,
echolinkdefault=1, and telemdefault=1.

#3: When the Rpi node is connected to the home network, overall network
throughput deteriorates. Netflex streaming slows to a crawl and buffers.
When the Allstar node is shut down, the problem disappears. This is a
repeatable error. The Internet conneciton is via Suddentlink cable and
normally has no problem running multiple streams (~50 Mbps). The node is
DHCP with the IP reserved at the router.

Thanks for any suggestions.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160813/83763b42/attachment.html>

More information about the arm-allstar mailing list