From: "Hakan" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.3) with ESMTP id 1595666 for os2-wireless_users@2rosenthals.com; Fri, 18 Jan 2008 13:03:41 -0500 Received-SPF: none (secmgr-ny.randr: 74.208.4.196 is neither permitted nor denied by domain of meddatainc.com) client-ip=74.208.4.196; envelope-from=agents@meddatainc.com; helo=mout.perfora.net; Received: from mout.perfora.net ([74.208.4.196]) by secmgr-ny.randr with esmtp (Exim 4.43) id 1JFvYx-0003mi-LM for os2-wireless_users@2rosenthals.com; Fri, 18 Jan 2008 13:03:37 -0500 Received: from progstn (pool-70-20-217-42.phil.east.verizon.net [70.20.217.42]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JFvYl0tIP-0008DU; Fri, 18 Jan 2008 13:03:20 -0500 To: "OS/2 Wireless Users Mailing List" Date: Fri, 18 Jan 2008 12:56:45 -0500 (EST) Reply-To: "Hakan" Priority: Normal X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [OS2Wireless] Logging network activity from VPC Message-Id: <0MKpCa-1JFvYl0tIP-0008DU@mrelay.perfora.net> X-Provags-ID: V01U2FsdGVkX18vFyjv/dpNqXYj/WpEggf8DEkZPrzf3NsAzqR hbF9EWDUiaxord3TDltyW4Qus0VtwfLNjyIo348mdAX+U4nAbE jJMH8hnFrgHIUL/3piCvg== X-Spam-Score: 0.9 (/) X-Spam-Report: 0.9 MSGID_FROM_MTA_ID Message-Id for external message added locally Dave, >>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. I was hoping that the 'net traffic originated by the Win application running in VPC would then be "managed" by the host operating system, i.e., eCS 1.2MR in my case, and that a program that logs all network card traffic would log also this traffic. Given that I would not do anything else on the 'net at the same time, I am hoping that it would be feasible to figure out what the Win application sends and receives.