IP Filter Driver problem.

NTDEV
1

I have a working IP Filter Driver, by doing some re-working of Extended
Passthru and what not. I’ve managed to get a rather nice Firewall Style
application working on All types of Ethernet Connections. Oddly enough, I
notice the Driver is installed to any Dial-up connection I have, but I can’t
access it to send the Allow/Block lists or any other settings I require.

I’m aware this list has recieved, probably many, requests for help along
this topic, but each one I’ve come across(and I’m starting to get tired of
looking through old requests that lead no where and coming up with nothing)
has done nothing.

The way the driver works, is it utilizes the \DEVICE\ name of the NIC to
send the required information. I think I can re-write things to send a
general broadcast of the information, but that might also screw things up a
bit more than I’d like. I believe that all I need to do is Enumerate the
\DEVICE\ name of the Modem that’s intalled on the computer, and then I’ll be
on a roll.

Currently, and when I get my laptop back, I work on Windows 2000 and Windows
XP with their respective DDKs.

The reason I believe all I need is the \DEVICE\ name is because I made many
successful connections with the Driver active and there were no for-see-able
problems. All the list entries I read, were of people having trouble with
their Driver.

Direct solutions, links or a general idea of what I need to do(so I atleast
have a better idea of what to look for) is appreciated.

For the record, this is my first time writing to a list of the sort, but
I’ve spent 2 weeks searching(while getting everything else with respect to
the Project working) with no avail; so my last option is this.

I thank you all for atleast reading this, and my great appreciate goes out
to those who help.

Thanks,
Andrew Nielsen

2

I *think* you are asking how to send configuration data to your NDIS
Intermediate IP filter driver. If so, you need to create a pseudo
device via NdisMRegisterDevice() within your kernel mode driver and
communicate with this device from your user-mode control application
using the Win32 DeviceIoControl routine. The DDK documents this
routine. Apologies if I am answering the wrong question here.

Douglas.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Andrew Nielsen
Sent: 17 August 2004 12:51
To: Windows System Software Devs Interest List
Subject: [ntdev] IP Filter Driver problem.

I have a working IP Filter Driver, by doing some re-working of Extended
Passthru and what not. I’ve managed to get a rather nice Firewall Style

application working on All types of Ethernet Connections. Oddly enough,
I
notice the Driver is installed to any Dial-up connection I have, but I
can’t
access it to send the Allow/Block lists or any other settings I require.

I’m aware this list has recieved, probably many, requests for help along

this topic, but each one I’ve come across(and I’m starting to get tired
of
looking through old requests that lead no where and coming up with
nothing)
has done nothing.

The way the driver works, is it utilizes the \DEVICE\ name of the NIC to

send the required information. I think I can re-write things to send a
general broadcast of the information, but that might also screw things
up a
bit more than I’d like. I believe that all I need to do is Enumerate
the
\DEVICE\ name of the Modem that’s intalled on the computer, and then
I’ll be
on a roll.

Currently, and when I get my laptop back, I work on Windows 2000 and
Windows
XP with their respective DDKs.

The reason I believe all I need is the \DEVICE\ name is because I made
many
successful connections with the Driver active and there were no
for-see-able
problems. All the list entries I read, were of people having trouble
with
their Driver.

Direct solutions, links or a general idea of what I need to do(so I
atleast
have a better idea of what to look for) is appreciated.

For the record, this is my first time writing to a list of the sort, but

I’ve spent 2 weeks searching(while getting everything else with respect
to
the Project working) with no avail; so my last option is this.

I thank you all for atleast reading this, and my great appreciate goes
out
to those who help.

Thanks,
Andrew Nielsen

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@neverfailgroup.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

I got the same impression you did, and that is the way I would also
solve the problem. This is demonstrated in the passthru sample, as well
(at least in the 3790 DDK).

-sd

On Tue, 2004-08-17 at 06:59, Douglas G. Hanley wrote:

