Re: [WinPcap-users] Capture Filter on port - strange behavior

2005-05-09 Thread James Garrison
I should have thought of that :-) However, when I do what you suggest, the offline filter shows BOTH sides of the conversation. The problem seems to occur only when filtering during an actual live capture. I have followed the website procedures for submitting a bug and sent the info to the

Re: [WinPcap-users] Capture Filter on port - strange behavior

2005-05-06 Thread Vasily Borovyak
Hello James, I'm using Ethereal 0.10.3 and WinPCap 3.0. WinXP-SP2 Filter was port 25. And I've captured both incoming and outgoing packets. So, the problem I think is in the Ethereal sources. P.S. src port 25 || dst port 25 filter works fine too. JG Originally posted on ethereal-users,

Re: [WinPcap-users] Capture Filter on port - strange behavior

2005-05-06 Thread Guy Harris
Vasily Borovyak wrote: I'm using Ethereal 0.10.3 and WinPCap 3.0. WinXP-SP2 Filter was port 25. And I've captured both incoming and outgoing packets. So, the problem I think is in the Ethereal sources. Unlikely, given that Ethereal doesn't do anything particularly unusual with libpcap/WinPcap

[WinPcap-users] Capture Filter on port - strange behavior

2005-05-05 Thread James Garrison
Originally posted on ethereal-users, referred to winpcap-users from there. Running on Windows XP SP2 with Ethereal versions 0.10.10 and WinPCap 3.0. If I provide the following capture filter: port 25 in order to capture an SMTP transaction, I see only packets with destination port 25 -- I.e. I