Keyboard Shortcuts
Likes
- Direwolf
- Messages
Search
|
Re: Digipeater filter rules
On Sun, Jan 22, 2017 at 6:12 AM, wb2osz@... [direwolf_packet]?<direwolf_
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
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
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
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
¿ªÔÆÌåÓý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:
? |
|
Re: Use Direwolf with TNCPi
The purpose of direwolf is to provide a more flexible modem via a soundcard -- TNC Pi has a built-in modem. for some examples. On Fri, Jan 6, 2017 at 2:55 PM, n7qnm-lists@... [direwolf_packet] <direwolf_packet@...> wrote:
--
John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223  ? |
|
Re: Direwolf stuck in transmit
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
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 |
|
Re: Permission Denied with mkiss to Direwolf on Debian Hamradio Pure blend install
As an experiment I started direwolf with sudo, and mkiss connects ok, and I can use axcall to make a call to a nearby node successfully.
Is there something I need to do to open permissions on /tmp/kisstnc so I can run direwolf without sudo? Thanks, Kevin KK6DCT |
|
Re: Permission Denied with mkiss to Direwolf on Debian Hamradio Pure blend install
Thanks David, here's the output from strace:
kev@kh-debian:~$ sudo mkiss /tmp/kisstnc /dev/pts/3 mkiss: open: Permission denied kev@kh-debian:~$ sudo strace mkiss /tmp/kisstnc /dev/pts/3 execve("/usr/local/sbin/mkiss", ["mkiss", "/tmp/kisstnc", "/dev/pts/3"], [/* 14 vars */]) = 0 brk(0)????????????????????????????????? = 0x11be000 access("/etc/ld.so.nohwcap", F_OK)????? = -1 ENOENT (No such file or directory) mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f594967b000 access("/etc/ld.so.preload", R_OK)????? = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=109904, ...}) = 0 mmap(NULL, 109904, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5949660000 close(3)??????????????????????????????? = 0 access("/etc/ld.so.nohwcap", F_OK)????? = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/tls/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/tls/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/x86_64-linux-gnu/tls", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/x86_64-linux-gnu/x86_64", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/x86_64-linux-gnu", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0 open("/usr/lib/x86_64-linux-gnu/tls/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/usr/lib/x86_64-linux-gnu/tls/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/x86_64-linux-gnu/tls", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 open("/usr/lib/x86_64-linux-gnu/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/x86_64-linux-gnu/x86_64", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/usr/lib/x86_64-linux-gnu/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/x86_64-linux-gnu", {st_mode=S_IFDIR|0755, st_size=69632, ...}) = 0 open("/lib/tls/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/tls/x86_64", 0x7fff60a9e070) = -1 ENOENT (No such file or directory) open("/lib/tls/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/tls", 0x7fff60a9e070)??????? = -1 ENOENT (No such file or directory) open("/lib/x86_64/libax25.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/lib/x86_64", 0x7fff60a9e070)???? = -1 ENOENT (No such file or directory) open("/lib/libax25.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260$\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=144600, ...}) = 0 mmap(NULL, 2136192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5949253000 mprotect(0x7f594925c000, 2097152, PROT_NONE) = 0 mmap(0x7f594945c000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x9000) = 0x7f594945c000 close(3)??????????????????????????????? = 0 access("/etc/ld.so.nohwcap", F_OK)????? = -1 ENOENT (No such file or directory) open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=1738176, ...}) = 0 mmap(NULL, 3844640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5948ea8000 mprotect(0x7f594904a000, 2093056, PROT_NONE) = 0 mmap(0x7f5949249000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7f5949249000 mmap(0x7f594924f000, 14880, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f594924f000 close(3)??????????????????????????????? = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f594965f000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f594965e000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f594965d000 arch_prctl(ARCH_SET_FS, 0x7f594965e700) = 0 mprotect(0x7f5949249000, 16384, PROT_READ) = 0 mprotect(0x7f594967d000, 4096, PROT_READ) = 0 munmap(0x7f5949660000, 109904)????????? = 0 brk(0)????????????????????????????????? = 0x11be000 brk(0x11df000)????????????????????????? = 0x11df000 open("/var/lock/LCK..kisstnc", O_RDONLY) = -1 ENOENT (No such file or directory) open("/var/lock/LCK..3", O_RDONLY)????? = -1 ENOENT (No such file or directory) open("/tmp/kisstnc", O_RDWR|O_NONBLOCK) = -1 EACCES (Permission denied) dup(2)????????????????????????????????? = 3 fcntl(3, F_GETFL)?????????????????????? = 0x8002 (flags O_RDWR|O_LARGEFILE) fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f594967a000 lseek(3, 0, SEEK_CUR)?????????????????? = -1 ESPIPE (Illegal seek) write(3, "mkiss: open: Permission denied\n", 31mkiss: open: Permission denied ) = 31 close(3)??????????????????????????????? = 0 munmap(0x7f594967a000, 4096)??????????? = 0 exit_group(1)?????????????????????????? = ? +++ exited with 1 +++ |
|
Re: Permission Denied with mkiss to Direwolf on Debian Hamradio Pure blend install
David Ranch
Strange. Try installing 'strace' and send us the trailing part from the output of:
toggle quoted message
Show quoted text
sudo strace mkiss /tmp/kisstnc /dev/pts/4 --David On December 23, 2016 12:00:01 PM CST, "kevin_hooke@... [direwolf_packet]" wrote: ? |
|
Permission Denied with mkiss to Direwolf on Debian Hamradio Pure blend install
I have direwolf and ax25 setup on a Raspberry Pi with Raspbian and it's all working good. I just tried to install and setup Debian Hamradio Pure Blend on a desktop that comes with ax25 and Direwolf preinstalled, and I'm having trouble getting the kissattach and mkiss to Direwolf to work
I start direwolf with the -p option, and then do: kev@kh-debian:~$ sudo kissattach /dev/ptmx 1 44.56.4.118 Then I do: kev@kh-debian:~$ sudo mkiss /tmp/kisstnc /dev/pts/4 And I get this Permission denied, and I'm stuck. I've tried the other workaround with socat, so I've tried starting without the -p, and then doing socat PTY,raw,echo=0,link=/tmp/kisstnc TCP4:127.0.0.1:8001 and it sits there, but at that point I'm not sure what I need to mkiss to. Do I need to know what the /dev/pts number is, and presumably socat has created a pts that I need to pass to mkiss? I've tried these same steps on Mint 17.3 and got exactly the same error too, so not sure how to work around this at this point? Thanks, Kevin KK6DCT |
|
Re: Direwolf Command Line Options
¿ªÔÆÌåÓýHowdy David.. It is not gating aprs traffic because i am not using it on APRS here..?? Using it as a traditional packet station on Net105 for 300 baud hf with LinBPQ.? A fix was issued, which is working great as well.?? Tnx for the response though.... 73,? --steve,kb9pvh-- Packet: 14.105 (LSB) ARDOP: 7101 (USB) On 12/16/2016 10:50 AM, David Ranch
dranch@... [direwolf_packet] wrote:
? |
|
Re: Direwolf Command Line Options
Indeed...? that makes sense.? Yes, i am using the direwolf modem
in a traditional packet enviroment.? It has been performing extremely well on hf.?? Tnx for the explanation and fix... 73,? --steve,kb9pvh--
Sent from
On Dec 17, 2016, at 8:20 AM, "wb2osz@... [direwolf_packet]" <direwolf_packet@...> wrote: ? |
|
Re: Direwolf Command Line Options
Short answer: The fix is now in the "dev" branch. ?Just ignore the error message until you get a newer version. ?It doesn't hurt anything. Explanation: When using APRS, the first character of the information part of the field is called the "data type indicator." ? "T" indicates telemetry. ?In this case the following character should be "#". ?This message would be appropriate when using APRS. ? However, it looks like you are using traditional packet radio. ?Here the UI frames (broadcasts, not to a particular station) can have any text without any formatting rules. |
|
Re: Direwolf Command Line Options
¿ªÔÆÌåÓýHere is another one: KB7ITU audio level = 30(15/14)?? [NONE]?? _|||||| It only seems to be my station and this one..?? wonder if it has something to do with the letter T at the beginning of the data line maybe ???
73,?? --steve,kb9pvh-- =============================================== On 12/16/2016 08:40 AM, steve phelps
kb9pvh@... [direwolf_packet] wrote:
? |
|
Re: Direwolf Command Line Options
David Ranch
¿ªÔÆÌåÓýHmmm... this VE1JOT-5 station is gating non-APRS traffic which Direwolf is complaining about: ? #It didn't complain about this packet for some reason but this is not an APRS formatted packet ? [0.2] EI2GYB-3>MBX,VE1JOT-5*:Mail for: W6OAV VA3HRA KO4OP UZ7HO Maybe Direwolf 1.4 is more strict about non-APRS formatted packets that v1.3 because of it's enhanced telemetry support.? Curious, are you using any FIX_BITS settings??? If you are, there is an option to train the bit level repairs around APRS formatted strings.? If you like to see these On 12/16/2016 06:40 AM, steve phelps
kb9pvh@... [direwolf_packet] wrote:
? |
John Hays - K7VE / WRJT-215