Date: Fri, 7 Apr 2006 15:27:49 +0300 From: Nikos Vassiliadis <nvass@teledomenet.gr> To: freebsd-questions@freebsd.org Cc: Karl Pielorz <kpielorz@tdx.co.uk> Subject: Re: OT: tcp redictor with dump-(in|out)put-to-stdout capability Message-ID: <200604071527.50074.nvass@teledomenet.gr> In-Reply-To: <62E5CE298B1A036558020135@unsupported> References: <200604071132.05193.nvass@teledomenet.gr> <200604071500.27465.nvass@teledomenet.gr> <62E5CE298B1A036558020135@unsupported>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 07 April 2006 15:10, Karl Pielorz wrote: > >> Why dont you wish use tcpdump? > > > > Cause I want to debug http, which is ASCII. Having every > > tcp segment in hex and/or ASCII won't help much. > > 'GET / HTTP/1.1' is much easier to read than the hexdump. > > 0x4174206c6561737420666f72206d653a29 > > Have you tried tcpflow? That can either dump the actual flows to files - or > you can dump them to the console... > I have already found what I was looking for. net/balance:) > If you're sending it to the console, and it might be gifs / other binary, > piping it through 'strings' is usually a good idea :) > > -Kp > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604071527.50074.nvass>