Winsock bug/feature/fail safe??? - Programmer

This is a discussion on Winsock bug/feature/fail safe??? - Programmer ; I'm not sure if this is the correct newsgroup for this question, but it was the closest to the topic of my question. Apologies if I'm mistaken. So, this is what I was doing, I'm using raw sockets in winsock ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Winsock bug/feature/fail safe???

  1. Winsock bug/feature/fail safe???

    I'm not sure if this is the correct newsgroup for this question, but it was
    the closest to the topic of my question. Apologies if I'm mistaken.

    So, this is what I was doing, I'm using raw sockets in winsock 2.2 and I set
    the length field of the IP header for my packets. However, upon analyzing
    the packets I generated, I noticed that what I put in the length field and
    what actually appeared in the length field (after being sent) were differ.
    It turns out that the value I was putting into the length field and the
    number of bytes I was telling sendto() to write were different. The value
    that I read in the actual packet was the number of bytes that I gave to
    sendto().

    So, my question is why does this happen? Is there any way around it? (I
    just need to have total control over the packets I'm creating and I foresee
    that this might be a problem) Was winsock designed specifically with this
    "feature" to prevent something?

    Any information or pointers on where to find information would be greatly
    appreciated. Thanks.



  2. Re: Winsock bug/feature/fail safe???

    This newsgroup sucks. The closest thing to a response I've gotten (in 3
    days) is a porn ad regarding Angelina Jolie. >:-O


    "Aaron Shbeeb" wrote in message
    news:bumsd7$ob4$1@news.cis.ohio-state.edu...
    > I'm not sure if this is the correct newsgroup for this question, but it

    was
    > the closest to the topic of my question. Apologies if I'm mistaken.
    >
    > So, this is what I was doing, I'm using raw sockets in winsock 2.2 and I

    set
    > the length field of the IP header for my packets. However, upon analyzing
    > the packets I generated, I noticed that what I put in the length field and
    > what actually appeared in the length field (after being sent) were differ.
    > It turns out that the value I was putting into the length field and the
    > number of bytes I was telling sendto() to write were different. The value
    > that I read in the actual packet was the number of bytes that I gave to
    > sendto().
    >
    > So, my question is why does this happen? Is there any way around it? (I
    > just need to have total control over the packets I'm creating and I

    foresee
    > that this might be a problem) Was winsock designed specifically with this
    > "feature" to prevent something?
    >
    > Any information or pointers on where to find information would be greatly
    > appreciated. Thanks.
    >
    >




+ Reply to Thread