- App_rpt-users - lists.keekles.org

Discontinuance of IRLP support
by Jim Duuuude 22 Oct '10

22 Oct '10

Per request of Dave Cameron, VE7LTD, support and functionality for IRLP connectivity is officially dropped from the app_rpt project. It is being removed from the SVN today, and will no longer be present in any further releases. If you have IRLP configured on your system, PLEASE REMOVE IT! Do NOT make any further connections into the IRLP network from an Allstar Link node (or anything else running app_rpt), as that is now officially against the rules on their network. Thank you for your cooperation. JIM WB6NIL

3 2

urb0
by Darril Holland 22 Oct '10

22 Oct '10

On linux console keep getting " cannot submit datapipe for urb0, error-22 internal error. What could be causing this? Darril/WD5GJP

4 4

Re: [App_rpt-users] Re Chan_IRLP updates
by Jon Rorke 21 Oct '10

21 Oct '10

Ok I will stop barking about this and await the solution. I will have a look at my node tonight. Jon > Hi, > > I *think* I got it sorted out. The change was to the statupdate script. > > Check for /home/irlp/update-files/scripts/statupdate and copy it to /home/irlp/scripts . > > Then, you may need to edit the file to add the wget variable. You can either change $WGET to /usr/bin/wget or add this line after the line to source common functions: > WGET=/usr/bin/wget > > > It seems to have run. Hopefully this means my node is now correctly updated. > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > On Oct 21, 2010, at 3:23 PM, Jon Rorke wrote: > >> See attached info. The updates seem to affect the status server reporting. >> Does anybody know which script(s) this affects? >> >> Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C. >> >> Jon VA3RQ >> >> >>> All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly. >>> >>> The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis. >>> >>> If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system. >>> >>> Dave Cameron >>> VE7LTD >>> >>> --- Inirlp(a)yahoogroups.com, Buddy Brannan<buddy@...> wrote: >>>> So, what's the new URL, and where is it updated? >>>> -- >>>> Buddy Brannan, KB5ELV - Erie, PA >>>> Phone: (814) 860-3194 or 888-75-BUDDY >>>> >>>> >>>> >>>> On Oct 21, 2010, at 11:19 AM, ve7ltd wrote: >>>> >>>>> Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night. >>>>> >>>>> These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention. >>>>> >>>>> 1160 >>>>> 1250 >>>>> 1840 >>>>> 1882 >>>>> 2015 >>>>> 2020 >>>>> 2154 >>>>> 2184 >>>>> 2270 >>>>> 2304 >>>>> 2365 >>>>> 2414 >>>>> 2509 >>>>> 2537 >>>>> 2590 >>>>> 2600 >>>>> 2651 >>>>> 2736 >>>>> 2739 >>>>> 2882 >>>>> 2949 >>>>> 3018 >>>>> 3029 >>>>> 3059 >>>>> 3066 >>>>> 3075 >>>>> 3078 >>>>> 3088 >>>>> 3098 >>>>> 3102 >>>>> 3145 >>>>> 3152 >>>>> 3158 >>>>> 3170 >>>>> 3174 >>>>> 3192 >>>>> 3212 >>>>> 3225 >>>>> 3299 >>>>> 3330 >>>>> 3337 >>>>> 3396 >>>>> 3402 >>>>> 3415 >>>>> 3418 >>>>> 3440 >>>>> 3486 >>>>> 3500 >>>>> 3517 >>>>> 3530 >>>>> 3539 >>>>> 3629 >>>>> 3659 >>>>> 3667 >>>>> 3696 >>>>> 3727 >>>>> 3734 >>>>> 3744 >>>>> 3753 >>>>> 3759 >>>>> 3765 >>>>> 3767 >>>>> 3778 >>>>> 3793 >>>>> 3795 >>>>> 3826 >>>>> 3829 >>>>> 3865 >>>>> 3913 >>>>> 3917 >>>>> 3924 >>>>> 3927 >>>>> 3932 >>>>> 3962 >>>>> 3967 >>>>> 3969 >>>>> 3971 >>>>> 3976 >>>>> 3986 >>>>> 3994 >>>>> 4067 >>>>> 4068 >>>>> 4076 >>>>> 4077 >>>>> 4100 >>>>> 4103 >>>>> 4134 >>>>> 4147 >>>>> 4170 >>>>> 4200 >>>>> 4204 >>>>> 4280 >>>>> 4410 >>>>> 4467 >>>>> 4486 >>>>> 4494 >>>>> 4503 >>>>> 4529 >>>>> 4563 >>>>> 4606 >>>>> 4610 >>>>> 4650 >>>>> 4661 >>>>> 4671 >>>>> 4715 >>>>> 4722 >>>>> 4765 >>>>> 4777 >>>>> 4802 >>>>> 4835 >>>>> 4881 >>>>> 4922 >>>>> 4952 >>>>> 4967 >>>>> 5056 >>>>> 5070 >>>>> 5361 >>>>> 5429 >>>>> 5444 >>>>> 5466 >>>>> 5468 >>>>> 5503 >>>>> 5515 >>>>> 5588 >>>>> 5612 >>>>> 5660 >>>>> 5690 >>>>> 5717 >>>>> 5720 >>>>> 5776 >>>>> 5961 >>>>> 6122 >>>>> 6796 >>>>> 7001 >>>>> 7010 >>>>> 7011 >>>>> 7012 >>>>> 7013 >>>>> 7014 >>>>> 7015 >>>>> 7016 >>>>> 7018 >>>>> 7019 >>>>> 7020 >>>>> 7058 >>>>> 7149 >>>>> 7192 >>>>> 7550 >>>>> 7580 >>>>> 7661 >>>>> 7671 >>>>> 7689 >>>>> 7697 >>>>> 7718 >>>>> 7731 >>>>> 7820 >>>>> 7841 >>>>> 8038 >>>>> 8066 >>>>> 8190 >>>>> 8289 >>>>> 8322 >>>>> 8327 >>>>> 8365 >>>>> 8380 >>>>> 8484 >>>>> 8562 >>>>> 8720 >>>>> 8937 >> >> >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)qrvc.com >> http://qrvc.com/mailman/listinfo/app_rpt-users >

