RouteViews now has a looking glass
Dear colleagues Just to let you know, we at RouteViews AS6447 have launched a global looking glass so you no longer have to log into each collector using telnet to check global routing. You can read more in our blog at our website. You can find the looking glass here: https://lg.routeviews.org/lg/ Nina RouteViews
Hi, Thanks for informing. Could you share the blog? Best, Lancheng
-----Original Messages----- From: "Nina Bargisen via NANOG" <nanog@lists.nanog.org> Send time:Wednesday, 21/05/2025 20:04:47 To: nanog@lists.nanog.org Cc: "Nina Bargisen" <nihbster@gmail.com> Subject: RouteViews now has a looking glass
Dear colleagues
Just to let you know, we at RouteViews AS6447 have launched a global looking glass so you no longer have to log into each collector using telnet to check global routing. You can read more in our blog at our website.
You can find the looking glass here:
Nina RouteViews _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/IEJ4UZM5...
On Thu, 22 May 2025 at 10:29, Lancheng via NANOG <nanog@lists.nanog.org> wrote:
Thanks for informing.
Could you share the blog? https://www.routeviews.org/routeviews/2025/05/20/the-routeviews-looking-glas... Kind regards, Job
Seems to not be reachable via IPv6: ``` $ curl -6 -I https://lg.routeviews.org/lg/ curl: (28) Failed to connect to lg.routeviews.org port 443 after 19893 ms: Could not connect to server $ curl -4 -I https://lg.routeviews.org/lg/ HTTP/2 200 server: nginx/1.18.0 (Ubuntu) date: Thu, 22 May 2025 08:56:39 GMT content-type: text/html x-served-by: lg.routeviews.org x-frame-options: DENY x-content-type-options: nosniff referrer-policy: strict-origin-when-cross-origin ``` 2025-05-22T00:03:05Z Nina Bargisen via NANOG <nanog@lists.nanog.org>:
Dear colleagues
Just to let you know, we at RouteViews AS6447 have launched a global looking glass so you no longer have to log into each collector using telnet to check global routing. You can read more in our blog at our website.
You can find the looking glass here:
Nina RouteViews _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/IEJ4UZM5...
On May 21, 2025, at 19:04, Nina Bargisen via NANOG <nanog@lists.nanog.org> wrote: You can read more in our blog at our website. From the weblog post: 'The looking glass is our first step towards removing the direct telnet access to all collectors.’ Will ssh CLI access replace telnet CLI access? Thanks much!
On Thu, May 22, 2025 at 09:49:34AM +0000, Dobbins, Roland via NANOG wrote:
On May 21, 2025, at 19:04, Nina Bargisen via NANOG <nanog@lists.nanog.org> wrote:
You can read more in our blog at our website.
From the weblog post:
'The looking glass is our first step towards removing the direct telnet access to all collectors.’
Will ssh CLI access replace telnet CLI access?
I hope the future is something like (IETF standardised?) HTTPS-based APIs - in order to support a broader set of user experiences (be it terminal or browser-based). It seems incredibly hard to (continue to) support a terminal-emulator-based unauthenticated query system with virtually no flow-control between client/server, ON THE SERVER DOING THE $THING. A fundamental problem is that some (well meaning?) entities just keep hogging the remote system ala "show ip bgp [ENTER]", and in turn doing awful screenscraping things to extract data out of the system that's already overlaoded doing THE $THING. I'm not sure the answer is as obvious as "replace telnet with SSH", it might be good for us as community to take a step back and reflect on what exactly we hope routeviews does and what the economics ways are to achieve the desired outcomes. Kind regards, Job p.s. Don't get me wrong - I love logging into remote machines around the world through SSH! https://ring.nlnog.net/
Hi Roland, Dobbins, Roland via NANOG wrote on 22/5/2025 16:49:
'The looking glass is our first step towards removing the direct telnet access to all collectors.’
Will ssh CLI access replace telnet CLI access?
Thanks much!
No, SSH won't be replacing telnet... We are working on an API, which some folks are helping us testing. We want that to be available to all well before telnet is turned off, just to make sure that we are covering what folks are currently using with their automated scripts using telnet queries. More news about the API soon. :-) (I just mentioned here at BKNIX Peering Forum in Bangkok, btw, hints are in that slide deck once they publish it.) philip --
participants (6)
-
Dobbins, Roland -
Job Snijders -
Lancheng -
lists＠at.encryp.ch -
Nina Bargisen -
Philip Smith