October 2010 - App_rpt-users - lists.keekles.org

NodeShark v0.93 available
by Keith Williamson 05 Oct '10

05 Oct '10

All, I just uploaded v0.93 of NodeShark which fixes a "Nil object exception" that crashes the app if the user specifies an invalid path to the local copy of the archive in his NodeShark preferences. You can download this latest version at http://www.arizuni.com/NodeShark 73's, Keith KF7DRV AllStar: 2541 Echolink: 477448

1 0

Audio connectivity files
by Keith 04 Oct '10

04 Oct '10

Good morning all, The locals who use my node have noticed that when connecting to the IRLP nodes they no longer get the individual audio files that each node has in particular the older hams who are confused with numbers but remember the connection audio files. To try and keep the old boys happy is there a way in downloading a batch off my regular weekly connections so they again here what they use to hear please? Many thanks Keith G7DNT Sent from my Ipod

1 0

Network Configuration
by Darril Holland 04 Oct '10

04 Oct '10

When I go to Allstar.org then -Server-Server config-Network config.I have Hostname(groves1) UDP port(4569) Type(DHCP) I have IP address & Netmask from what is on the ACID(linux machine) Where do I find or set up the Gateway,DNS1,DNS2 info?Iam using a Linksys BEFSR81 router. Darril/WD5GJP

1 0

Reverse autopatch / Bad router
by Neil Addis (WA5JXY) 03 Oct '10

03 Oct '10

My reverse autopatch is now working. Thanks to Jim who discover I had a bad router! (Never, ever, ever, ever buy a cheap router made by "ENCORE", and honestly, just never buy a cheap router made by anybody!). I am now registering as 4569 not 60001 ! I threw the Encore in the bit bucket.... THANKS JIM !! U the Man! Neil

1 0

Still Lost, and still running around in circles
by Darril Holland 03 Oct '10

03 Oct '10

After successful load of ACID ,I get to groves1 login(my server name) I was told by Steve(WA6ZFT) to use my Allstarlink.org login info(call sign & password) I get login incorrect.I can type in on groves1 root& then my Unix password and get a command line promt. Darril/WD5GJP

2 1

Re: [App_rpt-users] NodeShark archive utility now available for download
by Doug Hutchison 03 Oct '10

03 Oct '10

TU D On 03/10/2010 20:47:44, Keith Williamson (hkwilliamson(a)gmail.com) wrote: > On Sun, Oct 3, 2010 at 12:40 PM, Doug Hutchison > <specialq.que(a)ntlworld.com>wrote: > > > ? requirements to set up archivedir? > > > > Doug > > > > > > On 03/10/2010 20:33:08, Keith Williamson (hkwilliamson(a)gmail.com) wrote: > > > Hello fellow node ops, > > > > > > The first version of NodeShark (v.0.92) is now available for download. > > It > > > hasn't been tested extensively but appears to be in good enough shape to > > > distribute more widely and have real users provide feedback. > > > > > > NodeShark is a simple Windows utility that allows the AllStar node > > operator > > > to filter through and analyze the logfiles generated by app_rpt and > > > find/playback the associated transmission recordings. Of course, for > > this to > > > be useful, you must have the "archivedir" directive enabled in > > rpt.conf. If > > > you already have "archivedir" enabled, you can start using NodeShark > > after > > > "sync"ing your archivedir directory with the Windows system you run > > > NodeShark on. NodeShark provides a built-in facility (in conjunction > > with > > > PuTTY) to keep your archived files synced up with a local copy on your > > > Windows system. > > > > > > NodeShark is free and available for download at: > > > > > > http://www.arizuni.com/NodeShark/ > > > > > > Many thanks to Jim Duuude for testing and finding bugs with the first > > couple > > > of versions! Jim also sent me a zip of an archive directory that had > > some > > > log record types I hadn't come across and was more typical of a > > high-traffic > > > node (unlike my little link node). > > > > > > 73's, > > > > > > Keith > >

1 0

Re: [App_rpt-users] NodeShark archive utility now available for download
by Doug Hutchison 03 Oct '10

03 Oct '10

? requirements to set up archivedir? Doug On 03/10/2010 20:33:08, Keith Williamson (hkwilliamson(a)gmail.com) wrote: > Hello fellow node ops, > > The first version of NodeShark (v.0.92) is now available for download. It > hasn't been tested extensively but appears to be in good enough shape to > distribute more widely and have real users provide feedback. > > NodeShark is a simple Windows utility that allows the AllStar node operator > to filter through and analyze the logfiles generated by app_rpt and > find/playback the associated transmission recordings. Of course, for this to > be useful, you must have the "archivedir" directive enabled in rpt.conf. If > you already have "archivedir" enabled, you can start using NodeShark after > "sync"ing your archivedir directory with the Windows system you run > NodeShark on. NodeShark provides a built-in facility (in conjunction with > PuTTY) to keep your archived files synced up with a local copy on your > Windows system. > > NodeShark is free and available for download at: > > http://www.arizuni.com/NodeShark/ > > Many thanks to Jim Duuude for testing and finding bugs with the first couple > of versions! Jim also sent me a zip of an archive directory that had some > log record types I hadn't come across and was more typical of a high-traffic > node (unlike my little link node). > > 73's, > > Keith > > KF7DRV > AllStar: 2541 > Echolink: 477448

