-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows binding Raw Socket with TCP protocol immediately kills process #411
Comments
Can you reduce the code example? It has a lot of stuff in it unrelated to socket2 such as running a command and an infinite loop. |
The reason for doing so is to provide the privileges needed. Given privileges, the else statement is sufficient. The loop is there simply to demonstrate the failure - the process immediately dies. Im on Win 11. According to the docs On Windows 7, Windows Vista, Windows XP with Service Pack 2 (SP2), and Windows XP with Service Pack 3 (SP3), the ability to send traffic over raw sockets has been restricted in several ways:
its not clear if these docs are stale or not... this will suffice :
|
According to Nmap Nmap only supports ethernet interfaces (including most 802.11 wireless cards and many VPN clients) for raw packet scans. Unless you use the -sT -Pn options, RAS connections (such as PPP dialups) and certain VPN clients are not supported. This support was dropped when Microsoft removed raw TCP/IP socket support in Windows XP SP2. Now Nmap must send lower-level ethernet frames instead. if you read the MS docs above TCP Raw sockets are treated as datagram sockets, in the case of TCP / UDP... and if I use a DGRAM / TCP socket then the process fails just like a RAW / TCP socket.... |
no errors captured. If I simply try to send and not bind I get
An invalid argument was supplied. (os error 10022)
The text was updated successfully, but these errors were encountered: