TCP Variants on Linux

Hello,

I'm looking for an OS (unix) on which I can run the following TCP
variants:
- TCP-Tahoe
- TCP-Reno
- TCP-NewReno
- TCP-SACK
- TCP-Vegas
- TCP-Westwood

Which Linux distribution is able to run all of a subset of them. Or is
there
one I can use after installing some available package?

Your help is much appreciated.

Thanks,
Khaled

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Khaled wrote:
> Hello,
>
> I'm looking for an OS (unix) on which I can run the following TCP
> variants:
> - TCP-Tahoe
> - TCP-Reno
> - TCP-NewReno
> - TCP-SACK
> - TCP-Vegas
> - TCP-Westwood
>
> Which Linux distribution is able to run all of a subset of them.

None.

All the TCP implementations you named are part of or come from BSD. Linux does
not use the BSD networking code at all, and instead implements the "NET-2/3/4"
code developed independantly for Linux.

> Or is there > one I can use after installing some available package?

Go check out the FreeBSDs. One of them might have remnants of the BSD networking
stack in it.

> Your help is much appreciated.
>
> Thanks,
> Khaled
>


- --
Lew Pitcher
IT Specialist, Enterprise Data Systems,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed are my own, not my employers')
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFCn1qlagVFX4UWr64RAmXuAJ0UR2j5KtspYgWdmgIwsk V7ZRbTiwCguzlt
J1CJmjt6flyG548oynstm7Q=
=AMC1
-----END PGP SIGNATURE-----

Lew Pitcher wrote:
>
> None.
>
> All the TCP implementations you named are part of or come from BSD. Linux does
> not use the BSD networking code at all, and instead implements the "NET-2/3/4"
> code developed independantly for Linux.
>

Thanks much Lew, I'll certainly go and read about this "NET-2/3/4". I
thought I could just ask you first, what TCP is implemented within
Linux's tcp/ip stack implementation?

Thanks again,
Khaled

Khaled wrote:
>
> Lew Pitcher wrote:
>
>>None.
>>
>>All the TCP implementations you named are part of or come from BSD. Linux does
>>not use the BSD networking code at all, and instead implements the "NET-2/3/4"
>>code developed independantly for Linux.
>>
>
>
> Thanks much Lew, I'll certainly go and read about this "NET-2/3/4". I
> thought I could just ask you first, what TCP is implemented within
> Linux's tcp/ip stack implementation?
>
> Thanks again,
> Khaled
>
Have a look at the /proc/sys/net/ipv4/ directory

Lots of TCP options and implementations.


Eddy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lew Pitcher wrote:
> Khaled wrote:
>
>>>Hello,
>>>
>>>I'm looking for an OS (unix) on which I can run the following TCP
>>>variants:
>>>- TCP-Tahoe
>>>- TCP-Reno
>>>- TCP-NewReno
>>>- TCP-SACK
>>>- TCP-Vegas
>>>- TCP-Westwood
>>>
>>>Which Linux distribution is able to run all of a subset of them.
>
>
> None.
>
> All the TCP implementations you named are part of or come from BSD. Linux does
> not use the BSD networking code at all, and instead implements the "NET-2/3/4"
> code developed independantly for Linux.

Specifically, in the Linux 2.4 kernel, the TCP/IP stack is
"Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039"

and reports

"NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0."

[snip]

- --
Lew Pitcher

Master Codewright & JOAT-in-training | GPG public key available on request
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCn5anagVFX4UWr64RAoBXAKCQlrzVc9x+t7iIC4ivIf EKLOSeggCggMTW
psNe8SUeHqrWTrf+hKOVWkk=
=R/TL
-----END PGP SIGNATURE-----

"Khaled" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...

> Thanks much Lew, I'll certainly go and read about this "NET-2/3/4". I
> thought I could just ask you first, what TCP is implemented within
> Linux's tcp/ip stack implementation?

What do you mean by "what TCP"? If you mean what implementation, then
the answer is that Linux has its own implemenation.

DS

David Schwartz wrote:
> What do you mean by "what TCP"? If you mean what implementation, then
> the answer is that Linux has its own implemenation.
>
> DS

Isn't this "own implementation" supposed to conform to one or more of
the standards? This is actually what I meant, TCP has several standards
(commonly called TCP variants). They differ particularly in the
protocol behaviour reacting to congestion and packet loss.

So my question is, which TCP variant(s) is/are built within Linux
implementation? The old plain TCP (TCP-Tahoe)? others?

Thank you!
Khaled

"Khaled" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Isn't this "own implementation" supposed to conform to one or more of
> the standards? This is actually what I meant, TCP has several standards
> (commonly called TCP variants). They differ particularly in the
> protocol behaviour reacting to congestion and packet loss.

Of course.

> So my question is, which TCP variant(s) is/are built within Linux
> implementation? The old plain TCP (TCP-Tahoe)? others?

Pretty much everything you would expect is supported.

DS

> So my question is, which TCP variant(s) is/are built within Linux
> implementation? The old plain TCP (TCP-Tahoe)? others?

You can find the answer to this and much of your original query in about
10 minutes on google.

In article <(E-Mail Removed) .com>,
Khaled wrote:

>Isn't this "own implementation" supposed to conform to one or more of
>the standards?

0793 Transmission Control Protocol. J. Postel. Sep-01-1981. (Format:
TXT=172710 bytes) (Updated by RFC3168) (Also STD0007) (Status:
STANDARD)

1122 Requirements for Internet Hosts - Communication Layers. R.
Braden, Ed.. October 1989. (Format: TXT=295992 bytes) (Updated by
RFC1349) (Also STD0003) (Status: STANDARD)

3168 The Addition of Explicit Congestion Notification (ECN) to IP. K.
Ramakrishnan, S. Floyd, D. Black. September 2001. (Format: TXT=170966
bytes) (Obsoletes RFC2481) (Updates RFC2474, RFC2401, RFC0793)
(Status: PROPOSED STANDARD)

>This is actually what I meant, TCP has several standards
>(commonly called TCP variants). They differ particularly in the
>protocol behaviour reacting to congestion and packet loss.

What you listed upthread is merely the Berkeley implementations. Linux is
another implementation. The standards are the RFCs.

ftp://ftp.isi.edu/in-notes/rfc-index.txt

http://www.ietf.org/rfc/rfc0000.txt
http://www.faqs.org/rfcs/rfc0000.html
http://www.rfc-editor.org/rfc/rfc0000.txt
http://www.ccd.bnl.gov/network/general/rfc0000.html
http://www.cis.ohio-state.edu/htbin/rfc/rfc0000.html

Replace the four zeros with the four digit document number (0793, not 793).

Old guy