Re: [ns] Problems using TcpApp wit FullTcp

[Mark Janssen <M.P.C.Janssen@phys.uu.nl>]

Although the fixes do make sense, they don't solve my problem. I included the changes you mentioned in your post, but that doesn't help. I do agree that the problem is probably in FullTcp and that your changes are part of the problem. Could you please check whether my script (maybe with an inserted $tcp2 reset) runs correctly while using your tcp-full.cc and .h. 
If that's the case could you send me a copy? (You can also send me a copy anyway and I can try it myself) I am really not looking forward to going through the entire tcp-full code to explain what's happening, although I will probably end up doing just that ;-).

Regards,

Mark Janssen

On Sat, Dec 09, 2000 at 10:09:48AM -0800, Xuan Chen wrote:
> We will fix it asap. Thanks.
> 
> -chen xuan
> 
> On Sat, 9 Dec 2000, Felix Hernandez Campos wrote:
> 
> > I'm not sure this is going to fix your problem, but it will help. reset is
> > partially broken in FullTcp. The main problem is that closed_ is defined in
> > tcp.h and then redefined in tcp-full.h. This *is* wrong. I submitted a bug
> > report three month ago, but it has not been committed yet. Read my (lengthy)
> > posting for more details,
> > 
> > http://www.isi.edu/nsnam/archive/ns-users/webarch/2000/msg03812.html
> > 
> > (see also John Heidemann's reply:
> > http://www.isi.edu/nsnam/archive/ns-users/webarch/2000/msg03859.html)
> > 
> > You may want to contact Tarik Alj (aljtarik@inrs-telecom.uquebec.ca). He was
> > doing real work with FullTcp at that time, while I was just trying to help. He
> > may have a more mature version of FullTcp.
> > 
> > By the way, someone with writing access should have a look to this and make some
> > changes. Thanks.
> > 
> > Mark Janssen wrote:
> > 
> > > Hello all,
> > >
> > > I am trying to use TcpApp over FullTcp to simulate some application
> > > behaviour. While doing that I run into a problem while connecting different
> > > apps. What I would like to accomplish is the following:
> > >
> > > I have a linear topology of three nodes with an attached FullTcp agent:
> > >
> > > (1)-----------(2)-----------(3)
> > >
> > > After that I create three apps and put the TCP agent at the second node in
> > > the listen state. And connect tcp1 with tcp2 with app1 and app2.
> > > Now app1 sends a message to app2. This all works great. Now because of this
> > > message app2 needs to contact app3. So I connect tcp2 with tcp3 and app2
> > > with app3 and I put tcp3 in listen mode.
> > > When I now send a message from app2 to app3 I only see ACK packets without
> > > TCP packets. I suspect this occurs because tcp2 is still in a different
> > > state then when you create it. I tried to do a "$tcp2 reset" but that
> > > doesn't solve my problem. Below I have include the tcl script, the ns output
> > > and the tracefile.
> > > Unfortunately I couldn't find any information on this in the documentation
> > > or the list-archive. I have looked at the webcache testsuite. But that only
> > > test a 2-node setup (with TcpApp and FullTcp) and that works fine.
> > > Do you have any ideas of how I should accomplish this?
> > >
> > > Thanks,
> > > Mark Janssen
> > >
<SNIP>