June 2016 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] make uridiag to test URIx in Dial
by kk6ecm 01 Jun '16

01 Jun '16

Follow-up: Testing using other means (listening to audio out), the URIx seems to be working, at least as an output. Not sure why uridiag is showing errors. Thanks, Bob k6ecm -----Original Message----- From: kk6ecm [mailto:kk6ecm@gmail.com] Sent: Wednesday, June 01, 2016 6:32 AM To: 'app_rpt-users(a)ohnosec.org' Subject: RE: [App_rpt-users] make uridiag to test URIx in Dial Thanks. Now that works, but I'm failing known good URIx analog (out of range). I know the blind plug works (2, 1 each for URI and URIx). This is the first time I've run this on a RPi2 with DIAL. I had this happen under ACID (CentOS 5.10) with hardware that was not quite compatible. Guess I'm questioning this build of uridiag on DIAL and RPi. Thoughts? Thanks, Bob k6ecm Menu: For Left Channel: 1 - 1004Hz, 2 - 204Hz, 3 - 300Hz, 4 - 404Hz, 5 - 502Hz 6 - 1502Hz, 7 - 2004Hz, 8 - 3004Hz, 9 - 5004Hz For Right Channel: 11 - 1004Hz, 22 - 204Hz, 33 - 300Hz, 44 - 404Hz, 55 - 502Hz 66 - 1502Hz, 77 - 2004Hz, 88 - 3004Hz, 99 - 5004Hz Tests, etc. t - test normal operation (use uppercase 'T' for verbose output) i - test digital signals only (COR,TONE,PTT,GPIO) e - test EEPROM, E - Initialize EEPROM l - list EEPROM contents c - show test (loopback) connector pinout q,x - exit program Enter your selection:t Testing digital I/O (PTT,COR,TONE and GPIO).... Digital I/O passed!! Testing Analog at 204 (and 700) Hz... Analog level on left channel for 204.0 Hz (270.9) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 700.0 Hz (295.9) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 504 (and 700) Hz... Analog level on left channel for 504.0 Hz (285.7) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 700.0 Hz (267.7) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 1004 (and 700) Hz... Analog level on left channel for 1004.0 Hz (263.4) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 700.0 Hz (290.4) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 2004 (and 700) Hz... Analog level on left channel for 2004.0 Hz (277.2) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 700.0 Hz (285.4) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 3004 (and 700) Hz... Analog level on left channel for 3004.0 Hz (266.4) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 700.0 Hz (285.2) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 5004 (and 700) Hz... Analog level on left channel for 5004.0 Hz (53.3) is out of range!! Must be between 93.6 and 140.4 Analog level on right channel for 700.0 Hz (284.9) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 204) Hz... Analog level on left channel for 700.0 Hz (282.8) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 204.0 Hz (271.6) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 504) Hz... Analog level on left channel for 700.0 Hz (307.0) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 504.0 Hz (275.8) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 1004) Hz... Analog level on left channel for 700.0 Hz (291.4) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 1004.0 Hz (263.4) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 2004) Hz... Analog level on left channel for 700.0 Hz (287.0) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 2004.0 Hz (272.2) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 3004) Hz... Analog level on left channel for 700.0 Hz (286.0) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 3004.0 Hz (265.0) is out of range!! Must be between 440.0 and 660.0 Testing Analog at 700 (and 5004) Hz... Analog level on left channel for 700.0 Hz (286.9) is out of range!! Must be between 440.0 and 660.0 Analog level on right channel for 5004.0 Hz (52.8) is out of range!! Must be between 93.6 and 140.4 24 Error(s) found during test(s)!!!! -----Original Message----- From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Steve Zingman Sent: Wednesday, June 01, 2016 3:39 AM To: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] make uridiag to test URIx in Dial Bob, The version of uridiag on the svn is correct svn co http://svn.ohnosec.org/svn/projects/allstar/uridiag/trunk uridiag cd uridiag make make install 73, Steve N4IRS On 06/01/2016 05:27 AM, kk6ecm wrote: >> Ive included three things, contents of the folder containing uridiag files, a listing of Makefile, and the make install results. > root@K6ECM-2:/trunk_uri# ls > fftsg.c Makefile uridiag.c > root@K6ECM-2:/trunk_uri# cat Makefile > > CFLAGS=-Wall > > all: uridiag > > install: all > install -m 755 uridiag /usr/bin/uridiag > > uridiag: uridiag.c fftsg.c > cc -Wall uridiag.c fftsg.c -o uridiag -lusb -lasound -lm > > > root@K6ECM-2:/trunk_uri# make install > cc -Wall uridiag.c fftsg.c -o uridiag -lusb -lasound -lm > /usr/bin/ld: /tmp/cc1hh6L8.o: undefined reference to symbol 'pthread_join@@GLIBC_2.4' > //lib/arm-linux-gnueabihf/libpthread.so.0: error adding symbols: DSO missing from command line > collect2: error: ld returned 1 exit status > Makefile:10: recipe for target 'uridiag' failed > make: *** [uridiag] Error 1 > root@K6ECM-2:/trunk_uri# > > > thanks, > Bob > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

