Re: IGate not sending rx data, only beacons

[email protected]

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

Re: IGate not sending rx data, only beacons

[email protected]

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 can wade in with a better suggestion.

73 Keith G6NHU

Re: IGate not sending rx data, only beacons

[email protected]

#1735

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

Re: IGate not sending rx data, only beacons

[email protected]

#1734

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 local RF onto the internet.

73 Keith G6NHU

Re: IGate not sending rx data, only beacons

[email protected]

#1733

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 it come up in magenta on the Direwolf console, but that is not being sent or seen anywhere.

The only thing that can be seen are beacons I send.

I've gone through all the conf files and everything looks correct.?

Dale

de 2W0ODS

Re: IGate not sending rx data, only beacons

[email protected]

#1732

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 I can't see anything being uploaded.

Would appreciate any advice regarding this.

73 Keith G6NHU

(ex SysOp MB7UIV, the first licenced APRS gateway in the UK, many years ago)

Re: Digipeater filter rules

#1731

On Sun, Jan 22, 2017 at 12:11 PM, Angus Ainslie?<angus.ainslie@...>?wrote:

I'm my case I think it would be sufficient to delay 100 milliseconds and then a clear channel as the packet is either digipeated immediately or not at all.

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.

?

With APRX running on the kiss interface it probably can't do clear channel detection.

Aprx has nothing to do with clear channel detection. Aprx processes packets handed to it from the TNC over the KISS interface and hands back packets to be transmitted. Channel access and buffering is entirely handled by the TNC.

Can it do subsecond delays ?

Not really; with the time length of APRS packets, there isn't much use to sub-second viscous delays because you'll never hear an echo in that time.

--
Kenneth Finnegan, W6KWF

Re: Digipeater filter rules

Angus Ainslie

#1730

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 100 milliseconds and then a clear channel as the packet is either digipeated immediately or not at all. With APRX running on the kiss interface it probably can't do clear channel detection.

Can it do subsecond delays ?

Angus

--------------------------------------------

Show quoted text

