KevinMidboe/mktxp-no-cli
1
0
Fork 0
mirror of https://github.com/KevinMidboe/mktxp-no-cli.git synced 2025-10-29 09:40:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #109 from FinlayDaG33k/patch-1

Browse Source 
Update README.md
This commit is contained in:
Arseniy Kuznetsov
2024-02-09 13:49:20 +01:00
committed by GitHub
parent fcbb033ab2 71f5a2e92a
commit 1be2ed805b
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -277,7 +277,15 @@ When gathering various IP address-related metrics, MKTXP automatically resolves
```
remote_dhcp_entry = None # An MKTXP entry for remote DHCP info resolution in capsman/wireless
```
`MKTXP entry` in this context can be any other mktxp.conf entry, and for the sole purpose of providing DHCP info it does not even need to be enabled.
`MKTXP entry` in this context can be any other mktxp.conf entry, and for the sole purpose of providing DHCP info it does not even need to be enabled.
An example below:
```
[RouterA]
... # RouterA settings as normal
[RouterB]
remote_dhcp_entry = RouterA # Will resolve via RouterA
```
### Connections stats
With many connected devices everywhere, one can often only guess where do they go to and what they actually do with all the information from your network environment. MKTXP let's you easily track those with a single option, with results available both from [mktxp dashboard](https://grafana.com/grafana/dashboards/13679-mikrotik-mktxp-exporter/) and the command line: