December 2013 - App_rpt-users - lists.keekles.org

Debian wheezy (7) install?
by Bryan Fields 15 Dec '13

15 Dec '13

Greetings all, it's literally been 7-8 years since I've been building repeaters with app_rpt, and the project has certainly come a long way. At the time i last had it going on Debian with a quad PCI card. I've found some older documentation on compiling it from source on debian now that it's a fork of the main asterisk project. http://ohnosec.org/pipermail/app_rpt-users/2011-February/002266.html This link has a script which I've taken a look at, and suspect my issues compiling zaptel/asterisk are kernel 3.2 related. I had to modify zaptel/kernel/zconfig.h to #include <generated/autoconf.h> in the headers Now I'm seeing the following error about what looks like an initialization of an ioctl variable. make[2]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64' CC [M] /usr/src/astsrc/zaptel/kernel/zaptel-base.o /usr/src/astsrc/zaptel/kernel/zaptel-base.c: In function ‘zt_rbs_sethook’: /usr/src/astsrc/zaptel/kernel/zaptel-base.c:2160:2: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’ [-Wparentheses] /usr/src/astsrc/zaptel/kernel/zaptel-base.c: At top level: /usr/src/astsrc/zaptel/kernel/zaptel-base.c:7650:2: error: unknown field ‘ioctl’ specified in initializer /usr/src/astsrc/zaptel/kernel/zaptel-base.c:7650:2: warning: initialization from incompatible pointer type [enabled by default] /usr/src/astsrc/zaptel/kernel/zaptel-base.c:7650:2: warning: (near initialization for ‘zt_fops.fsync’) [enabled by default] make[5]: *** [/usr/src/astsrc/zaptel/kernel/zaptel-base.o] Error 1 make[4]: *** [_module_/usr/src/astsrc/zaptel/kernel] Error 2 make[3]: *** [sub-make] Error 2 make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/astsrc/zaptel' make: *** [all] Error 2 As I'm not a kernel programer, any idea what this might mean? Anyone else do this, and maybe I missed it in the archives? Thanks, -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

nodes3 server is back up
by Jim Duuuude 14 Dec '13

14 Dec '13

Once the new DNS entry for this propagates through the "system" (whatever *that* is :-) ), and the "dust" settles, the nodes3.allstarlink.org server should be available for use. It is currently up and running now. Jim WB6NIL

1 0

Node filtering
by Ross Johnson 14 Dec '13

14 Dec '13

Hello Group, I was wondering if it was possible to only allow specific nodes to connect to a remote base node??? Thanks Guys, Ross www.kc7rjk.net

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 58, Issue 41
by zeppelin.1＠netzero.com 13 Dec '13

13 Dec '13

Hello to all; #hwclock --show #hwclock --set --date="2013-12-13 09:20:00" --localtime #hwclock --sysohc Hope it helps. 73 Anton/kc2rqr node 29103 ---------- Original Message ---------- From: app_rpt-users-request(a)ohnosec.org To: app_rpt-users(a)ohnosec.org Subject: App_rpt-users Digest, Vol 58, Issue 41 Date: Thu, 12 Dec 2013 22:26:05 -0500 Send App_rpt-users mailing list submissions to app_rpt-users(a)ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)ohnosec.org You can reach the person managing the list at app_rpt-users-owner(a)ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. Re: Time 6 hours fast (Lu Vencl) 2. Re: Time 6 hours fast (Robert A. Poff) 3. Re: Time 6 hours fast (mike(a)midnighteng.com) 4. Re: Time 6 hours fast (Doug Crompton) 5. Re: Time 6 hours fast (Paul J. Agamata) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Dec 2013 19:32:16 -0500 From: Lu Vencl <vencl(a)att.net> To: Harry Romano <hromano(a)earthlink.net> Cc: "<app_rpt-users(a)ohnosec.org>" <app_rpt-users(a)ohnosec.org> Subject: Re: [App_rpt-users] Time 6 hours fast Message-ID: <10D381CC-ABD9-4003-A596-DA4A22EA3D3D(a)att.net> Content-Type: text/plain; charset="us-ascii" Did you check the time in your BIOS? Do that first if you have not already. I seem to recall this issue in one of my ACiD boxes and I think that was the underlying issue. However someone else may reply with additional information that I don't recall. In the back of my head I seem to recall that there was a setting you need change in one of the files as well but I just don't recall. Sent from my iPhone, Lu Vencl > On Dec 12, 2013, at 5:46 PM, "Harry Romano" <hromano(a)earthlink.net> wrote: > > Hello all, > I have a really weird issue. Beside me personally ,When I press *81 to have allstar say the time Its says the time but 6 hours later so if its 12 midnight it says 6 am . When I key in the date command to allstar from the terminal It gives me the correct date and time month day and est. The minutes are always correct. So I the time is 12:30 midnight it will say 6:30 am . I also was shown how to use the crontab and that works just fine . So why does the time say its 6 hour later. Can anyone help with this issue please!!! > > 73 > > Harry KC4RPP > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Re: [App_rpt-users] Question
by Ross Johnson 13 Dec '13

