Because more and more ISPs, firewalls, companies, etc are blocking telnet
due to security concerns, especially with IOT and industrial devices which
still use it instead of SSH. So the end user (like myself) might not be
able to telnet to public addresses without VPN/VPS or other workarounds as
network owners start to take action against hackers who like compromising
telnet services. This probably doesn't affect most people (hams) right now,
but due to the vulnerability of telnet it might be in any ISPs best
interest to block that traffic by default.
An HTTP pub/sub stream is a workaround that is more or less future proof
(until ISPs start blocking non-HTTPS or something weird like that).
-Sterling N0SSC
On Thu, Sep 5, 2019 at 3:16 PM N4ZR <n4zr@comcast.net> wrote:
> I'm curious - why is Telnet "a fact of history"? It seems to work fine
> for most of us.
>
> 73, Pete N4ZR
> Check out the Reverse Beacon Network
> at <http://reversebeacon.net> <http://reversebeacon.net>, now
> spotting RTTY activity worldwide.
> For spots, please use your favorite
> "retail" DX cluster.
>
> On 9/5/2019 2:35 PM, Sterling Mann wrote:
>
> Gerry,
>
> Following up on the status of your project. I was at a hamfest recently and
> talked to a guy about telnet's deprecation and it reminded me of your
> pub/sub idea. Understandable if bigger fish came by to fry but if you have
> anything source you could share. i know of a few codemonkeys who could
> help.
>
> Thanks & 73,
> Sterling N0SSC
>
> On Wed, May 22, 2019 at 9:37 PM Gerry Hull <gerry@yccc.org> <gerry@yccc.org>
> wrote:
>
>
> I believe Sterling is looking for an end-user solution. The problem with
> running telnet on port 80 is that it is the well-known http port. You can
> telnet to http and vice versa, but it would not be much fun.
>
> I'm working on a pub/sub service that has an http service endpoint. I'll
> provide a windows app client that will give you spots on telnet using
> localhost (127.0.0.1).
> It should be ready in the next week or so.
>
> For those techies out there, I'm running a RabbitMQ instance on a beefy
> VPS that my AB5K cluster is running on.
>
> Distributed pub/sub is where DX spots should be going; telnet is a fact of
> history.
>
>
> 73,
>
> Gerry W1VEdxc.w1ve.com
>
> On Wed, May 22, 2019, 8:30 AM rjairam@gmail.com <rjairam@gmail.com>
> <rjairam@gmail.com> wrote:
>
>
> https://www.dxcluster.co.uk/api
>
> A lot of APIs in there.
>
> 73
> Ria, N2RJ
>
> On Tue, 21 May 2019 at 19:44, Sterling Mann <kawfey@gmail.com>
> <kawfey@gmail.com> wrote:
>
> In a nutshell, I'm on a network that blocks non-standard ports including
> telnet, making it a pain to use DX cluster since I can only access web
> clients like DXsummit.fi. Before I go down the route of begging for
> telnet/non standard port access, is anyone aware of any development of
>
> HTTP
>
> cluster streams? Or maybe a telnet cluster on port 80?
>
> I lack networking expertise so go easy on me.
>
> Thanks,
> Sterling N0SSC
> _______________________________________________
> CQ-Contest mailing
> listCQ-Contest@contesting.comhttp://lists.contesting.com/mailman/listinfo/cq-contest
>
> _______________________________________________
> CQ-Contest mailing
> listCQ-Contest@contesting.comhttp://lists.contesting.com/mailman/listinfo/cq-contest
>
> _______________________________________________
> CQ-Contest mailing
> listCQ-Contest@contesting.comhttp://lists.contesting.com/mailman/listinfo/cq-contest
>
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|