I *think* you are asking how to send configuration data to your NDIS
Intermediate IP filter driver. If so, you need to create a pseudo
device via NdisMRegisterDevice() within your kernel mode driver and
communicate with this device from your user-mode control application
using the Win32 DeviceIoControl routine. The DDK documents this
routine. Apologies if I am answering the wrong question here.

Douglas.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Andrew Nielsen
Sent: 17 August 2004 12:51
To: Windows System Software Devs Interest List
Subject: [ntdev] IP Filter Driver problem.

I have a working IP Filter Driver, by doing some re-working of Extended
Passthru and what not. I’ve managed to get a rather nice Firewall Style

application working on All types of Ethernet Connections. Oddly enough,
I
notice the Driver is installed to any Dial-up connection I have, but I
can’t
access it to send the Allow/Block lists or any other settings I require.

I’m aware this list has recieved, probably many, requests for help along

this topic, but each one I’ve come across(and I’m starting to get tired
of
looking through old requests that lead no where and coming up with
nothing)
has done nothing.

The way the driver works, is it utilizes the \DEVICE\ name of the NIC to

send the required information. I think I can re-write things to send a
general broadcast of the information, but that might also screw things
up a
bit more than I’d like. I believe that all I need to do is Enumerate
the
\DEVICE\ name of the Modem that’s intalled on the computer, and then
I’ll be
on a roll.

Currently, and when I get my laptop back, I work on Windows 2000 and
Windows
XP with their respective DDKs.

The reason I believe all I need is the \DEVICE\ name is because I made
many
successful connections with the Driver active and there were no
for-see-able
problems. All the list entries I read, were of people having trouble
with
their Driver.

Direct solutions, links or a general idea of what I need to do(so I
atleast
have a better idea of what to look for) is appreciated.

For the record, this is my first time writing to a list of the sort, but

I’ve spent 2 weeks searching(while getting everything else with respect
to
the Project working) with no avail; so my last option is this.

I thank you all for atleast reading this, and my great appreciate goes
out
to those who help.

Thanks,
Andrew Nielsen

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@neverfailgroup.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

The Extended PassThru driver includes a test application that can enumerate
the IM driver’s bindings using IOCTL_PTEXTEND_ENUM_BINDINGS. This gives
information such as this for the NDISWANIP binding:

Driver Bindings:

==========================================================
Virtual AdapterName: “\Device{24637459-A211-4C39-A62B-DDA12B9467FA}”
Opened Virtual Adapter

Lower AdapterName: “\DEVICE\NDISWANIP”
Query For OID 0x00010104 On MS-DOS Device Name: “NDISWANIP”
DOS Device Name Existed.
LinkName: “\Device\NdisWanIp”
Medium: 802.3
Query For OID 0x01010102 On MS-DOS Device Name: “NDISWANIP”
DOS Device Name Existed.
LinkName: “\Device\NdisWanIp”
Mac address = 92-FE-20-52-41-53
Opened Lower Adapter
Medium: 802.3 (0x00000000)
Current Address: 92-FE-20-52-41-53
Open Virtual Adapter By Link Address Succeeded

This should be th information that you need to open a handle to the
NDISWANIP device on the Extended PassThru driver.

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