2 1

NodeShark archive utility now available for download
by Keith Williamson 03 Oct '10

03 Oct '10

Hello fellow node ops, The first version of NodeShark (v.0.92) is now available for download. It hasn't been tested extensively but appears to be in good enough shape to distribute more widely and have real users provide feedback. NodeShark is a simple Windows utility that allows the AllStar node operator to filter through and analyze the logfiles generated by app_rpt and find/playback the associated transmission recordings. Of course, for this to be useful, you must have the "archivedir" directive enabled in rpt.conf. If you already have "archivedir" enabled, you can start using NodeShark after "sync"ing your archivedir directory with the Windows system you run NodeShark on. NodeShark provides a built-in facility (in conjunction with PuTTY) to keep your archived files synced up with a local copy on your Windows system. NodeShark is free and available for download at: http://www.arizuni.com/NodeShark/ Many thanks to Jim Duuude for testing and finding bugs with the first couple of versions! Jim also sent me a zip of an archive directory that had some log record types I hadn't come across and was more typical of a high-traffic node (unlike my little link node). 73's, Keith KF7DRV AllStar: 2541 Echolink: 477448

1 0

Re: [App_rpt-users] Changing Node Numbers
by Jim Duuuude 03 Oct '10

03 Oct '10

You didnt change the IAX2 port number in the portal. It really needs to know the accurate info. Look at the Server under the Network Configuration Tab. Change the UDP port to whatever you made it. This will help immensely. JIM > From: david.osborn(a)manx.net > To: app_rpt-users(a)qrvc.com > Date: Sun, 3 Oct 2010 13:09:02 +0100 > Subject: [App_rpt-users] Changing Node Numbers > > Hi, > > I have just followed Jim's instructions to change a node's port number. > > 1. Visit the portal and change the number there. > 2. Edited IAX.Conf and restarted. > > This is a test node that is co-sited with node 2481 on port 4569 - hence the > need for another port. > > When I attempted to connect to the node (2484) from the web transceiver, the > call failed. Looking at the console for 2484 showed no incoming activity, it > turned out that the call was being directed to node 2481 on port 4569; the > Web Transceiver was using the old port number. > > I attempted to connect to 2484 from another node and that also failed. It > transpired that rpt_extnodes had now got two entries for 2484. Here's an > extract from the file: > > 2480=radio@87.254.94.29:4568/2480,87.254.94.29 > 2481=radio@89.107.6.110:4569/2481,89.107.6.110 > 2482=radio@87.254.94.29:4569/2482,87.254.94.29 > 2483=radio@217.28.14.128:4569/2483,217.28.14.128 > 2484=radio@89.107.6.110:4569/2484,89.107.6.110 > 2484=radio@89.107.6.110:4568/2484,89.107.6.110 > 2490=radio@68.227.84.117:4569/2490,68.227.84.117 > > This extract was taken more than an hour after making the portal changes. > > Is this a problem with the node list updates, or have I missed something? > > Incidentally, I manually corrected the list and the call succeeded straight > off the bat. > > Another, somewhat unrelated thing.... > > I instructed the portal to download the configuration to the server - it > didn't! What am I missing here? I have run the scripts on the support page, > which did the first-time download, but nothing since. > > David > GD4HOZ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)qrvc.com > http://qrvc.com/mailman/listinfo/app_rpt-users

2 1

Changing Node Numbers
by David Osborn 03 Oct '10

03 Oct '10

Hi, I have just followed Jim's instructions to change a node's port number. 1. Visit the portal and change the number there. 2. Edited IAX.Conf and restarted. This is a test node that is co-sited with node 2481 on port 4569 - hence the need for another port. When I attempted to connect to the node (2484) from the web transceiver, the call failed. Looking at the console for 2484 showed no incoming activity, it turned out that the call was being directed to node 2481 on port 4569; the Web Transceiver was using the old port number. I attempted to connect to 2484 from another node and that also failed. It transpired that rpt_extnodes had now got two entries for 2484. Here's an extract from the file: 2480=radio@87.254.94.29:4568/2480,87.254.94.29 2481=radio@89.107.6.110:4569/2481,89.107.6.110 2482=radio@87.254.94.29:4569/2482,87.254.94.29 2483=radio@217.28.14.128:4569/2483,217.28.14.128 2484=radio@89.107.6.110:4569/2484,89.107.6.110 2484=radio@89.107.6.110:4568/2484,89.107.6.110 2490=radio@68.227.84.117:4569/2490,68.227.84.117 This extract was taken more than an hour after making the portal changes. Is this a problem with the node list updates, or have I missed something? Incidentally, I manually corrected the list and the call succeeded straight off the bat. Another, somewhat unrelated thing.... I instructed the portal to download the configuration to the server - it didn't! What am I missing here? I have run the scripts on the support page, which did the first-time download, but nothing since. David GD4HOZ

1 0