xlxd v2.5.3 - not passing packets from linked reflectors to BM

[va3uv]

Hello Luc and All:

We recently updated xlxd on one of our (old) systems, from 2.4.3 to the latest 2.5.3.

We have XLX416A peered with BM3102 (BM TG 302050). Stations connected to XLX416A are being heard on our BM TG; the xlxd log shows the ambe stream being opened, and we can see the corresponding activity on the ambed side (all good).

However, when there is activity on a linked reflector (e.g., XLX405A, which is peered with XLX416A), the packets are not being passed to the ambe server (the ambe server is offsite / as specified in the unit file on XLX416).

Last night, when there was D-STAR activity on a peered reflector, in the XLX416 log, we were also seeing stuff like:

"ambed stream open on port 10189" - this should not have been happening on XLX416 per se, the packets should have been sent to the transcoder (as specified in the unit file on XLX416). Looking at the embed log file, there is no activity ... since the packets are not being sent to the ambed server.

Hope I am explaining this correctly. Please let me know if you require further evidence to support an investigation / problem resolution.

Thanks!

Ramesh, VA3UV, WA3UV, G4PNQ

[LX3JL]

Hi,

When receiving inbound traffic from peered XLX reflector, it is only sent to the attached AMBE server for translation if it needs to. Indeed, XLX peer protocol have provision for both AMBE versions of the packet (DSTAR and DMR-YSF) and if the peered reflector have already translated the AMBE packet, ie filling both versions of the AMBE packets in the frame, your local XLX does not need to do it again.
So, in your case, verify first that XLX405 is equipped or not with AMBE server capabilities. If it is, it is normal that traffic you receive from it does not need to be translated (again).

73

[va3uv]

Hello Luc:

On XLX416A, we have several peered reflectors, so while I do not have an AMBE decoder on XLX405, I cannot 100% guarantee that there is no other linked reflector with an AMBE decoder (example, I know 2 of the linked reflectors have Peanut rooms, so would be using an AMBE decoder on their reflectors).

So, to test this out, I linked XLX427 C to XLX416 C (so just 2 reflectors linked..... and both under my control, so I can see the logs on both sides, as well as the AMBE decoder).

Same thing now... I talk on XLX427 C, and I am not heard on DMR:

From 427C logs:

Dec 14 06:23:02 XLX427-AST2200 xlxd[60464]: XLX (2.5.3) connect packet for modules C from XLX416 at 192.46.223.219
Dec 14 06:23:04 XLX427-AST2200 xlxd[60464]: Sending connect packet to XLX peer XLX416 @ 192.46.223.219 for modules C
Dec 14 06:23:05 XLX427-AST2200 xlxd[60464]: XLX ack packet for modules C from XLX416 at 192.46.223.219
Dec 14 06:23:05 XLX427-AST2200 xlxd[60464]: New peer XLX416 at 192.46.223.219 added with protocol XLX
Dec 14 06:23:05 XLX427-AST2200 xlxd[60464]: New client XLX416 at 192.46.223.219 added with protocol XLX on module C
Dec 14 06:23:47 XLX427-AST2200 xlxd[60464]: DCS connect packet for module C from VE3RSD B at 70.aa.bb.153
Dec 14 06:23:47 XLX427-AST2200 xlxd[60464]: New client VE3RSD B at 70.aa.bb.153 added with protocol DCS on module C
Dec 14 06:24:37 XLX427-AST2200 xlxd[60464]: Opening stream on module C for client VE3RSD B with sid 16959
Dec 14 06:24:43 XLX427-AST2200 xlxd[60464]: Closing stream of module C
Dec 14 06:29:55 XLX427-AST2200 xlxd[60464]: Opening stream on module C for client VE3RSD B with sid 44082
Dec 14 06:29:56 XLX427-AST2200 xlxd[60464]: Closing stream of module C
Dec 14 06:30:00 XLX427-AST2200 xlxd[60464]: Opening stream on module C for client VE3RSD B with sid 26163
Dec 14 06:30:02 XLX427-AST2200 xlxd[60464]: Closing stream of module C

From XLX416:

