I sent this a while back but it was bounced for the wrong mail address. I don't see it ever made it to the list. This was re: someone being advised that their app_rpt node is not permitted on the Echolink network.
Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them.
I looked this up recently when I started to talk about IRLP and how they don't want other traffic on their network. Then I looked at their Access Policy: 4. Stations operating in Sysop mode may interconnect EchoLink only with equipment operating on Amateur frequencies. EchoLink does not permit use of the system with other services such as GMRS, FRS, or MARS. For security reasons, it is also not permitted to interconnect EchoLink with other VoIP systems that support direct access from a computer. 10. The "addressing servers" are designed to be accessed by EchoLink software only. For the sake of system security and stability, any other access requires the permission of the server administrator. As a matter of security, in no event should the IP addresses (or Internet hostnames) of logged-in stations be displayed to anyone who is not a validated, logged-in user. 11. Although every effort will be made to apply these policies universally and fairly, the EchoLink Support staff reserves the right to withdraw a station's access privileges at any time, without notice. EchoLink is a privately owned and operated system that has no connection with, and is not governed by, any radio licensing authority. So, I interpret that as that you are not supposed to connect to with asterisk at all anyways, if you read that verbosely, via app_rpt or otherwise. I don't have the history to know if they've made any statement about what app_rpt is doing, but it seems like it's not permitted via their policy only they are less vocal about it than the IRLP folks.
Well, thats bad. But if echolink remove my node from there system It's their Loss,not mine. Some would day that I am arrogant. nope, I just dont care for poeple that wont think more then that.. the more system on their or other networks that can interact together, the best for every one. -----Message d'origine----- From: Pawlowski, Adam Sent: Thursday, March 21, 2013 3:48 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connectivity Issue I sent this a while back but it was bounced for the wrong mail address. I don't see it ever made it to the list. This was re: someone being advised that their app_rpt node is not permitted on the Echolink network.
Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them.
I looked this up recently when I started to talk about IRLP and how they don't want other traffic on their network. Then I looked at their Access Policy: 4. Stations operating in Sysop mode may interconnect EchoLink only with equipment operating on Amateur frequencies. EchoLink does not permit use of the system with other services such as GMRS, FRS, or MARS. For security reasons, it is also not permitted to interconnect EchoLink with other VoIP systems that support direct access from a computer. 10. The "addressing servers" are designed to be accessed by EchoLink software only. For the sake of system security and stability, any other access requires the permission of the server administrator. As a matter of security, in no event should the IP addresses (or Internet hostnames) of logged-in stations be displayed to anyone who is not a validated, logged-in user. 11. Although every effort will be made to apply these policies universally and fairly, the EchoLink Support staff reserves the right to withdraw a station's access privileges at any time, without notice. EchoLink is a privately owned and operated system that has no connection with, and is not governed by, any radio licensing authority. So, I interpret that as that you are not supposed to connect to with asterisk at all anyways, if you read that verbosely, via app_rpt or otherwise. I don't have the history to know if they've made any statement about what app_rpt is doing, but it seems like it's not permitted via their policy only they are less vocal about it than the IRLP folks. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Hmmm.. I have never actually seen this policy before... somewhat disturbing... However, practical experience shows that Echolink seems to be perfectly aware of our interconnections and seems to be perfectly content with what we are doing. So, I guess its okay.... ??? Jim WB6NIL
From: petem001@hotmail.com To: app_rpt-users@ohnosec.org Date: Thu, 21 Mar 2013 15:59:34 -0400 Subject: Re: [App_rpt-users] Echolink Connectivity Issue
Well, thats bad.
But if echolink remove my node from there system It's their Loss,not mine.
Some would day that I am arrogant. nope, I just dont care for poeple that wont think more then that..
the more system on their or other networks that can interact together, the best for every one.
-----Message d'origine----- From: Pawlowski, Adam Sent: Thursday, March 21, 2013 3:48 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connectivity Issue
I sent this a while back but it was bounced for the wrong mail address. I don't see it ever made it to the list.
This was re: someone being advised that their app_rpt node is not permitted on the Echolink network.
Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them.
I looked this up recently when I started to talk about IRLP and how they don't want other traffic on their network. Then I looked at their Access Policy:
4. Stations operating in Sysop mode may interconnect EchoLink only with equipment operating on Amateur frequencies. EchoLink does not permit use of the system with other services such as GMRS, FRS, or MARS. For security reasons, it is also not permitted to interconnect EchoLink with other VoIP systems that support direct access from a computer.
10. The "addressing servers" are designed to be accessed by EchoLink software only. For the sake of system security and stability, any other access requires the permission of the server administrator. As a matter of security, in no event should the IP addresses (or Internet hostnames) of logged-in stations be displayed to anyone who is not a validated, logged-in user.
11. Although every effort will be made to apply these policies universally and fairly, the EchoLink Support staff reserves the right to withdraw a station's access privileges at any time, without notice. EchoLink is a privately owned and operated system that has no connection with, and is not governed by, any radio licensing authority.
So, I interpret that as that you are not supposed to connect to with asterisk at all anyways, if you read that verbosely, via app_rpt or otherwise. I don't have the history to know if they've made any statement about what app_rpt is doing, but it seems like it's not permitted via their policy only they are less vocal about it than the IRLP folks.
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Wait a minute...... I do fully understand WHY Dave Cameron wanted us to all yank IRLP out of our systems, it interfered with his SELLING you a piece of shit PCB for IRLP to the tune of $170/with a FREE node number thrown in for a bonus. (thats my opinion).Thats OK by me....about 85% of the IRLP installations sound like shit anyways. But Echolink should be HAPPY (YAYYYY) that the Allstar crowd is having access to BOTH modes...... Smells like a rumor to me.Everyone else (other than IRLP) has YOU the owner install/set up/operateYOUR hardware. It's only IRLP that makes you wait till THEIR "Install team" can install your software for you. Echolink probably wouldnt care if you ran it on a Proctor-Silex toaster if you can do it....(Jim can do it) Kirk On Thu, Mar 21, 2013 at 10:14 AM, Jim Duuuude <telesistant@hotmail.com>wrote:
Hmmm..
I have never actually seen this policy before... somewhat disturbing...
However, practical experience shows that Echolink seems to be perfectly aware of our interconnections and seems to be perfectly content with what we are doing. So, I guess its okay.... ???
Jim WB6NIL
From: petem001@hotmail.com To: app_rpt-users@ohnosec.org Date: Thu, 21 Mar 2013 15:59:34 -0400 Subject: Re: [App_rpt-users] Echolink Connectivity Issue
Well, thats bad.
But if echolink remove my node from there system It's their Loss,not mine.
Some would day that I am arrogant. nope, I just dont care for poeple that wont think more then that..
the more system on their or other networks that can interact together, the best for every one.
-----Message d'origine----- From: Pawlowski, Adam Sent: Thursday, March 21, 2013 3:48 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connectivity Issue
I sent this a while back but it was bounced for the wrong mail address. I don't see it ever made it to the list.
This was re: someone being advised that their app_rpt node is not permitted on the Echolink network.
Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them.
I looked this up recently when I started to talk about IRLP and how they don't want other traffic on their network. Then I looked at their Access Policy:
4. Stations operating in Sysop mode may interconnect EchoLink only with equipment operating on Amateur frequencies. EchoLink does not permit use of the system with other services such as GMRS, FRS, or MARS. For security reasons, it is also not permitted to interconnect EchoLink with other VoIP systems that support direct access from a computer.
10. The "addressing servers" are designed to be accessed by EchoLink software only. For the sake of system security and stability, any other access requires the permission of the server administrator. As a matter of security, in no event should the IP addresses (or Internet hostnames) of logged-in stations be displayed to anyone who is not a validated, logged-in user.
11. Although every effort will be made to apply these policies universally and fairly, the EchoLink Support staff reserves the right to withdraw a station's access privileges at any time, without notice. EchoLink is a privately owned and operated system that has no connection with, and is not governed by, any radio licensing authority.
So, I interpret that as that you are not supposed to connect to with asterisk at all anyways, if you read that verbosely, via app_rpt or otherwise. I don't have the history to know if they've made any statement about what app_rpt is doing, but it seems like it's not permitted via their policy only they are less vocal about it than the IRLP folks.
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 3/21/13 4:23 PM, Kirk Just Kirk wrote:
Echolink probably wouldnt care if you ran it on a Proctor-Silex toaster if you can do it....(Jim can do it)
OOOH...let's bring back the Internet Coffee Machine...or was that a Coke machine back in the early 90s...:) *73 for a fresh brew on the Keurig? (And start up the "What's New On Mosaic" page again...:)) -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. Sent from my MacBook Pro.
It was a coke machine at CMU.. http://www.cs.cmu.edu/~coke/history_long.txt We *REALLY* need to bring back the "creative" use of FINGER. Jim
Date: Thu, 21 Mar 2013 16:36:15 -0400 From: bdboyle@bdboyle.com To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connectivity Issue
On 3/21/13 4:23 PM, Kirk Just Kirk wrote:
Echolink probably wouldnt care if you ran it on a Proctor-Silex toaster if you can do it....(Jim can do it)
OOOH...let's bring back the Internet Coffee Machine...or was that a Coke machine back in the early 90s...:) *73 for a fresh brew on the Keurig?
(And start up the "What's New On Mosaic" page again...:))
-- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me.
Sent from my MacBook Pro. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 3/21/13 4:40 PM, Jim Duuuude wrote:
It was a coke machine at CMU..
Stand corrected. I'm not perfect...I thought I made a mistake once, but I was wrong...;)
http://www.cs.cmu.edu/~coke/history_long.txt
We *REALLY* need to bring back the "creative" use of FINGER.
I do, all the time, when I drive in NJ...just sayin'... -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. Sent from my MacBook Pro.
Before this goes too far astray, I wrote that posting, and I'll go over the sequence as briefly as possible. For about three years I had a TBD node running at home, very low traffic, mainly as a convenience to me (the reason is unimportant). It was W2DB-L Last October 1 I asked them to allow me an official "Concerence" using this box and the reply I got was that TBD is not permitted on Echolink, and therefore my continued use that was was a violation of...something... I asked that is it were not permitted why is the software available? Their response was really nil. I was tending to my gravely ill mom at the time and never checked again until this past week. I might add that within ten minutes of their October 2nd email saying I was a bad guy I killed TBD and never started it again. Since I started playing allstar with node 2360 I have had W2DB-R on that same box, something like three years. Suddenly IT didn't work. So last week I needed to place W2DB-L on one of my "private" asterisk/acid nodes(ok...really Limey) and found it didn't work. So I sent an email when their web site shoewd W2DB-L as unauthorized, and authorization failed. They replied with a curt note saying that had I read their prior email (never got it) I'd know that I was blocked. I explained that W2DB-L has been off, and W2DB-R gets regular use on the echolink side. They then accused me of still running a TBD box on W2DB-R (node allstar 2360... ACID...etc) which isn't and was never the case. And I told them so. They said then why is it they could not connect to it. Well, after too many drive by echolink connects from some pile of dirt calling itself a sovereign nation on the other side of teh planet at 3AM I established an acceptable connect list. SO... Echolink informed me that there are three callsigns with all three flavors of suffix that MUST be allowed: permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l, vk2jtp-r, w1cdm, w1cdm-l, w1cdm-r And that's where it ended. Sorry it took so many words, this didn't need to turn into a we hate echolink discussion. But yeah, they really should be happy we are there to at least let them know what good audio sounds like, since they get to remind us of what BAD audio is. W2DB out GeorgeC ----- Original Message ----- From: Kirk Just Kirk To: Jim Duuuude Cc: app_rpt mailing list Sent: Thursday, March 21, 2013 3:23 PM Subject: Re: [App_rpt-users] Echolink Connectivity Issue Wait a minute...... I do fully understand WHY Dave Cameron wanted us to all yank IRLP out of our systems, it interfered with his SELLING you a piece of shit PCB for IRLP to the tune of $170/with a FREE node number thrown in for a bonus. (thats my opinion).Thats OK by me....about 85% of the IRLP installations sound like shit anyways. But Echolink should be HAPPY (YAYYYY) that the Allstar crowd is having access to BOTH modes...... Smells like a rumor to me.Everyone else (other than IRLP) has YOU the owner install/set up/operateYOUR hardware. It's only IRLP that makes you wait till THEIR "Install team" can install your software for you. Echolink probably wouldnt care if you ran it on a Proctor-Silex toaster if you can do it....(Jim can do it) Kirk On Thu, Mar 21, 2013 at 10:14 AM, Jim Duuuude <telesistant@hotmail.com> wrote: Hmmm.. I have never actually seen this policy before... somewhat disturbing... However, practical experience shows that Echolink seems to be perfectly aware of our interconnections and seems to be perfectly content with what we are doing. So, I guess its okay.... ??? Jim WB6NIL > From: petem001@hotmail.com > To: app_rpt-users@ohnosec.org > Date: Thu, 21 Mar 2013 15:59:34 -0400 > Subject: Re: [App_rpt-users] Echolink Connectivity Issue > > Well, thats bad. > > But if echolink remove my node from there system It's their Loss,not mine. > > Some would day that I am arrogant. nope, I just dont care for poeple that > wont think more then that.. > > the more system on their or other networks that can interact together, the > best for every one. > > > -----Message d'origine----- > From: Pawlowski, Adam > Sent: Thursday, March 21, 2013 3:48 PM > To: app_rpt-users@ohnosec.org > Subject: Re: [App_rpt-users] Echolink Connectivity Issue > > I sent this a while back but it was bounced for the wrong mail address. I > don't see it ever made it to the list. > > This was re: someone being advised that their app_rpt node is not permitted > on the Echolink network. > > > Echolink is a nice service > > that allows hams around the world to keep up pc to pc. And nobody asks > > for any money, nice. But this is very, very out of the norm for them. > > > > I looked this up recently when I started to talk about IRLP and how they > don't want other traffic on their network. Then I looked at their Access > Policy: > > 4. Stations operating in Sysop mode may interconnect EchoLink only with > equipment operating on Amateur frequencies. EchoLink does not permit use of > the system with other services such as GMRS, FRS, or MARS. For security > reasons, it is also not permitted to interconnect EchoLink with other VoIP > systems that support direct access from a computer. > > 10. The "addressing servers" are designed to be accessed by EchoLink > software only. For the sake of system security and stability, any other > access requires the permission of the server administrator. As a matter of > security, in no event should the IP addresses (or Internet hostnames) of > logged-in stations be displayed to anyone who is not a validated, logged-in > user. > > 11. Although every effort will be made to apply these policies universally > and fairly, the EchoLink Support staff reserves the right to withdraw a > station's access privileges at any time, without notice. EchoLink is a > privately owned and operated system that has no connection with, and is not > governed by, any radio licensing authority. > > So, I interpret that as that you are not supposed to connect to with > asterisk at all anyways, if you read that verbosely, via app_rpt or > otherwise. I don't have the history to know if they've made any statement > about what app_rpt is doing, but it seems like it's not permitted via their > policy only they are less vocal about it than the IRLP folks. > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users@ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users@ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
On 3/21/13 4:14 PM, Jim Duuuude wrote:
Hmmm..
I have never actually seen this policy before... somewhat disturbing...
However, practical experience shows that Echolink seems to be perfectly aware of our interconnections and seems to be perfectly content with what we are doing. So, I guess its okay.... ???
Jim WB6NIL
Hope so, though, to tell the truth, I'd not be lost if I had to turn it off (as it is, it's just connected to a simplex node that links via RF into the Penn Wireless system rather than my "allstar-connected" network of 2/220/440/900 machines). The fewer drive-bys, the better. Besides, with all the systems connected to the NJ/PA network (not the size of the WAN system...), it cuts down on the noise/kerchunking/blind "CQ" calling...) I'm thinking it's in there for the CYA aspect more than Jonathan using it as a club over repeater owners' heads. Not discounting that they might...just that they've had no reason to. But, one would think that with the experience of folks using or with exerience in the 2 technologies, they'd come to some meeting of the minds in the spirit of cooperation, fellowship, improvements, and sharing ideas. Unlike other linking system developers who will remain north of the border...oops, did I say that? -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. Sent from my MacBook Pro.
participants (6)
-
Bryan D. Boyle -
George Csahanin -
Jim Duuuude -
Kirk Just Kirk -
Pawlowski, Adam -
pete M