From 71f5a2e92ab972f69af7015ce331f64ca763a38b Mon Sep 17 00:00:00 2001 From: Aroop 'FinlayDaG33k' Roelofs Date: Fri, 9 Feb 2024 13:04:53 +0100 Subject: [PATCH] Update README.md Update documentation to make remote DHCP resolution easier to understand --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 493d5b4..6fbc85a 100644 --- a/README.md +++ b/README.md @@ -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: