Logging a person’s IP address is not impossible. You can use the message logging policy to log the IP address of a requester. For more information about message logging, see the documentation link. Another option is to use attribute logging, which shows the requester’s IP address. These methods may require advanced knowledge about IP address logging and are not recommended for all situations. However, if your IP address is critical to your business, it is possible to log the information based on the IP address of the requester.
Luminate Online
To ensure that Luminate Online doesn’t use the IP address of a site visitor, you must have a system administrator account and configure the Luminate Online web services to use the IP address. You can configure the Luminate Online web services by specifying the IP range of allowed servers and generating a default partition for the database. This partition restricts the access of website visitors to constituents and not site administrators. If you want Luminate Online to use your IP address for logging, you must configure the Luminate Online web services to run on a different system. If you’re not sure what the API key is, you can leave it blank.
Luminate Online’s server API requires a user to add the IP address of the machine they’re using to allow access to the website. You can do this by adding the local IP address of the machine where the Luminate server is installed to the IP whitelist. Alternatively, you can regenerate the connector by using the company’s management dashboard. This is a simple process that will regenerate the connector in Luminate.
LiveJournal
LiveJournal records IP addresses of commenters additional hints for security and auditing purposes. While this information is not personally identifiable and does not point to your home, you can use it to identify who is commenting on your journal. You can also enable commenting or disable it altogether. Using the “IP address log” option in the My Account Settings, you can choose whether to log IP addresses for everyone, anonymous commenters, or nobody.
After you log in, you can select whether or not to save the IP address in the cookie. In most cases, LiveJournal will only save the IP address in the cookie, so dial-up users will not be affected by this. If you have dial-up Internet access, you should not use this feature because it discourages account hijacking. To protect yourself from being logged out, you should disable this option, which deletes all current logging sessions. You may also want to bind your IP address to a username to prevent the cookie from being stored in the wrong place.
Avi Service Engines (SEs)
The underlying reason that Avi Service Engines (SEs) use an IP address for logging is because they need to be able to access the internet. This is because they perform data plane operations, which require direct or routable network access. To enable IP logging, it is best to configure the SEs to use a static IP address. Otherwise, you will lose data when you log in to your SE.
You can allocate IP addresses to each SE individually or as a group. The Networks tab of your AVI Controller contains many network settings, such as the logging settings. The Service Engine Edit popup allows you to customize these settings. Changes made to the Network tab will apply to any new SE created in write access mode. However, if you change the settings on a single SE, you can also change the IP address for the whole group of SEs.
Avi Service Engines (SEs) source-NAT (SNAT)
An SE’s source-NAT IP address is assigned to it by default. You can allocate a different IP address for each SE via the Networks tab. You can configure a number of network settings for your SEs via the Networks tab, as well as through the Service Engine Edit popup. Your network settings for the SE will apply to any new SE that is created in write access mode. However, you can also customize a specific SE’s SNAT IP address for logging.
The SEs are installed on the servers using the Avi Controller. It manages all the SEs and is deployed in a redundant three-node cluster. You can view the details of each SE in the Control Panel by expanding the table. Click on an SE’s name and you’ll be taken to its page. Clicking on the SE’s icon will show you the health score of the engine. Hovering your mouse over it displays the health score breakdown.