Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Bpq32
- Messages
Search
Re: Unidentified node appeared on AXIP
There is a Dutch packet network on CB Channel 36 LSB at 300 and 1200bd.? Sometimes I hear it here in Brazil. Em seg., 19 de ago. de 2024 10:10, Charles Hargrove via <n2nov=[email protected]> escreveu: European CB callsign/node. |
Re: Unidentified node appeared on AXIP
¿ªÔÆÌåÓýI recommend not using AUTOADDMAP unless you have a very compelling reason to use it.73, John On 19/08/2024 13:55, Gary - K7EK via
groups.io wrote:
|
Re: Unidentified node appeared on AXIP
trace it backward to see who gave you that node entry and so on and so on...
toggle quoted message
Show quoted text
On 8/19/2024 9:34 AM, Gary - K7EK via groups.io wrote:
Hmmm.. I wonder why it is permitted on the amateur AXIP network? --
Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan |
Re: Unidentified node appeared on AXIP
Hmmm.. I wonder why it is permitted on the amateur AXIP network?
Best regards,
Gary, K7EK
Get
On Aug 19, 2024, at 09:10, Charles Hargrove <n2nov@...> wrote: European CB callsign/node. |
Re: Unidentified node appeared on AXIP
European CB callsign/node.
toggle quoted message
Show quoted text
On 8/19/2024 8:55 AM, Gary - K7EK via groups.io wrote:
HARDIN:K7EK-7} Routes to:*AP3:AP3NOD* 203 4 3 AP3NOD --
Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan |
Unidentified node appeared on AXIP
HARDIN:K7EK-7} Routes to: AP3:AP3NOD 203 4 3 AP3NOD This node was noticed today. I connected and it appears to be in Germany. Unfortunately, I could not find any bona fide amateur call sign associated with it. If this is a non-amateur, it would permit unauthorized access? to radio ports around the world. Perhaps I am overly concerned with security, however I believe it is best to be safe than sorry in bringing this? to light. In the extreme, it could potentially pass payloads? of malware and other unwanted problems. Just how safe is BPQ32 (and other amateur radio software for that matter) in this respect? This would be a good reason for not enabling AUTOADDMAP. Does anyone know anything about this node? Is it legitimate, and what is the amateur radio call sign associated with it? Thanks. Best regards, Gary, K7EK |
Re: Packets don't get acknowledged by the receiving node
So after some setbacks, I was able to try a new setup, where the client side actually ran paracon instead of bpq32, with miniircd on the server, and it worked perfectly with miniircd's small script. I was able to send irc messages from a laptop to my cell phone over an rf connection. It was great. I'm not dead set on using bpq for the client side, so I'm satisfied.
?
...though, I can still try the kiss tcp connection to see what it does. |
Re: IL2P in HF
On Fri, Aug 2, 2024 at 9:25?AM Rich Sahlender via <wa3wlh=[email protected]> wrote:
By the way, Roy WW6Q and I are running both the QPSK V26A 600 and IL2P modems on 7101.3 usb?@ 2000Hz - doesn't seem to be a problem given one uses one or the other, and the QPSK modem is used pretty sparingly. 73, Lee K5DAT
|
Re: Packets don't get acknowledged by the receiving node
Reede I think the thing to consentrate on is why 7 cannot get to 1? It sends 3 packets and fails. This says 1 has a) not decoded these b) stopped working / replying to that callsign / L2 circuit.? My suggestion was, if they are on the same LAN I would be interested to see if you pointed them at each other in tcp kiss,removing the rf element. Although you state telnet works fine, this does not include the kiss side.? An axudp link is an option and possibly easier than 2 tcp kiss statements and a port redirect to connect the two. Not sure if BPQ works with 0.0.0.0 as the host to listen on all IPs?? If you send me the irc script off list, I'll set it up here across RF as well and test, if I can?? 73 Steve? On Sat, 17 Aug 2024, 22:43 reede7376 via , <reede7376=[email protected]> wrote:
|
Building with libminiupnpc 2.2.8
Hi there,
?
libminiupnpc has been updated and now UPNP_GetValidIGD() requires another argument - you can see the change and new definition on Github here:
?
?
This is what's being shipped in debian unstable/testing, so it's going to filter down to other systems soon and is preventing me from building packages for the repo.
?
This has impact on upnp.c only (so far).
?
It builds for bookworm fine still, as that version won't change for the life of the distro! |
Re: Packets don't get acknowledged by the receiving node
¿ªÔÆÌåÓýThat TXDELAY looks way too short. I suggest 350 as a good starting point.Ron VE3CGR On 2024-08-17 5:15 p.m., Brent WG0A via
groups.io wrote:
|
Re: Packets don't get acknowledged by the receiving node
Brent,
I took a look at the readout for the client side direwolf. It looks very similar if not identical to the server side. Maybe that means that something is getting fudged between bpq and direwolf on one of the computers? Steve, I can reconnect after it disconnects, if that's what you're asking. It just does the same thing over again when I try to load the irc application. I did try putting more txdelay and txtail in the configuration, but it didn't seem to fix anything. When I get some time to tinker with it, I will try the agw mode. As for how much data is being sent.. it doesn't have to be very much. I can use an irc program that doesn't spit too much out when you connect to it, which will only help. ?
As for setting up a kiss tcp link.. I think I misunderstood something.. Is this the page that has the instructions? ?
I looked at that page and it seems to have a very similar config to the one I'm already using.. Though, it also seemed like you were intending that I remove direwolf from the equation. In very blunt terms, how would I go about doing that? I hope I'm not helpless here.. haha
|
Re: Packets don't get acknowledged by the receiving node
And, to answer your original question. This does not look like a situation where too much data is being sent through direwolf. It is only sending 4 packets before waiting for an ack. This looks more like one side can't hear the other reliably, or something is going wrong on the KQ4RST-1 side.
?
By the way, what is the soundcard/radio setup for these stations?
?
And if it helps. here are? some of the bpq port settings that have worked for my 300 baud HF port.
?
FRACK=8000 MAXFRAME=1 PACLEN=60 TXDELAY=200 TXTAIL=20 SLOTTIME=100 PERSIST=64 NOKEEPALIVES=1 ? -Brent WG0A |
Re: Packets don't get acknowledged by the receiving node
When it goes wrong, can you still.connect to the other station or do you have to restart things? The log shows it trying but no reply, so as suggested, things have crashed?? Direwolf is not good with connected mode packet. It was designed for aprs and the logic with connected mode is not 100% in my experience. It works, yes but there are issues.? This I think might be something else however.? The suggestion of a kiss link - setup a kiss port over tcp and point the two together. That just misses out the DW.? Look on the BPQ32 Web page for instructions.? The other thing, if my suggestion of slowing the script down has not worked would be to try AGW mode with DW. This has more control? DW <-> BPQ than kiss.? If that's works, you know it's the data being sent too fast to the node.? How much data is it? Is the script available to test?? 73s? Steve? On Fri, 16 Aug 2024, 22:31 reede7376 via , <reede7376=[email protected]> wrote:
|
Re: Packets don't get acknowledged by the receiving node
Is there anything telling in the direwolf logs from the other side of that link. I feels like something on the other side of the link may have gone sideways.
For the record, I've been running bpq and direwolf together for years and it has been working well for me. So this should be a solvable problem.
?
-Brent WG0A |
Re: Packets don't get acknowledged by the receiving node
I tried using the higher TXDELAY, but it didn't seem to make a difference.
?
It seems like it is on the verge of losing connection at one point but recovers.
?
Sorry, I'm a tad new to this stuff.. how would I set up a kiss tcp/udp link? I can get in with the telnet port from the client computer and everything works fine if that's what you mean.. Is that what you meant?
?
Does Direwolf typically have problems with this type of thing?
?
Thanks for your time, everybody. |
Re: Packets don't get acknowledged by the receiving node
That's not really what I was getting at but it could be worth a try. I was meaning slow down the data rate.? It seems the remote end stops replying. Does it recover after the failure?? On Fri, 16 Aug 2024, 17:00 Jeff KP3FT via , <kp3ft=[email protected]> wrote:
|
Re: Packets don't get acknowledged by the receiving node
Typically you can bring the TXD down to 350 ms for radios since the 90s.
toggle quoted message
Show quoted text
On 8/16/2024 12:00 PM, Jeff KP3FT via groups.io wrote:
What Steve said.? Add a TXDELAY=500 line to both nodes' ports to start with and if that works, reduce the TXDELAY till it's shorter but still long enough to work.? Also, disable your KISSOPTIONS=NOPARAMS line in your port config. --
Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan |
Re: Packets don't get acknowledged by the receiving node
This looks like it might be a DW connected mode issue, which it does not do well at all! The trace shows it sends multiple RR frames with no reply and then discs. The -1 mode does hear - 7 Does it work over a kiss tcp /udp link?? Try adding a 0.5sec delay between each send from the application to see if it has any effect?? 73s? Steve? On Fri, 16 Aug 2024, 15:42 reede7376 via , <reede7376=[email protected]> wrote:
|
to navigate to use esc to dismiss