1 0

make uridiag to test URIx in Dial
by kk6ecm 01 Jun '16

01 Jun '16

Bob here showing my Debian ignorance. I'd like to test a URIx in DIAL on a RPi, but receive an error 1 when attempting to "make" the file. Is it incompatible, or am I doing something wrong? Thanks, Bob k6ecm 73

4 5

Re: [App_rpt-users] Node list problem on node 29997
by Jeremy Lincicome 01 Jun '16

01 Jun '16

After doing some research, I think the problem is being caused by the ISP. 29997 seams to be the only node having the issue. I think there might be a routing issue with Forethought. I'll contact Forethought tomorrow and see what they say. However, I think it's weird that I'm only seeing the issue on allstarlink.org and register.allstarlink.org. On 05/30/2016 06:27 AM, Mark Johnston wrote: > If you have a way to change you public IP, if it isn't static/fixed - > could be as simple as changing the MAC of the WAN side on the router > (assuming it has a pub IP) , hopefully after a refresh/reboot get a > new IP, if it's banned at the server side then that would show it... > > > > "Got Root?" > > How many software engineers does it take to change a light bulb? > *None. It's a hardware problem.* > > > Unix is user friendly. It's just very particular about who it's > friends are. > WINDOWS: Will Install Needless Data On Whole System > MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools > Teenagers. > > > A ntennas > P oorly > P laced > L acks > E ngineering > > The best way to accelerate a computer running Windows is at 9.81 m/s². > > /*_/"I get paid to support Windows, I use Linux to get work done."/_*/ > > > On Mon, May 30, 2016 at 2:10 AM, Jeremy Lincicome <w0jrl1(a)gmail.com > <mailto:w0jrl1@gmail.com>> wrote: > > The traceroute, ping, and nslookup were all run from a laptop on > the same network as the node. I wonder, is something like fail2ban > blocking the node server side? If I run: > wget http://stats.allstarlink.org > I am able to download index.html. I'll try putting the node in the > DMZ and see what happens. > > > On 05/30/2016 02:21 AM, Mark Johnston wrote: >> Is there another computer on this same router/network >> PC/Mac/Linux anything? can it ping/complete a traceroute to >> allstarlink.org <http://allstarlink.org> or the IP either way...? >> if it can, perhaps something with this computer's configuration, >> might try getting a diff internal IP for it... make sure iptables >> and all that are not enabled >> is it practical to bypass the router? as a test. >> >> /etc/hosts.deny is there anything in there etc? >> >> >> >> "Got Root?" >> >> How many software engineers does it take to change a light bulb? >> *None. It's a hardware problem.* >> >> >> Unix is user friendly. It's just very particular about who it's >> friends are. >> WINDOWS: Will Install Needless Data On Whole System >> MICROSOFT: Most Intelligent Customers Realize Our Software Only >> Fools Teenagers. >> >> >> A ntennas >> P oorly >> P laced >> L acks >> E ngineering >> >> The best way to accelerate a computer running Windows is at 9.81 >> m/s². >> >> /*_/"I get paid to support Windows, I use Linux to get work >> done."/_*/ >> >> >> On Sun, May 29, 2016 at 11:16 PM, Jeremy Lincicome >> <w0jrl1(a)gmail.com <mailto:w0jrl1@gmail.com>> wrote: >> >> Loren, >> That script has been on the node since I built it over a year >> ago. Thank you for the suggestion though. DNS is provided by >> the ISP through the router. >> David, >> When I run: >> >> wget http://register.allstarlink.org >> >> The terminal just hangs. I have to kill it with CTRL c. >> However, if I ping google.com <http://google.com>, I get an >> immediate response. >> >> Jeremy W0JRL >> >> >> On 05/29/2016 11:32 PM, David McGough wrote: >> >> Jeremy, >> >> To confirm if your Internet is working and you can get to the >> registration server, try: >> >> wget http://register.allstarlink.org >> >> >> If you get a "401 Authorization Required" error back, you >> can see the >> registration server just fine via TCP. >> >> >> 73, David KB4FXC >> >> >> On Sun, 29 May 2016, Jeremy Lincicome wrote: >> >> Mark, >> Here are the results of nslookup, ping, and traceroute. >> >> nslookup allstarlink.org <http://allstarlink.org> >> Server: 127.0.1.1 >> Address: 127.0.1.1#53 >> >> Non-authoritative answer: >> Name: allstarlink.org <http://allstarlink.org> >> Address: 67.215.233.179 >> >> ping -c4 67.215.233.179 <http://67.215.233.179>: >> PING 67.215.233.179 (67.215.233.179) 56(84) bytes of >> data. >> >> --- 67.215.233.179 ping statistics --- >> 4 packets transmitted, 0 received, 100% packet loss, >> time 3024ms >> >> traceroute 67.215.233.179 >> traceroute to 67.215.233.179 (67.215.233.179), 30 >> hops max, 60 byte packets >> 1 DD-WRT (192.168.55.1) 5.094 ms 22.644 ms >> 22.651 ms >> 2 216-98-194-1.forethought.net >> <http://216-98-194-1.forethought.net> (216.98.194.1) >> 25.671 ms 31.059 ms >> 40.912 ms >> 3 vl203.de01.forethought.net >> <http://vl203.de01.forethought.net> (206.124.21.201) >> 40.914 ms 40.908 ms >> 40.908 ms >> 4 216-241-35-213.static.forethought.net >> <http://216-241-35-213.static.forethought.net> >> (216.241.35.213) 40.904 ms >> 40.897 ms 40.888 ms >> 5 206-124-24-110.static.forethought.net >> <http://206-124-24-110.static.forethought.net> >> (206.124.24.110) 44.864 ms >> 44.866 ms 75.615 ms >> 6 te4-1.cr01.lax.citylinkfiber.net >> <http://te4-1.cr01.lax.citylinkfiber.net> >> (216.243.117.17) 86.184 ms 58.349 >> ms 45.012 ms >> 7 te4-1.cr01.sjc.citylinkfiber.net >> <http://te4-1.cr01.sjc.citylinkfiber.net> >> (216.243.119.129) 59.803 ms >> 59.797 ms 59.789 ms >> 8 * * * >> 9 * * * >> 10 * * * >> 11 * * * >> 12 * * * >> 13 * * * >> 14 * * * >> 15 * * * >> 16 * * * >> 17 * * * >> 18 * * * >> 19 * * * >> 20 * * * >> 21 * * * >> 22 * * * >> 23 * * * >> 24 * * * >> 25 * * * >> 26 * * * >> 27 * * * >> 28 * * * >> 29 * * * >> 30 * * * >> >> Jeremy W0JRL >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> and scroll down to the bottom of the page. Enter your >> email address and press the "Unsubscribe or edit options >> button" >> You do not need a password to unsubscribe, you can do it >> via email confirmation. If you have trouble >> unsubscribing, please send a message to the list >> detailing the problem. >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and >> scroll down to the bottom of the page. Enter your email >> address and press the "Unsubscribe or edit options button" >> You do not need a password to unsubscribe, you can do it via >> email confirmation. If you have trouble unsubscribing, please >> send a message to the list detailing the problem. >> >> > >

1 1