“Andrew Nielsen” wrote in message
news:xxxxx@ntdev…
> I have a working IP Filter Driver, by doing some re-working of Extended
> Passthru and what not. I’ve managed to get a rather nice Firewall Style
> application working on All types of Ethernet Connections. Oddly enough, I
> notice the Driver is installed to any Dial-up connection I have, but I
can’t
> access it to send the Allow/Block lists or any other settings I require.
>
> I’m aware this list has recieved, probably many, requests for help along
> this topic, but each one I’ve come across(and I’m starting to get tired of
> looking through old requests that lead no where and coming up with
nothing)
> has done nothing.
>
> The way the driver works, is it utilizes the \DEVICE\ name of the NIC to
> send the required information. I think I can re-write things to send a
> general broadcast of the information, but that might also screw things up
a
> bit more than I’d like. I believe that all I need to do is Enumerate the
> \DEVICE\ name of the Modem that’s intalled on the computer, and then I’ll
be
> on a roll.
>
> Currently, and when I get my laptop back, I work on Windows 2000 and
Windows
> XP with their respective DDKs.
>
> The reason I believe all I need is the \DEVICE\ name is because I made
many
> successful connections with the Driver active and there were no
for-see-able
> problems. All the list entries I read, were of people having trouble with
> their Driver.
>
> Direct solutions, links or a general idea of what I need to do(so I
atleast
> have a better idea of what to look for) is appreciated.
>
> For the record, this is my first time writing to a list of the sort, but
> I’ve spent 2 weeks searching(while getting everything else with respect to
> the Project working) with no avail; so my last option is this.
>
> I thank you all for atleast reading this, and my great appreciate goes out
> to those who help.
>
> Thanks,
> Andrew Nielsen
>
>
>

5

Ok, I think I tried that once, and it failed. But it’s very possible I
didn’t do it right. I’ll give it a shot and see what happens.

Thanks.

From: “Thomas F. Divine”
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: Re:[ntdev] IP Filter Driver problem.
Date: Tue, 17 Aug 2004 10:34:10 -0400
Received: from lists.osr.com ([208.13.232.245]) by mc11-f7.hotmail.com with
Microsoft SMTPSVC(5.0.2195.6824); Tue, 17 Aug 2004 07:35:46 -0700
X-Message-Info: JGTYoYF78jHidl65NY2SAdq+cCIIZ62i
Newsgroups: ntdev
References:
Lines: 86

The Extended PassThru driver includes a test application that can enumerate
the IM driver’s bindings using IOCTL_PTEXTEND_ENUM_BINDINGS. This gives
information such as this for the NDISWANIP binding:

Driver Bindings:

==========================================================
Virtual AdapterName: “\Device{24637459-A211-4C39-A62B-DDA12B9467FA}”
Opened Virtual Adapter

Lower AdapterName: “\DEVICE\NDISWANIP”
Query For OID 0x00010104 On MS-DOS Device Name: “NDISWANIP”
DOS Device Name Existed.
LinkName: “\Device\NdisWanIp”
Medium: 802.3
Query For OID 0x01010102 On MS-DOS Device Name: “NDISWANIP”
DOS Device Name Existed.
LinkName: “\Device\NdisWanIp”
Mac address = 92-FE-20-52-41-53
Opened Lower Adapter
Medium: 802.3 (0x00000000)
Current Address: 92-FE-20-52-41-53
Open Virtual Adapter By Link Address Succeeded

This should be th information that you need to open a handle to the
NDISWANIP device on the Extended PassThru driver.

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

“Andrew Nielsen” wrote in message
news:xxxxx@ntdev…
> I have a working IP Filter Driver, by doing some re-working of Extended
> Passthru and what not. I’ve managed to get a rather nice Firewall Style
> application working on All types of Ethernet Connections. Oddly enough,
I
> notice the Driver is installed to any Dial-up connection I have, but I
can’t
> access it to send the Allow/Block lists or any other settings I require.
>
> I’m aware this list has recieved, probably many, requests for help along
> this topic, but each one I’ve come across(and I’m starting to get tired
of
> looking through old requests that lead no where and coming up with
nothing)
> has done nothing.
>
> The way the driver works, is it utilizes the \DEVICE\ name of the NIC to
> send the required information. I think I can re-write things to send a
> general broadcast of the information, but that might also screw things up
a
> bit more than I’d like. I believe that all I need to do is Enumerate the
> \DEVICE\ name of the Modem that’s intalled on the computer, and then I’ll
be
> on a roll.
>
> Currently, and when I get my laptop back, I work on Windows 2000 and
Windows
> XP with their respective DDKs.
>
> The reason I believe all I need is the \DEVICE\ name is because I made
many
> successful connections with the Driver active and there were no
for-see-able
> problems. All the list entries I read, were of people having trouble
with
> their Driver.
>
> Direct solutions, links or a general idea of what I need to do(so I
atleast
> have a better idea of what to look for) is appreciated.
>
> For the record, this is my first time writing to a list of the sort, but
> I’ve spent 2 weeks searching(while getting everything else with respect
to
> the Project working) with no avail; so my last option is this.
>
> I thank you all for atleast reading this, and my great appreciate goes
out
> to those who help.
>
> Thanks,
> Andrew Nielsen

