[Nfd-dev] [Ndn-interest] UDP_retransmissiom

[Giuseppe Carella]

Good morning,

I have done what you told but I still continue to loose some packets, much
less than before but I still continue to loose:

This is what I have done:
Consumer:
nfdc face create udp4://$1 reliability on
nfdc route add /app1 udp4://$1

Producer:
nfdc face create udp4://$1 reliability on


Should it be enough, right?

Thank you.
Giuseppe

2018-01-10 19:49 GMT+01:00 Davide Pesavento <davide.pesavento at lip6.fr>:

> Giuseppe,
>
> You didn't need to change the code. As Eric said, to enable the
> LpReliability feature, you can specify "reliability on" when creating
> a face with nfdc.
>
> That being said, make sure you enable LpReliability on *both* ends of
> the link, otherwise the receiver won't know that it has to send ACKs
> back.
>
> Best regards,
> Davide
>
> On Wed, Jan 10, 2018 at 10:10 AM, Giuseppe Carella
> <gcarella228 at gmail.com> wrote:
> > Good morning Eric,
> >
> > I tried to use this functionality changing the NFD code (I set the
> boolean
> > variable isEnalbe = true into the file lp-reliability.hpp).
> > It seems that the retransmission becomes mandatory in this way (every
> time
> > the request is sent maxRetx + 1 times).
> > Does it behave like that or the retransmission verifies only if the ack
> is
> > not received within RTO?
> > Is it possible to customize the value of RTO?
> >
> > Thank you.
> > Giuseppe.
> >
> > 2018-01-04 20:18 GMT+01:00 Eric Newberry <enewberry at email.arizona.edu>:
> >>
> >> Hi Giuseppe,
> >>
> >> By default, the number of retransmissions is set to 3. The option
> >> controlling this is in LpReliability::Options as maxRetx. However,
> currently
> >> there is no way to set this option using nfdc or any other management
> tool.
> >> Therefore, if you want to change this, you would need to modify the NFD
> >> source code, recompile, and reinstall. There are no options relating to
> the
> >> reliability system in nfd.conf.
> >>
> >> Eric
> >>
> >>
> >> On 01/04/2018 02:10 AM, Giuseppe Carella wrote:
> >>
> >> Good morning Eric,
> >>
> >> Thank you for your answer.
> >> I understood that it's possible to implement the retransmission by means
> >> of NDNLPv2, which is a protocol located upon the transport layer.
> >> So I have to set a maximum number of retransmissions, that's all (I
> hope).
> >> Is it enough modifying some properties into nfd.conf to choose the
> maximum
> >> number of retransmissions or I have to add some new APIs into
> applicative
> >> layer?
> >>
> >> Thank you.
> >> Giuseppe.
> >>
> >> 2018-01-04 9:31 GMT+01:00 Eric Newberry <enewberry at email.arizona.edu>:
> >>>
> >>> Giuseppe,
> >>>
> >>> NFD release 0.6.0 implements a link-layer reliability system as part of
> >>> NDNLPv2 for unicast TCP, UDP, and Ethernet faces. It can be enabled by
> >>> specifying "reliability on" when creating (or updating) a face with
> nfdc. In
> >>> order for the system to function, it must be enabled on both ends of
> the
> >>> link. The above command only enables it on one end.
> >>>
> >>> Eric
> >>>
> >>>
> >>> On 01/04/2018 01:24 AM, Giuseppe Carella wrote:
> >>>
> >>> Good morning community,
> >>>
> >>> is it possible to configure NFD in order to allow an UDP communication
> >>> with retransmission?
> >>> I know that I could use TCP, but for my purpose it's necessary having
> UDP
> >>> with retransmission.
> >>>
> >>> Thank you.
> >>> Giuseppe.
> >>>
> >>>
> >>> _______________________________________________
> >>> Ndn-interest mailing list
> >>> Ndn-interest at lists.cs.ucla.edu
> >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Ndn-interest mailing list
> >>> Ndn-interest at lists.cs.ucla.edu
> >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> >>>
> >>
> >>
> >
> >
> > _______________________________________________
> > Nfd-dev mailing list
> > Nfd-dev at lists.cs.ucla.edu
> > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180112/d95ae14a/attachment.html>