Re: L4Compress in linbpq 6.0.24.61
On Wednesday, February 12th, 2025 at 20:49, Scott VE3QBZ <ve3qbz@...> wrote: Has anyone played with this new setting yet?
On the surface, it looks like compression of layer 4 packets between willing/capable BPQ nodes?
I currently have L4Compress set to 0 in my config file, until I find someone else running .61 ? I saw John testing it out earlier yesterday and today but didn't know exactly what they were working on. I just downloaded the latest pre-compiled version of linbpq64 but it seems to be version .59. Is there a changelog available? 73, Eric WG3K FM18rp Packet: WG3K@WG3K.#SMD.MD.USA.NOAM E-Mail: wg3k@...
|
L4Compress in linbpq 6.0.24.61
Has anyone played with this new setting yet?
On the surface, it looks like compression of layer 4 packets between willing/capable BPQ nodes?
I currently have L4Compress set to 0 in my config file, until I find someone else running .61 ?
Regards,
Scott
|
Hi,
?
Thanks for the post.? This config works for me BUT when I send unproto beacons to the port (setup in the web browser) the PTC reboots.? ?However, C 3 CALLSIGN works fine.??
?
It's a shame it doesn't like to UNPROTO.? ?
?
Cheers,
Dave
|
Bleh I hate formatting here sometimes. I should have previewed. But formatting here is almost as bad as MS Teams unless you force Markdown mode.
that should be
RADIO BLAH
00:00
DWELL_TIME,FREQ..
DWELL_TIME,FREQ..
01:00
DWELL_TIME,FREQ..
...
****
|
Be sure to use format of something like:
RADIO blah
00:00
DWELL_NUM,FREQ,...
DWELL_NUM,FREQ,...
01:00
DWELL_NUM,FREQ...
...
If you try to put times out of order it may do also what you have indicated.
I had to specify the 00:00 in this form tho the docs say that it is implied else it would also 'lockup' the scanning.
In some cases it would work a bit, then over time the timer would start to creep longer than dwell time until it ultimately stopped.
There was nothing logged in linbpq I could find to indicate any errors or issue.
|
Jim,
Are you by chance using any frequency scanning in BPQ? I have had similar issues with formatting that with times in radio/rigcontrol. It can be particular about formatting there.
|
Re: forwarding error - jnos forwards to bpq
Yes - you were essentially correct Charles - Jnos fbb=2 - bpq set for plain text - all ok now - thanks!
jerome
|
Re: SYSOP command STOPPORT
Thanks Rich,
?
Greatly appreciated.? ?I have another project? :-)
?
Regards
Dave VK2NA
|
Re: SYSOP command STOPPORT
Hello Dave,
On the Debian Bookworm systems here using stopport releases the associated device regardless of whether it is a h/w or virtual serial port or even a network port to a s/w tnc. I am able to temporarily use the device for something else and when finished easily "reactivate" it in linbpq using startport.
I assume most linux variants will behave the same.
73 de Rich WA3WLH
|
Hi,
I have a PTC-IIpro on /dev/ttyUSB0 (PORT 3) on my linux node.? I use this node for all RF connections to my BPQ that lives on a separate Raspberry Pi.
?
If I use the SYSOP command STOPPORT 3 does this release the /dev/ttyUSB0 completely or does it just close the port on the BQP Port?
?
I assume the PORT 3 is just closed at the switch.
?
Cheers,
?
Dave.?
|
The first thing I would do is try and determine if it was BPQ or the Pi causing it.
?
First by checking syslog or other logs available on a Pi.
?
Then, the next time it happens simply do a KILL and restart BPQ.? If it does not immediately work then the problem likely lies in the Pi.
?
If it is determined that it is in BPQ then an analysis of your config file may be in order.? (Looking for comflicts.)
?
?
--
73,
Mark, N5MDT
Montgomery, Texas
?
?
?
|
I¡¯m run liBPQ 6.0.24.42 on raspi talking to kenwood 590sg, scanning/forwarding has been working fine for over a month, then suddenly stopped working. ?Radio cmds no longer work until I reboot system and BPQ restarts and all works again until it doesnt. The failures are now less then a week apart.
Is this a known issue, is there a way to identify the cause?
any help appreciated.
jim KI0BK?
|
Re: Risks of running BPQ32 Windows in Administrative Mode
Running in in administrative mode just violates the rule of least privilege.
If a piece of software is compromised in windows, the threat actor will have the same privileges as the application itself.
I have demonstrated a remote code execution exploit on older versions of BPQ that did not require any action by the sysop besides exposing the telent port.
For more information, see CVE-2024-34087
In this case, the exploit is now public.
But either way, if the application were to be compromised (as they exploit does), and the application is running as a regular user, it will greatly reduce the impact and ability for the attacker to move around your network, or access other files.
If the application is running as administrator, the attacker now has complete control over the whole system, and can use it in any way they please as an administrator on your computer.
Regular users can't see each other files, and can't navigate to areas of the computer where sensitive user data is kept. They also can't install applications and often can't leverage network resources, as you experienced.
This helps keep the attacker contained within the system, and greatly reduces the ability for them to move laterally through the network.
|
Re: forwarding error - jnos forwards to bpq
No FBB B1F compressed forwarding turned on for either box?
toggle quoted message
Show quoted text
On 2/10/2025 4:10 PM, Jerome Schatten via groups.io wrote: VE7ASS-7 to VE7POO-7 ttl 25 cct=0107 ?<INFO S0 R0>:
[BPQ-6.0.24.56-FWIHJM$]
de VE7ASS>
03:35:19R VE7POO-7>VE7ASS-7 Port=3 <RR R F R2>
03:35:21R VE7POO-7>VE7ASS-7 Port=3 <I C S3 R2> NET/ROM
VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE ?<INFO S0 R1>:
[JNOS-2.0p.5-FHIM$]
FB B VE7SPY USA TEST3 3PN_VE7POO 429
F>
--
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
|
forwarding error - jnos forwards to bpq
I tried posting this to nos-bbs and it garnered no replies. ve7ass-7 is the bpq node; ve7ass-1 is the bpq bbs.? It's jnos that complains as? you can see from the bpq side below:
?
[...]
What is this error trying to tell me? ?ve7ass is the bpq machine and ve7poo is the jnos machine -- In jnos, 'mbox kick' initiates the forward cycle. A prepared message from a jnos-non bbs user (ve7spy) is in the 'usa' area. Below is the transaction after the 'jnos mbox kick'.
VE7POO-7 to VE7ASS-1 ttl 15 cct=0107 <CON REQ> w=4 VE7POO-1 at VE7POO-7 t/o 0
03:35:19T VE7ASS-7>VE7POO-7 Port=3 <I C P S0 R3> NET/ROM
??VE7ASS-1 to VE7POO-7 ttl 25 cct=0107 ?<CON ACK> w=71 my cct=02DE
03:35:19R VE7POO-7>VE7ASS-7 Port=3 <RR R F R1>
03:35:19T VE7ASS-7>VE7POO-7 Port=3 <I C P S1 R3> NET/ROM
??VE7ASS-7 to VE7POO-7 ttl 25 cct=0107 ?<INFO S0 R0>:
[BPQ-6.0.24.56-FWIHJM$]
de VE7ASS>
03:35:19R VE7POO-7>VE7ASS-7 Port=3 <RR R F R2>
03:35:21R VE7POO-7>VE7ASS-7 Port=3 <I C S3 R2> NET/ROM
??VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE ?<INFO S0 R1>:
[JNOS-2.0p.5-FHIM$]
FB B VE7SPY USA TEST3 3PN_VE7POO 429
F>
03:35:22T VE7ASS-7>VE7POO-7 Port=3 <I C P S2 R4> NET/ROM
??VE7ASS-7 to VE7POO-7 ttl 25 cct=0107 ?<INFO S1 R1>:
>
*** DONE
03:35:22R VE7POO-7>VE7ASS-7 Port=3 <RR R F R3>
03:35:26R VE7POO-7>VE7ASS-7 Port=3 <I C S4 R3> NET/ROM
??VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE ?<INFO S0 R1>:
[JNOS-2.0p.5-FHIM$]
FB B VE7SPY USA TEST3 3PN_VE7POO 429
F>
03:35:26R VE7POO-7>VE7ASS-7 Port=3 <I C S5 R3> NET/ROM
??VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE ?<INFO S1 R2>:
FBB Error: Expected 'FS ' string. Received '>' string.
03:35:26T VE7ASS-7>VE7POO-7 Port=3 <I C P S3 R6> NET/ROM
??VE7ASS-7 to VE7POO-7 ttl 25 cct=0107 ?<DISC REQ>
[...]
==============================================================
I can recall running into this problem before, many years ago.
?
Thanks for your thoughts on this!
jerome
|
Looking to add AXUDP links
I am looking for interested stations that would like to establish an AXIP link for forwarding messages.
?
WA, ME, ND, SD, LA, WY, MS, AL, SC, NH, CT mainly.? Will consider others, especially if you need any assistance with your node. I'm always willing to help.
?
Also, lost my main chat link if any current partners can get me? back on the bulk of the chat network.
?
?
?
QRZ email works, or http://n5mdt.ham-radio-op.net:52852
?
?
Thanks
Mark
--
73,
Mark, N5MDT
Montgomery, Texas
?
?
?
|
Still no crashes here with .59 after nearly a week running on x86 and x64.
In case the errors described have nothing to do with rPi's or ARM processors I should mention that I always build linbpq from source and I do not include support for I2C or MQTT.
I thought this worth a mention since the gdb backtrace provided by Roy looks like there is a problem with threading and / or libc but that could be misleading without digging deeper with gdb or something like strace.
73 de Rich WA3WLH
|
I noticed some other issues building and using .59.
Cheaders.h seems to replace cheaders.h but I dont think it was reflected fully or something in Makefile.
Another issue with .59 is try clawsmail out for smtp/nntp feeds from bpq. Mine would abort going through some of the nntp lists.
I reverted to .56, but I dont have the 'vara' issue others have on .56. I have previously discussed this with K5DAT in private mail.
Here my build/packet system is deb 10.
|
I had what might have been the same problem a while back when upgrading from the .53 to the .56 version. Crashes seemed to correlate with incoming VARA connections, but not every incoming connection would trigger a crash.
73, Lee K5DAT
|
|
|
David VK2NA
KN4MKB Billy