6

I don’t think you quite get what I meant. I can communicate with my
Intermediate Filter Driver on Ethernet, but I couldn’t figure out how to
communicate with the modem. I have learned that the \DEVICE\NDISWANIP may
be what I want, and it might also be the Class in which I am installing my
Driver to(defined inside the INF). I will be giving them both a shot, but
just incase neither really works, other suggestiuons are still welcome…
Maybe a suggestion for another style of Driver that will Filter Traffic on
the Modem.

I think I remember reading about a TDI Driver that will do what I want. I
haven’t really wanted to waste time incase I can get this to work, so I
didn’t research that. Will it do what I want?

Thanks,
Andrew Nielsen

From: Steve Dispensa
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] IP Filter Driver problem.
Date: Tue, 17 Aug 2004 09:14:47 -0500
MIME-Version: 1.0
Received: from lists.osr.com ([208.13.232.245]) by mc5-f24.hotmail.com with
Microsoft SMTPSVC(5.0.2195.6824); Tue, 17 Aug 2004 07:17:04 -0700
X-Message-Info: JGTYoYF78jGW3cuty9VVOHRenDwx4DGj
In-Reply-To:
<8E1D6FAA50041A4CB4C2A0179B608D15672676@ng-ald-mail.aldermaston.neverfailgroup.com>
References:
<8E1D6FAA50041A4CB4C2A0179B608D15672676@ng-ald-mail.aldermaston.neverfailgroup.com>
Organization: Positive Networks

I got the same impression you did, and that is the way I would also
solve the problem. This is demonstrated in the passthru sample, as well
(at least in the 3790 DDK).

-sd

On Tue, 2004-08-17 at 06:59, Douglas G. Hanley wrote:
> I think you are asking how to send configuration data to your NDIS
> Intermediate IP filter driver. If so, you need to create a pseudo
> device via NdisMRegisterDevice() within your kernel mode driver and
> communicate with this device from your user-mode control application
> using the Win32 DeviceIoControl routine. The DDK documents this
> routine. Apologies if I am answering the wrong question here.
>
> Douglas.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Andrew Nielsen
> Sent: 17 August 2004 12:51
> To: Windows System Software Devs Interest List
> Subject: [ntdev] IP Filter Driver problem.
>
> I have a working IP Filter Driver, by doing some re-working of Extended
> Passthru and what not. I’ve managed to get a rather nice Firewall Style
>
> application working on All types of Ethernet Connections. Oddly enough,
> I
> notice the Driver is installed to any Dial-up connection I have, but I
> can’t
> access it to send the Allow/Block lists or any other settings I require.
>
> I’m aware this list has recieved, probably many, requests for help along
>
> this topic, but each one I’ve come across(and I’m starting to get tired
> of
> looking through old requests that lead no where and coming up with
> nothing)
> has done nothing.
>
> The way the driver works, is it utilizes the \DEVICE\ name of the NIC to
>
> send the required information. I think I can re-write things to send a
> general broadcast of the information, but that might also screw things
> up a
> bit more than I’d like. I believe that all I need to do is Enumerate
> the
> \DEVICE\ name of the Modem that’s intalled on the computer, and then
> I’ll be
> on a roll.
>
> Currently, and when I get my laptop back, I work on Windows 2000 and
> Windows
> XP with their respective DDKs.
>
> The reason I believe all I need is the \DEVICE\ name is because I made
> many
> successful connections with the Driver active and there were no
> for-see-able
> problems. All the list entries I read, were of people having trouble
> with
> their Driver.
>
> Direct solutions, links or a general idea of what I need to do(so I
> atleast
> have a better idea of what to look for) is appreciated.
>
> For the record, this is my first time writing to a list of the sort, but
>
> I’ve spent 2 weeks searching(while getting everything else with respect
> to
> the Project working) with no avail; so my last option is this.
>
> I thank you all for atleast reading this, and my great appreciate goes
> out
> to those who help.
>
> Thanks,
> Andrew Nielsen
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@neverfailgroup.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@hotmail.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

