Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Source IP addresses in Proxy/HTTP History

Bug | Last updated: Jun 24, 2015 07:24AM UTC

It would be great if an additional column for the source IP address would exist, so we could see which client makes the selected request.

PortSwigger Agent | Last updated: Jun 24, 2015 08:02AM UTC

Thanks for this request. Virtually all users employ Burp as a single user on the same machine as their browser. Can you describe your use case where you need to identify the source IP address of incoming requests, so we can assess the value of this possible change? Thanks.

Burp User | Last updated: Jun 30, 2015 09:11AM UTC

I use Burp on a dedicated machine, this has two advantages for me: - I can use it on systems, where I am not able to install Burp (e.g. proprietary operating systems or Burp not supported on that platform, embedded devices etc.) - I can use this proxy on multiple machines and don't have to install it everywhere or install it again when I reinstall this machine. I see that the localhost use case is more common, I have it also on some machines running locally.

PortSwigger Agent | Last updated: Jul 20, 2015 01:55PM UTC

I've just coded a simple extension that helps with this: - https://github.com/pajswigger/show-client-ip

Burp User | Last updated: Jan 31, 2018 09:29AM UTC

+1 Using Burp to intercept traffic from many machines and I'd like to be able to tie the request to its origin.

Burp User | Last updated: Feb 06, 2018 03:39PM UTC

Ditto. I sometimes use Burpsuite to proxy our java applications so I can see web calls going out and to where, but I have a few servers in the cluster going through 1 burpsuite, so source IP would greatly help here.

Burp User | Last updated: May 03, 2018 09:26PM UTC

+1 to this request. A use case example: I'm working on some IoT device security testing and setup the devices to proxy their communications through my Burp instance, running on a test network. I would like to know which device is issuing the request, as they are all communicating to each other and the internet. Instead of watching tcpdumps for each and correlating, it would be great to have this column in BurpSuite.

Burp User | Last updated: Jul 11, 2018 10:19AM UTC

+1 to this. Working with multiple devices and would like to identify each of them.

Liam, PortSwigger Agent | Last updated: Jul 11, 2018 10:34AM UTC

We still have this logged in our development backlog. Unfortunately, we can't provide an ETA.

Burp User | Last updated: Oct 04, 2018 12:14PM UTC

+1. I'm also using it to intercept traffic from multiple devices.

Burp User | Last updated: Jan 05, 2019 07:20AM UTC

+1 I also use burp to intercept requests from multiple devices and it will be a great feature and time-saving to know the source request ip.

Burp User | Last updated: May 29, 2019 03:38PM UTC

+1 I am testing multiple clients over a long period of time.

Roy | Last updated: Feb 25, 2021 08:10PM UTC

Hi Burp team. Just pinging you on this again as it is still needed! Please consider bumping it up in the backlog?

Liam, PortSwigger Agent | Last updated: Feb 26, 2021 03:46PM UTC

We've added a note to the development story of your interest in this feature. Thanks!

Hannah, PortSwigger Agent | Last updated: Mar 23, 2021 03:25PM UTC

Unfortunately, on review of this feature request, it has been decided that we will not be implementing this functionality.

Shomi | Last updated: Jun 26, 2024 08:04AM UTC