From: "Dave Saville" <os2-wireless_users@2rosenthals.com>
Received-SPF: pass (secmgr-ny.randr: domain of deezee.org designates 81.187.184.98 as permitted sender) client-ip=81.187.184.98; envelope-from=dave@deezee.org; helo=mail.deezee.org.uk;
Message-ID: <004-03649047-11320.002@deezee.org>
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Date: Fri, 18 Jan 2008 08:32:03 +0000 (GMT)
Priority: Normal
User-Agent: PMMail/2.90 (os/2; U; Warp 4.5; en-GB; i386; ver 2.90.04.0852)
In-Reply-To: <list-1594935@2rosenthals.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [OS2Wireless] Logging network activity from VPC

On Fri, 18 Jan 2008 09:07:40 +0100, Jan van Wijk wrote:

>Hello Hakan,
>
>On Thu, 17 Jan 2008 23:04:49 -0500 (EST), Hakan wrote:
>
>>I have a Win application I run in VPC under Win 2000.  This application=

>>communicates with my TiVo DVR and I'd like to see if I can write a
>>small application under OS/2 to transfer files back and forth between
>>the computer and the TiVo.
>
>OK, sounds like a nice reverse-engineering project :-)
>
>>Can I use the OS/2 program -- is it tracert=3F -- to log network activi=
ty
>>that originates from an application running in VPC=3F
>
>No, tracert is 'trace route' and is a little tool to see how TCP/IP
>packages are being sent to a specific URL. It displayes all
>the intermediate nodes visited while underway ...
>
>To really trace TCP/IP traffic contents you need a sniffer
>program that can do that. There are quite a few for Windows
>and Linux, but I am not sure there is something for OS/2.
>
>These programs have device-drivers that hook to the
>network card and can filter out and interpret TCP/IP
>(or other protocols) packets from there.
>
>There are also dedicated LAN-sniffer machines that
>can be attached to a router or switch that can monitor
>or trace the traffic on a whole LAN ...

I *think* it depends on VPC using virtual switch or not. In the former
case a sniff on the host will *not* see any packets, I know 'cos I
tried it, but the fake NAT the other mode uses ought to show up.

Also bear in mind that if you use say a *nix box on the network to
sniff then you need a hub and not a switch. Otherwise the sniffer won't
see anything. There are methods around to sniff switches but it is a
lot of faffing about. I keep a hub on my network and if I need to sniff
a box I move it's ethernet cable and the *nix box's one to the hub.

-- 
Regards

Dave Saville