7

You cannot communicate with the modem after it have dialed the number and
got the carrier. After this, it is just like a hardware extension to the serial
port :slight_smile: transparent to the software.

Modem knows nothing on:

  • IP
  • PPP
  • TCP
  • UDP
  • traffic filtering

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Andrew Nielsen”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, August 18, 2004 2:54 AM
Subject: RE: [ntdev] IP Filter Driver problem.

> I don’t think you quite get what I meant. I can communicate with my
> Intermediate Filter Driver on Ethernet, but I couldn’t figure out how to
> communicate with the modem. I have learned that the \DEVICE\NDISWANIP may
> be what I want, and it might also be the Class in which I am installing my
> Driver to(defined inside the INF). I will be giving them both a shot, but
> just incase neither really works, other suggestiuons are still welcome…
> Maybe a suggestion for another style of Driver that will Filter Traffic on
> the Modem.
>
> I think I remember reading about a TDI Driver that will do what I want. I
> haven’t really wanted to waste time incase I can get this to work, so I
> didn’t research that. Will it do what I want?
>
> Thanks,
> Andrew Nielsen
>
>
> From: Steve Dispensa
> Reply-To: “Windows System Software Devs Interest List”
> To: “Windows System Software Devs Interest List”
> Subject: RE: [ntdev] IP Filter Driver problem.
> Date: Tue, 17 Aug 2004 09:14:47 -0500
> MIME-Version: 1.0
> Received: from lists.osr.com ([208.13.232.245]) by mc5-f24.hotmail.com with
> Microsoft SMTPSVC(5.0.2195.6824); Tue, 17 Aug 2004 07:17:04 -0700
> X-Message-Info: JGTYoYF78jGW3cuty9VVOHRenDwx4DGj
> In-Reply-To:
>
<8E1D6FAA50041A4CB4C2A0179B608D15672676@ng-ald-mail.aldermaston.neverfailgroup.
com>
> References:
>
<8E1D6FAA50041A4CB4C2A0179B608D15672676@ng-ald-mail.aldermaston.neverfailgroup.
com>
> Organization: Positive Networks
>
> I got the same impression you did, and that is the way I would also
> solve the problem. This is demonstrated in the passthru sample, as well
> (at least in the 3790 DDK).
>
> -sd
>
> On Tue, 2004-08-17 at 06:59, Douglas G. Hanley wrote:
> > I think you are asking how to send configuration data to your NDIS
> > Intermediate IP filter driver. If so, you need to create a pseudo
> > device via NdisMRegisterDevice() within your kernel mode driver and
> > communicate with this device from your user-mode control application
> > using the Win32 DeviceIoControl routine. The DDK documents this
> > routine. Apologies if I am answering the wrong question here.
> >
> > Douglas.
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Andrew Nielsen
> > Sent: 17 August 2004 12:51
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] IP Filter Driver problem.
> >
> > I have a working IP Filter Driver, by doing some re-working of Extended
> > Passthru and what not. I’ve managed to get a rather nice Firewall Style
> >
> > application working on All types of Ethernet Connections. Oddly enough,
> > I
> > notice the Driver is installed to any Dial-up connection I have, but I
> > can’t
> > access it to send the Allow/Block lists or any other settings I require.
> >
> > I’m aware this list has recieved, probably many, requests for help along
> >
> > this topic, but each one I’ve come across(and I’m starting to get tired
> > of
> > looking through old requests that lead no where and coming up with
> > nothing)
> > has done nothing.
> >
> > The way the driver works, is it utilizes the \DEVICE\ name of the NIC to
> >
> > send the required information. I think I can re-write things to send a
> > general broadcast of the information, but that might also screw things
> > up a
> > bit more than I’d like. I believe that all I need to do is Enumerate
> > the
> > \DEVICE\ name of the Modem that’s intalled on the computer, and then
> > I’ll be
> > on a roll.
> >
> > Currently, and when I get my laptop back, I work on Windows 2000 and
> > Windows
> > XP with their respective DDKs.
> >
> > The reason I believe all I need is the \DEVICE\ name is because I made
> > many
> > successful connections with the Driver active and there were no
> > for-see-able
> > problems. All the list entries I read, were of people having trouble
> > with
> > their Driver.
> >
> > Direct solutions, links or a general idea of what I need to do(so I
> > atleast
> > have a better idea of what to look for) is appreciated.
> >
> > For the record, this is my first time writing to a list of the sort, but
> >
> > I’ve spent 2 weeks searching(while getting everything else with respect
> > to
> > the Project working) with no avail; so my last option is this.
> >
> > I thank you all for atleast reading this, and my great appreciate goes
> > out
> > to those who help.
> >
> > Thanks,
> > Andrew Nielsen
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@neverfailgroup.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@hotmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

