ximum number of addresses advertised on a message.
#define OLSR_MAX_ADDRS 64
I've fixed it to a higher value and the problem was solved.
Unfortunately, I don't know if this fix has collateral effects :-(
Regards
Víctor González
El sáb, 03-03-2007 a las 17:12 +, d
OLSR_NEIGHB_HOLD_TIME is 3*OLSR_REFRESH_INTERVAL, which is always 2.
To correct it you may assign OLSR_REFRESH_INTERVAL to hello_ival
Regards,
Víctor González.
Hi,
try to check this extension:
http://www.telematica.polito.it/fiore/
bye,
Víctor González
El mar, 31-10-2006 a las 11:14 -0600, Edwin Cruz escribió:
>
> >
> >
> > Hi Guys
> >
> > I have a problem whith 802.11.
> >
> > I need a form
also to compare the simulation with the theoretical
> propagation model equations .
>
> Regards
>
> Miguel
>
>
> Víctor González <[EMAIL PROTECTED]> escribió:
>
>
> Hi all,
>
> we are simulating a wireless scenar
x27;t lost packets in our tracefile. We also tried to simulate without
the extensions we mentioned previously with the same result.
We think this is a very strange situation, may be, produced by some
mistake in our NS2 script. You can see it below.
Thanks to all and kind regards,
Víctor Gonzál
OK,
thanks, your answer has been very helpful.
Víctor.
El mié, 27-09-2006 a las 19:17 +0200, Daniel Mahrenholz escribió:
> Víctor González schrieb:
> > Hi,
> > I am simulating an ad-hoc environment under NS 2.29 in a Ubuntu
> > 6.06(Dapper) LTS.
> > In m
this bug was fixed in the ns 2.28
version.
So, why I am getting this huge value? Maybe it comes from an incorrect
parameter I am giving to the Shadowing propagation model?
Thanks for your help
Víctor González