Sending my own TCP packet / the RST problem
- From: "Rune Simonsen" <rrs@xxxxxxxxxxx>
- Date: 6 Dec 2005 06:47:58 -0800
Hi.
I am trying to send some TCP packets where I am building the packet
myself with IP header, TCP header and TCP payload.
I am currently sending the packet with a SOCK_RAW and using the
IP_HDRINCL option. Sending the SYN works fine, but when I recieve the
SYN/ACK, the TCP stack in windows replies with a RST which of cause
destroys the connection. I know that this happends because the TCP
stack does not know that I have sent the SYN and then it thinks
something is wrong when seeing the SYN/ACK.
The question is: How do you do this stuff on Windows then? I dont
strictly need to build the IP header myself, but I need to build the
TCP header. Can I make this work by using winsock in any way and if
not, how do you typically do something like this on Windows?
Thanks for your time reading (and hopefully replying on) this message.
--
Rune Simonsen
.
- Follow-Ups:
- Re: Sending my own TCP packet / the RST problem
- From: Arkady Frenkel
- Re: Sending my own TCP packet / the RST problem
- Prev by Date: Re: Which one is more efficient: Mail slots or Named Pipes
- Next by Date: Check if TCP port is in use?
- Previous by thread: Which one is more efficient: Mail slots or Named Pipes
- Next by thread: Re: Sending my own TCP packet / the RST problem
- Index(es):
Relevant Pages
|
