开云体育

The beta version does it as well. Do you think it has to do the the KISS terminal?

BTW I am bulding and running on a Debian Jessie AMD64 system. DW only starts to make the questionable transmissions after I attach the KISS termainal. I have check the kissattach command line

Double check the way you're starting Direwolf. Since it uses the split PTY system, the output of Direwolf starting up needs to be fed into kiss-attach and the AX.25 device must match with that you

All that's good in my system. I noticed that the same thing was happening with soundmodem. So, I started looking into other things. The problem turned out to be some services running on my

Ah yes... Samba, Avahi (netconf / Bonjour), and other daemons that do broadcasts need to be updated to only INCLUDE configured interfaces and not bind to "all" interfaces. Was your problem daemon

The problem services were avahi, samba, and rpcbind, along wtih CUPS. CUPS I want to keep, and it was sending out mDNS broadcasts. So, that's the one I filtered. Also, I changed the filtering from

Is there any way to turn off the following messages, Past 100 seconds, 4410000 audio samples, 0 errors. and only report when errs occur? SR

Are you logging the terminal output to file?? You can 'grep' for whatever you want (or don't want) then. Ian VK1IAN

Ha, that's a thought. I was wanting to use this for packet chat, and the status updates just take up room in the chat log. Thanks, SR

Can you make that work on an ongoing basis with only one call to grep?

Not sure I understand what you are asking however if you want all the "Past 100 seconds, 4410000 audio samples, 0 errors" lines removed, assuming you've started direwolf piping it's output

What you mentioned still outputs blank lines. This did what I want: tail -f dw.log | grep "^\[0L\]" I believe I'm ready to finish my computer-radio inter-connect now and do some packet chatting.

There isn't any way to disable all the chattiness of Direwolf today though I've asked John to add some additional command line options in future versions to suppress a lot of these. Until then, I

That's fine. The log file and grep do what I wanted. Together with a beacon wrapper script I modidied they make quite the clean packet chat client. This method requires the use of two windows,

Ok and I understand what you're doing with beacon to have an UNPROTO or UI chat but check out Linpac. It's F10 screen gives you a very nice UNPROTO chat window. Did you enable one channel or two?

In the configuration file I enabled only 1 channel. And it seems seldom but random that DW wiill try to send the beacon messages out over channel 2, 7, or 8 etc. and the message for that particular

As my old Alinco HT and probably all other HTs without a data port use the tip of a stereo plug for the audio input and output, as as the tip is specidied as the left channel. I would think it best

The only Linux packet radio BBSs I can find will only run on linux kernel 2.x. I was wondering if there were any packet BBSs that will run on a 3.x kernel with modern ax25 libraries.

The current ones I'm aware of is JNOS and FBB. BPQ32 is lighter weight but still has a bit of BBS functionality. Lighter weight yet again includes Linpac, etc. --David

Maybe I'm trying to take on more than I need to here at the moment. Since I have completed my computer-radio connector and have successully tested it at sending and recieveing various digital modes