Re: Not accepting mail to yourself...
My guess is that since the message was forwarded from k4wof to me it could not be forwarded back his way so my bbs looked at the next HA (USA) and sent it on - same as Mark couldn't send it back to
By
John - wb4moz
·
#41994
·
|
Re: Not accepting mail to yourself...
I would also question why WB4MOZ passed it along to TX when it should
have remained in FL. So two issues are at play - proper hierarchical
addressing and proper forwarding.
--
Charles J. Hargrove -
By
Charles Hargrove
·
#41993
·
|
Not accepting mail to yourself...
Pretty sure this is what is happening, so everyone be sure you can accept and hold messages addressed to you.
I received a personal message on my BBS today addressed from KD4WLE and addressed to
By
Mark Taylor
·
#41992
·
|
Re: piQtBPQAPRS on Raspbian (bookworm) 64bit
Thank you!!
Looks like you started a new repository for QtBPQAPRS. :)
It will be awesome to be able to recompile each piece if needed.
-Jon
By
Jon Simonds
·
#41991
·
|
Re: piQtBPQAPRS on Raspbian (bookworm) 64bit
Yes, you need a 64 bit version. I've uploaded piBPQAPRS64 to my beta downloads.
73,
John
By
John G8BPQ
·
#41990
·
|
piQtBPQAPRS on Raspbian (bookworm) 64bit
I apologize if this has been covered, I searched the messages, but didn't seem to find anything.
When I try to run the binary piQtBPQAPRS, I receive this error:
./piQtBPQAPRS: error while loading
By
Jon Simonds
·
#41989
·
|
Re: BPQ32/LinBPQ vulnerability.
CVE-2024-34087
73, John
By
John G8BPQ
·
#41988
·
|
Hanging Connects
John:
I've been having some issues with "hanging" connects that never seem to go away.? Here's an example:
COSCO:KE0GB-7} G8BPQ Network System 6.0.24.40 for Linux (820)
Circuit(#USWCH:WA3WLH-14
By
Richard Hendricks - KE0GB <rickh6155@...>
·
#41987
·
|
Re: BPQ32/LinBPQ vulnerability.
*CVE-2024-34087*
By
KN4MKB Billy
·
#41986
·
|
Re: BPQ32/LinBPQ vulnerability.
Thank you Eric and Ben. Learned something new today.73 Chrisww2bsa
By
Chris Lance WW2BSA
·
#41985
·
|
Re: BPQ32/LinBPQ vulnerability.
Common Vulnerability and Exposures[0], or CVE, is a system that provides a reference method for vulnerabilities. A unique identifier is given to every vulnerability along with related information
By
Eric H. Christensen
·
#41984
·
|
Re: BPQ32/LinBPQ vulnerability.
https://en.m.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures
The security community uses a vulnerabiliy's CVE number when working with a vulnerability. The data in the CVR database links to
By
Ben Kuhn
·
#41983
·
|
Re: BPQ32/LinBPQ vulnerability.
Hmmm...never heard of that....what is a CVE and why is it important?ChrisWw2bsa
By
Chris Lance WW2BSA
·
#41982
·
|
Re: BPQ32/LinBPQ vulnerability.
We're CVEs issued for these vulnerabilities?
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
Sent from Proton Mail Android
By
Eric H. Christensen
·
#41981
·
|
Re: BPQ32/LinBPQ vulnerability.
BPQMail and BPQChat have also been updated....
By
Mark Taylor
·
#41980
·
|
BPQ32/LinBPQ vulnerability.
Someone has published an exploit for two buffer overflow vulnerability in BPQ32/LinBPQ.
The most serious one was fixed in 6.0.24.36 but many people may still be running older versions.
I suggest you
By
John G8BPQ
·
#41979
·
|
Re: Unidentified node appeared on AXIP
[email protected]> wrote:
all other internet facing ports besides the port that applies to Matt's
network. Then to address the one port where AUTOADDMAP is enabled, add
firewall rules to allow port
By
Lee Bengston
·
#41978
·
|
Re: Unidentified node appeared on AXIP
There are no credentials or keys for axudp/tcp mapping.
Its down to the sysop to allow the udp/tcp traffic. And then add to the
bpq32.cfg as a link partner.
73
Steve
[email protected]> wrote:
By
Steve G7TAJ
·
#41977
·
|
Re: Unidentified node appeared on AXIP
Hi, John:
I think I will add an additional AXIP port for the 1 neighbor not in Matt's network.
Thanks.
73, Chuck
By
Chuck Gelm
·
#41976
·
|
Re: Unidentified node appeared on AXIP
Hi, Gary:
Unknown to me, but not unknown to Matt.
Matt issues a credential/key for access.
Access is not 'open'.
I think.
73, Chuck
--
By
Chuck Gelm
·
#41975
·
|