We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As some machines aren't as visible to standard scans. Adding a few more options to the tool box to grab all the machines on the network
Feature Idea
nmap.py
plugin: community.general.nmap address: 192.168.1,2,3,4.0/24 strict: no ipv4: yes ports: yes cache: no sudo: yes cache_connection: './cache/ansible_inventory_cache' cache_timeout: 86400 icmp_timestamp: yes dns_resolve: yes udp_scan: yes groups: subnet1_vm: "'.1.' in ip" subnet2_vm: "'.2.' in ip" subnet3_vm: "'.3.' in ip" subnet4_vm: "'.4.' in ip"
The text was updated successfully, but these errors were encountered:
Pull request attached #5566
Sorry, something went wrong.
No branches or pull requests
Summary
As some machines aren't as visible to standard scans. Adding a few more options to the tool box to grab all the machines on the network
Issue Type
Feature Idea
Component Name
nmap.py
Additional Information
plugin: community.general.nmap
address: 192.168.1,2,3,4.0/24
strict: no
ipv4: yes
ports: yes
cache: no
sudo: yes
cache_connection: './cache/ansible_inventory_cache'
cache_timeout: 86400
icmp_timestamp: yes
dns_resolve: yes
udp_scan: yes
groups:
subnet1_vm: "'.1.' in ip"
subnet2_vm: "'.2.' in ip"
subnet3_vm: "'.3.' in ip"
subnet4_vm: "'.4.' in ip"
Code of Conduct
The text was updated successfully, but these errors were encountered: