# Master RTCM Timeout Regression in ASL3 (Build 22.10.1+asl3-3.10.5-1) **URL:** \ **Category:** AllStarLink\ **Tags:** asl3\ **Created:** [September 24, 2026, 9:48pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020 "2026-09-24T21:48:03Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 2:31am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/21 "2026-10-03T02:31:16Z")
Great, thanks Greg. Yes, if you can capture the console log at the same time from the Master RTCM to correlate with the Asterisk log, that would be helpful in trying to see who is initiating the timeout. 3.10.7 should significantly improve the packet processing on the host side, and reduce the amount of time/places we can get stuck processing client traffic. I am working up another firmware release for the RTCM right now (will be 4.01), that addresses an identified issue that could be related. See [Handle The ENC28J60 EIR\_RXERIF Condition Properly and Keep StackTsk() From Being Flooded · Issue #36 · AllStarLink/Voter · GitHub](https://github.com/AllStarLink/Voter/issues/36) for further explanation on the potential bug. I am suspicious that there could be traffic keeping the RTCM busy processing incoming packets, instead of servicing the watchdog. But without seeing the console log from the Master RTCM, and correlating it with the Asterisk events, that is just speculation. The incoming firmware update will also add a debug diagnostic to the firmware to see if the Ethernet chip is getting hammered and overflowing its RX buffer (which will lead to receive packets being dropped). I need to compile and test that the firmware loads, then will advise when it is in the repository. Lee ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 3:49am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/22 "2026-10-03T03:49:00Z")
The aforementioned test firmware can be downloaded from: [Voter/VOTER\_RTCM-firmware/firmware-images/4.01 at fix-rxoverflow · AllStarLink/Voter · GitHub](https://github.com/AllStarLink/Voter/tree/fix-rxoverflow/VOTER_RTCM-firmware/firmware-images/4.01) Once it is installed, you can enable Debug 2 to monitor for receive buffer overflows. From the Main Menu: 14 --\> 2 --\> 99 --\> r The other fix in this firmware may help regardless, so you may or may not see any overflows (hopefully not). I was able to force the buffer overflow by flooding the device with UDP traffic, so I can confirm the counter does in fact work. Lee ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 4:19am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/23 "2026-10-03T04:19:02Z")
Here's the last occurrence: ![image](https://community.allstarlink.org/uploads/default/original/2X/7/7c5128004b4c4e4403c856b5980c299fa28a7a91.png) ![image](https://community.allstarlink.org/uploads/default/original/2X/c/c6ece77b6ff04bed5530a11e914d265794a42c79.png) ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 4:24am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/24 "2026-10-03T04:24:35Z")
Interesting. When I try to post the latest screen shot, I get an error stating "An error occurred: Body is too similar to what you recently posted" Apparently a spam filter is prohibiting my post. Let me see if I can work around this. ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 4:25am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/25 "2026-10-03T04:25:12Z")
Trying again. ![image](https://community.allstarlink.org/uploads/default/original/2X/7/7c5128004b4c4e4403c856b5980c299fa28a7a91.png) ![image](https://community.allstarlink.org/uploads/default/original/2X/c/c6ece77b6ff04bed5530a11e914d265794a42c79.png) ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 4:38am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/26 "2026-10-03T04:38:49Z")
Let's see if this works. asl3\*CLI\> [2026-10-02 21:11:29.731] NOTICE[2806]: chan\_voter.c:5414 voter\_timer: VOTER 42833: Client Home\_Rptr disconnect (timeout) [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5420 voter\_timer: Lost master timing client, disconnecting remaining clients. [2026-10-02 21:11:29.731] NOTICE[2806]: chan\_voter.c:5424 voter\_timer: VOTER 42833: Master changed from client Home\_Rptr to NONE [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Pleasants\_Peak [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Signal\_Peak [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Pleasants\_AstroTac [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mirador [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: San\_Miguel [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Wilson\_Quantar [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Wilson\_AstroTac [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Woodson [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Black\_Mtn [2026-10-02 21:11:29.731] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Lab\_Test\_Quantar [2026-10-02 21:11:29.962] NOTICE[2805]: chan\_voter.c:5976 voter\_reader: VOTER 42833: Master changed from client NONE to Home\_Rptr [2026-10-02 21:11:35.292] WARNING[2805]: chan\_voter.c:6030 voter\_reader: VOTER lost master timing source!! [2026-10-02 21:11:35.311] NOTICE[2806]: chan\_voter.c:5414 voter\_timer: VOTER 42833: Client Home\_Rptr disconnect (timeout) [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5420 voter\_timer: Lost master timing client, disconnecting remaining clients. [2026-10-02 21:11:35.311] NOTICE[2806]: chan\_voter.c:5424 voter\_timer: VOTER 42833: Master changed from client Home\_Rptr to NONE [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Pleasants\_Peak [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Signal\_Peak [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Pleasants\_AstroTac [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mirador [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: San\_Miguel [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Wilson\_Quantar [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Wilson\_AstroTac [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Mt\_Woodson [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Black\_Mtn [2026-10-02 21:11:35.311] WARNING[2806]: chan\_voter.c:5435 voter\_timer: Forcing disconnect of client: Lab\_Test\_Quantar [2026-10-02 21:11:35.319] NOTICE[2805]: chan\_voter.c:5729 voter\_reader: Client Signal\_Peak connection blocked until master client connects [2026-10-02 21:11:35.676] NOTICE[2805]: chan\_voter.c:5729 voter\_reader: Client Mt\_Woodson connection blocked until master client connects [2026-10-02 21:11:36.174] NOTICE[2805]: chan\_voter.c:5729 voter\_reader: Client Black\_Mtn connection blocked until master client connects [2026-10-02 21:11:36.210] NOTICE[2805]: chan\_voter.c:5729 voter\_reader: Client Mt\_Woodson connection blocked until master client connects [2026-10-02 21:11:36.248] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 42833: Client Home\_Rptr connected. [2026-10-02 21:11:36.255] NOTICE[2805]: chan\_voter.c:5976 voter\_reader: VOTER 42833: Master changed from client NONE to Home\_Rptr [2026-10-02 21:11:36.280] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29474: Client Pleasants\_Peak connected. [2026-10-02 21:11:36.358] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29123: Client Mt\_Wilson\_AstroTac is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.358] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29123: Client Mt\_Wilson\_AstroTac connected. [2026-10-02 21:11:36.371] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29474: Client Signal\_Peak connected. [2026-10-02 21:11:36.380] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29123: Client Mt\_Wilson\_Quantar connected. [2026-10-02 21:11:36.391] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29476: Client San\_Miguel is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.392] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29476: Client San\_Miguel connected. [2026-10-02 21:11:36.421] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29474: Client Pleasants\_AstroTac connected. [2026-10-02 21:11:36.445] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29475: Client Mirador is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.445] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29475: Client Mirador connected. [2026-10-02 21:11:36.449] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29111: Client Lab\_Test\_Quantar is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.449] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29111: Client Lab\_Test\_Quantar connected. [2026-10-02 21:11:36.682] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29227: Client Black\_Mtn is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.682] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29227: Client Black\_Mtn connected. [2026-10-02 21:11:36.730] NOTICE[2805]: chan\_voter.c:5811 voter\_reader: VOTER 29222: Client Mt\_Woodson is sending mix mode flag, setting client to mix mode [2026-10-02 21:11:36.730] NOTICE[2805]: chan\_voter.c:5865 voter\_reader: VOTER 29222: Client Mt\_Woodson connected. 10/03/2026 04:11:35.180 ERROR! Host response timeout 10/03/2026 04:11:35.180 Host Connection Lost (Pri) (10.4.73.22) 10/03/2026 04:11:36.220 Host Connection established (Pri) (10.4.73.22) ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 4:51am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/27 "2026-10-03T04:51:37Z")
So this: ```auto 10/03/2026 04:11:35.180 ERROR! Host response timeout ``` Occurs before this: ```auto [2026-10-02 21:11:35.292] WARNING[2805]: chan_voter.c:6030 voter_reader: VOTER lost master timing source!! ``` That seems to indicate that the Master RTCM thinks it hasn't heard from the host in \>6 seconds, so it is the one that drops the connection. Not the host missing packets coming from the Master RTCM for 100ms. Since we're using GPS timing here, I am hoping that those timestamps are very accurate. But the only way to get the "Host response timeout" is for the RTCM to be missing traffic for \>6 seconds. What is the duplex setting of Home\_Rptr again? Are these logs you just posted with the 4.01 firmware on the RTCM, or the original 3.00 firmware? Lee ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 4:55am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/28 "2026-10-03T04:55:06Z")
They are from the 3.00 firmware. The Master RTCM Ethernet Duplex is set to Full. ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 5:23am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/29 "2026-10-03T05:23:35Z")
I installed 4.01 and am trying it now. With 4.01, after about seven minutes I saw the Connection Lost/ Connection Established messages on the RTCM but no overflow messages. ![image](https://community.allstarlink.org/uploads/default/original/2X/5/5ed9bb0e7365f4fe316657271c4598f39e2811bb.png) ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 5:42am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/30 "2026-10-03T05:42:19Z")
Ok, thanks for the update, Greg. I've got a couple other things to try and fix on the transmit side in the firmware in the RTCM, so I will work on those next, then go back to looking at the channel driver some more. Can you describe what the network looks like between where Home\_Rptr is and the Asterisk host? I know above you mentioned that they are on the same VLAN, but physically separated. What exactly does that entail, including the types of switches being used? Lee ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 5:46am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/31 "2026-10-03T05:46:25Z")
The server has two switches between it and the router. The Master has two switches between it and the router, with the switch closest to the router being common for both devices. The router is a Ubiquiti UDM SE which is connected to a Ubiquiti 48-port switch. The server is connected to another Ubiquiti 16-port switch, which is connected to the main 48-port switch. The Master RTCM is connected to a 24-port Cisco switch which is connected to the 48-port main switch. ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 4:26pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/32 "2026-10-03T16:26:14Z")
Thanks, that helps me understand the architecture a bit better. Have you looked at the port stats on the Cisco switch to see if the port is taking errors? I know I have seen my C3850's get unhappy in the past... can't remember why off the top of my head, but it effectively bounced the port once in a while. My notes say I had to switch the port to 10/auto to clean things up... but I don't quote me on that. I do know the RTCM doesn't do auto-negotiate. So an attached switch may not properly detect the 10mb/s speed... like a Cisco which may be too smart for its own good sometimes. Still working on another firmware update to fix some transmit path bugs in the TCP/IP stack. Lee ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [October 3, 2026, 5:00pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/33 "2026-10-03T17:00:25Z")
Do you happen to have 802.3x Ethernet flow control enabled on the switch? I have run into problems with switches that have it enabled where a sudden burst of traffic from a real-time source, like a node or RTCM, has hit the packet threshold and locked the port out for a period of time. It did not used to be enabled by default, but it seems like a lot of things I encounter recently have it turned on. I am assuming it helps some other use case for it to be on, but I don’t know what it is. But I’m a network curmudgeon 🙂 ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 5:48pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/34 "2026-10-03T17:48:34Z")
I have this setting on my UniFi switches. It doesn't specifically mention 802.3x, but it sounds consistent with what you’ve described. It isn't enabled by default although this is the way it's been configured for several years and I never had these issues until recently. ![image](https://community.allstarlink.org/uploads/default/original/2X/a/a690906fe3100d585827337e8e64b690756459c8.png) This is the current configuration of the Cisco switch: ![image](https://community.allstarlink.org/uploads/default/original/2X/4/4e4b323ebc2fda705c6475b5167ec9f6875e8080.png) ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 3, 2026, 7:53pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/35 "2026-10-03T19:53:57Z")
So, there's a problem. You said the RTCM was set for full duplex, but the Cisco is set for 10/half (looking at the actual negotiated port config on the right). Turn of autonegotiation, the RTCM doesn't support it. Manually set the port to 10/full, to match what the RTCM is configured for. Lee ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 9:10pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/36 "2026-10-03T21:10:45Z")
I changed to 10/Full, but same problem ![image](https://community.allstarlink.org/uploads/default/original/2X/8/8da683a7cf883efd6989bb01587d310f04648f3f.png) ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [October 3, 2026, 10:39pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/37 "2026-10-03T22:39:19Z")
> [@WB6ZSU](#): > > It isn't enabled by default although this is the way it's been configured for several years and I never had these issues until recently. The reason I suggested it is because if it's some code bug flooding enough packets at once to trigger flow control, that could be what's causing the drop and would hint at something to look at. ---
**Author:** ![WB6ZSU](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/94ad74/32.png) [@WB6ZSU](https://community.allstarlink.org/u/WB6ZSU)\ **Post date:** [October 3, 2026, 11:36pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/38 "2026-10-03T23:36:06Z")
But my current settings are correct, right? ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [October 3, 2026, 11:39pm UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/39 "2026-10-03T23:39:50Z")
You have flow control disabled so that rules out what I was asking about. ---
**Author:** ![VE7FET](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ve7fet/32/1267_2.png) [@VE7FET](https://community.allstarlink.org/u/VE7FET)\ **Post date:** [October 4, 2026, 12:38am UTC](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020/40 "2026-10-04T00:38:31Z")
Glad you got the duplex issue sorted out, Greg. That could definitely be a contributing factor for creating excess colissions and errors. I've update the 4.01 firmware to add some more fixes for Microchip silicon errata that wasn't necessarily being handled well/properly in the firmware. And in particular, there is a bug fix that could have prevented keepalive packets from being sent on the proper cadence under certain network conditions, which could lead to timeouts. The updated firmware is still 4.01, but with today's date. It can be pulled from: [Voter/VOTER\_RTCM-firmware/firmware-images/4.01 at fix-ENC28J60-txrx · AllStarLink/Voter · GitHub](https://github.com/AllStarLink/Voter/tree/fix-ENC28J60-txrx/VOTER_RTCM-firmware/firmware-images/4.01) AFAIK, that should address the outstanding firmware issues, that I have been able to find. Now back to looking at chan\_voter. Lee [Previous page](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020.md?page=1) [Next page](https://community.allstarlink.org/t/master-rtcm-timeout-regression-in-asl3-build-22-10-1-asl3-3-10-5-1/25020.md?page=3)