>>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.
Tillbaks till lista