Wireshark mailing list archives
Re: newbie question
From: M K <gedropi () gmail com>
Date: Wed, 28 Apr 2010 07:49:38 -0800
Within Preferences>Protocols>HTTP do you have the correct ports listed? Are you able to filter on tcp.port==8080 alone first before making it into a compound filter? If I am remembering correctly, after installing the virtual 127.0.0.1 from MS, I think that you need the correct interface to do the capture. On 4/28/10, Aaron Stromas <passogiau () gmail com> wrote:
Greetings, I am trying to capture HTTP traffic on my local box. The HTTP server is listening on port 8080, and the client (browser) also running on the local box submits requests to http://localhost:8080/... I've tried this filter http and (ip.dst_host==localhost || ip.dst==127.0.0.1) and this one tcp.port==8080 and (ip.dst_host==localhost || ip.dst==127.0.0.1) but nothing get captured! I expect, I'm missing something basic but what? TIA -- Aaron Stromas
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- newbie question Aaron Stromas (Apr 28)
- Re: newbie question Abhik Sarkar (Apr 28)
- Re: newbie question Aaron Stromas (Apr 28)
- Re: newbie question M K (Apr 28)
- TLS Alert Fatal Messages Sheahan, John (Apr 28)
- Re: TLS Alert Fatal Messages Sake Blok (Apr 28)
- Re: TLS Alert Fatal Messages Sheahan, John (Apr 28)
- TLS Alert Fatal Messages Sheahan, John (Apr 28)
- Re: newbie question Aaron Stromas (Apr 28)
- Re: newbie question Phil Paradis (Apr 28)
- Re: newbie question Abhik Sarkar (Apr 28)