On Sat, Sep 9, 2023 at 04:54 AM, Louis Botterill wrote:
?
When I first switched to agw I found ID ¡®beacon¡¯ no longer worked, turns out it is only for kiss mode. This would be same regardless direwolf or sm. I changed it to do the same with a port broadcast. Per port broadcast is perhaps nicer, as message can be tailored as needed for the purpose of each port. It was unexpected and caused me to scratch head for a moment but all is good now it¡¯s understood.
?
On Sep 9, 2023, at 5:33 AM, Chris, N6CTA <mail@...> wrote:
[Edited Message Follows]
Alright, I discovered that switching from direwolf KISS TNC to QtSoundModem using the BPQtoAGW driver introduced some automated behavior related to Nodes broadcasts. I set QUALITY=0 in the AX25 port config to stop that. Let me know if you see anything else bizarre. I also shortened my ID text, set the interval to 10min(legal minimum), and disabled beacon text.
Thanks!
When you say per port broadcast do you mean to say how level 3/4 traffic is handled? Here on Network 105 it seems that no level 3/4 traffic is acceptable. That makes sense to me for HF.
On a separate note it seems like my station is working and propagation is as forecasted by the NOAA SWPC 10cm flux outlook. RK3KPK was able to log in to my BBS and make an account from Moscow. We should have some real good DX windows in about a week or so.
