> Look at your sample in code, it is invalid. It cannot be > generated by some real TCP stack. Not actually having followed the conversation up to this point, is it worth pointing out that some TCP packets aren't actually generated by TCP stacks, and asking what impact such a bogus packet could have on the Linux stack? -- Kevin L. Mitchell <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
- tcp_input.c change Taral
- Re: tcp_input.c change David S. Miller
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
- Re: tcp_input.c change Taral
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Kev
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
- Re: tcp_input.c change Stephen Satchell
- Re: tcp_input.c change Taral
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
- Re: tcp_input.c change kuznet
- Re: tcp_input.c change Taral
