how to find Load balancer IP Address from host - linux

I am on of the linux server and I have to identify the Loadbalancer IP address to which this linux server is added to.
As per the image , I am on one of the Linux Server and trying to find the IP address of LB or IP address from where traffic is coming to Linux Server .

In server after logged in.
You can use command
"ifconfig"
But if you have load balancer alias name or IP address you can use 'ping website/ip'
IP address is not fixed for Load Balancer because load balancer provide multiple IPs by location and zone.
You use 'getaddrinfo' command and get information.
Also you can use nslookup www.example.com
If you are using AWS EC2 load balancer you can get IP address using AWS API.

Related

How to ping the load balancer ip address from Virtual machine in azure

I have created a internal load balancer in azure and backend pool configured two vm's health probe and rule also configured, If I browse the Load balance ip it work fine but while i'm checking the ping request from the VM to Load balancer it shows time out error. Is it possible to make a successful ping request.
Regular icmp traffic is not allowed on Azure load balancers, you should either try a port ping (psping), telnet, nmap, nc, or other utilities to check E2E connectivity.
Some extra details here:
https://social.msdn.microsoft.com/forums/azure/en-US/e9e53e84-a978-46f5-a657-f31da7e4bbe1/icmp-outbound-ping-on-azure-vm
Not only ICMP, any traffic from backend VM to frontend IP of internal load balancer will not work. This is one of the limitation of azure internal load balancer.
Bhuvanesh Kumar Kumaresan, Cloud Solution Architect

xss-attack took place in our webapp hosted in Azure. How to find the IP address of the attacker Machine?

Our webapp had a XSS attack today and i work in the monitoring team. My client want to confirm the IP address of the attacker. How to find the IP address of the attacker machine.
Look for the access logs. Something like the apache access logs. Once you have identified the request, take the corresponding IP address.
Bear in mind and check following:
That the IP address is external and not e.g. of your load balancer.
If the IP belongs to your load balancer, check the logs on your log balancer or check the X-Forwarded-For header value.
Most probably the IP address will not help at all, because if the attacker was not stupid, he used TOR or proxy himself to hide his real IP address. All you will get will be the exit TOR node IP address or proxy address.

Load Balancer IP Configuration

We have configured load balancer with 2 Linux virtual machines. we have planned to remove one server from the Load balancer and Load balancer too. Is there any possibility to assigning the load balancer ip address to remaining server.
E.g
We have VM1 and VM2 and both configured with load balancer. is there any way to assign load balancer IP to VM1.
Short answer, yes. Public IP are resources of their own in ARM.
Confirm the existing Frontend IP address is static
Assign LB an additional Frontend IP
Remove existing Frontend IP
Associate IP with VM1's nic
Done

HTTP_X_FORWARDED_FOR returns Load balancer IP how to get the real IP

Our sites use a load balancer. The server variable "HTTP_X_FORWARDED_FOR" returns the load balancer ip address, Is it possible to bypass the load balancer and get the actual user IP

MS network load balancing with multiple host header

Currently, I have a webserver running multiple websites. All these websites each have a host name of xxx.domain.com. I am told to implement MS load balancing on the server. After I have implemented NLB to cluster to 2 server, how am I supposed to bind the websites using host name ? Below is my NLB configurations:
webserver01 IP : 10.10.0.1
webserver02 IP : 10.10.0.2
ClusterIP IP : 10.10.0.3
website 1 is to have a hostname of web1.domain.com
website 2 is to have a hostname of web2.domain.com
Thanks
Joe
Its pretty simple just replace the IP of
website 1 hostname of web1.domain.com with Cluster IP in DNS
website 2 hostname of web2.domain.com with Cluster IP in DNS
in your case ClusterIP IP : 10.10.0.3
because when we create NLB the Cluster IP is directly transfer your request to the nodes
It works. I have already checked it.

Resources