@Vinicius_Arcanjo wrote:
So far, one of the greatest drawback of VIRL is the fact that you don`t have a detailed print on the link connecting the routers. What I mean by detailed print is a kind of summary which includes the IPv4/v6 addressing used on that segment and a short string which tells what interfaces are connected on both sides of the link. I'll elaborate on what I'm saying by short string.
Currently, indeed, we can highlight our links on our topology to see their interfaces name, but the string is extremely huge (there is no need to print the entire string). For example, if you highlight a link you'll see something like GigabitEthenetX/Y which could be better presented if you shorten this string to Gi X/Y, this way the whole topology would look much cleaner and nicer. Besides, the other requirement that I still miss a lot is the fact that you don't print the IP of the infrastructure on the links which can be a pain in the neck sometimes. As a result, you never know what subnet is being used by a certain segment. This information is extremely useful to understand the routing protocols and troubleshoot eventual circumstances.
Finally, I suppose that I can sum up the above paragraphs requirement by using this image, this is what I somehow expect to be shown on the "detailed print" that you guys could implement (note how clean/well formatted the information is presented):
![]()
VIRL is such an amazing product and you guys have been doing a great job. I just purchased VIRL recently and this detailed print would definitely be the icing on the cake. I hope you guys can implement this extra enhancement that would bring VIRL to the next level! Thanks a lot!
Posts: 1
Participants: 1