Dec 14 06:23:02 XLX416-TORONTO xlxd[45400]: Sending connect packet to XLX peer XLX427 @ 15.157.128.240 for modules C
Dec 14 06:23:02 XLX416-TORONTO xlxd[45400]: XLX ack packet for modules C from XLX427 at 15.157.128.240
Dec 14 06:23:02 XLX416-TORONTO xlxd[45400]: New peer XLX427 at 15.157.128.240 added with protocol XLX
Dec 14 06:23:02 XLX416-TORONTO xlxd[45400]: New client XLX427 at 15.157.128.240 added with protocol XLX on module C
Dec 14 06:23:04 XLX416-TORONTO xlxd[45400]: XLX (2.5.3) connect packet for modules C from XLX427 at 15.157.128.240
Dec 14 06:23:36 XLX416-TORONTO xlxd[45400]: Opening stream on module A for client XLX405 with sid 65409
Dec 14 06:23:37 XLX416-TORONTO xlxd[45400]: Closing stream of module A
Dec 14 06:23:42 XLX416-TORONTO xlxd[45400]: Opening stream on module A for client XLX405 with sid 62107
Dec 14 06:23:49 XLX416-TORONTO xlxd[45400]: Closing stream of module A
Dec 14 06:24:12 XLX416-TORONTO xlxd[45400]: ambed stream open on port 10110
Dec 14 06:24:12 XLX416-TORONTO xlxd[45400]: Opening stream on module C for client BM3102 with sid 12895
Dec 14 06:24:12 XLX416-TORONTO xlxd[45400]: Closing stream of module C
Dec 14 06:24:12 XLX416-TORONTO xlxd[45400]: ambed stats (ms) : 1.0/41.1/58.4
Dec 14 06:24:12 XLX416-TORONTO xlxd[45400]: ambed 0 of 36 packets timed out
Dec 14 06:24:22 XLX416-TORONTO xlxd[45400]: ambed stream open on port 10111
Dec 14 06:24:22 XLX416-TORONTO xlxd[45400]: Opening stream on module C for client BM3102 with sid 24524
Dec 14 06:24:27 XLX416-TORONTO xlxd[45400]: Closing stream of module C
Dec 14 06:24:27 XLX416-TORONTO xlxd[45400]: ambed stats (ms) : 0.0/44.4/60.2
Dec 14 06:24:27 XLX416-TORONTO xlxd[45400]: ambed 0 of 252 packets timed out
Dec 14 06:24:37 XLX416-TORONTO xlxd[45400]: Opening stream on module C for client XLX427 with sid 16959
Dec 14 06:24:43 XLX416-TORONTO xlxd[45400]: Closing stream of module C
Dec 14 06:29:55 XLX416-TORONTO xlxd[45400]: Opening stream on module C for client XLX427 with sid 44082
Dec 14 06:29:56 XLX416-TORONTO xlxd[45400]: Closing stream of module C
Dec 14 06:30:00 XLX416-TORONTO xlxd[45400]: Opening stream on module C for client XLX427 with sid 26163
Dec 14 06:30:02 XLX416-TORONTO xlxd[45400]: Closing stream of module C

From AMBE Server:

Dec 14 06:24:12 ambe-server ambed[3968]: Stream Open from XLX416 at 192.46.223.219
Dec 14 06:24:12 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 open
Dec 14 06:24:12 ambe-server ambed[3968]: Opened stream 10
Dec 14 06:24:12 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 closed
Dec 14 06:24:12 ambe-server ambed[3968]: 0 of 36 packets lost
Dec 14 06:24:12 ambe-server ambed[3968]: Stream 10 closed
Dec 14 06:24:22 ambe-server ambed[3968]: Stream Open from XLX416 at 192.46.223.219
Dec 14 06:24:22 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 open
Dec 14 06:24:22 ambe-server ambed[3968]: Opened stream 11
Dec 14 06:24:27 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 closed
Dec 14 06:24:27 ambe-server ambed[3968]: 0 of 252 packets lost
Dec 14 06:24:27 ambe-server ambed[3968]: Stream 11 closed
Dec 14 06:24:12 ambe-server ambed[3968]: Stream Open from XLX416 at 192.46.223.219
Dec 14 06:24:12 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 open
Dec 14 06:24:12 ambe-server ambed[3968]: Opened stream 10
Dec 14 06:24:12 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 closed
Dec 14 06:24:12 ambe-server ambed[3968]: 0 of 36 packets lost
Dec 14 06:24:12 ambe-server ambed[3968]: Stream 10 closed
Dec 14 06:24:22 ambe-server ambed[3968]: Stream Open from XLX416 at 192.46.223.219
Dec 14 06:24:22 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 open
Dec 14 06:24:22 ambe-server ambed[3968]: Opened stream 11
Dec 14 06:24:27 ambe-server ambed[3968]: Vocodec channel DVstick-33:DO47JCFP:1 -> DVstick-33:DO47JCFP:0 closed
Dec 14 06:24:27 ambe-server ambed[3968]: 0 of 252 packets lost
Dec 14 06:24:27 ambe-server ambed[3968]: Stream 11 closed

