David S. Miller wrote:
> From: [EMAIL PROTECTED] (David Wagner)
>
> How could it be for another connection, if it has source and
> destination port numbers?
>
>Consider previously existing connections with the same src/dst/ports
>and the effects of massive packet reordering and other
Hello!
> namely, it only happens with probability 1/2^32 (you hope).
This can happen with probability close to 1 or even exactly 1,
depending on sequence number selection algorithm.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hello!
namely, it only happens with probability 1/2^32 (you hope).
This can happen with probability close to 1 or even exactly 1,
depending on sequence number selection algorithm.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
David S. Miller wrote:
From: [EMAIL PROTECTED] (David Wagner)
How could it be for another connection, if it has source and
destination port numbers?
Consider previously existing connections with the same src/dst/ports
and the effects of massive packet reordering and other transmission
Andi Kleen wrote:
>On Fri, Oct 06, 2000 at 09:06:31PM +, David Wagner wrote:
>> David S. Miller wrote:
>> >Linux should not honor the incorrect sequence number. If the sequence
>> >number is incorrect, the RST could legitimately be for another
>> >connection.
>>
>> How could it be for
From: [EMAIL PROTECTED] (David Wagner)
Date:6 Oct 2000 21:06:31 GMT
How could it be for another connection, if it has source and
destination port numbers?
Consider previously existing connections with the same src/dst/ports
and the effects of massive packet reordering and
On Fri, Oct 06, 2000 at 09:06:31PM +, David Wagner wrote:
> David S. Miller wrote:
> >Linux should not honor the incorrect sequence number. If the sequence
> >number is incorrect, the RST could legitimately be for another
> >connection.
>
> How could it be for another connection, if it has
David S. Miller wrote:
>Linux should not honor the incorrect sequence number. If the sequence
>number is incorrect, the RST could legitimately be for another
>connection.
How could it be for another connection, if it has source and destination
port numbers? I thought the sequence number was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 5 Oct 2000, Alan Curry wrote:
> Questions:
>
> 1. Could/should the Linux kernel be patched to recognize the one-off sequence
>number and return ECONNREFUSED?
Nope, the sequence number could be correct for another Connection.
> 2. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 5 Oct 2000, Alan Curry wrote:
Questions:
1. Could/should the Linux kernel be patched to recognize the one-off sequence
number and return ECONNREFUSED?
Nope, the sequence number could be correct for another Connection.
2. If the
David S. Miller wrote:
Linux should not honor the incorrect sequence number. If the sequence
number is incorrect, the RST could legitimately be for another
connection.
How could it be for another connection, if it has source and destination
port numbers? I thought the sequence number was there
From: [EMAIL PROTECTED] (David Wagner)
Date:6 Oct 2000 21:06:31 GMT
How could it be for another connection, if it has source and
destination port numbers?
Consider previously existing connections with the same src/dst/ports
and the effects of massive packet reordering and
From: "Alan Curry" <[EMAIL PROTECTED]>
Date:Thu, 5 Oct 2000 18:03:55 -0500 (EST)
3. Does anybody know where to file a bug report on the Sega
Dreamcast TCP?
Eventually it should reach Microsoft, since if I remember correctly
the dreamcast uses their networking stack.
Usually, when I try to connect to a port with nothing listening on it, it
looks like this:
17:11:20.809712 eth0 > MYHOST.2514 > OTHERHOST.auth: S 2807001202:2807001202(0) win
32120 (DF)
17:11:20.819712 eth0 < OTHERHOST.auth > MYHOST.2514: R 0:0(0) ack 2807001203 win 0
MYHOST is my Linux box.
Usually, when I try to connect to a port with nothing listening on it, it
looks like this:
17:11:20.809712 eth0 MYHOST.2514 OTHERHOST.auth: S 2807001202:2807001202(0) win
32120 mss 1460,sackOK,timestamp 39176091 0,nop,wscale 0 (DF)
17:11:20.819712 eth0 OTHERHOST.auth MYHOST.2514: R 0:0(0)
From: "Alan Curry" [EMAIL PROTECTED]
Date:Thu, 5 Oct 2000 18:03:55 -0500 (EST)
3. Does anybody know where to file a bug report on the Sega
Dreamcast TCP?
Eventually it should reach Microsoft, since if I remember correctly
the dreamcast uses their networking stack.
Linux
16 matches
Mail list logo
