CIPE-Win32 has 2 parts:
a) The CIPE adapter driver which is responsible for implementing the CIPE
adapters and their respective TAP devices. The network adapter will send any
packets it receives out of the TAP device. Conversely, anything sent to the
TAP device will appear to "leave" the adapter.
b) The CIPE service implements the (possibly encrypted) tunnel and handles,
usermode, all of the packets going through the TAP device/s.
On Monday 16 September 2002 09:00 am, Csabai Csaba wrote:
> Hi Everybody!
> I look CIPE-win32 source code. And it is very intresting for me.
> I watch this in code:
> - have adapter NDIS miniport code. I dont know what work it.
> - have userspace service, this is controll for kernel-space miniport
> service with ioctl, and IRJ controll. - have an userspace control panel
> applet. With use registry to communicate peer informations and controll
> userspace service.
> My questions:
> - What do the kernelspace NDIS miniport ? Only connect all ethernet card
> and create TAP devices ? - All communication on ethernet card go to
> userspace, or only that communication whit into the peer rules ? - Where
> determine witch packet is into peer rules ? (userspace, kernelspace, and
> where can i found it in source code ?)
> Sorry, for my bad english.