1 0

Re Chan_IRLP updates
by Jon Rorke 21 Oct '10

21 Oct '10

See attached info. The updates seem to affect the status server reporting. Does anybody know which script(s) this affects? Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C. Jon VA3RQ > All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly. > > The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis. > > If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system. > > Dave Cameron > VE7LTD > > --- Inirlp(a)yahoogroups.com, Buddy Brannan<buddy@...> wrote: > > > > So, what's the new URL, and where is it updated? > > -- > > Buddy Brannan, KB5ELV - Erie, PA > > Phone: (814) 860-3194 or 888-75-BUDDY > > > > > > > > On Oct 21, 2010, at 11:19 AM, ve7ltd wrote: > > > > > Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night. > > > > > > These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention. > > > > > > 1160 > > > 1250 > > > 1840 > > > 1882 > > > 2015 > > > 2020 > > > 2154 > > > 2184 > > > 2270 > > > 2304 > > > 2365 > > > 2414 > > > 2509 > > > 2537 > > > 2590 > > > 2600 > > > 2651 > > > 2736 > > > 2739 > > > 2882 > > > 2949 > > > 3018 > > > 3029 > > > 3059 > > > 3066 > > > 3075 > > > 3078 > > > 3088 > > > 3098 > > > 3102 > > > 3145 > > > 3152 > > > 3158 > > > 3170 > > > 3174 > > > 3192 > > > 3212 > > > 3225 > > > 3299 > > > 3330 > > > 3337 > > > 3396 > > > 3402 > > > 3415 > > > 3418 > > > 3440 > > > 3486 > > > 3500 > > > 3517 > > > 3530 > > > 3539 > > > 3629 > > > 3659 > > > 3667 > > > 3696 > > > 3727 > > > 3734 > > > 3744 > > > 3753 > > > 3759 > > > 3765 > > > 3767 > > > 3778 > > > 3793 > > > 3795 > > > 3826 > > > 3829 > > > 3865 > > > 3913 > > > 3917 > > > 3924 > > > 3927 > > > 3932 > > > 3962 > > > 3967 > > > 3969 > > > 3971 > > > 3976 > > > 3986 > > > 3994 > > > 4067 > > > 4068 > > > 4076 > > > 4077 > > > 4100 > > > 4103 > > > 4134 > > > 4147 > > > 4170 > > > 4200 > > > 4204 > > > 4280 > > > 4410 > > > 4467 > > > 4486 > > > 4494 > > > 4503 > > > 4529 > > > 4563 > > > 4606 > > > 4610 > > > 4650 > > > 4661 > > > 4671 > > > 4715 > > > 4722 > > > 4765 > > > 4777 > > > 4802 > > > 4835 > > > 4881 > > > 4922 > > > 4952 > > > 4967 > > > 5056 > > > 5070 > > > 5361 > > > 5429 > > > 5444 > > > 5466 > > > 5468 > > > 5503 > > > 5515 > > > 5588 > > > 5612 > > > 5660 > > > 5690 > > > 5717 > > > 5720 > > > 5776 > > > 5961 > > > 6122 > > > 6796 > > > 7001 > > > 7010 > > > 7011 > > > 7012 > > > 7013 > > > 7014 > > > 7015 > > > 7016 > > > 7018 > > > 7019 > > > 7020 > > > 7058 > > > 7149 > > > 7192 > > > 7550 > > > 7580 > > > 7661 > > > 7671 > > > 7689 > > > 7697 > > > 7718 > > > 7731 > > > 7820 > > > 7841 > > > 8038 > > > 8066 > > > 8190 > > > 8289 > > > 8322 > > > 8327 > > > 8365 > > > 8380 > > > 8484 > > > 8562 > > > 8720 > > > 8937

2 1

chan_echolink improvements
by Jim Duuuude 21 Oct '10

