firewall
-
i want to implement a personal firewall with packet filtering api's but i dont want to just filtering packets iwant do some more works like other firewalls 1-i want to notify the user when a program try to access to internet do you think is there any event in .net or in windows for this purpose and if there is which events 2- i want to see all open ports in mycompuetr somthing like netstat command in windows but iwant do this programmatically 3-if i saw a port is open how can i close it programmatically koosha
-
i want to implement a personal firewall with packet filtering api's but i dont want to just filtering packets iwant do some more works like other firewalls 1-i want to notify the user when a program try to access to internet do you think is there any event in .net or in windows for this purpose and if there is which events 2- i want to see all open ports in mycompuetr somthing like netstat command in windows but iwant do this programmatically 3-if i saw a port is open how can i close it programmatically koosha
1. no 2. look at the windows SDK 3. kill the process top secret xacc-ide 0.0.1
-
i want to implement a personal firewall with packet filtering api's but i dont want to just filtering packets iwant do some more works like other firewalls 1-i want to notify the user when a program try to access to internet do you think is there any event in .net or in windows for this purpose and if there is which events 2- i want to see all open ports in mycompuetr somthing like netstat command in windows but iwant do this programmatically 3-if i saw a port is open how can i close it programmatically koosha
Most, if not all, firewall programs work by using an NDIS Hook to (in simplified terms) see all the packets fly through the network adapter. They get a chance to examine every packet that passes through and can optionally pass the packet to the network adapter (on the way out) or pass it on to Windows (on the way in). A firewall works by just dropping any packet it doesn't like the look of. In answer to #3. If you want to close a port then all you need to do in your NDIS Hooked code is to block any packets on that port. As you examine every packet as is passed through, this means that you just don't pass the packed on the ports you want closed.
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way! My Blog
-
Most, if not all, firewall programs work by using an NDIS Hook to (in simplified terms) see all the packets fly through the network adapter. They get a chance to examine every packet that passes through and can optionally pass the packet to the network adapter (on the way out) or pass it on to Windows (on the way in). A firewall works by just dropping any packet it doesn't like the look of. In answer to #3. If you want to close a port then all you need to do in your NDIS Hooked code is to block any packets on that port. As you examine every packet as is passed through, this means that you just don't pass the packed on the ports you want closed.
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way! My Blog
Really i thought that using the hook would wind up degrading performance, and that a seperate socket layer was used. Interesting thanks ;) Discovery consist of seeing what everybody has seen and thinking what nobody has thought -- Albert Szent-Györgyi Name the greatest of all the inventors: accident --Mark Twain