Whenever you have a network of that size someone somewhere should be archiving everything. We do that on our main hub. EVERYTHING is recorded.
...at least what node it came from. That's just it. We know which node from which it came. (Philadelphia area) Where it was in the coverage area of that machine is anyone's guess. (The machine has a HUGE footprint.)
Since this last outbreak, there are plans in the works to clean up the airwaves in the Phila. area, don't worry. ;) Scott Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531 On 8/6/2014 8:46 PM, Doug Crompton wrote:
Whenever you have a network of that size someone somewhere should be archiving everything. Doing that you could look back through the logs and audio and determine who it is or at least what node it came from. It would take some sleuthing but the logs are time stamped down to the second.
*73 Doug WA3DSP http://www.crompton.com/hamradio*
Date: Wed, 6 Aug 2014 10:50:40 -0400 From: n3xcc@repeater-builder.com To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Nodes with Traffic
Skyler,
I can assure you that yesterday's event was a VERY sporadic event. As with any big link system, there are those that try to ruin it for everyone.
The evet has been documented, and we are working to figuring out where this traffic originated. With as many nodes as are normally connected to the WAN hub, it's nearly impossible to figure out which node a 5s transmission came from. I can assure you, we do our best to keep things in order.
As with ANY repeater system, linked or not, sometimes things happen.
Scott - Core Member of the WAN system
Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531
On 8/6/2014 8:21 AM, Skyler Fennell wrote:
Well I'm not connecting to the WAN system again, yesterday someone came in and started just saying bad words and not ID'ing. Not a good thing at all for the wide area repeater here in Denver.
Is allstar developing in other countries? It would be nice if there was a map of all the nodes.
73
Skyler
On Aug 5, 2014, at 10:31 PM, Doug Crompton <doug@crompton.com <mailto:doug@crompton.com>> wrote:
** The biggest problem with a large net like the Alaska Morning Net is that you have stations coming in from IRLP, Echolink, Allstar, Phone, and other means. Some with great audio and some with audio so bad you can hardly understand what they are saying. Even the net controls often have lousy audio or connections. Level is the biggest problem. Lower is better than higher. Digital networks need headroom! There is nothing more grating than clipped audio! If you don't tell someone they have bad audio they may never know. If you tell them it is bad and they don't fix it then it is on them.
*73 Doug WA3DSP http://www.crompton.com/hamradio*
Date: Tue, 5 Aug 2014 09:17:54 -0500 From: ars.w5omr@gmail.com <mailto:ars.w5omr@gmail.com> To: app_rpt-users@ohnosec.org <mailto:app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Nodes with Traffic
On 07/31/2014 07:36 PM, Kirk Just Kirk wrote:
Yes indeed!!! connect to 2560 and get your fill of..... Non stop radio checks..... Audio critics..... Operating critics..... I love myself Coronado Dave...... Comments..... Breaks....... Mouth farts...... REAL Farts...... Burps..... 500 pound women telling you how to operate, that you need to shut up every 20 minutes while they talk all day and night Shorty telling you how to operate/act.... Made up technical standards..... Just ask for a check in hahaha....
This should either burn your transmitter in or UP.......
Please have a bottle of TUMS ready...possibly a bottle of Damn-It-All
Exactly why the 'Alaska Net' sounds appeasing, and even -it- turns my stomach...
You can go there, Skylar, for quantity, but I have a feeling that if you -did- connect there, the Rocky Mountain Repeater Club would tell you to take that crap off of their repeater.
... just saying ...
-Geoff/W5OMR 29655
_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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@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@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.