IBRDTN discovery and summary vector exchange issues
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunistic contact NodeB<--------------------------------------->NodeU<---------------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem: * For many contacts (given the above mobility assumptions), NodeU does not seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file. * Even for contacts where NodeU seems to have discovered the other node, Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
Hello, how are you recording the log file to know neighbors detected? Is it from API? I sugest you try print a neighbor list also with it, and maybe also event list (protocol event in API), since I assume you get the log from deamon messages.
On Fri, May 5, 2017 at 8:53 AM, Vijayasarathy Rajagopalan <shanv82@gmail.com
wrote:
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunisticcontact NodeB<--------------------------------------->NodeU<-------- -------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem:
- For many contacts (given the above mobility assumptions), NodeU does not
seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file.
- Even for contacts where NodeU seems to have discovered the other node,
Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
Hi Leonel,
Thanks for the email. I am running the command line DTN daemon dtnd with log level 100 (print all logs, that is) with the following command:
dtnd -c <ibrdtnd.conf with path> -d 100 -v >$HOSTNAME.log
I am not sure how to print the neighbour list/event list given this.
On Tue, May 9, 2017 at 2:11 AM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
Hello, how are you recording the log file to know neighbors detected? Is it from API? I sugest you try print a neighbor list also with it, and maybe also event list (protocol event in API), since I assume you get the log from deamon messages.
On Fri, May 5, 2017 at 8:53 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunisticcontact NodeB<--------------------------------------->NodeU<-------- -------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem:
- For many contacts (given the above mobility assumptions), NodeU does
not seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file.
- Even for contacts where NodeU seems to have discovered the other node,
Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <ibr-dtn-request@ibr.cs.tu-bs.de
!! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
If you are familiar with python, I would sugest taking a look at this script, and use some similar one to note time of new neighbors in nodes:
https://github.com/ibrdtn/ibrdtn/wiki/API
(take a look at example:python) and see if you can get any conclusion from the API
On Tue, May 9, 2017 at 7:08 AM, Vijayasarathy Rajagopalan <shanv82@gmail.com
wrote:
Hi Leonel,
Thanks for the email. I am running the command line DTN daemon dtnd with log level 100 (print all logs, that is) with the following command:
dtnd -c <ibrdtnd.conf with path> -d 100 -v >$HOSTNAME.log
I am not sure how to print the neighbour list/event list given this.
On Tue, May 9, 2017 at 2:11 AM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
Hello, how are you recording the log file to know neighbors detected? Is it from API? I sugest you try print a neighbor list also with it, and maybe also event list (protocol event in API), since I assume you get the log from deamon messages.
On Fri, May 5, 2017 at 8:53 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunisticcontact NodeB<--------------------------------------->NodeU<-------- -------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem:
- For many contacts (given the above mobility assumptions), NodeU does
not seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file.
- Even for contacts where NodeU seems to have discovered the other node,
Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <ibr-dtn-request@ibr.cs.tu-bs. de> !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
Hi Leonel,
I ran the neighbour list in NodeB above, and the neighbour list clearly doesnt change for a long time despite the opportunity for NodeB to have multiple contacts with NodeU. From the log, it seems that NodeB receives discovery beacons from NodeU every 3 seconds, but it does not seem to act on it. The log file attached in the original message stays.
I dont see any "New node available" when NodeU and NodeB are in contact, other than once. I am expecting that NodeB discovers NodeU everytime contact happens, they exchange summary vectors, and NodeB will have a delivery predictability corresponding to NodeG.
I have disabled cross layer discovery. Would that have an impact ?
On Tue, May 9, 2017 at 6:45 PM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
If you are familiar with python, I would sugest taking a look at this script, and use some similar one to note time of new neighbors in nodes:
https://github.com/ibrdtn/ibrdtn/wiki/API
(take a look at example:python) and see if you can get any conclusion from the API
On Tue, May 9, 2017 at 7:08 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi Leonel,
Thanks for the email. I am running the command line DTN daemon dtnd with log level 100 (print all logs, that is) with the following command:
dtnd -c <ibrdtnd.conf with path> -d 100 -v >$HOSTNAME.log
I am not sure how to print the neighbour list/event list given this.
On Tue, May 9, 2017 at 2:11 AM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
Hello, how are you recording the log file to know neighbors detected? Is it from API? I sugest you try print a neighbor list also with it, and maybe also event list (protocol event in API), since I assume you get the log from deamon messages.
On Fri, May 5, 2017 at 8:53 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunisticcontact NodeB<--------------------------------------->NodeU<-------- -------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem:
- For many contacts (given the above mobility assumptions), NodeU does
not seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file.
- Even for contacts where NodeU seems to have discovered the other
node, Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <ibr-dtn-request@ibr.cs.tu-bs. de> !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
It seems to me that something in your network does not allow nodes to comunicate in DTN. Have you configured ad-hoc network? What OS are you using?
On Mon, May 15, 2017 at 7:02 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi Leonel,
I ran the neighbour list in NodeB above, and the neighbour list clearly doesnt change for a long time despite the opportunity for NodeB to have multiple contacts with NodeU. From the log, it seems that NodeB receives discovery beacons from NodeU every 3 seconds, but it does not seem to act on it. The log file attached in the original message stays.
I dont see any "New node available" when NodeU and NodeB are in contact, other than once. I am expecting that NodeB discovers NodeU everytime contact happens, they exchange summary vectors, and NodeB will have a delivery predictability corresponding to NodeG.
I have disabled cross layer discovery. Would that have an impact ?
On Tue, May 9, 2017 at 6:45 PM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
If you are familiar with python, I would sugest taking a look at this script, and use some similar one to note time of new neighbors in nodes:
https://github.com/ibrdtn/ibrdtn/wiki/API
(take a look at example:python) and see if you can get any conclusion from the API
On Tue, May 9, 2017 at 7:08 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi Leonel,
Thanks for the email. I am running the command line DTN daemon dtnd with log level 100 (print all logs, that is) with the following command:
dtnd -c <ibrdtnd.conf with path> -d 100 -v >$HOSTNAME.log
I am not sure how to print the neighbour list/event list given this.
On Tue, May 9, 2017 at 2:11 AM, Leonel Gaspar Soares < leonelgasparsoares@gmail.com> wrote:
Hello, how are you recording the log file to know neighbors detected? Is it from API? I sugest you try print a neighbor list also with it, and maybe also event list (protocol event in API), since I assume you get the log from deamon messages.
On Fri, May 5, 2017 at 8:53 AM, Vijayasarathy Rajagopalan < shanv82@gmail.com> wrote:
Hi All,
I am using the IBR-DTN to demonstrate simple file transfer in my experiments.
Setup: A cross section of my network looks like this:
Opportunistic contact Opportunisticcontact NodeB<--------------------------------------->NodeU<-------- -------------------------------->NodeG
NodeU moves between NodeB and NodeG to make opportunistic contact. For each contact NodeU pauses for 5-10 seconds.
I have configured prophet with the following parameters in all three nodes.
### prophet configuration ### #prophet_p_encounter_max = 0.8 #affects how strong the predictability is #increased on an encounter prophet_p_encounter_first = 0.7 #the predictability of a neighbor on the #first encounter prophet_p_first_threshold = 0.1 #lowest predictability when neighbors #predictabilities are forgotten prophet_beta = 0.9 #Weight of the transitive property prophet_gamma = 0.999 #Determines how quickly predictabilities #age #prophet_delta = 0.01 #(1-delta) is the maximum predictability prophet_time_unit = 1 #time unit in seconds prophet_i_typ = 120 #typical time interval between two node #encounters #prophet_next_exchange_timeout = 120 #timeout how often handshakes should be #executed prophet_forwarding_strategy = GRTR #The forwarding strategy used GRTR | GTMX #prophet_gtmx_nf_max = 30 #Maximum times to forward in the GTMX #strategy
For each node contact, I expect that the predictability map will be exchanged via call to the dtn://NodeName.dtn/routing service, and bundles will be transferred suitably.
Problem:
- For many contacts (given the above mobility assumptions), NodeU does
not seem to discover NodeB/NodeG. I assume that discovery has happened, if I see a "New node available" string in the log file.
- Even for contacts where NodeU seems to have discovered the other
node, Predictability map does not seem to be exchanged. A partial log file has been attached, where NodeU seems to have discovered NodeG (at the first beacon exchange itself), but they do not seem to exchange their predictability maps.
Am I configuring anything wrong with respect to prophet ? Also, I see a "summary vector of <node eid> is expired" in log every 60 seconds for some nodes. Please help.
I have attached the following: a) ibrdtn config file for NodeB; b) ibrdtn config files for NodeG and NodeU (same file); c) Portion of NodeU.log
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to < ibr-dtn-request@ibr.cs.tu-bs.de> !! or look at https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn.
participants (2)
-
Leonel Gaspar Soares -
Vijayasarathy Rajagopalan