| Localip.txt processing [message #148562] |
Fri, 14 August 2020 12:57 |
 |
Gekus123
Messages: 1
Registered: July 2019
Location: Moscow, Russia
|
|
|
|
My request is to change localip.txt processing. Now it can contain only one fixed IP. Please see for information: https: //support.gfi.com/hc/en-us/articles/360012853254-Configuring -an-Agent-to-Return-a-Specific-IP-Address-to-GFI-LanGuard.
It will be better that file can contain local IP ranges or CIDRs.
My situation is following.
Target hosts obtain local IPs from DHCP (e.g. 172.30.0.0/16). This is main local IP to communicate with other hosts (including Languard console).
There are others local IPs on the host. Hyper-V, WSL2, Docker, VirtualBox additionally assign local IP and non-domain scan target name (like HOST.DOCKER.INTERNAL). This violates the integrity of the domain infrastructure and OU in Languard.
I need the hosts reports IP from predefined IPs range (taken e.g. from localip.txt) and correct domain-specific scan target name.
|
|
|
|
Members
Search
Help
Register
Login
Home
