From: "Hakan" <os2-wireless_users@2rosenthals.com>
Received-SPF: none (secmgr-ny.randr: 74.208.4.195 is neither permitted nor denied by domain of meddatainc.com) client-ip=74.208.4.195; envelope-from=agents@meddatainc.com; helo=mout.perfora.net;
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Date: Fri, 18 Jan 2008 15:39:05 -0500 (EST)
Reply-To: "Hakan" <agents@meddatainc.com>
Priority: Normal
In-Reply-To: <list-1595757@2rosenthals.com>
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-1JFy0h2Sv5-0008KN@mrelay.perfora.net>

Dave,

I won't be able to try until early next week but if iptrace does /not/
see any traffic, and since this is a Win application in VPC, I should
be able to log the activity using another Win program running
simultaneously under VPC.

Does anyone have any recommendation for such a program?  Free, of
course...

On Fri, 18 Jan 2008 19:04:11 +0000 (GMT), Dave Saville wrote:

>On Fri, 18 Jan 2008 12:56:45 -0500 (EST), Hakan wrote:
>
>>Dave,
>>
>>I wsas 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.
>
>iptrace should see it - provided you are not using virtual switch. I
>know that does *not* work. If using the NAT mode does not show up in
>iptrace then *nothing* you run on the host will see anything. As I said
>you will need a hub and a *nix box with snoop or similar on it. 
>
>The reason you need a hub is that hubs send everything they get to all
>ports. Normally a box only acts on packets with it's own address in. A
>sniffer gets the NIC to pass everthing and that is how it sees the
>packets from the other machine. A switch OTH makes "virtual circuits"
>between it's ports because it "knows" what is connected to each. So a
>box can not see anything not directed at it. This is why, with a hub, a
>massive FTP between two boxes will kill performance for everything
>else. With a switch you don't notice anything - because you never see
>the FTP packets.
>
>HTH
>
>-- 
>Regards
>
>Dave Saville
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>This message is sent to you because you are subscribed to
>  the mailing list <os2-wireless_users@2rosenthals.com>.
>To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
>To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
>To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
>Send administrative queries to  <os2-wireless_users-request@2rosenthals.com>
>To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
>Web archives are publicly available at: http://lists.2rosenthals.com
>
>This list is hosted by Rosenthal & Rosenthal, LLC
>P.O. Box 281, Deer Park, NY 11729-0281. Non-
>electronic communications related to content
>contained in these messages should be directed
>to the above address. (CAN-SPAM Act of 2003)
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>