开云体育

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,

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

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.

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

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

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

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

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

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

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

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

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

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

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

I believe all the PBEACON and OBEACON lines are commented out. I'll try the beta I guess. Does linpac have to be run as superuser? I get a socket err if I try to run it as a regular user.

You must have that in your config. Make sure you have all PBEACON and OBEACON lines disabled. Else.. it might be a bug. I see you're running 1.0A but the current posted version is 1.0 and there is

Yes, I found the -s switch for beacon. That does keep the chat packet transmissions to one each. I did notice DW issues a significant number of packets by itself. At the moment I'm just listing

Direwolf isn't like a fully functional hardware TNC that offers "command" mode, an area to leave people messages, etc. It's meant to be used with other packet systems via protocols like KISS,

I don't think that Direwolf supports "one time" beacons. If you want something like that (sending UI frames), just use ax25tool's "beacon program with the "-s" option to send once. If you're

Well, I found that I can send out messages with beacon, although the messages repeat their transmissions automatically after a period of time. Is there a way to stop the retransmission of beaconed