On Sun, 1/22/17, Kenneth Finnegan KennethFinnegan2007@... [direwolf_packet] <direwolf_packet@...> wrote:

 Subject: Re: [direwolf_packet] Re: Digipeater filter rules
 To: direwolf_packet@...
 Date: Sunday, January 22, 2017, 10:15 AM


 ?









       On Sun, Jan 22, 2017 at 6:12 AM,
 wb2osz@...
 [direwolf_packet]?<direwolf_
 packet@...>?wrote:
 As
 far as I know there has been only one implementation.
 And that implementation is
 the one I now maintain, Aprx:?.
 com/aprx/
 Some of the old guard APRS
 developers don't like it, but the situation that Bob
 describes in the linked thread where he wants digipeaters to
 all have PWAIT=0 and walk over each other rarely happens
 anyways due to poor documentation / his packet fratricide
 theory lacking universal support, so I have lots of users
 who run viscous delay and are very happy with the reduced
 load on their local network / reduced transmit duty cycle on
 their digi (particularly users who suffer desense on their
 home base station).
 I believe you can use
 Direwolf to expose a KISS socket for Aprx, then you add a
 "viscous-delay 5" line in your digipeater config.
 It will queue every digipeated packet for 5-7 seconds
 checking for any echos from other digipeaters before
 transmitting it. It's impact on the local transmitter
 can be seen here:?
 PhirePhly/aprx/blob/master/
 ViscousDigipeaterTxEffect.png
 If you have any questions
 about setting up Aprx, you can post them on our forum
 here:?.
 com/forum/#!forum/aprx- software
 --
 Kenneth Finnegan, W6KWF
 .
 com/








 



 #yiv6957833027 #yiv6957833027 --
   #yiv6957833027ygrp-mkp {
 border:1px solid #d8d8d8;font-family:Arial;margin:10px
 0;padding:0 10px;}
 
 #yiv6957833027 #yiv6957833027ygrp-mkp hr {
 border:1px solid #d8d8d8;}

 #yiv6957833027 #yiv6957833027ygrp-mkp #yiv6957833027hd {
 color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
 0;}

 #yiv6957833027 #yiv6957833027ygrp-mkp #yiv6957833027ads {
 margin-bottom:10px;}

 #yiv6957833027 #yiv6957833027ygrp-mkp .yiv6957833027ad {
 padding:0 0;}

 #yiv6957833027 #yiv6957833027ygrp-mkp .yiv6957833027ad p {
 margin:0;}

 #yiv6957833027 #yiv6957833027ygrp-mkp .yiv6957833027ad a {
 color:#0000ff;text-decoration:none;}
 #yiv6957833027 #yiv6957833027ygrp-sponsor
 #yiv6957833027ygrp-lc {
 font-family:Arial;}

 #yiv6957833027 #yiv6957833027ygrp-sponsor
 #yiv6957833027ygrp-lc #yiv6957833027hd {
 margin:10px
 0px;font-weight:700;font-size:78%;line-height:122%;}

 #yiv6957833027 #yiv6957833027ygrp-sponsor
 #yiv6957833027ygrp-lc .yiv6957833027ad {
 margin-bottom:10px;padding:0 0;}

 #yiv6957833027 #yiv6957833027actions {
 font-family:Verdana;font-size:11px;padding:10px 0;}

 #yiv6957833027 #yiv6957833027activity {
 background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

 #yiv6957833027 #yiv6957833027activity span {
 font-weight:700;}

 #yiv6957833027 #yiv6957833027activity span:first-child {
 text-transform:uppercase;}

 #yiv6957833027 #yiv6957833027activity span a {
 color:#5085b6;text-decoration:none;}

 #yiv6957833027 #yiv6957833027activity span span {
 color:#ff7900;}

 #yiv6957833027 #yiv6957833027activity span
 .yiv6957833027underline {
 text-decoration:underline;}

 #yiv6957833027 .yiv6957833027attach {
 clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
 0;width:400px;}

 #yiv6957833027 .yiv6957833027attach div a {
 text-decoration:none;}

 #yiv6957833027 .yiv6957833027attach img {
 border:none;padding-right:5px;}

 #yiv6957833027 .yiv6957833027attach label {
 display:block;margin-bottom:5px;}

 #yiv6957833027 .yiv6957833027attach label a {
 text-decoration:none;}

 #yiv6957833027 blockquote {
 margin:0 0 0 4px;}

 #yiv6957833027 .yiv6957833027bold {
 font-family:Arial;font-size:13px;font-weight:700;}

 #yiv6957833027 .yiv6957833027bold a {
 text-decoration:none;}

 #yiv6957833027 dd.yiv6957833027last p a {
 font-family:Verdana;font-weight:700;}

 #yiv6957833027 dd.yiv6957833027last p span {
 margin-right:10px;font-family:Verdana;font-weight:700;}

 #yiv6957833027 dd.yiv6957833027last p
 span.yiv6957833027yshortcuts {
 margin-right:0;}

 #yiv6957833027 div.yiv6957833027attach-table div div a {
 text-decoration:none;}

 #yiv6957833027 div.yiv6957833027attach-table {
 width:400px;}

 #yiv6957833027 div.yiv6957833027file-title a, #yiv6957833027
 div.yiv6957833027file-title a:active, #yiv6957833027
 div.yiv6957833027file-title a:hover, #yiv6957833027
 div.yiv6957833027file-title a:visited {
 text-decoration:none;}

 #yiv6957833027 div.yiv6957833027photo-title a,
 #yiv6957833027 div.yiv6957833027photo-title a:active,
 #yiv6957833027 div.yiv6957833027photo-title a:hover,
 #yiv6957833027 div.yiv6957833027photo-title a:visited {
 text-decoration:none;}

 #yiv6957833027 div#yiv6957833027ygrp-mlmsg
 #yiv6957833027ygrp-msg p a span.yiv6957833027yshortcuts {
 font-family:Verdana;font-size:10px;font-weight:normal;}

 #yiv6957833027 .yiv6957833027green {
 color:#628c2a;}

 #yiv6957833027 .yiv6957833027MsoNormal {
 margin:0 0 0 0;}

 #yiv6957833027 o {
 font-size:0;}

 #yiv6957833027 #yiv6957833027photos div {
 float:left;width:72px;}

 #yiv6957833027 #yiv6957833027photos div div {
 border:1px solid
 #666666;height:62px;overflow:hidden;width:62px;}
 
 #yiv6957833027 #yiv6957833027photos div label {
 color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

 #yiv6957833027 #yiv6957833027reco-category {
 font-size:77%;}

 #yiv6957833027 #yiv6957833027reco-desc {
 font-size:77%;}

 #yiv6957833027 .yiv6957833027replbq {
 margin:4px;}

 #yiv6957833027 #yiv6957833027ygrp-actbar div a:first-child {
 margin-right:2px;padding-right:5px;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg {
 font-size:13px;font-family:Arial, helvetica, clean,
 sans-serif;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg table {
 font-size:inherit;font:100%;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg select,
 #yiv6957833027 input, #yiv6957833027 textarea {
 font:99% Arial, Helvetica, clean, sans-serif;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg pre, #yiv6957833027
 code {
 font:115% monospace;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg * {
 line-height:1.22em;}

 #yiv6957833027 #yiv6957833027ygrp-mlmsg #yiv6957833027logo {
 padding-bottom:10px;}


 #yiv6957833027 #yiv6957833027ygrp-msg p a {
 font-family:Verdana;}

 #yiv6957833027 #yiv6957833027ygrp-msg
 p#yiv6957833027attach-count span {
 color:#1E66AE;font-weight:700;}

 #yiv6957833027 #yiv6957833027ygrp-reco
 #yiv6957833027reco-head {
 color:#ff7900;font-weight:700;}

 #yiv6957833027 #yiv6957833027ygrp-reco {
 margin-bottom:20px;padding:0px;}

 #yiv6957833027 #yiv6957833027ygrp-sponsor #yiv6957833027ov
 li a {
 font-size:130%;text-decoration:none;}

 #yiv6957833027 #yiv6957833027ygrp-sponsor #yiv6957833027ov
 li {
 font-size:77%;list-style-type:square;padding:6px 0;}

 #yiv6957833027 #yiv6957833027ygrp-sponsor #yiv6957833027ov
 ul {
 margin:0;padding:0 0 0 8px;}

 #yiv6957833027 #yiv6957833027ygrp-text {
 font-family:Georgia;}

 #yiv6957833027 #yiv6957833027ygrp-text p {
 margin:0 0 1em 0;}

 #yiv6957833027 #yiv6957833027ygrp-text tt {
 font-size:120%;}

 #yiv6957833027 #yiv6957833027ygrp-vital ul li:last-child {
 border-right:none !important;
 }
 #yiv6957833027

