I am trying to solve the following problem: I am simulating moving hosts (with different speed, mobility models etc.) and I want to know how these nodes are connected over time, thus determining the connection graph which of course changes over time. To determine the graph I need to determine the one-hop neighbors of each node. Therefore, I would like to use a pro-active neighborhood discovery. Before implementing it myself I want to ask:
1) Does a neighborhood discovery protocol for MANET already exist? (I haven't found on in INETMANET)
2) Does a better solution exists to my problem than building upon neighborhood discovery?
Thanks for any reply!
Kind Regards,
Dennis
--
GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 ¿/mtl.!*
http://portal.gmx.net/de/go/dsl
--
You received this message because you are subscribed to the Google Groups "omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.
I wrote my own neighborhood discovery protocol, which basically
periodically broadcasts hello messages. I took a look at the AODV
implementation, but I didn't want to change the AODV source code.
As far as i understood I had to mess with the AODV internals to get the
number of neighbors. Or is their any easy way to get access to the
internal table without changing any of the AODV soruce code?
Bye,
Dennis
Am Samstag, den 11.09.2010, 09:20 +0200 schrieb Omnet User:
> Thanks for you reply Alfonso. I will try it...
>
>
>
> On Fri, Sep 10, 2010 at 6:12 PM, Alfonso Ariza Quintana
> <aari...@hotmail.com> wrote:
>
> Aodv with hello can do this, the protocol has a table with the
> know neigbord, you only need to add a method that could access
> to this table
>
>
> ______________________________________________________________
> For more options, visit this group at
> http://groups.google.com/group/omnetpp?hl=en.
>
>
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "omnetpp" group.
> To post to this group, send email to omn...@googlegroups.com.
> To unsubscribe from this group, send email to omnetpp
> For more options, visit this group at
> http://groups.google.com/group/omnetpp?hl=en.
>
> --
>
> You received this message because you are subscribed to the
> Google Groups "omnetpp" group.
> To post to this group, send email to omn...@googlegroups.com.
> To unsubscribe from this group, send email to omnetpp
> For more options, visit this group at
> http://groups.google.com/group/omnetpp?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "omnetpp" group.
> To post to this group, send email to omn...@googlegroups.com.
> To unsubscribe from this group, send email to omnetpp
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
network
= cream2010.CReaMNetworkrecord-eventlog
= true#fname-append-host = true
# basic
*.playgroundSizeX = 5
00*.playgroundSizeY = 5
00**.numHosts =
5# UDP
**.CReaMHost[*].numUdpApps =
1**.CReaMHost[*].udpAppType =
"UDPApplication"**.udpApp[
0].localPort = 1234**.udpApp[
0].destPort = 1234**.udpApp[
0].messageLength = 512B**.udpApp[
0].messageFreq = 0.1s# mobility
**.manetmanager.routingProtocol =
"AODV"**.CReaMHost[*].mobilityType =
"RandomWPMobility"**.mobility.speed =
30mps**.mobility.waitTime =
0s# channel, radio and mac
**.channelcontrol.carrierFrequency =
2.4GHz**.channelcontrol.pMax =
2.0mW**.channelcontrol.sat = -
110dBm**.channelcontrol.alpha =
2**.channelcontrol.numChannels =
1**.radio.transmitterPower=
2.0mW**.radio.pathLossAlpha=
2**.radio.snirThreshold =
4dB # in dB**.radio.bitrate=
54Mbps**.radio.thermalNoise=-
110dBm**.radio.sensitivity=-
90dBm**.radio.phyOpMode =
2**.radio.channelModel =
1**.radio.berTableFile =
"per_table_80211g_Trivellato.dat"**.mac.maxQueueSize =
14**.mac.bitrate =
54Mbps
**.manetmanager.routingProtocol =
"AODV"but still the routing table of the node has just one ligne contains the node itself
I appreciate your help
The AODV code synchronize both tables, the ipv4 table has, at least, the same entries that the aodv table