[arm-allstar] Chasing Multiple Rpi Node Gremlins

[David McGough]

John,

I'm not sure what is going on in any of these problems, but, here are some 
things to check:

Items 1 and 2:  I suspect a configuration problem, likely in the rpt.conf
file.

Item 3: The bandwidth required for nodes is quite small, as an example, 
I'm typing this, browsing the web and have 3 nodes up and running right 
now on my DSL, which is 6Mbps down / 768Kbps up...And, I've got plenty of 
bandwidth to spare.

Does the Internet performance problem show up when the node is
transmitting??  If so, the transmitter RF is the place to look. 

73, David KB4FXC



On Sat, 13 Aug 2016, John via arm-allstar wrote:

> 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.
> 
> John
>