13 Dec '13

Hello group, Any progress with this issue I'm having the same problem. Ross www.kc7rjk.com Sent from my Verizon Wireless 4G LTE DROID Larry <n3vsi1(a)verizon.net> wrote: >_______________________________________________ >App_rpt-users mailing list >App_rpt-users(a)ohnosec.org >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

2 1

Re: [App_rpt-users] Time 6 hours fast
by mike＠midnighteng.com 13 Dec '13

13 Dec '13

4 3

Re: [App_rpt-users] Time 6 hours fast
by mike＠midnighteng.com 13 Dec '13

13 Dec '13

3 2

cop, Foreign Link Local Output Path ???
by Chuck Henderson 13 Dec '13

13 Dec '13

Does anyone know what these are expected to do? cop,36 ; Foreign Link Local Output Path Enable cop,37 ; Foreign Link Local Output Path Disable cop,38 ; Foreign Link Local Output Path Follows Local Telemetry cop,39 ; Foreign Link Local Output Path on Demand When I try to do these absolutely nothing happens. >From looking at the source file I see that the following line is what stops the case statement from doing anything. if (!mylink) return DC_ERROR; My expectation was that these would let me avoid connects to connected nodes from being announced on my system, while still allowing connects to my node to be announced on my system. Obviously that isn't what these do so what are they there for and why don't they do anything? Chuck Henderson, CCIE2285, WB9UUS Midlands Networking, Inc.

1 0

Time 6 hours fast
by Harry Romano 13 Dec '13

13 Dec '13

Hello all, I have a really weird issue. Beside me personally ,When I press *81 to have allstar say the time Its says the time but 6 hours later so if its 12 midnight it says 6 am . When I key in the date command to allstar from the terminal It gives me the correct date and time month day and est. The minutes are always correct. So I the time is 12:30 midnight it will say 6:30 am . I also was shown how to use the crontab and that works just fine . So why does the time say its 6 hour later. Can anyone help with this issue please!!! 73 Harry KC4RPP

3 2

Node connection issue
by Serge Bérubé 12 Dec '13

12 Dec '13

Node connection issue : I have an issue connecting 2 private nodes all together... I previously did this with 10 nodes with great success and working for months perfectly. The way I proceeded is fresh instals and I used the very same password at the installation time on all the machines , same for iaxrpt access same for machine access, basic setup with a usb fob and a repeater connected , I enter the nodes in rpt.conf , I comment the correct file for no registration on allstarlink, since those machines are part of a private network, etc. In fact all is correct ! the only difference now is that I want to connect a node that has been built the same , but the password given at the end of the installation different than mine. I checked everything and went to conclusion that this probably the offending action... This situation is on a local net , in the lab , and also is the same if the nodes are on internet. May someone help me ? It will be very appreciated, since this happens in the lab while I am teaching 16 students to configure a small network of Xelatec radio servers I was to forget to tell that we use the ISO downloaded from xelatec site with the current version and this is a non profit task I do to promote Ham radio to my students in Radio-Communications course. Best regards, Serge Berube ve2abc

1 0