It means you run two daemons. The second one with the modified configuration can never be reached by applications, because there is still another instance of the daemon running.keep in mind that the daemon from the debian packages might autostart upon boot. So maybe you just need to stop it before starting it manually.

Sebastian

Dimitrios Giotas <dimigiotas@gmail.com> wrote:
>Hello,
>
>I am facing a weird problem with the ibr daemon. When I run it with a
>modified configuration file, both the log and the daemon itself say the
>active configuration file is the modified one.
>
>However, in order for the daemon to ping himself I have to use the
>default
>eid and not the one I specified in my conf file.
>
>Therefore I assume that the daemon runs in its default configuration as
>a
>whole.
>
>Moreover, I get the following message in the daemon : ERROR ApiServer:
>cannot bind socket with address [::1]:4550
>
>Lastly, the daemon cannot be pinged by its neighbor, an OpenWrt router,
>no
>matter the eid I use.
>
>Any help would be greatly appreciated.
>
>Regards
>Dimitris Giotas
>
>
>------------------------------------------------------------------------
>
>--
>!! 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://www.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn.

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.