From: "ghand" <ghand45@hotmail.com>
Reply-To: "ghand" <ghand45@hotmail.com>
Subject: Re: test protocol at client?
Newsgroups: comp.os.linux.networking
References: <4f76acb9$1@x-privat.org> <as4j49x081.ln2@news.roaima.co.uk>
NNTP-Posting-Host: $$_ewhrlensdzs.feeder.x-privat.org
Message-ID: <4f7963cc$1@x-privat.org>
Date: 2 Apr 2012 10:31:08 +0100
Organization: X-Privat NNTP Server - http://www.x-privat.org
Lines: 28
X-Authenticated-User: $$wp9v91t666kpbjaqevnc6hy$bm0
X-Complaints-To: abuse@x-privat.org
Path: csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.x-privat.org!x-privat.org!not-for-mail
Xref: csiph.com comp.os.linux.networking:1225


Chris Davies <chris-usenet@roaima.co.uk> wrote:
>ghand <ghand45@hotmail.com> wrote:
>> but is there anything that can test the protocol being used by a
>client?  
>
>Not meaningfully, no, short of sniffing the wire between client and
>server.
>Chris

OK so I suppose it can't set itself up as a server let the client connect,
and then detect what protocol is used at the client?

How about..

Suppose I have a client and SOCKS server, and sniff the packets between them
and capture them. (with tcpdump)

I have done that with a SOCKS server I have. And i'd like something to detect
whether the packets, are SOCKS4 or SOCKS5.

Wireshark doesn't seem to tell me.

Is there anything that would? 

What are my options for what would tell me?