First, there is no simple solution for this problem. It involves filter
driver and and simple encryption filter driver is contradiction in terms.
Count with months of development and don’t forget to study IPSEC RFCs for
standards.
NDIS IM driver is standard encryption firewall solution. As for
communication, Bryan already answered it; there is no real problem.
As for passthru, I’d recommend to use it for reference and write own driver
from scratch. It is IMHO the only way how to really understand the code and
believe me, you’ll need it during debugging.
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]
From: xxxxx@mynetsec.com[SMTP:xxxxx@mynetsec.com]
Reply To: xxxxx@lists.osr.com
Sent: Saturday, May 03, 2003 8:07 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Revised Query: Is NDIS intermediate a valid option
for me?Hi (again),
I am trying to develop a simple solution which handles (drops or encrypts)
the packets depending upon the target machine.Driver is maintaining a list
of target machines, which are eligible for this action (drop or encrypt).
This list is changing dynamically (user changes the configuration).
Earlier I posted the query [Interacting intermediate NDIS drivers]
assuming
that user can update this list by sending some request directly to NDIS
IM.
But I am not sure whether NDIS IM is a good solution for this. If yes,
then
in brief, what are the steps to be taken in “passthru” example.Any suggestions?
Thank you all for your invaluable suggestion.
–
Amit Manocha
You are currently subscribed to ntdev as: michal.vodicka@st.com
To unsubscribe send a blank email to xxxxx@lists.osr.com