Forum Discussion
F5 Internal IPs Nessus Scans
I just can guess: He is scanning a network range where the virtual ips sitting and the mgmt-ip. He is scanning the self-ip and has port-knockdown not disabled. So nexuss is listening the same problems on the mgmt ip and self ip.
BUT ... I dont understand how he is asking for his management IP when he must be logged in already to the gui. So he does not know what "mgmt ip" means or is ... but is administrating nexus and bigip ...
times are wild
But he clearly said that scaning self ips does not work. So port lockdown must be enabled.
Of course accessing gui should be done through mgmt ip, unless there is another tmm ip which allowing https.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com