in fact would a capture filter of "host proxy.mycompany.com and host
<my local host ip>" be enough to solve this? i.e. would wireshark
then, irrespective of the actual proxy server my request gets assigned
to (noting there are several nominated under the one DNS name for
resiliency), just double check that the IP address for this proxy
server resolves to "proxy.mycompany.com" and then if it does put it in
scope?
On 13 August 2010 15:08, Greg Hauptmann <greg.hauptmann.ruby@xxxxxxxxx> wrote:
> Hi,
>
> Can anyone advise how I could set up a filter that covered off only
> traffic that is
>
> (a) going in/out through the company internet proxy [e.g.
> proxy.mycompany.com] - note here I want to be able to put the DNS name
> for the proxy here [as there can be a number of different IP's that
> DNS may issue back to give you your specific proxy server to use]
>
> (b) to/from my PC that is running wireshark?
>
>
> thanks
>
--
Greg
http://blog.gregnet.org/
