开云体育

Hello Skyler, Ok, so you're compiling with Rasbian Jessie but what version of Direwolf? 1.3 is stable and works well but there are some cool new features in 1.4 that you might want to try. --David

Odd .. i didnt see the previous post ... sorry if this is a repeat ... did you verify all the dependencies ? I just did a git pull on master (1.3) ... and was stil up to date and didint have that

Precompiled version -- https://nw-digital-radio.groups.io/g/compass/wiki/Compass-Linux-Packages-on-Other-Debian-Based-Systems Then apt-get update apt-get install direwolf [direwolf_packet]

For got to say, I am running a raspberry pi with the latest release of jessie.

I am trying to build direwolf on my raspberry pi 3. I ran the command make, but got the following error: make: *** [demod_afsk.o] Error 1 When I ran make again, here it the entire output: Any

direwolf_packet@...> wrote: Unless they're using the 0N 0W null position... I think the most correct way to implement the original objective is to use the send-only UDP port, where every

Fred, I'll give it a try. The worst I could do is break something I'm testing, so it's also easy to fix. Thanks, Arnold KQ6DI

Jim, I already have a filter on what goes to APRS-IS, and that works well. Note to everyone, 50 km is a decent range, but definitely anything beyond 300 km is completely bogus. Just about everyone

A filter like this might help. I think it won’t receive anything that has TCPIP or TCPXX in the packet. I don’t know it messages will pass if you are looking to pass them. Maybe there is a filter

Yes, there are two issues here. I have recently been testing Direwolf for this. you can limit what you send to the APRS-IS, by putting in a filter like this in the config file: "FILTER 0 IG

Yes, I have a RX-only IGate. Below is a snip (with the receiver off) of a bunch of data coming from the internet that wants to be transmitted. It's about 5 minutes worth. I realize it isn't a lot, but

Arnold, It seems you want to undertake a RX-only IGate. AFAIK, it doesn't matter if you are using direwolf or anything else, if you are directly connected to an APRS-IS server TCP port 14580, you will

I have a receive only IGate using DireWolf. I would like to stop ALL traffic coming from the IS server that wants to be transmitted, but I don't know the best parameter(s) to enter. Suggestions? I

Thx David, Yes, I changed the direwolf port to 8005. Will do with the winlink folks, but I guess the question will always surface on who uses what port. But I guess you are just saying the error

After testing and studying various documents, I would like to recommend the following entries in the Direwolf config file for a home (WIDE1-1) digi: as the direwolf documentation recommends, to not

Hey Tom, So you changed Direwolf port 8001 to something else? I would argue that the error coming from Winlink is misleading (it's not a file, it's a socket on Windows). I'd recommend you file a bug

Some users of direwolf, dstarrepeater, and fldigi may find this useful, especially for mobile operation.

No problem. Glad to know you got it working. Matthew PittsN8OHU? Sent from an Android Device

Mathew, Thx a bunch... that was the problem. changed direwolf tcpip port and everything works as advertised. ...73 Tom ve7did

Tom, Have you tried a different tcpip port for direwolf? It sounds like whatever port it's set for is the same as what Winlink Express is usig for the forms engine. Matthew PittsN8OHU? Sent from an