i've seen this behavior on XP ( the bridge not working) without winpcap
being any where near the box. i've never been able to get connection sharing
working. I must admit though that i haven't tried that much. moved to linux
to handle the complex stuff.

as far as the IEEE1394 crashing is concerned, i see similar behavior when i
accidently try to attach to the ndiswan adapter. i know that there are
issues with attaching to wan adapters w/ winNT/2k/XP, but i didn't think my
machine would instantaneously reboot.

anyone know why it does that? just curious, because my solution was to never
attach to the wan thing again.

Jake Helfert
[EMAIL PROTECTED]

----- Original Message -----
From: "Denis Bujoreanu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 20, 2002 1:55 AM
Subject: Re: [WinPcap-users] IP1394 reboot under Windows XP


> I also encountered something strange about networking with FireWire ports
on
> WinXP, namely if an ethernet adapter and a firewire adapter are coupled
> together in a bridged adapter (or something like that) the networking
ceases
> to function, no more IP conectivity no nothing. I don't believe it's a
> WinPcap bug, it looks like it is a NDIS bug if working with firewire
> adapters. I know NDIS 5 introduces an intermediate driver layer in the
NDIS
> binding stack to support devices like ATM, USB or IEEE1394. Could this be
> the problem? So far I don't know of any ATM interface cards for NDIS,
> perhaps there are but haven't seen nor worked with them yet.
>
>
> Denis
> ----- Original Message -----
> From: "Loris Degioanni" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, September 19, 2002 10:28 AM
> Subject: Re: [WinPcap-users] IP1394 reboot under Windows XP
>
>
> > To be honest, I've noticed that after installing WinXP WinPcap starts
> > showing the firewire adapter of my laptop, but I've no idea what to do
> with
> > it, so I never tested it.
> > Evidently, the driver of your Firewire adapter doesn't like WinPcap, but
> > it's difficult to understand if the cause is a bug in the WinPcap driver
> or
> > if it's due to some non-standard behaviors of NDIS or of the Firewire
> > driver.
> > Can you explain me how can I use my firewire adapter to make some tests?
> >
> > Loris
> >
> > ----- Original Message -----
> > From: "thomi markus" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, September 17, 2002 2:14 PM
> > Subject: [WinPcap-users] IP1394 reboot under Windows XP
> >
> >
> > Hello all
> >
> > I'm developing software for IP1394 (IP over Firewire).
> > Unfortunately the WinpCap driver can not capture packets
> > >From the Windows XP IP1394 driver.
> >
> > On the first read or write to or from the Firewire adapter the WinpCap
> > driver
> > Is rebooting the system.
> >
> > Can anybody help or is aware of this problem ?
> >
> > I'm using the latest WINPCAP 3.0.
> >
> > Thanks for any help and have a nice day
> > Markus
> >
> >
> >
> > ======================
> >  This is the WinPcap users list. It is archived at
> >  http://www.mail-archive.com/[email protected]/
> >
> >  To unsubscribe use
> >  mailto: [EMAIL PROTECTED]?body=subscribe
> > ======================
> >
> >
> >
> > ==================================================================
> >  This is the WinPcap users list. It is archived at
> >  http://www.mail-archive.com/[email protected]/
> >
> >  To unsubscribe use
> >  mailto: [EMAIL PROTECTED]?body=unsubscribe
> > ==================================================================
>
>
>
> ==================================================================
>  This is the WinPcap users list. It is archived at
>  http://www.mail-archive.com/[email protected]/
>
>  To unsubscribe use
>  mailto: [EMAIL PROTECTED]?body=unsubscribe
> ==================================================================
>



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

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

Reply via email to