The IP address for logging function is a DHCP server feature which allocates IP addresses to clients. It also records the information about each IP address allocation and the conflict, renewal or release of addresses. The logging function is useful for routine maintenance and fault location. To see the status of the logging function, use the display ip pool name command. Once you have created a global address pool, you can type the ip pool name command to see its status.
Outgoing Interface
The Outgoing Interface policy is used when the application protocol needs to match an IP address with a source. When the IP address matches a policy, the source IP address is translated to the outgoing interface, which prints a warning message. This rule is a good way to identify suspects and narrow down the list.
The IP address of the requesting host is recorded in the DNS logs. You can use this information to determine which DNS requests are causing the problem.
Configured IP Address
Logging from an IP address is not supported by TACACS and RADIUS. These protocols require a database that contains the full range of valid IP addresses. This can make system logging on the 192.168.o.1 server difficult to interpret. If the same IP address is used on both the server and the client, the logging results will not be consistent.
IP addresses are assigned by Internet service providers (ISPs). IP addresses can either be dynamic or static. Static addresses are usually more expensive than dynamic addresses. Some ISPs don’t provide static addresses. If you’d like to have a static IP address, you’ll have to configure it manually.
SNIP/MIP
You need to know the SNIP/MIP IP address for your logging solution. In addition, you also need to know the port for the logging. Port number is important, as you need to be able to send and receive data through the remote SNIP.
SNIP is used by Netscaler appliances to connect to a subnet. It is similar to the local network of the appliance. This is useful when the backend servers are directly connected to L2 switches and are in a different subnet than the NetScaler.
Backend server IP address
In order to log to your backend server, you need to know the IP address of the server. You can set this by adding a listener to the management console. Afterwards, you can change its settings. Click on the listener’s name to edit the settings. You can also configure its port.
If you don’t use a reverse proxy, your server should be able to log the IP address of the client. This address is usually available in your backend server logs or scripting languages. Many HAProxy users struggle to obtain this address. In a number of cases, they try modifying the script or the code that logs to the server.
XFF header
An XFF header is used to capture IP addresses of requests to a web server. The header is also used by server-based web analytic tools. The information is used by many different applications, including standard web applications and endpoint applications. The XFF header can also be used by proxy servers.
Most web applications use the origin IP address to identify a user. For instance, if a user attempts to log into a member area of a website, an X-Forwarded-For header will be needed. In most cases, this header contains the IP address of the client that initiated the request.