Incorrectly I-gating Third-Party Packets from APRS-IS

#1729

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 something stripping SSIDs). Is this a known issue which has been corrected in a more recent release of Direwolf?

If not, can someone familiar with running Direwolf investigate the issue?

--
Kenneth Finnegan, W6KWF

IGate not sending rx data, only beacons

[email protected]

#1728

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 seem to be sending anything I Rx over the air to the internet.

I see everything that has been picked up and decoded in Green and Blue, but nothing ever goes Magenta other than the Beacon about my station that I set up.

I've read the manuals and a few guides online but everything seems to be set up correct.

Any help would be gratefully appreciated.

Dale

de 2W0ODS

Re: Digipeater filter rules

#1727

On Sun, Jan 22, 2017 at 6:12 AM, wb2osz@... [direwolf_packet]?<direwolf_packet@...>?wrote:

As far as I know there has been only one implementation.

And that implementation is the one I now maintain, Aprx:?

Some of the old guard APRS developers don't like it, but the situation that Bob describes in the linked thread where he wants digipeaters to all have PWAIT=0 and walk over each other rarely happens anyways due to poor documentation / his packet fratricide theory lacking universal support, so I have lots of users who run viscous delay and are very happy with the reduced load on their local network / reduced transmit duty cycle on their digi (particularly users who suffer desense on their home base station).

I believe you can use Direwolf to expose a KISS socket for Aprx, then you add a "viscous-delay 5" line in your digipeater config. It will queue every digipeated packet for 5-7 seconds checking for any echos from other digipeaters before transmitting it. It's impact on the local transmitter can be seen here:?

If you have any questions about setting up Aprx, you can post them on our forum here:?

--
Kenneth Finnegan, W6KWF

RF Preference

[email protected]

#1726

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 version of Raspbian.

What I have noticed recently is that on aprs.fi, my beacons are being shown as being received from the server instead of over rf. I would prefer the rf info be displayed when possible. I verified that my rf beacons are going out and being passed along, but I assume my igate sending beacon to server gets there first, so that is what is shown on aprs.fi. I shut off the server connection temporarily and then I could see my station being routed through other stations.

Is there a way to delay the beacon going to the server? Or a way to stop my beacons from being sent to the server but still be able send and receive other info to the server?