8

On Tue, 2004-08-17 at 17:54, Andrew Nielsen wrote:

I don’t think you quite get what I meant.

I think you’re right. :slight_smile: What *are* you trying to do? What sort of
communication do you want to have with your modem? Maxim already
pointed out that modems are more or less impossible to talk to (save for
an escape sequence or something) once they connect. I’m not sure I
understand what you’re trying to accomplish.

-sd

9

Here’s what I’m doing. I’m trying to design a Firewall Application for a
client. He wants to be able to stop incoming connections that he doesn’t
want. But, he wants it designed so he has to say which ones he wants in and
which ones he wants out upon attempted connection.

I have this working by doing a variation of the Extended Passthru. For
those unfamiliar with this, basically an IM Driver does all the Filtering,
and an application will use the IOCTL commands to send what IPs to block and
what IPs to allow and so on. The Driver is designed to communicate with the
App via Pipes(currently only using one way from Driver to App 'cause App to
Driver utilizes IOCTL commands).

The driver is being installed as a NetService, and get’s installed to all
Network Adapters aswell(in Windows 2k & XP) as Dial-up Connections. I go
into the Dial-up connection, then Properties, then Network, and the IP
Filter Driver is listed there. I have taken that to mean that all I need is
the \DEVICE\ modem address(\DEVICE{5FDB0983-E77A-4430-93FA-06BF250695FF}
being an example of my NIC Card) so that way I can communicate with the
Modem’s IP Filter Driver. If I am wrong, by all means correct me before I
go mad. If I am wrong, how should I go about to filter the Modem’s traffic
like I would the NIC’s traffic?

Thanks,
Andrew Nielsen

From: Steve Dispensa
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] IP Filter Driver problem.
Date: Tue, 17 Aug 2004 23:30:45 -0500
MIME-Version: 1.0
Received: from lists.osr.com ([208.13.232.245]) by mc4-f39.hotmail.com with
Microsoft SMTPSVC

On Tue, 2004-08-17 at 17:54, Andrew Nielsen wrote:
> I don’t think you quite get what I meant.

I think you’re right. :slight_smile: What are you trying to do? What sort of
communication do you want to have with your modem? Maxim already
pointed out that modems are more or less impossible to talk to (save for
an escape sequence or something) once they connect. I’m not sure I
understand what you’re trying to accomplish.

-sd

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@hotmail.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

10

> what IPs to allow and so on. The Driver is designed to communicate with the

App via Pipes(currently only using one way from Driver to App 'cause App to
Driver utilizes IOCTL commands).

You can WMI instead of pipes. Can be a good idea.
You can also try NdisMRegisterDevice and IOCTLs to it.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com