Unit file from XLX427:

ExecStart=/bin/bash -c "/usr/local/bin/xlxd XLX427 172.26.29.237 127.0.0.1"

Unit file from XLX416:

ExecStart=/bin/bash -c "/usr/local/bin/xlxd XLX416 192.46.223.219 70.XX.YY.189"

Thank you for looking into this. Please let me know if I have misconfigured something on my side.

Ramesh.

[LX3JL]

Sorry, but I don't understand your setup configuration. For instance which XLX is equipped with what AMBE server. What protocol are you entering with ? What protocol are you listening with etc..

May I suggest you simplify the setup to make a complete test ?

• just 2 XLX paired together, one with AMBE server and the other one without (no other peer, no BM)
• make a table and try with all in/out scenarios with different in and out protocols and status (working, not working)

for example:
XLXa : no AMBE server, XLXb : AMBE server
enter XLXa with DCS :
do you ear on XLXa using DCS (should), XLXa using DMR (should not), XLXb using DCS (should), XLXB using DMR (should)?

enter XLXa with DMR :
do you ear on XLXa using DCS (should not), XLXa using DMR (should), XLXb using DCS (should), XLXB using DMR (should)?

enter XLXb wit DCS :
do you ear on XLXa using DCS (should), XLXa using DMR (should), XLXb using DCS (should), XLXB using DMR (should)?

enter XLXB with DMR :
do you ear on XLXa using DCS (should), XLXa using DMR (should), XLXb using DCS (should), XLXB using DMR (should)?

[va3uv]

Hi Luc:

OK,, I now only have XLX416 and 427 Peered together (no other reflectors):

Here is the start of my testing... please let me know if I am on the right track:

I'm happy to share the Google sheet with you, which may allow for more interactive testing, please let me know your email address, if that works for you.

Thanks!

Ramesh.

[va3uv]

Updated table...

[LX3JL]

ok. Thanks for the testing.
I assume that in your table, the column "XLX416C" means listening to XLX416C with DMR. Right?
Can you document software versions of both XLX?

[va3uv]

Hi Luc:

I have added the xlxd s/w version to the table (v2.5.3 in both cases - XLX416 and XLX427).

The column XLX416C really means listening on DCS 416C (I clarified that in the table) - updated screenshot attached.

I am not sure what you mean by listening on XLX416 using DMR.... for the DMR side, we connect directly to the appropriate TG (302453).

[va3uv]

Even 2 D-STAR repeaters alone (no DMR), one on XRF427 C, the other on DCS416C, we are finding audio loss, some of the audio gets through, some does not.

Thanks!

[LX3JL]

Random packet loss and inconsistent behaviour strongly suggests network connectivity and/or workload issues. What hardware your reflectors are running on? Do you have reliable, reasonably low latency network connectivity (ethernet, fiber, no wireless)?
When I mean listening to XLXxxx via DMR, I mean listening to the XLX via a DMR capable hotspot/relay like a MMDVM for example.

[va3uv]

OK, Luc - now I understand what you mean by listening to XLX via DMR. I will test that late

Both XLX427 and XLX416 are in commercial DC's.

XLX427:

root@XLX427-AST2200:/xlxd# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

root@XLX427-AST2200:/xlxd# w
14:16:08 up 6 days, 17:17, 2 users, load average: 0.07, 0.06, 0.07

XLX416:

root@XLX416-TORONTO:/home/va3uv# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.2
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

root@XLX416-TORONTO:/home/va3uv# w
14:16:46 up 3 days, 19:43, 2 users, load average: 0.02, 0.12, 0.12

Ping is blocked on both FW's; I will check response times and report back later.

Thanks!

Ramesh.

[va3uv]

network ping times as requested...

FROM XLX427 TO XLX416:

