开云体育

Yes - you were essentially correct Charles - Jnos fbb=2 - bpq set for plain text - all ok now - thanks! jerome

Thanks Rich, Greatly appreciated.? ?I have another project? :-) Regards Dave VK2NA

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

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

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

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

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.

No FBB B1F compressed forwarding turned on for either box? -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline

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

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

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

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

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

Pat

Hey Glenn Yes, I had this happen yesterday after I downloaded .59 and started it up. It ran for 5 or 10 mins and then and then crash. I'm running pilinbpq on a RPI4b with Bullseye OS. I'm running

Hi Glenn, I do not use rPi's but .59 has been stable here on x64. I've had it running on 10m in the "lab" for about 2-3 days now. RF connects are only from me as I move around the house but include

This should have read:? You definately need a Digimap 3=3,IS And that is the only Digimap statement you need.? At least until you fully understand it. -- 73, Mark, N5MDT Montgomery, Texas

Upgraded Pilinbpq to 6.0.24.59 and after about 5 minutes BPQ closes down with the following message. SIGSEGV Received Went back to .45 which is working fine. Anyone else seeing this? -- -- *Apologies

Gee, I'm no expert but I periodically activate my digimap feature in order to assist others.? I have never seen a reason to 'connect' to telnet.? What exactly is being accomplished by this? AprsDigi

Hello Rory, In the attached version I did the following: - Removed the multi-line comment beginning markers that preceded ports 1 and 2 (changed them to comments) - Commented out your port 3 and