开云体育

I removed the digipeat line from my sdr.conf file as it has been suggested that for an RX only iGate, it's not needed. Checking today, still only my beacons have been forwarded onto the internet. 73

Arnold, Did you ever find out what your problem is/was? I am having a very similar issue. I am setting up an Igate and Direwolf will not decode any packets. I would go into detail, but I don't want to

That seems like a lot of effort just to eliminate a few seconds of digipeater latency, but to each his own. -- Kenneth Finnegan, W6KWF http://blog.thelifeofkenneth.com/

Correct but if you waited a couple hundred milliseconds the RX would have started by then. If the packet duplicate check was done after the clear channel detection then you would weed out digipeated

IGTXVIA 0 didn't disable anything. Keith, if you look at your Raw data on aprs.fi do you see anything other than your Beacons now? I still don't see anything other than beacons on mine after changing

I did see a few [IG>TX] in the console so I just added: IGTXVIA 0 to sdr.conf.

Maybe not but I'm certainly seeing more magenta lines flashing up my screen now. With hindsight, maybe not as much as I'd expect so perhaps it's not quite the correct way to do it. Hopefully someone

From what I understand that isn't needed on a Rx only IGate?

I'm replying to myself now because I think I've resolved this. In sdr. conf, I added a line: DIGIPEAT 0 ig ^WIDE[3-7]-[1-7]$ ^WIDE[12]-[12]$ ... and it now looks as though I'm relaying stuff from

Hi Keith, I just fired up APRSIS32 on my windows machine and connected to Direwolf on my Pi using port 8001, all the decodes are showing fine on there too. I just hit "Transmit" on APRSIS32 and I saw

I've just done exactly the same thing today and am seeing the same thing - I'm receiving plenty of stations which are being decoded and shown in green or blue but only my own beacon shows magenta and

wrote: There is no way to be able to tell within 100ms if a packet has been digipeated or not. A typical packet is 500-1200ms long. Aprx has nothing to do with clear channel detection. Aprx processes

Hi Kenneth, Thanks fro the ideas with APRX. With the digipeaters in my area I don't ever see the packet fratricide that was described in the link. I'm my case I think it would be sufficient to delay

Greetings, I'm seeing evidence on other lists that Direwolf is incorrectly I-gating the payload of third-party packets with a network ID of "TCPIP" back to the APRS-IS (Namely the SMSGTE threads on

I have Direwolf set up on a Pi with a RTL SDR, I intended on putting an IGate up here, Everything appears to be working, I am receiving lots of APRS packets, I can send a beacon however it does not

direwolf_packet@...> wrote: And that implementation is the one I now maintain, Aprx: http://thelifeofkenneth.com/aprx/ Some of the old guard APRS developers don't like it, but the

Hello. I have tried to search this issue but didn't have any luck. I am running a Raspberry Pi2 with Direwolf v1.4 setup to run an APRS station and a mainly receive IGate. The RPi2 is running Jessie

What you are describing is known as "viscous" digipeating. The idea is that a digipeater would not retransmit frames immediately. Instead the frames are put into a holding area and transmitted after a

Hi I see that you can create a filter that doesn't digipeat packets that have already been digipeated is there a way to augment that filter is it also doesn't digipeat packets that have been

Hello Frank, What help do you need? If you have Direwolf working on Linux, you would again follow the Direwolf User Guide to compile the code for OSX and then configure it just like you did for Linux.