Latency on Pi3?

As part of my setting up my nodes, I’ve got 2 Pi3s, each configured as a private node, at my home QTH and connected to my local AREDN router. So the same local nettwork, right?

But man, there is a good 1 to 1.5 seconds of latency between Pi’s

I don’t think there’s any kind of audio delay setting I missed so perhaps this is simply processing time issues for the Pi?

That is much longer than normal. I’d expect a ½ second at the most. I don’t know what is wrong but something is not right. One thought… are the nodes behind a NAT router? If so take a look at Two Servers Behind NAT Router - AllStarLink Wiki

As all traffic between them is on the LAN side of my AREDN router, I don’t think NAT is an issue.

Also, perhaps I didn’t use the correct terminology (sorry, I am new to Allstar). I have 2 Raspberry Pi 3s, each one runs Allstar and they are connected to each other as private nodes via that router. I am also using Repeater-Builder RIM Lites as the interface to my controller

Are you using a usb radio interface and if so what is it ?

Yep, the Repeater-Builder RIM Lite:

http://www.repeater-builder.com/products/usb-rim-lite.html

As a test, could you connect in via iaxrpt and see if the latency shows as well.
Unplug the RIM. Reboot. Test
I have found some RIM’s have issues that cause the latency.

I have the same issue. Also using the rim.

Removed it and rebooted and then set it back up. Doesn’t seem to fix it. What did help was compiling in the dahdi dummy module.

That was not exactly what I was looking for in a test.

I wanted to see if it had the same effect without the rim.

To test that, you need to make a connection with iaxrpt software without the rim connected and without any of the usb drivers loaded (that’s why the reboot after unplugging).

Try this command…

iax2 show netstats
                                ------------- LOCAL ----------------  ------------- REMOTE ---------------
Channel                    RTT  Jit  Del  Lost   %  Drop  OOO  Kpkts  Jit  Del  Lost   %  Drop  OOO  Kpkts FirstMsg    LastMsg
IAX2/104.153.109.212:4569    4    3   61    10   1     0    0      0    0   40     0   0     0    0      0 Rx:NEW      Tx:ACK
(None)                    1000    0   40     0   0     0    0      0    0    0     0   0     0    0      0 Rx:  Rx:
2 active IAX channels

Here’s the decoder ring:

                            ------------- LOCAL ----------------  ------------- REMOTE ---------------

Channel RTT Jit Del Lost % Drop OOO Kpkts Jit Del Lost % Drop OOO Kpkts FirstMsg LastMsg
IAX2/10.150.180.35:4569-2 5 59 100 720 10 1 5 159 60 100 260 10 0 1 23 Tx:NEW Rx:ACK
1 active IAX channel

Looks ok. How about dahdi_test? It’s a Linux CLI.

dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.993% 99.991% 99.994% 99.988% 100.000% 99.988% 99.997% 99.998%
99.997% 99.999% 99.992% 99.994% 99.999% 99.991% 99.998% 99.994%
99.992% 100.000% 99.991% 99.998% 99.996% 99.995% 99.991% 99.992%
99.987% 99.993% 100.000% 99.992% 99.999% 99.993% 99.999% 99.994%
100.000% ^C
--- Results after 33 passes ---
Best: 100.000% -- Worst: 99.987% -- Average: 99.994647%
Cumulative Accuracy (not per pass): 99.996
root@rambo4:/etc/asterisk#

No such command ‘dahdi_test’ (type ‘help dahdi_test’ for other possible commands)

Did you run as root?

Indeed I did. And I ran from the CLI line (missed your comment about it being a Linux CLI).

However, I notice there’s a binary in /usr/sbin but the permissions are wrong. So I made dahdi_test executable and ran from the command line:

Opened pseudo dahdi interface, measuring accuracy…
99.608% 98.488% 99.637% 99.605% 99.601% 99.601% 99.601% 98.445%
99.602% 99.593% 99.603% 98.445% 99.600% 99.601% 99.601% 99.600%
99.603% 98.496% 99.572% 99.574% 99.570% 99.574% 98.477% 99.569%
99.574% 99.553% 99.572% 98.475% 99.571% 99.572% 99.570% 99.577%
98.476% 99.554% 99.568% 99.572% 99.601% 98.445% 99.599% 99.604%
99.601% 99.551% 98.476% ^C
— Results after 43 passes —
Best: 99.637% – Worst: 98.445% – Average: 99.352910%
Cumulative Accuracy (not per pass): 99.994

Are you running ASL 1.01? If so try the beta. It runs much better on a Pi.

Yes I am running 101. I will give the beta a try

Being that you are only running private nodes, you’ll want to disable stat_post (in rpt.conf) and update-node-list (with systemctl).

Beta doesn’t fix latency issue and do not see stat_post in rpt.conf. In fact, grep doesn’t show “stat_post” in any file in /etc/asterisk

Sorry it’s statpost_url=

Got it, thanks

Still…latency issues but I must admit I feel better about running Debian/Raspian Butch with the latest updates and kernel rather than 9/Stretch