Raw socket implementation in windows?

Question

I need to create TCP/IP headers manually for my application. For that i used Raw socket. My system os is win xp (SP3).

My code compiles fine :) but it throws a run time error:

Initialising Winsock...Initialised successfully. Creating Raw TCP Socket...Raw TCP Socket Created successfully. Setting the socket in RAW mode...Successful. Enter hostname : 192.168.1.152

Resolving Hostname...Resolved. Enter Source IP : 192.168.1.151

Sending packet... Error sending Packet : 10022

I have set IP_HDRINCL to 1. What am i doing wrong? I switched off the firewall too but still get the same result.

Answer 1

Hi - not an answer, but hopefully a start...

From MSDN:

WSAEINVAL 10022 Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.

What are the arguments to your send call?

---

I found this update on raw sockets:

On Windows XP with Service Pack 2 (SP2) and Windows Vista, the ability to send traffic over raw sockets has been restricted in several ways:

• TCP data cannot be sent over raw sockets.

Not sure if that applies to XP SP3 though...

Answer 2

I suggest using WinPcap for this purpose. Even when you figure out how to do this properly with the win32 API it is going to be horribly slow.

I've used WinPcap successfully to inject packets to a Gigabit ethernet port as fast as the hardware can handle.

Answer 3

Starting with Windows XP SP2, raw sockets are intentionally disabled by Microsoft.

• http://msdn.microsoft.com/en-us/library/ms740548.aspx
• http://seclists.org/nmap-hackers/2005/0004.html
• http://www.zdnet.com.au/news/security/soa/Microsoft-tries-to-quell-TCP-IP-danger-/0,130061744,139189876,00.htm

Answer 4

Microsoft has limited the RAWSockets, but just use WinPcap http://www.winpcap.org/ . With that you can send all kind of packets.