Re: [ibr-dtn] Reconnect monitoring

28 Dec 2014


      Hi,
do you want to measure the time it takes until the connection is
reestablished after the node is physically available again? Then you
could have a log at the time stamped log files. (Start `dtnd -v
--timestamp` to get the information.)
I don't know how you get the information when the network is back up
again, but most likely, you can read this from dmesg or some other log
files (syslog, ...).
A bit of script/sed/grep/cut/...-magic and you should be done ;)
HTH,
Stephan
Am Mittwoch, den 24.12.2014, 09:02 +0700 schrieb abu fahruddin:
...
Dear All,
I want to check performance of IBR-DTN trough reconnect time but I
still confuse how monitor that performance.
Inline image 2
any idea for my problem,, please share to me...
Regards
On Tue, Dec 23, 2014 at 6:00 PM, ibr-dtn-request@ibr.cs.tu-bs.de
wrote:
        Send Ibr-dtn mailing list submissions to
                ibr-dtn@ibr.cs.tu-bs.de
    To subscribe or unsubscribe via the World Wide Web, visit
            https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn
    or, via email, send a message with subject or body 'help' to
            ibr-dtn-request@ibr.cs.tu-bs.de

    You can reach the person managing the list at
            ibr-dtn-owner@ibr.cs.tu-bs.de

    When replying, please edit your Subject line so it is more
    specific
    than "Re: Contents of Ibr-dtn digest..."


    Today's Topics:

       1. Re: Ibr-dtn Digest, Vol 53, Issue 2 (abu fahruddin)


    ----------------------------------------------------------------------

    Message: 1
    Date: Tue, 23 Dec 2014 07:37:15 +0700
    From: abu fahruddin <abu.fahruddin@gmail.com>
    To: ibr-dtn@ibr.cs.tu-bs.de
    Subject: Re: [ibr-dtn] Ibr-dtn Digest, Vol 53, Issue 2
    Message-ID:

    <CAMekmc8FSqtqEaAyh8t_9K0=XrZtsk9s93O2WE0cq=qfojw6eg@mail.gmail.com>
    Content-Type: text/plain; charset="utf-8"

    Dear Sebastian,

    Thank you very much,

    The problem already solve, I change the Api interface to Any,
    before I use
    Api interface = wlan0 because I use ad-hoc for my mesh
    network. So I think
    this item make the problem occur.

    Thank's very much

    On Sun, Dec 21, 2014 at 6:00 PM,
    <ibr-dtn-request@ibr.cs.tu-bs.de> wrote:

    > Send Ibr-dtn mailing list submissions to
    >         ibr-dtn@ibr.cs.tu-bs.de
    >
    > To subscribe or unsubscribe via the World Wide Web, visit
    >         https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn
    > or, via email, send a message with subject or body 'help' to
    >         ibr-dtn-request@ibr.cs.tu-bs.de
    >
    > You can reach the person managing the list at
    >         ibr-dtn-owner@ibr.cs.tu-bs.de
    >
    > When replying, please edit your Subject line so it is more
    specific
    > than "Re: Contents of Ibr-dtn digest..."
    >
    >
    > Today's Topics:
    >
    >    1. Re: can not connect to the deamon (Sebastian Schildt)
    >
    >
    >
    ----------------------------------------------------------------------
    >
    > Message: 1
    > Date: Sat, 20 Dec 2014 22:19:21 +0100
    > From: Sebastian Schildt <schildt@ibr.cs.tu-bs.de>
    > To: ibr-dtn <ibr-dtn@ibr.cs.tu-bs.de>
    > Subject: Re: [ibr-dtn] can not connect to the deamon
    > Message-ID:
    <D83CC2DC-F037-46B8-AAC3-BE91B3A561B2@ibr.cs.tu-bs.de>
    > Content-Type: text/plain; charset=us-ascii
    >
    > Hi,
    >
    > This implies, that the daemon on A is running, but was
    unable to  bind the
    > API port. (Because the dtn tools are also using a TCP port
    to communicate
    > with a locally installed daemon). You can check whether
    IBR-DTN is bound to
    > the API port (usually 4550) by using
    >
    > netstat -lnp
    >
    > (assuming you are using linux). It should be bound to a
    loopback interface.
    >
    >
    > Also, when the daemon is starting, you should get a message
    that the API
    > has been bound to the correct interface.
    >
    > For reference, on a correctly configured system it might
    look like this
    > for netstat -lnp
    >
    > tcp        0      0 127.0.0.1:4550          0.0.0.0:*
    >  LISTEN      7085/dtnd
    >
    > You will find other lines with port 4556 for every interface
    where a TCP
    > convergence layer is used and udp port 4551 if discovery is
    enabled.
    >
    > The startup of the daemeon should look similar to  this:
    >
    >
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: IBR-DTN daemon
    0.13.0-414
    > (build 63c8a50)
    > Sat Dec 20 21:15:37 2014 INFO Configuration: Configuration:
    > /tmp/ibrdtn.config
    > Sat Dec 20 21:15:37 2014 INFO BundleCore: Local node name:
    dtn://sbase.dtn
    > Sat Dec 20 21:15:37 2014 INFO BundleCore: Lifetime limited
    to 1209600
    > seconds
    > Sat Dec 20 21:15:37 2014 INFO BundleCore: Pre-dated
    timestamp limited to
    > 604800 seconds in the future
    > Sat Dec 20 21:15:37 2014 INFO BundleCore: Forwarding of
    bundles enabled.
    > Sat Dec 20 21:15:37 2014 INFO SecurityKeyManager:
    initialized; path:
    > /etc/ibrdtn/keys
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: using sqlite
    bundle storage in
    > /mnt/sda1/ibrdtn/bundles
    > Sat Dec 20 21:15:37 2014 INFO SQLiteDatabase: Database
    version 8 found.
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: using BLOB path:
    > /mnt/sda1/ibrdtn/blobs
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: API initialized
    using tcp
    > socket: loopback:4550
    > ^^This line is important, it tells, that the API port is
    successfully
    > bound, so that tools such as dtnping/dtnsend etc. can talk
    to the daemon. I
    > guess this failed in your case
    >
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: TCP
    ConvergenceLayer added on
    > eth0:4556
    > Sat Dec 20 21:15:37 2014 INFO NativeDaemon: TCP
    ConvergenceLayer added on
    > br-lan:4556
    > ^^This tells that TCP convergence layers are bound to the
    two listed
    > interfaces. I guess this worked on your host A, which
    explains why it can
    > answer to pings
    >
    >
    > MfG
    >
    > Sebastian
    >
    >
    >
    > > On 20 Dec 2014, at 09:44, abu fahruddin
    <abu.fahruddin@gmail.com> wrote:
    > >
    > > Hi,
    > >
    > > I get problem with my IBR-DTN connection. I make
    connection for 2 laptop
    > (A and B)
    > > I have been setting A for time reference= yes,
    time_discovery=yes and B
    > time_reference=no, time_syncronize=yes. When I test ping frm
    B to A is OK
    > but ping A to B get a problem "can not connect to the
    daemon. Does it run" .
    > >
    > > Could you help me for this problem, please.
    > >
    > > regards.
    > >
    > >
    > >
    > >
    > > On Thu, Nov 27, 2014 at 6:00 PM,
    <ibr-dtn-request@ibr.cs.tu-bs.de>
    > wrote:
    > > Send Ibr-dtn mailing list submissions to
    > >         ibr-dtn@ibr.cs.tu-bs.de
    > >
    > > To subscribe or unsubscribe via the World Wide Web, visit
    > >         https://mail.ibr.cs.tu-bs.de/listinfo/ibr-dtn
    > > or, via email, send a message with subject or body 'help'
    to
    > >         ibr-dtn-request@ibr.cs.tu-bs.de
    > >
    > > You can reach the person managing the list at
    > >         ibr-dtn-owner@ibr.cs.tu-bs.de
    > >
    > > When replying, please edit your Subject line so it is more
    specific
    > > than "Re: Contents of Ibr-dtn digest..."
    > >
    > >
    > > Today's Topics:
    > >
    > >    1. Re: ibr dtn (from Indonesia) (abu fahruddin)
    > >    2. Re: ibr dtn (from Indonesia) (Johannes Morgenroth)
    > >
    > >
    > >
    ----------------------------------------------------------------------
    > >
    > > Message: 1
    > > Date: Thu, 27 Nov 2014 09:54:22 +0700
    > > From: abu fahruddin <abu.fahruddin@gmail.com>
    > > To: ibr-dtn@ibr.cs.tu-bs.de, Johannes Morgenroth
    > >         <morgenroth@ibr.cs.tu-bs.de>
    > > Subject: Re: [ibr-dtn] ibr dtn (from Indonesia)
    > > Message-ID:
    > >         <
    > CAMekmc8QjLSbE1FVVBGvHVgbTvQm
    +MSWuLLtMLjVFW4gHW9O4Q@mail.gmail.com>
    > > Content-Type: text/plain; charset="utf-8"
    > >
    > > Hi Johannes,
    > >
    > > I make 4 nodes for my mesh network. 2 PC can connect each
    other but 2 PC
    > > cannot connect by using #dtnping dtn://name/echo. and
    there is a warning
    > > :bundle rejected: bundle has expired. I try to reinstall
    and change my OS
    > > become single OS Ubuntu 14.04 but the problem still occur.
    > >
    > > Could you help me to solve the problem.
    > > regards.
    > >
    > >
    > > On Thu, May 8, 2014 at 1:18 PM, abu fahruddin
    <abu.fahruddin@gmail.com>
    > > wrote:
    > >
    > > > Dear Sir,
    > > >
    > > > I am herman yuliandoko, currently i am lecture at State
    Polytechnic of
    > > > Banyuwangi. And now I am doing research in DTN.
    > > >
    > > > I try to install DTN from
    > > >
    > > > wget -O -
    > > >
    >
    http://download.opensuse.org/repositories/home:/j_morgenroth/xUbuntu_12.04/Release.key
    > > > |   sudo apt-key add -
    > > >
    > > >
    https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/ibr-dtn-tut
    > > >
    > > >
    > > > but i get problem to acces above repository
    > > >
    > > > W: Failed to fetch
    > > >
    >
    http://download.opensuse.org/repositories/home:/j_morgenroth/xUbuntu_12.04/i386/./Packages
    > > > 404  Not Found
    > > >
    > > > I am using ubuntu for my trial, could you help me to
    solve above
    > problem.
    > > >
    > > > Your advice is wellcome.
    > > >
    > > > best regards
    > > >
    > > > herman yuliandoko
    > > >
    > > > +6281334436478
    > > >
    > >

Re: [ibr-dtn] Reconnect monitoring

Stephan Rottmann