Default build of olsrd (v0.6.6) issue

[Thijs van Veen]

Hi,

I don't know if it's a known issue, but I think it might be worth
noting.

When building olsrd (v0.6.6) from source (git) using all defaults (make
&& make install), the txtinfo plugin is not built and installed.
While this is not a problem in itself (it is a plugin after all), the
default configuration file does attempt to load it (and of course fails
because it doesn't exist).

It was my understanding that the idea of the default configuration was
to allow a (new) user to run the protocol by simply inserting the
interfaces (and possibly HNA) to be used.

There are two ways to fix this:
1. default building and installing to include the txtinfo plugin;
2. disable the LoadPlugin block from the default configuration file.

I suggest commenting out the LoadPlugin block in the default
configuration file.
This way users can still see how plugins could be used, while keeping
the plugins seperate from the main application.
--
Thijs van Veen
***@operamail.com

[Henning Rogge]

Post by Thijs van Veen
Hi,

(REPOST because someone ate my first response ^^)

Post by Thijs van Veen
I don't know if it's a known issue, but I think it might be worth
noting.
When building olsrd (v0.6.6) from source (git) using all defaults (make
&& make install), the txtinfo plugin is not built and installed.
While this is not a problem in itself (it is a plugin after all), the
default configuration file does attempt to load it (and of course fails
because it doesn't exist).

"make" and "make install" have always only compiled and installed the
core of Olsrd.

You have to run "make build_all" and "make install_all" to get the
plugins too. As an alternative, there are make-targets for every plugin.

Post by Thijs van Veen
It was my understanding that the idea of the default configuration was
to allow a (new) user to run the protocol by simply inserting the
interfaces (and possibly HNA) to be used.
1. default building and installing to include the txtinfo plugin;
2. disable the LoadPlugin block from the default configuration file.

If you want to run a minimal Olsrd setup, the "minimal" configuration
file might be the right choice anyways.

Henning Rogge

[Henning Rogge]

Post by Thijs van Veen
Hi,
I don't know if it's a known issue, but I think it might be worth
noting.
When building olsrd (v0.6.6) from source (git) using all defaults (make
&& make install), the txtinfo plugin is not built and installed.
While this is not a problem in itself (it is a plugin after all), the
default configuration file does attempt to load it (and of course fails
because it doesn't exist).

"make" and "make install" have always only compiled and installed the
core of Olsrd.

You have to run "make build_all" and "make install_all" to get the
plugins too. As an alternative, there are make-targets for every plugin.

Post by Thijs van Veen
It was my understanding that the idea of the default configuration was
to allow a (new) user to run the protocol by simply inserting the
interfaces (and possibly HNA) to be used.
1. default building and installing to include the txtinfo plugin;
2. disable the LoadPlugin block from the default configuration file.

If you want to run a minimal Olsrd setup, the "minimal" configuration
file might be the right choice anyways.

Henning Rogge

[Thijs van Veen]

Henning,

I am aware of the different make targets, I just thought it would make
sense to have the default also work.

Like I said, it's no problem that the plugin isn't built by default; in
fact that's good and expected.
The problem is the incompatibility with the default config file that's
generated (because it does try to load the plugin).

What I assumed here is:
default build + default config + correct interface = default (core)
protocol on correct interface
--
Thijs van Veen

Post by Henning Rogge

Post by Thijs van Veen
Hi,
I don't know if it's a known issue, but I think it might be worth
noting.
When building olsrd (v0.6.6) from source (git) using all defaults (make
&& make install), the txtinfo plugin is not built and installed.
While this is not a problem in itself (it is a plugin after all), the
default configuration file does attempt to load it (and of course fails
because it doesn't exist).

"make" and "make install" have always only compiled and installed the
core of Olsrd.
You have to run "make build_all" and "make install_all" to get the
plugins too. As an alternative, there are make-targets for every plugin.

Post by Thijs van Veen
It was my understanding that the idea of the default configuration was
to allow a (new) user to run the protocol by simply inserting the
interfaces (and possibly HNA) to be used.
1. default building and installing to include the txtinfo plugin;
2. disable the LoadPlugin block from the default configuration file.

If you want to run a minimal Olsrd setup, the "minimal" configuration
file might be the right choice anyways.
Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon [phone], Fax [phone]
--
Olsr-users mailing list
https://lists.olsr.org/mailman/listinfo/olsr-users
+ smime.p7s
8k (application/pkcs7-signature)