3.1. Menu system settings
The logical step after installing the system is to configure the system parameters, which will be discussed in this section. The transition to the system settings menu is performed by pressing the “Settings” button on the main panel ( see figure 3.1).
The settings made in the system settings menu will be applied by default when adding devices. However, when adding devices, you can specify personal settings that will be applied to a device or group of devices. Personal settings devices take precedence over system settings.
3.1.1 SNMP setup
In the SNMP tab, you configure the details for polling devices. The setting is a system of profiles in which the following parameters are specified ( see figure 3.2):
- SNMP version;
- SNMP requisites (the set of requisites depends on the version used);
- Number of polling attempts;
- Pause between polling attempts.
Three profiles are added to the system by default. Let's add a profile that we will use within the framework of the article and select it as the default profile:
3.1.2 Polling setup
Tab “ Polling” is responsible for configuring device polling ( see figure 3.4). The tab contains the following options:
| Parameter | Default value | Description |
|---|---|---|
| enable | yes | Enable/disable device polling. |
| Probe Interval | 30s | The interval at which devices will be polled. |
| Probe Timeout | 10s | The interval during which the system will wait for a response from the device after sending a request. |
| Probe Down Count | 5 | The number of requests that will cause the system to consider the device unavailable if not answered. In the Dude interface, available devices are highlighted in green, unavailable devices in red, and partially available devices in orange. |
| notification | log to syslog | A way to notify about a change in device status. Alert settings are detailed in Section 3.3. |
3.1.3 Configuring agents
In the tab " Agents” Agents are selected through which devices will be polled. Since this section of the menu performs the configuration that is applied by default to devices, then configuring the agent in this section is only useful in a scheme where most network devices are accessible through an agent device.
3.1.4 Setting up the logging server
Dude can act as a syslog server, both writing logs on its own, and receiving log data directly from devices. In order for devices to send logs to the Dude syslog server, you must configure the appropriate settings on the end devices.
The syslog server configuration is performed on the “ syslog” in the system settings menu ( see figure 3.6). The administrator can configure the following settings:
3.1.5 Map setup
On the tab " Map” performs display settings for new maps, which will be applied by default. The configuration of each card can be changed individually ( see section 3.4).
3.1.6 Customizing graphs
Configuration of parameters for displaying graphs of interrogated device parameters is performed on the “ charts” in the system settings menu ( see figure 3.8). The mechanism for adding graphs is discussed in Section 5.3.
3.1.7 Setting up reports
Dude sections that display data as a list (for example, a list of devices in the system) allow you to download this data in the format *. csv and *. pdf. Setting the parameters for uploading information to *. pdf performed in the “Report” tab of the system settings menu ( see figure 3.9).
3.1.8 Configuring Device Autodiscovery
One of the methods for adding devices to the monitoring system is device auto-discovery. General settings of the mechanism are performed on the tab “ discovery” system settings menu ( see figure 3.10).
The key search parameters are set when performing the search procedure ( see section 4.2), but in this menu The administrator can make the following settings:
| Parameter | Description |
|---|---|
| black list | The name of the list of devices that will not be added to the monitoring system when they fall within the scan range. |
| Name Preference | Parameter responsible for naming devices when adding them to the system. For example, if DNS is specified, then the name assigned to this device on the DNS server will be used. |
| mode | Device scan method:
|
| Recursive Hops | The number of recursive hops. If the scan detects devices to which other networks will be connected, then these networks will also be scanned for devices. The parameter determines the depth of network scanning. |
| Biggest Network Size Allow Hop To | The maximum network size displayed on the map. The parameter defines the depth of the network, as the number of hops. |
| Advanced | A set of actions to be performed when a device is added. |
| Services | List of services scanned when adding devices. When choosing mode=reliable the list of services to check will be taken from this list. |
| Device Types | List of device types that will be recognized when added. The device type affects the icon that will be assigned to the device on the network map. |
| Item Placement Settings | Parameters for the location of the device icon on the network map. |
3.1.9 Configuring connection with RouterOS
Connection parameters with devices on which RouterOS is installed are configured on the “ RouterOS” (see figure 3.11).
3.1.10 Other Dude settings
On the tab " misc” system settings menu, you can configure the network map update period and the behavior of the client application ( see figure 3.12).
Dude has two sections where you can track the history of changes made to the system ( see figure 3.13) and a list of logs ( see figure 3.14). The sections are located in the left menu of the system management and, since they are visualized in the form of a list, they can be uploaded as a report in the formats *. csv and *. pdf.
In chapter " HistoryActions” reflects all the changes that the administrator made in the Dude system. In chapter " Logs” reflects all the logs received by the built-in syslog server and the logs of the monitoring system itself.
3.3 Setting alerts
The configuration of notification methods for occurred events is performed in the section “ Notifications” in the left system management menu ( see figure 3.15).
Several notification methods are pre-installed in the system, the administrator can create his own set. Let's create new method alerts by clicking on the “ + ". The configuration menu for the new notification method opens ( see figure 3.16), on the tab " General” you must specify a name for the alert, enable or disable it, and set the alert method. The system supports the following notification methods:
| Alert Method | Description |
|---|---|
| beep | Playing a sound signal. |
| Sending a letter by e-mail. | |
| execute locally | Executing a script on the PC running the client application. |
| execute on server | Executing a script on the Dude server. |
| flash | Blinking of the client application window on the taskbar. |
| group | A combination of other notification methods. |
| log | Creating a log entry on the Dude server. |
| popup | Pop-up window. |
| sound | Plays the specified audio file. |
| speak | Alert text-to-speech and playback (performed by Windows tools). |
| syslog | Creating a log entry on a remote syslog server. |
AT created method alerts, select the group method and select the alert through the popup window and local entry to the log ( see figure 3.16). The system allows you to perform a test by creating a test alert by clicking the “ test”.
On the tab " Schedule” is setting the notification time ( see figure 3.17).
On the tab " Advanced” configuring events for which alerts will be generated and configuring repeated alerts. Events look like a change in the status of device services ( see figure 3.18).
3.4 Setting up the network map
Using the map allows you to visualize the network diagram, which is useful when diagnosing some problems, since the map displays the statuses and indicators of monitored device parameters online.
The administrator can create several maps with different settings, for example, you can create separate maps for the network of each city. In addition to display convenience, each map allows you to use a unique survey and alert profile that will apply to all devices located on the map.
Each map has two layers: communication channels and dependencies. Using the Device Dependency Layer “ dependencies” allows you to create a network hierarchy that affects alerts.
The default map is " Local”, the map is opened through the left system management menu ( see figure 3.19).
The network map menu is a menu bar with basic controls and the map itself. can be placed on the map the following items (see figure 3.19):
| Map element | Description |
|---|---|
| device | The network device for which its status and polled values will be displayed. |
| network | Network image. A non-interactive element used to draw a network diagram. |
| Submap | Link to another map displaying statistical information on devices. |
| Static | A static object used to draw a network diagram. |
| Link | Communication channel between network devices. |
| Dependency | Dependency between network devices. The use of dependencies allows you to form a hierarchy, which can be used when generating alerts. The element is only available on the layer “ dependencies”. |
In order to go to the map settings menu, you must press the “ Settings” on the map menu bar ( see figure 3.19). You can make the following settings for the card:
3.5 Files
In Dude you can change standard icons devices, sound alerts and expand the set of MIBs. In addition, to update device firmware, it is necessary that files with these firmware are present in the monitoring system. For these purposes, the menu section “ Files” (see figure 3.20).
Editing a directory with files through the client application is not available starting from ver.6.37, however, files can be loaded/deleted using the following methods:
- winbox;
- webfig;
- SFTP.
Upload the firmware file via Winbox to the directory “ dude/files” and check the existence of the file through the client application ( see figure 3.20).
3.6 Instrument settings
When called context menu for each device will be offered quick launch a set of management and diagnostic tools. The set of these tools is configured in the section “ Tools” of the left system management menu ( see figure 3.21).
The system comes pre-installed with a set of default tools, consisting of:
| Tool | Limitation | Description |
|---|---|---|
| Bandwidth Test | only for RouterOS | Running the test utility bandwidth on the selected device. |
| Dude | only for RouterOS | Connecting to Dude-server. |
| ftp | Connect to an FTP server using the IP address of the selected device. | |
| Ping | Run the ping utility with the IP address of the selected device. | |
| remote connection | only for RouterOS | Launches the utility for connecting to the end device through the selected device. |
| snmpwalk | Runs the SNMP OID polling utility for the selected device. | |
| Spectral Scan | only for RouterOS | Launches the spectrum scan utility on the selected device. |
| telnet | Run the telnet utility with the IP address of the selected device. | |
| Terminal | only for RouterOS | Running the utility command line on the selected device. |
| Torch | only for RouterOS | Run the torch utility on the selected device. |
| traceroute | Run the traceroute utility with the IP address of the selected device. | |
| Web | Opening the selected device through a web browser. |
In addition to the default set of tools, the administrator can add others. There is no launch of the Winbox tool in the list, let's add it. To do this, press the key + ” and in the menu that opens, write the command that launches Winbox ( depends on the location of the executable) and pass the command as a parameter the IP address of the device ( for example, the command might look like this: “ D:\Distrib\winbox.exe”) (see figure 3.22). In this example, only the IP address of the device is passed as a parameter, but the system allows you to pass many other parameters, such as login and password.
3.7 Function setting
Data for plotting ( see section 5.3) and monitoring are formed based on the set of functions located in the menu section “ Functions” (see figure 3.23).
By default, the system has created a set of logical functions, polling functions, data transformation, mathematical operations etc. In addition to the standard functions, the administrator can create a set of functions, which can be a combination of standard functions or perform different operations. For example, there is a function for polling the level of processor load, or you can invert it and display the level of free resources.
AT standard set functions include function cpu(), which returns the CPU usage level. Let's add a function that returns True if the load value is CPU less than 5% and False if the load value is greater (function text: if((cpu_usage()<5),"1","0") ):
3.8 Configuring Polled Services
The formation of a set of services for monitoring is performed in the “Probes” section of the main menu ( see figure 3.25). The system includes a pre-installed set of services, but the administrator can add his own services or edit the existing ones.
The system has a fairly flexible system of survey settings, which includes:
- DNS — formation of a DNS query with specified field values;
- function — use of user-defined functions (see section 3.7);
- ICMP — formation of an ICMP request with the given field values, waiting for a response with the set field values;
- logic is a logical function;
- TCP — formation of a TCP request with the given field values, waiting for a response with the set field values;
- UDP - formation of a UDP request with the given field values, waiting for a response with the set field values;
- SNMP — Polling a specific OID via SNMP;
- Random - a random decision about the availability of the service (used in testing).
The system is pre-installed to poll the CPU load service cpu, which generates an accident if the polling of the sticky OID fails, i.e. no response received from the device. This approach checks the availability of the device, but in practice it is convenient to generate an accident when the processor load reaches a certain threshold.
Let's create a service that will generate an accident when the processor load is above 5%, for which we will use the previously created function spw_cpu() (see section 3.7).
Free monitoring system The Dude from Mikrotik.
I want to start a series of articles about the monitoring system from Mikrotik named The Dude. Translated from English DUDE. I don’t know by what principle the developers called the monitoring system, but apparently they wanted to add a little humor so that it would not be so boring.
I want to immediately warn copypasteers and plagiarizers, when copying and posting these materials, a link to the author and the site is required. For the lazy, the author is Vitaliy (obsessionsys) - tranz-it.net. Â
Let's start to analyze in more detail. Since I am a remote employee of the company, and I serve remote servers and systems, and I do not have direct physical contact with the equipment, I needed a monitoring system.
Chosen according to many criteria:
1. Free, i.e. OPEN SOURCE
2. Ability to expand on various systems those. CROSS-PLATFORM
3. Easy initial setup
4. Not bulky like monsters Nagios, Cacti, Zabbix
5. Intuitive interface
6. Without financial investments (make on what is from iron)
7. Minimum time costs
8. Expandable functionality
9. Scalability
10. Undemanding to resources
11. Monitoring based standard means all OS families (SNMP, TCP, etc.) without the use of agents
12. Device typing based on auto polling
13. Syslog-Server was on board
14. MAIN -> NETWORK MAPS with the ability to manually build maps.
15. MAIN -> STARTING PROGRAMS ON A REMOTE MACHINE WITH PASSING CONTEXT PARAMETERS
16. BUILT-IN LANGUAGE FOR WRITING POLLING FUNCTIONS
17. NOTIFICATIONS BY E-MAIL AND SMS and others.
18. Use of standard programson a work PCTo connect to servers
Well, it looks like you haven't missed anything. Thus, monitoring systems such as NAGIOS, CACTI, ZABBIX were discarded immediately for many reasons, I don’t even want to list them. I sorted through a bunch of software for a very long time, and even came across paid and even terribly paid ones, but this didn’t suit me, somehow I didn’t want to pay, because we need to get off with a little blood.
And when I started using Mikrotik equipment, and installed myself at home instead of Draytek, Mikrotik RB800 + 816, I came across a wonderful thing, this free system monitoring The Dude. I was very surprised that the company provides this development for free (1st point satisfied). Many will pour mud and say that The Dude is garbage and so on, there is no comrade for the taste and color. But still I will continue.
The system can be installed on both Linux and Windows, but it is best this system works under its OS - RouterOS.
The monitoring system itself different platforms can be downloaded from the official website MIKROTIK.COM. You can also try the demo mode on the official website, using the link above, the IP address is indicated, after downloading and installing The Dude (it is both a client and a server, i.e. it comes all in one bottle, but only for Windows and Linux ) you can connect and view the test grid using the admin login and without a password.
I will describe a slightly sad experience of installing under Linux and Windows, only briefly, what jambs and bugs I found, but maybe it was just me, please do not kick much. Installation on the axis Windows Server or Windows XP with an unlocked number of TCP sessions, failed, with an increase in the number of monitoring devices, the socket stack overflowed, and the server began to slow down terribly, it was impossible to log in via RDP, and all this continued until a reboot, after which it repeated after a while. With Linux, as such, there were no problems, because. Windows and Linux sockets are similar, but in Linux it works a little differently, and there were no overflows, although with large and frequent requests via the TCP / IP protocol, the sockets were overloaded, but this happened very rarely, and again a banal reboot of the system helped. Minus everything in Linux, monitoring can work through Wine, and is not automatically assigned to autoload, but with a little manipulation it can be done, but you can’t run away from wine.
Therefore, I still chose the native RouterOS system to install the monitoring system, and installed it on virtual machine virtual box. After that, through the graphical utility, Winbox connected to RouterOS. Registered IP address (IP -> Addresses - [+]), gateway (IP -> Routes -> [+]), well, DNS (for polling on local DNS servers)
From offsite we download the .npk file of the monitoring system, in Winbox we open the Files menu item and drop it using drag-and-drop (mouse transfer) and then reboot the system (System -> Reboot -> Yes)
Everything, after rebooting the system, the monitoring system is installed on RouterOS.
For Windows servers everything is trivial, when you install be sure to specify the Server Files checkbox, and everything else is up to your taste.
Now, on a working PC (if it is Windows), install the same The Dude file, only uncheck the Server Files item, if the OS is Linux, install using Wine and run the client. For clarity, I installed a test version of The Dude on a virtual Windows machine, which will be both a server and a client.
After that, in the Server field, enter the IP address of our virtual machine or server where The Dude is installed, the mode is secure, the port is 2211, the username is admin, the password field is left blank, and click the "Connect" button. I have localhost registered, because I have the server installed on the same machine. After connecting, an automatic polling window will immediately pop up. local network based on IP address operating system on which The Dude is installed. For the first test, you can click poll, and you will see how the system polls all the IP addresses of your local network, while adding all found devices to the map. (Item 12 - Satisfied)
I did not do this, and pressed cancel, because. I myself will control the process of adding devices to the map, and even more so The Dude system itself is not configured.
First you need to configure the system itself. In fact, all the settings of the monitoring system are very intuitive and understandable, but I will analyze in more detail and give a few recommendations that I found as a result of using this system. Accordingly, we go to the settings:
And we will see the following:
Section: General
In the General tab, you can immediately see what's what, though with sending an email there are many problems, but they can be solved. Thus, on the main tab, DNS servers are configured to search for devices by the monitoring system and configure sending to email.
Section: SNMP
In the picture above, SNMP polling is configured, i.e. SNMP profiles for which data will be collected from devices. The profile includes the community, port, and version. MY ADVICE: Use different SNMP profiles for different networks, and different agents if you have a distributed network. For more aesthetic than practical purposes. Be sure to include comments on all points where it is possible to do this, since it will be much easier for you to navigate later.
At this stage, the default snmp profile is public version 1, which will be applied automatically to all networks and devices. You can choose your own or create your own and set it as default. The Dude supports all three versions of the snmp protocol. (Point 11 - mostly satisfied)
Section: Poll
IT IS VERY IMPORTANT TO STOP ON THIS TAB
The most interesting tab in my opinion. And very dangerous. I WILL SAY IMMEDIATELY: THE LESS THE "SOUNDING INTERVAL" PARAMETER COSTS AND THE "SOUNDING TIMEOUT" and "NUMBER OF PROBES..." PARAMETER COST MORE, the greater the load on the monitoring system and the more system resources are required from hardware. MY ADVICE: Set the parameter "Probing interval" more (everything depends on the number of devices) at the first stage, about 5-10 minutes, and accordingly, than more devices you will monitor, this parameter should be proportionally increased slightly. The "Probing timeout" parameter should be set less, but not equal to zero, I set myself about 2-3 seconds. I set the parameter "Number of probes in the "Not working" state" to about 2. Why two, the more probes you will have in monitoring the device itself (i.e. monitoring CPU, DNS, TELNET, SSH, HTTP, etc. ) the more the load on the monitoring system increases, so I try to rationally use the resources of the hardware on which the monitoring system is installed. Proverb - Saving should be economical.
Well alerts, this is the section where you can customize the alert system to your heart's content. Information about any activity on devices. You can add to alerts, playback sound files, or sending SMS, or sending a letter. For example, I have to play a pig squeal when the server turns off, and even sitting in another room I already know for some reason my server turned off, probably my son pressed the reset button on the server's system unit. Or, for example, send the IT department staff the sound of a funeral mush when the 1C server is cut off, so that they know that the accountants will come soon, and the chief accountant will bury them one by one in the system administrator's closet. Thus, in this monitoring system, you can flexibly configure the notification system for IT department employees, up to displaying a map on a separate monitor, for a visual display of all network nodes, which will make some kind of sounds. (Item 17 satisfied)
Section: Server
In this section, you can specify the ports to which you can connect to the monitoring system, by default, the normal port for connecting to The Dude monitoring server is 2210, safe 2211. You can set your own ports, only when connecting you will need to specify which port to connect to. You can also specify the networks from which you can connect to the monitoring server, by default, all networks are allowed to connect. You can add multiple networks by clicking the down arrow. And the monitoring system in its core will prescribe the firewall rules for accessing the monitoring system.ÂÂÂÂÂÂÂÂ
Wow, and there is even a web interface, stunned, which can work both on port 80 and on SSL, well, isn’t it beautiful, it’s true that you must first generate a certificate on the SSL port and transfer it to the monitoring system in the Files section of the left menu. I think that there should be no problems with this section, everything is very clear.
Section: Agents
This section specifies and configures the connection of agents for distributed monitoring remote networks. The Dude server of the same version as the main one, ours, which we are setting up now, is indicated as an agent. (Item 9 - Satisfied)
Section: Syslog
(Item 13 - Satisfied)
In the syslog server, we can turn it on, set the port, and add a bunch of profiles for devices that will dump logs on our server, and you can also distribute it so that each server dumps its logs into its own file (Logs section in the left menu of the monitoring system where you can configure as much as you want system logs and for different devices).
Section: Map
In this section, you can configure the visual display of objects on the map (this is the Background, Appearance Devices, Network View, Submap View, Static View, etc.)
Section: Diagram
Here you can configure How long to save graphs and chart history, specify the initial storage size, and specify the color scheme for displaying charts. As for the history, I did not touch anything and left it as it is, I just changed the Font so that it would be clear what is written on the diagram.
The rest of the sections are not that important to begin with, but you can play around with the settings, but only carefully. :)
Then we press the "OK" button. We can say that the system is configured.
Summing up
1. Free, i.e. OPEN SOURCE- free
2. Possibility to deploy on different systems i.e. CROSS PLATFORM - cross-platform
3. Easy initial setup - I think everyone will agree that it is not difficult to set up
4. Not bulky like monsters Nagios, Cacti, Zabbix - yes, it's definitely only 3.9 megabytes
5. Intuitive interface - very good for me (IMHO)
6. Without financial investments (make on what is made of iron) - virtual machine
7. Minimum time costs -ÂÂÂÂ to be honest, I managed to set up the system in 20 minutes
8. Expandable functionality - I will describe this later.
9. Scalability - yes scalable, with small agents on the same system the Dude
10. Undemanding to resources - virtual machine 1CPU, RAM 512 Mb, HDD-RouterOs 1 GB, HDD-Dude 8 Gb, ÂÂÂÂ virtual CPU load 34% when monitoring 41 devices (hardware Intel Desktop Board DN2800MT)
11. Monitoring based on standard tools of all OS families (SNMP, TCP, etc.) without the use of agents - yes, monitoring without agents
12. Device typing based on auto polling - there is
13. Syslog-Server was on board - there is not bad, and it works
14. MAIN -> NETWORK MAPS with the ability to manually build maps. - yes, there are maps, and they are very flexible (there is a minus, you have to finely and manually configure the display of data for each device)
15. MAIN -> STARTING PROGRAMS ON A REMOTE MACHINE WITH PASSING CONTEXT PARAMETERS (there is, the main thing is brains and hands in the right place)
16. BUILT-IN LANGUAGE FOR WRITING POLLING FUNCTIONS (very flexible - available)
17. NOTIFICATIONS BY E-MAIL AND SMS and others. (there is)
18. Using standard programs on a working PC d To connect to servers(where the soul lies, I use Linux Mint + The Dude Client + Remmina + mini scripts)
In the next article I will describe how to add devices to the map and set up monitoring.
Some time ago, I began my acquaintance with a rather convenient and functional network monitoring tool from the company Mikrotik - The Dude. This thing is not easy and it will take a lot of time to fully understand its capabilities. But I have already begun to form some idea. Therefore, now a little practice of working with The Dude.
It all starts with installation. Rather, the first difficulties already begin with the installation. The point is that earlier this program was a "thing in itself", combining client and server. Now everything is somewhat more convenient and more complicated at the same time - we have a separate lightweight client that can be installed in a minute and reach the server part, which can be anywhere ... Where is Router OS. At first I was delighted, this is ideal, because The Dude is just a separate plugin for Mikrotik routers. That is, we update the firmware on the router, download the server part, and it would seem that this is happiness. But no.
The Dude server is put on a rather limited the lineup piece of iron - on architecture TILE (CCR, Cloud Core Router), ARM (CRS3xx, RB3011, RB1100AHx4), X86 (RB230, X86), MMIPS (RB750Gr3). Thus, the owners of the most common MIPSBE decisions suck paw. These are, for obvious reasons, points NetMetal, wAP, Sextant etc., routers hAP/mAP/etc., modifications based on RB2011 and further down the list. Pain and suffering. What to do? The solution lies in the magic abbreviation X86- we will install RouterOS on our hardware.
In the simplest case, for this we need Oracle VM VirtualBox and Router OS distribution kit from the Mikrotik website CD Image, relevant at the time of this writing - on top of which we will put The Dude server .
Note. The distribution kit on the .iso-image will already have a pre-installed server part of Duda.
Now for the installation process. Of course, to begin with, we set virtual box. With him, everything is relatively simple - further, further and further again. Now about creating a virtual machine.
Click on Create and follow the suggested steps.
1.
We set the name of the virtual machine and its type. The type will be Linux 2.6/3.x/4.x (32-bit)
2.
Specify the volume random access memory, which our virtual machine will have
3. Virtual hard. Choose new virtual hard disk.
4. Set as hard type VDI (VirtualBox Disk Image)
5. And choose the storage format dynamic virtual hard disk.
6. We set the name of our hard and its size.
7. As a result, we get such a virtual machine:
8. Now you need to go to its settings and configure Net. Required to create network bridge (Bridge) with a real network card.
That's all. It remains to mount the image mikrotik-X.XX.X.iso(at the time of reading the article, the version is clearly not the one presented at the link above).
Great, we launch the virtual machine and follow the steps of the installation wizard, that is, we select the installation of all components, and on and on. The installation is complete, unmount the .iso image and boot from the virtual hard. The download is complete, but our virtual Mikrotik has no connection to the local area, much less the Internet. Its interface ether1 need to be configured. You can do this from the console of the virtual machine if you are friends with terminal commands.
And if not, then everything is again not at all difficult. We need a program winbox(downloaded from offsite Mikrotik). If you manage at least one piece of hardware running RouterOS, this program is available on your working machine.
We launch winbox and open tab Neighbors. It is possible that far from one device will be displayed, but you and I are interested in something without an IP address and with the inscription x86 in the board column. We select it, the user is admin and without a password.
Next we need to set the IP. Which? From the pool that distributes the router to which the machine with VirtualBox is connected. Let's say it's a pool 192.168.88.0/24 , the machine gets 192.168.88.90, and our x86 will be 192.168.88.100, which is what we will set in the section IP > Addresses:
The Dude is a powerful application designed to scan networks and monitor the operation of connected devices (laptops, computers, routers). The software has a good potential in terms of functionality, which we hasten to tell you about in today's new review.
Let's start by tradition with the answer to the question, who needs the program? - First of all system administrators(it’s clear why), merchants and businessmen, Internet providers, as well as those users who want to “be in the know” of what is happening in the network processes (environment) of their device (for example, if they organize a mini office at home).
The Dude for Windows
In the process of monitoring, the scanner determines the types and types of detected devices, “draws” a map of the networks found (of any complexity), with which it will be easier for you to interact visually in the future. Also, you can make your own maps and work with them.I like its autonomy in the utility and auto mode scanning in the specified subnets, as well as the fact that if there are problems, the software issues a warning. If we talk about the other features of the software, they include:
- network layout + type recognition ∕ device brands;
- support for custom icons and backgrounds;
- work with SNMP, ICMP, DNS and TCP;
- channel monitoring, etc.
Help: operates on the basis of Windows 7 / 8 / 10, Linux.
Now a few words about the Mikrotik The Dude interface. It is quite concise, there is a Russian language. The main window contains the main keys, commands (there are quite a lot of them) and tabs - only 6. In fact, having a utility at hand, you can easily track any network changes, “ping” the connection and at the same time test it for reliability. There is a lot of necessary analytical information and specialized charts. Installing the client on a computer is standard, so we won’t talk about it too much.
With this utility, you will undoubtedly improve the performance of the network environment, you will be able to control and manage devices. Recently, developers with renewed vigor have begun to improve their "brainchild", and therefore please us updated versions. We hope you will evaluate the program as positively as thousands of users around the world have done.
You can download The Dude for free on our web portal via a direct link (from the official website) - the latest version is available.