4

I am trying to install IPFW on a 64 bit version of Windows 7 using the package provided here

I am able to successfully add the ipfw+dummynet service to my network adapter using the instructions supplied in this stack overflow answer

However, while executing the ipfw.exe provided in the package, I face the following error :

my_socket failed 2, cannot talk to kernel module

Need assistance in getting past this error so that ipfw can be run successfully from the command line.

Ahmed Ashour
  • 5,179
  • 10
  • 35
  • 56
Sanat Vij
  • 207
  • 1
  • 4
  • 13

2 Answers2

1

The first method explained here worked for me.

I also succeed to install the driver with the 2nd methode but I had to sign the driver myself first, as explained here. To bypass the error related to the catalog file, add the following line after the version tag on the INF file :

CatalogFile.NTAMD64 = wipfwamd64.cat

I hope it helps.

Ahmed Ashour
  • 5,179
  • 10
  • 35
  • 56
Franck H
  • 26
  • 3
  • Perfect ! The first method worked for me as well. For the second method, although the driver runs in test mode, i still needed to install it after disabling driver signature as described in the first method. – Sanat Vij Jul 20 '13 at 22:11
0

I'm getting the same message error as you with my windows server 2012 based on a 64 bit architecture.

I checked the code, the error value is returned from the windows function GetLastError :

2 (0x2) : ERROR_FILE_NOT_FOUND

This error occurs when the windows function CreateFile is called on I/O device "Ipfw".

If the specified file or device does not exist, the function fails and the last-error code is set to ERROR_FILE_NOT_FOUND (2).

To make it quick I think the "Ipfw" service is missing, it shows as right installed but its not.

Franck H
  • 26
  • 3
  • i agree. Disabling and Re-Enabling the adapter causes an error which i think is indicative of the service not being correctly installed. – Sanat Vij Jul 07 '13 at 18:30