[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ns] wnd_init_option in Vegas
I encountered same problem couple weeks ago and posted a question. If I
run multiply Vegas connections (say more than 30 connections, note: for
small number of connections there is no problem at all.) the same error
will occur even I set every vegas connection's windowInitOption_ to 1.
And it also has something to do with "trace-all" command. If I am not
using this command then the problem will not appear. What I did is
changing the code in tcp.cc to make window_init_option_ to 1 if user does
not specify window_init_option or does not specify to 2. This might not
be a good way but it works fine in my code.
Hyunah Park wrote:
> wnd_init_option could have 2 values which are 1 or 2.
> int wnd_init_option_; /* 1 for using wnd_init_ */
> /* 2 for using large initial
> windows */
> You could find more information in ns manual page about various
> TCP options
> at http://www-mash.CS.Berkeley.EDU/ns/ns-man.html
>
> - Huyunah
>
> > Hi!
> > What does "wrong wnd_init_option_ 0" mean when runnin a TCP/Vegas
> > connection?
> > Thanks in advance,
> > Ana
> >
> > ________________________________
> > Ana Delgado
> > Centre for Telecommunications Research
> > King's College London
> > London England
> > [email protected]
> >
> > ______________________________________________________
> > Get Your Private, Free Email at http://www.hotmail.com
--
Jun Ke
[email protected]
Dept. of Computer Science
University of Saskatchewan