search

Vadims06 / topolograph

Topolograph.com is an online project which can visualize OSPF/ISIS topology based on LSDB output from a single network device. Then you can not only see (and check) the shortest path from source to destination, but also see the outcome from link or node failure along the path to the destination.
https://topolograph.com
MIT License
177 stars 23 forks source link

Mikrotik Support #8

Closed nlgotz closed 3 years ago

nlgotz commented 3 years ago

Hello,

Are there any plans to add support for Mikrotik routers? I can provide the necessary database outputs if needed.

Thanks!

Vadims06 commented 3 years ago

Hi @nlgotz, thank you for your request. Sure, I need the output describing LSA1, LSA2, LSA5. Please send me the output to admin@topolograph.com

rinchen commented 3 years ago

I have LSAs and Routes in a text file to send you but the email above is bouncing and I can't seem to create an account on your slack. I don't want to push my routes in a public github ticket. Please advise.

Vadims06 commented 3 years ago

I have LSAs and Routes in a text file to send you but the email above is bouncing and I can't seem to create an account on your slack. I don't want to push my routes in a public github ticket. Please advise.

Hi @rinchen , sure, but let me clarify, if you send the email to admin@topolograph.com - you get an error?..

Vadims06 commented 3 years ago

@rinchen i just sent test email and i received it successfully. Please check emaik spelling, or probably i can send you init email and you replay back.

rinchen commented 3 years ago

I sent it from two different email providers:

admin@topolograph.com 550 admin@topolograph.com 550 rejected: Unknown recipient : previously hard-bounced and is currently blocked. If you think the recipient will no longer hard-bounce they can be unblocked from the 'Reports > Suppressions' page at app.smtp2go.com. Reporting-MTA: dns; mail.smtp2go.com

Action: failed Final-Recipient: rfc822;admin@topolograph.com Status: 5.0.0

and

admin@topolograph.com: host mx2.spaceweb.ru[77.222.41.158] said: 550 rejected: Unknown recipient (in reply to RCPT TO command) Reporting-MTA: dns; helm.stanford.tel X-Postfix-Queue-ID: E3AD43011D6 X-Postfix-Sender: rfc822; joey@stanford.tel Arrival-Date: Sun, 7 Mar 2021 14:18:08 +0000 (UTC) Final-Recipient: rfc822; admin@topolograph.com Original-Recipient: rfc822;admin@topolograph.com

Action: failed Status: 5.0.0 Remote-MTA: dns; mx2.spaceweb.ru Diagnostic-Code: smtp; 550 rejected: Unknown recipient

Vadims06 commented 3 years ago

I sent it from two different email providers:

admin@topolograph.com 550 admin@topolograph.com 550 rejected: Unknown recipient : previously hard-bounced and is currently blocked. If you think the recipient will no longer hard-bounce they can be unblocked from the 'Reports > Suppressions' page at app.smtp2go.com. Reporting-MTA: dns; mail.smtp2go.com

Action: failed

Final-Recipient: rfc822;admin@topolograph.com Status: 5.0.0 and

admin@topolograph.com: host mx2.spaceweb.ru[77.222.41.158] said: 550 rejected: Unknown recipient (in reply to RCPT TO command) Reporting-MTA: dns; helm.stanford.tel X-Postfix-Queue-ID: E3AD43011D6 X-Postfix-Sender: rfc822; joey@stanford.tel Arrival-Date: Sun, 7 Mar 2021 14:18:08 +0000 (UTC) Final-Recipient: rfc822; admin@topolograph.com Original-Recipient: rfc822;admin@topolograph.com

Action: failed

Status: 5.0.0 Remote-MTA: dns; mx2.spaceweb.ru Diagnostic-Code: smtp; 550 rejected: Unknown recipient

Hi @rinchen. Thank you for your email! I am going to create a ticket in my domain hosting provider and additionally i sent to joey@stanford.tel hello email. Please kindly check. I come back as soon as i get any details regarding email error.

Vadims06 commented 3 years ago

Hi all, I have just added templates for Mikrotik. Thank you @rinchen for your data. @nlgotz please kindly check too. Single command is only needed - /routing ospf lsa print detail file=lsa.txt

archhorde commented 3 years ago

Hello, when I try uploading my lsdb nothing seems to happen. I have tried both the docker desktop version and the website. I used the correct command to generate the lsa.txt file as well. There does not appear to be any debug output or errors to show why it fails. Any help is appreciated!

Vadims06 commented 3 years ago

Hello, when I try uploading my lsdb nothing seems to happen. I have tried both the docker desktop version and the website. I used the correct command to generate the lsa.txt file as well. There does not appear to be any debug output or errors to show why it fails. Any help is appreciated!

Hi @archhorde, thank you for your message , could you please send me your file to my email admin@topolograph.com

archhorde commented 3 years ago

Hi @Vadims06 , I do not feel comfortable sharing that file as it contains proprietary data. However, I will spin up a lab environment and generate a simple lsdb for debugging purposes. Once I have that I will get back to you.

Vadims06 commented 3 years ago

Hi @Vadims06 , I do not feel comfortable sharing that file as it contains proprietary data. However, I will spin up a lab environment and generate a simple lsdb for debugging purposes. Once I have that I will get back to you.

@archhorde sure. Short notice, please make sure that you select Mikrotik radio button during file uploading.

archhorde commented 3 years ago

@Vadims06 I have just email you with the file.

rinchen commented 3 years ago

If either of you @Vadims06 & @archhorde want me to check that file let me know. I suspect @Vadims06 will be able to figure it out though. @archhorde are you on a relatively current firmware such as 6.48.1? What device are you using? I probably have one I can export and send to Vadims but the format should be the same.

Vadims06 commented 3 years ago

Hi Joey @rinchen, thank you for your openness to help! You were absolutely right, there was a different output depending on Router OS version. Fresh versions (like 6.48.1) print out this row Transit 10.15.5.5 10.15.5.1 10 but older (6.44.6) - print this link-type=Transit id=10.15.5.5 data=10.15.5.1 metric=10 I adapted templates in order to match even such output.

rinchen commented 3 years ago

Multiple CVEs for those older versions so I would not recommend running them. 6.47 (LTS) and 6.48 (stable) are the ones people should be running whenever possible.

Vadims06 commented 3 years ago

Hi @archhorde, does the last update work for you?

archhorde commented 3 years ago

Hi @Vadims06 apologies for the delay. Yes it is working now thank you so much!

Vadims06 commented 3 years ago

Hi @archhorde , I just released topolograph:v2.17 where added my fixes for 6.44.6 as well as other features, like coloring graph based on host to group (site/office) membership. Thank you all, I'm always available on the email. Closing this issue,

Vadims06 commented 2 years ago

Hi @rinchen @nlgotz @archhorde I would like to share with you and offer another extension of Topolograph - OSPF Watcher. The watcher connects to a real network via GRE tunnel and logs any changes in the topology. Logs then are exported to Elastic Search stack where can be filtered by the required time period. So you can always find out what has been happening with your topology in the past.

rinchen commented 2 years ago

Excellent thanks. I'll have a look. It sounds very useful.