Using the get-hosts module in discovery mode, using -r "ip" of a router or firewall (likely the default gateway) that does know anything about cdp or lldp neighbors is less or more useless. Discovery stops after 1 node. This is by design.
Of course -r could start at the first switch ip in the tree and ignore the router/firewall ip, but then using the arp discovery on these switches does not bring much useful information either. This is by design also, since the switch does not necessarily talk to devices, especially in VLANs where a switch does not have a management IP. Moreover -n has to be used on all switches that one must know from discovery mode.
Wouldn´t it be nice to have the behavior of the get-hosts single node module (using -n "ip" together with -r "ip" ) in the get-hosts module working in discovery mode by adding something like an "arp helper" ?
Example:
natlas-cli get-hosts -r "first switch ip in tree" --arp-helper "firewall/router ip" -c file -d depth
Using the get-hosts module in discovery mode, using -r "ip" of a router or firewall (likely the default gateway) that does know anything about cdp or lldp neighbors is less or more useless. Discovery stops after 1 node. This is by design.
Of course -r could start at the first switch ip in the tree and ignore the router/firewall ip, but then using the arp discovery on these switches does not bring much useful information either. This is by design also, since the switch does not necessarily talk to devices, especially in VLANs where a switch does not have a management IP. Moreover -n has to be used on all switches that one must know from discovery mode.
Wouldn´t it be nice to have the behavior of the get-hosts single node module (using -n "ip" together with -r "ip" ) in the get-hosts module working in discovery mode by adding something like an "arp helper" ?
Example:
natlas-cli get-hosts -r "first switch ip in tree" --arp-helper "firewall/router ip" -c file -d depth