It should not be possible to set send beacon too often in dig/wx some users are setting this on 30s with is flooding network. Minimum should be 5 or 10 minutes.
It should not be possible to set send beacon too often in dig/wx some users are setting this on 30s with is flooding network. Minimum should be 5 or 10 minutes.
<!-- github-sync-id:3761682966 -->
This has many validations to avoid this. Unless someone forked it and changed the code to allow this.
It I remember it right, 15 min was the minimum as interval.
Hi
What firmware ? Igate firmware?
This has many validations to avoid this. Unless someone forked it and changed the code to allow this.
It I remember it right, 15 min was the minimum as interval.
<!-- github-comment-id:3691296625 -->
Us far us i get from user the newest made it after installation. So just after update it happened. He changed it now but seams some upgrade issues
2025-12-25 10:03:59 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2\(_ G.../...g...t018h66b10358LoRa iGate Batt=4.25V
2025-12-25 10:04:29 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2\(_ G.../...g...t018h66b10357LoRa iGate Batt=4.27V
2025-12-25 10:05:00 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2\(_ G.../...g...t018h66b10359LoRa iGate Batt=4.26V
2025-12-25 10:05:28 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SQ2LXT-10:!L3aE(S2\(_ G.../...g...t018h67b10358LoRa iGate Batt=4.25V
2025-12-25 10:06:01 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2\(_ G.../...g...t018h66b10359LoRa iGate Batt=4.26V
Us far us i get from user the newest made it after installation. So just after update it happened. He changed it now but seams some upgrade issues
<!-- github-comment-id:3691376483 -->
Us SQ2JAD told me it happened after update to newest software so he didnt set that on purpose his setting was 15 minutes. It happened by itself that he started flooding network
Us SQ2JAD told me it happened after update to newest software so he didnt set that on purpose his setting was 15 minutes. It happened by itself that he started flooding network
<!-- github-comment-id:3691384479 -->
Is he using only packets over Rf? Does he has tnc connected?
Does he have more info about the other configurations?
Is he using only packets over Rf? Does he has tnc connected?
Does he have more info about the other configurations?
<!-- github-comment-id:3691389651 -->
Ahh, now I think I appreciate better the issue reported by SP2ATJ. Locally, W2MIX flashed from the website a brand-new LilyGO V1.6.1 70 cm board and it was beaconing about once every 20 seconds. I communicated with W2MIX, he tried flashing it again, but it ended up doing the same excessive beacon rate. As far as I know, he's still having that problem. I will attempt to investigate further.
Cheers and 73 - Jon N7UV
Ahh, now I think I appreciate better the issue reported by SP2ATJ. Locally, W2MIX flashed from the website a brand-new LilyGO V1.6.1 70 cm board and it was beaconing about once every 20 seconds. I communicated with W2MIX, he tried flashing it again, but it ended up doing the same excessive beacon rate. As far as I know, he's still having that problem. I will attempt to investigate further.
Cheers and 73 - Jon N7UV
<!-- github-comment-id:3860820921 -->
Ahh, now I think I appreciate better the issue reported by SP2ATJ. Locally, W2MIX flashed from the website a brand-new LilyGO V1.6.1 70 cm board and it was beaconing about once every 20 seconds. I communicated with W2MIX, he tried flashing it again, but it ended up doing the same excessive beacon rate. As far as I know, he's still having that problem. I will attempt to investigate further. Cheers and 73 - Jon N7UV
please let me know what you find
> Ahh, now I think I appreciate better the issue reported by SP2ATJ. Locally, W2MIX flashed from the website a brand-new LilyGO V1.6.1 70 cm board and it was beaconing about once every 20 seconds. I communicated with W2MIX, he tried flashing it again, but it ended up doing the same excessive beacon rate. As far as I know, he's still having that problem. I will attempt to investigate further. Cheers and 73 - Jon N7UV
please let me know what you find
<!-- github-comment-id:3881661020 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It should not be possible to set send beacon too often in dig/wx some users are setting this on 30s with is flooding network. Minimum should be 5 or 10 minutes.
Hi
What firmware ? Igate firmware?
This has many validations to avoid this. Unless someone forked it and changed the code to allow this.
It I remember it right, 15 min was the minimum as interval.
2025-12-25 10:03:59 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2(_ G.../...g...t018h66b10358LoRa iGate Batt=4.25V
2025-12-25 10:04:29 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2(_ G.../...g...t018h66b10357LoRa iGate Batt=4.27V
2025-12-25 10:05:00 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2(_ G.../...g...t018h66b10359LoRa iGate Batt=4.26V
2025-12-25 10:05:28 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SQ2LXT-10:!L3aE(S2(_ G.../...g...t018h67b10358LoRa iGate Batt=4.25V
2025-12-25 10:06:01 EET: SQ2JAD-10>APLRG1,WIDE1-1,WIDE2-1,qAR,SP2CDN-10:!L3aE(S2(_ G.../...g...t018h66b10359LoRa iGate Batt=4.26V
Us far us i get from user the newest made it after installation. So just after update it happened. He changed it now but seams some upgrade issues
I did not get your last sentence
Us SQ2JAD told me it happened after update to newest software so he didnt set that on purpose his setting was 15 minutes. It happened by itself that he started flooding network
Is he using only packets over Rf? Does he has tnc connected?
Does he have more info about the other configurations?
Ahh, now I think I appreciate better the issue reported by SP2ATJ. Locally, W2MIX flashed from the website a brand-new LilyGO V1.6.1 70 cm board and it was beaconing about once every 20 seconds. I communicated with W2MIX, he tried flashing it again, but it ended up doing the same excessive beacon rate. As far as I know, he's still having that problem. I will attempt to investigate further.
Cheers and 73 - Jon N7UV
please let me know what you find