21 Oct '10

I have made some major improvements to chan_echolink: 1. There were many problems stemming from use of the astdb for the echolink station entries. This has now been replaced with in-memory functionality. This included the /var/lib/asterisk/astdb file growing so large that the astdb didnt even work any more, and EXTREME slowness on writing to the database on ext4 filesystems. 2. There was a string buffer overflow problem if the connecting IP address had 3 digits in all 4 octets (e.g. 123.123.123.123). This caused intermittent (and in some cases consistent) failures in inbound connection authorization. 3. If an inbound connection is not recognized, it requests the latest info from the directory server, and lets the client automatically re-try the connection again (presumably after the download containing the clients information is completed) thus allowing the client to connect on the retry. 4. chan_echolink now has a couple of CLI commands: 'echolink debug level', 'echolink dbdump' and 'echolink dbget'. The latest versions of chan_echolink.c and app_rpt.c from SVN implement this. If you are going to upgrade, you *MUST* upgrade both chan_echolink *AND* app_rpt, since the interface between app_rpt and the chan_echolink database completely changed. Please let me know how it goes. If you find problems, let me know. Thanks. JIM WB6NIL

2 1

USB GPIO and Event handling
by Jim Duuuude 21 Oct '10

21 Oct '10

Is everyone that requested support of GPIO and/or event handling satisfied with the current state of the implementation?? Can this issue be 'put to bed'? Are there any more pending things to be concerned with in this realm currently?? If there is nothing else, I will duplicate the GPIO handling that was added into chan_usbradio into chan_simpleusb and basically consider it done for now. JIM WB6NIL

2 2

IRLP nodes not updating and may stop working
by Jon Rorke 20 Oct '10

20 Oct '10

According to the IRLP folks there has been a recent update. Seems that some nodes didn't take the update. I see that all my Chan-IRLP nodes are on the list of nodes that aren't updated correctly. I also see other know chan_IRLP nodes are also on the list. Dave Cameron is saying that the nodes will stop if the updates aren't done Perhaps the chan_IRLP group could look at the updates and see if they need to be modified for chan_IRLP? Or will it be ok to go an update with out any issues? I know some scripts were modified and are not updated for that reason. The list of nodes flagged can be found on the IRLP yahoo group. Jon VA3RQ > There was recently an update to the scheduled events and the status update system. There are a number of nodes that have not updated correctly. This is quite a long list, organized by node number. On these nodes, you have to make sure that they are receiving updates correctly. > > Your node also may be on this list because you stay connected for long periods of time to a reflector, for days and days on end. If that is the case, just disconnect and allow the update to proceed. > > You can manually try an update and look for errors by logging in as root, and trying the following commands: > > su - repeater > /home/irlp/scripts/update files > > If you can not solve the problem, please start a ticket withinstalls(a)irlp.net. Provide your node number, a description of the problem, your login info (root or repeater user password), and what port your node listens to SSH on (default 22). > > Dave Cameron > VE7LTD

1 0

Source Code
by Neil Addis (WA5JXY) 20 Oct '10

20 Oct '10

struct by_lightning Most excellent, Duuuuude.......... Neil

2 1

Re: [App_rpt-users] Confirmation of disconnection, DTMF function lists
by Chuck Kraly 19 Oct '10

19 Oct '10

http://app-rpt.qrvc.com/node/21 Sorry, I thought you were requesting info on individual nodes. The link above shows the basic DTMF functions..... Chuck K0XM byrg.net On Tue, Oct 19, 2010 at 9:51 AM, Dale Weber <n7pkt(a)hybotics.org> wrote: > On Tuesday, October 19, 2010 05:54:39 am you wrote: > > > As for the DMTF command list. I for one do NOT want the DMTF codes > > available to ANYONE especially those not registered. It is a security > > issue, plain and simple. There are functions that each repeater owner > > implements, and you do NOT need access to alot of it. > > I'm not running a repeater - just a simplex node. I don't think > the > functions that are available to regular users constitute a security risk. > :) > > > You want to publish > > your commands, good for you, but being in the rptr building biz since the > > late 70's I have learned that there are "players" out there and they do > > not need toys to have access to. > > I don't see how the basic AllStar DTMF functions being available to > users > would be a problem. Please explain what the issue might be, so I can > understand your response better. > > 8-Dale > -- > I can handle complexity. It's the simple things that confound me. > Open your mind, Read, Learn, Think, Apply. 73, from N7PKT! > http://www.hybotics.com - NEW main site > http://www.hybotics.info - Blog >

2 1

e/l un-authorized
by Ken 19 Oct '10

19 Oct '10

my node seems to have stopped accepting echo link connects - giving the un -authorized message, no matter how long the e/l station as been logged onto the network The message that appears on the console is: [Oct 18 12:51:24] ERROR[2620]: chan_echolink.c:2185 do_new_call: Cannot find DB entry for a/ipaddr/77.43.22.231 I note that astdb is about 17.4 MB in size - is this reasonable? If not, is there a way to shrink/reset safely? Ken

6 9