Thanks,

Kevin KJ5FA

Re: Digipeater filter rules

#1725

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 delay somewhere around 5 seconds. ?If a matching frame (excluding via path from the compare) is heard, it is removed from that holding area before it has a chance to be transmitted.

This approach is controversial. ?Google will lead you to discussions such as ??

While it might help in certain situations, it can also make things worse. ?As far as I know there has been only one implementation.

If one was determined to add this feature, you would not want to put checking in the transmit thread. ?That would interfere with the timing of other frames going out from attached applications, beacons, or an IGate.

The place to splice it in would be in digipeater.c where it calls tq_append, which adds a frame to the transmit queue. ?Instead the frame would be put into a new waiting area queue with a time stamp of when it should be released. ?It will be removed from the queue if a matching frame is received. ?Something would need to monitor that queue and release any frames after their waiting time is up.

?

Digipeater filter rules

[email protected]

#1724

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 digipeated even if they were heard directly.

Maybe I'm thinking about this wrong and there's a better solution. Where I live I basically in the centre between a 4 repeaters that are North south east and west of me. There is effectively a small hole in their coverage where I live. Each of these repeaters ?covers a good area because of their height and power.?

I'd like to fill in this hole by digipeating anything I hear directly that is not digipeated by one of the repeaters. By setting a distance limit I could likely achieve this with direwolf as it is but then I might miss some packets that weren't heard by the larger repeaters or digipeat packets they have already transmitted to a larger audience.

Looking at the code I think what I want to do is treat packets that are digipeated as if I had transmitted them by using?dedupe_remember on RXed digipeated packets. I'd also need to add some code that would look for dupes after?wait_for_clear_channel in xmit_thread.

Is there a way to do what I want with the current filter rules or must I start hacking code ?

Thanks

Angus

VE6GUS

?

Re: Dirwolf and MAC OS

David Ranch

#1723

开云体育

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.? Maybe your issue is around installing the compiler toolchain?

--David
KI6ZHD

On 01/06/2017 02:34 PM, frank_zappa@... [direwolf_packet] wrote:

Show quoted text

?

I am new to this group.? I sucessfully use Direwolf on one of my Ubuntu boxes.? I would like to get it to run on my Macbook Pro (running OS 10.9.5 Mavericks).? I would appreciate some help.? Thanks in advance
Frank DM3BC

Re: Use Direwolf with TNCPi

#1722

The purpose of direwolf is to provide a more flexible modem via a soundcard -- TNC Pi has a built-in modem.

for some examples.

Show quoted text

On Fri, Jan 6, 2017 at 2:55 PM, n7qnm-lists@... [direwolf_packet] <direwolf_packet@...> wrote:

?

I've got a Pi with a TNCPi (from Coastal Systems), currently running APRX.

Can Direwolf "talk" to the TNCPi, or do I really need to use the soundcard modem?

Thanks!

Clay
N7QNM

--

John D. Hays

K7VE

PO Box 1223, Edmonds, WA 98020-1223

?

??

Use Direwolf with TNCPi

#1721

I've got a Pi with a TNCPi (from Coastal Systems), currently running APRX.

Can Direwolf "talk" to the TNCPi, or do I really need to use the soundcard modem?

Thanks!

Clay
N7QNM

Dirwolf and MAC OS

[email protected]

#1720

I am new to this group.? I sucessfully use Direwolf on one of my Ubuntu boxes.? I would like to get it to run on my Macbook Pro (running OS 10.9.5 Mavericks).? I would appreciate some help.? Thanks in advance
Frank DM3BC

Re: Direwolf stuck in transmit

#1719

I recently tried my Rigblaster plug n play on Windows 10, and using the UZ7HO soundmodem it will start transmitting with the PTT but it does release it, and I have to kill my UZ7 modem app to get it to release.

Same Rigblaster works fine on Debian and Direwolf, but maybe I should test with Direwolf on Windows 10 too for a fair comparison.

Kevin KK6DCT

Packets not Seen in UISS Monitor

#1718

I've got UISS running with Direwolf so I can use the IGate feature of Direwolf.? It all seems to be working fine except no packets appear in the UISS monitor as when using AGWPE and I wanted to see if anyone knows of a way to make that happen.? I realize I can see everything in the Direwolf monitor but I would like to continue to use the MHeard and voice announcement features of UISS.? Thanks.

Ed

W4TBD