Regarding point 2:

Winpcap is programmed as a TDI (transport device). It's positioned above (or
after) the itnermediate and lower level drivers. This means that if ZA
blocked anything, then you won't get it, nor the TCP/IP stack. So it's
really a question of what exactly ZA blocks.

Daniel

----- Original Message ----- 
From: "Joe Acquisto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 2:23 PM
Subject: [WinPcap-users] PPP, zonealarm


> I'm posting to this list, per suggstion of the ethereal folks.  You may
ignore item 1, if you wish, as does
> not pertain to this list, directly.
>
> Actually, item 2, while not answered, appears to be hinted at in the docs,
far as reliability is concerned.
>
> But, I'd like a bit more info, if possible.
>
> Here goes -
>
> >>>
> I noted the posts on W2k and PPP.
>
> 1 - On win98 (winpcap 2.3) I can capture packets on the PPP adapter (dial
up networking).  Is it not
> supposed to do this?
>
> 2 - I was tasked with a challenge to monitor a dial up connection with
ZoneAlarm active.  This brings up a
> question in my mind as to how winPcap and ZoneAlarm mingle (or not) and
what I should expect,
> running ethereal and ZoneAlarm at the same time.  I guess I'm going
toward - can I count on ZA to block
> all packets?  If I see "leakage" is this due to a ZA fault or because
ethereal/winpcap are looking on the
> "wrong side" of the firewall?
>
> As you can see, I don't have a clue.
>
> joea.
>
>
>
>
>
>
>
> ==================================================================
>  This is the WinPcap users list. It is archived at
>  http://www.mail-archive.com/[EMAIL PROTECTED]/
>
>  To unsubscribe use
>  mailto: [EMAIL PROTECTED]
> ==================================================================
>




==================================================================
 This is the WinPcap users list. It is archived at
 http://www.mail-archive.com/[EMAIL PROTECTED]/

 To unsubscribe use 
 mailto: [EMAIL PROTECTED]
==================================================================

Reply via email to