root@XLX427-AST2200:/home/admin# ping 192.46.223.219
PING 192.46.223.219 (192.46.223.219) 56(84) bytes of data.
64 bytes from 192.46.223.219: icmp_seq=1 ttl=44 time=7.32 ms
64 bytes from 192.46.223.219: icmp_seq=2 ttl=44 time=7.32 ms
64 bytes from 192.46.223.219: icmp_seq=3 ttl=44 time=7.32 ms
64 bytes from 192.46.223.219: icmp_seq=4 ttl=44 time=7.27 ms
64 bytes from 192.46.223.219: icmp_seq=5 ttl=44 time=7.28 ms

FROM XLX416 TO XLX427:

root@XLX416-TORONTO:/home/va3uv# ping 15.157.128.240
PING 15.157.128.240 (15.157.128.240) 56(84) bytes of data.
64 bytes from 15.157.128.240: icmp_seq=1 ttl=51 time=7.34 ms
64 bytes from 15.157.128.240: icmp_seq=2 ttl=51 time=7.48 ms
64 bytes from 15.157.128.240: icmp_seq=3 ttl=51 time=7.27 ms
64 bytes from 15.157.128.240: icmp_seq=4 ttl=51 time=7.43 ms

Resources - XLX427:

root@XLX427-AST2200:/home/admin# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
BIOS Vendor ID: Intel(R) Corporation
Model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
BIOS Model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz CPU @ 2.5GHz
BIOS CPU family: 179
CPU family: 6
Model: 85
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 1
Stepping: 7
BogoMIPS: 4999.99

XLX416:

root@XLX416-TORONTO:/etc/systemd/system# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 48 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Vendor ID: AuthenticAMD
Model name: AMD EPYC 7713 64-Core Processor
CPU family: 25
Model: 1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Stepping: 1
BogoMIPS: 4000.00

Here is a tcpdump trace from XLX427 (where it is linked to XLX416 C) - you can see lots of traffic coming in from XLX416C:

21:12:25.276020 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.296128 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.316058 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.336034 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.356028 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.376019 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.396124 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.416040 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.436037 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.456011 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.476070 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.496078 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.505725 IP XLX427-AST2200.10002 > 192-46-223-219.ip.linodeusercontent.com.10002: UDP, length 9
21:12:25.516046 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.536059 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.556068 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.576080 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.596078 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.616034 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.636041 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.656034 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.676141 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.696047 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.716061 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.736045 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.750934 IP 192-46-223-219.ip.linodeusercontent.com.10002 > XLX427-AST2200.10002: UDP, length 9
21:12:25.756050 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.776063 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.796147 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.816099 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.836031 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.856404 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.876126 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.896034 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.916076 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.936024 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.956053 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164
21:12:25.976077 IP 192-46-223-219.ip.linodeusercontent.com.iax > XLX427-AST2200.iax: UDP, length 164

Now here is a tcpdump again from XLX427 - this time I am filtering host of one of my linked repeaters (meaning repeater linked to XLX427 using DEXTRA Protocol):

21:12:21.162495 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:24.176639 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:27.191414 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:28.232434 IP bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002 > XLX427-AST2200.30001: UDP, length 9
21:12:30.203547 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:33.218220 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:36.233099 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9
21:12:38.618582 IP bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002 > XLX427-AST2200.30001: UDP, length 9
21:12:39.241811 IP XLX427-AST2200.30001 > bras-vprn-ssvlon5203w-lp130-27-70-26-109-153.dsl.bell.ca.30002: UDP, length 9

As you can see, we just have the 9-byte keep alive packet, no audio.

Hope this is helpful.

Thanks!

Ramesh.

[LX3JL]

Thanks for all the info. You indeed seem to have strong hardware and network connectivity.
At this stage I can't figure out what the issue might be. Sorry for not beeping more helpfull.

[va3uv]

Hi Luc:

So we have an interesting finding (and perhaps an interim solution)...

We removed the XLX peers from XLX416 (leaving only the DMR Peer).

Next we connected an old XRF reflector (XRF221) to XLX416 A. We now see DMR traffic going to XRF221 (obviously this is using the DExtra protocol now, not the XLX peering protocol).

We then connected XRF221 to XLX405 (again using the DExtra protocol) and we see DMR transmissions now being relayed to XLX405 (also running xlxd v2.5.3 btw).

So it does seem that the XLX peering protocol is causing the issue here.

We tried to connect XLX416 to XLX405 directly (avoiding the XRF221 "bridge") - but it seems that the XRF linking capability in XLX is no longer supported. Can this be re-introduced, please?

Hope the above info helps with finding a solution.

Thanks,

Ramesh.