error: ‘TcpTahoe’ was not declared in this scope

[ns3user]

Hi

I am trying to execute a code which compares different TCP variants( code attached). On compilation, i am getting following error

../scratch/tcp-example.cc:185:71: error: ‘TcpTahoe’ was not declared in this scope

     Config::SetDefault("ns3::TcpL4Protocol::SocketType", TypeIdValue (TcpTahoe::GetTypeId()));

                                                                       ^

../scratch/tcp-example.cc:187:71: error: ‘TcpReno’ was not declared in this scope

     Config::SetDefault("ns3::TcpL4Protocol::SocketType", TypeIdValue (TcpReno::GetTypeId()));

I am not able to find the error in code. 

Help me

[Tommaso Pecorella]

Hi,

you're using an old example on a new ns-3 release. As much as it might seems strange, we removed TcpTahoe from ns-3, simply because Tahoe is... well, basically it's like the famous parrot: dead.

Cheers,

T.

[reena kasana]

I didn't know this..Anyway, Thank you

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/ovT6grh_wR4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

[Tommaso Pecorella]

No problem.

As a side note (or a clarification), Taohe has been removed during the TCP refactoring. At the same time, more TCP flavours have been added, and more will be in 3.26.

Right now the following are supported (in ns-3-dev):

1. TcpNewReno,
2. TcpHybla,
3. TcpHighSpeed,
4. TcpVegas,
5. TcpScalable, 
6. TcpVeno, 
7. TcpBic, 
8. TcpWestwood, 
9. TcpWestwoodPlus 
   

If I'm right also Reno has been dismissed.

Cheers,

T.

[Nat P]

Tommaso is right.

Please note that there is the possibility to add these back, but we need an extensive talk. Unfortunately, the thing is:

*) For Tahoe, I still have not found any reliable sources of its behavior. Wikipedia says one thing, the old ns-3 has done another. WIth a reliable source, adding it back should be easy (from wikipedia source, the difference is that after a fast retransmit it set the cwnd to 1, while Reno set it to ssthresh), but I still have some doubts (see later).
*) For Reno, the difference is in the Partial ACK management (they are ignored by Reno, but used by New Reno). In the actual code, that part is managed inside the TcpSocketBase and shared by all congestion control algorithms. Moreover, that part is standard since ages (more than 10 years). In my opinion, using Reno is going against the law, and demonstrating that the new law (NewReno) is better than Reno is a matter that has already been discussed in almost all environment (anyway we still miss the important grill-to-grill scenario, on a summer vacation with sands that introduces a variable packet error). Reintroducing Tahoe is, more or less, the same story.

have a nice day

Nat

[Nat P]

Yes, it is.

Don't know, seriously, from where this idea of porting back the .h and .cc files from older versions comes from...

Nat

Il giorno martedì 5 luglio 2016 15:08:41 UTC+2, Rajendra Hathwar ha scritto:

Hi,
   
    Is tcp-newreno the default tcp mode in ns3.25 ? or Are we supposed to add tcp-newreno.cc and .h files from previous versions to ns3.25?