Install them to different folders and create links to them.  Simple.  We have 
that we have clients with all different versions.  Else, why are you running 
dude the 750s, wow, that’s a bit underpowered.


Dennis Burgess – Network Solution Engineer – Consultant
MikroTik Certified 
Trainer/Consultant<http://www.linktechs.net/productcart/pc/viewcontent.asp?idpage=5>
 – MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE

For Wireless Hardware/Routers visit www.linktechs.net<http://www.linktechs.net/>
Radio Frequency Coverages: www.towercoverage.com<http://www.towercoverage.com/>
Office: 314-735-0270
E-Mail: [email protected]<mailto:[email protected]>

From: [email protected] 
[mailto:[email protected]] On Behalf Of ralph via Mikrotik-users
Sent: Friday, March 10, 2017 8:43 AM
To: 'Mikrotik Users' <[email protected]>
Subject: [Mikrotik Users] MT/Dude versions This is getting crazy

I have at least 5 different versions ROS running and I can’t find a version of 
The client that can talk to all of them.    Each one seems to need its own 
version of The Dude and it is pretty tedious to manage this.

Currently when I open The Dude (that formerly worked) I get that “Downloading 
or Upgrading” message and then Dude closes.

Why wont the current Dude version for the latest ROS work with the past couple 
of previous versions?  It would seem that they would do regression testing when 
they bring out new versions.

I am not talking about V6.x vs V5  or things like that, I mean  6.36 6.38  
6.35.4  6.38.3  6.17, etc.

My customers are 24 hour operations and I don’t want to upgrade all of them 
right now plus there are memory constraints on the RB750 units.

There has to be something I am missing about getting it to work on older 
versions of ROS. HELP!!!

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Scott Reed via 
Mikrotik-users
Sent: Thursday, March 9, 2017 4:32 PM
To: Mikrotik Users <[email protected]<mailto:[email protected]>>
Subject: Re: [Mikrotik Users] DUDE Discovery


I haven't done Dude discovery for a while so this may not work.

Justin is right, hard to move.  However, you may be able to put just the ones 
you want on the map.

It used to do discovery by subnet.  That doesn't have to be real subnets.  So, 
build a map for your PoP or AP or whatever.  Do discovery for the map on just 
the address range that should be on the map. You may need to do several small 
ranges, but this let's you get just what you want.

On 3/9/2017 4:23 PM, Justin Wilson via Mikrotik-users wrote:

+1 to what Dennis says.  The fact that you can’t move devices to different maps 
after discovery (at least without hassle) is a major reason I don’t let things 
auto discover.   Setup your map and submaps then add your devices.  It seems 
time consuming but you check as you go.





Justin Wilson

[email protected]<mailto:[email protected]>



---

http://www.mtin.net Owner/CEO

xISP Solutions- Consulting – Data Centers - Bandwidth



http://www.midwest-ix.com  COO/Chairman

Internet Exchange - Peering - Distributed Fabric



On Mar 9, 2017, at 9:44 AM, Dennis Burgess via Mikrotik-users 
<[email protected]><mailto:[email protected]> wrote:



Not to do DUDE discovery!! Seriously, just add and build it from scratch, much 
simpler and better.  It has no clue on subnets, how things are connected etc.





Dennis Burgess - Network Solution Engineer - Consultant

MikroTik Certified Trainer/Consultant - MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE



For Wireless Hardware/Routers visit www.linktechs.net<http://www.linktechs.net>

Radio Frequiency Coverages: www.towercoverage.com<http://www.towercoverage.com>

Office: 314-735-0270

E-Mail: [email protected]<mailto:[email protected]>





-----Original Message-----

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Nick Bright via 
Mikrotik-users

Sent: Wednesday, March 8, 2017 3:42 PM

To: [email protected]<mailto:[email protected]>

Subject: [Mikrotik Users] DUDE Discovery



What is the proper way to get dude to discover my RouterOS devices, and place 
them on the network map?



I can get it to put everything (or nothing) on the network map with a 
discovery, but that results in (literally) thousands of devices that don't need 
to be there. I want *ONLY* RouterOS devices to be discovered.



The documentation for Dude is quite insufficient 
(https://wiki.mikrotik.com/wiki/Manual:The_Dude/Device_discovery).

Following it results in a blank map.



--

-----------------------------------------------

-  Nick Bright                                -

-  Vice President of Technology               -

-  Valnet -=- We Connect You -=-              -

-  Tel 888-332-1616 x 315 / Fax 620-331-0789  -

-  Web http://www.valnet.net/                 -

-----------------------------------------------

- Are your files safe?                        -

- Valnet Vault - Secure Cloud Backup          -

- More information & 30 day free trial at     -

- http://www.valnet.net/services/valnet-vault -

-----------------------------------------------



This email message and any attachments are intended solely for the use of the 
addressees hereof. This message and any attachments may contain information 
that is confidential, privileged and exempt from disclosure under applicable 
law. If you are not the intended recipient of this message, you are prohibited 
from reading, disclosing, reproducing, distributing, disseminating or otherwise 
using this transmission. If you have received this message in error, please 
promptly notify the sender by reply E-mail and immediately delete this message 
from your system.



_______________________________________________

Mikrotik-users mailing list

[email protected]<mailto:[email protected]>

http://lists.wispa.org/mailman/listinfo/mikrotik-users

_______________________________________________

Mikrotik-users mailing list

[email protected]<mailto:[email protected]>

http://lists.wispa.org/mailman/listinfo/mikrotik-users





_______________________________________________

Mikrotik-users mailing list

[email protected]<mailto:[email protected]>

http://lists.wispa.org/mailman/listinfo/mikrotik-users


________________________________
[Avast logo]<https://www.avast.com/antivirus>


This email has been checked for viruses by Avast antivirus software.
www.avast.com<https://www.avast.com/antivirus>


_______________________________________________
Mikrotik-users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/mikrotik-users

Reply via email to