-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hello list,
running here 3 gateways serving two communities. Nearly everything is duplicated/separated logically: fastd, bridges, routing tables, batman domains, etc.
Operating System is currently Ubuntu 14.04.
alfred: Installed: 2014.1.0-1 Candidate: 2014.1.0-1 Version table: *** 2014.1.0-1 0 500 http://apt.rfc2324.org/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status
Guess what: We have the requirement to run one alfred instance for each batman domain. What is the suggested way to achieve this? For instance, I assume that this isn't intended by design because /etc/default/alfred in conjunction with the init script aren't multiple interface aware.
- From our POV the preferred solution for this would be to patch the init script in order to support multiple interfaces by reading this from /etc/default/alfred, like:
INTERFACES="bridge_one bridge_two" BATMANIFS="bat_one bat_two"
Just to fork multiple separated processes.
Maybe this is solved elsewhere and we didn't get it, yet.
Please give us your thoughts and hopefully a solution to this issue.
Regards, Tobias Hachmer
On 23/07/14 16:23, Tobias Hachmer wrote:
Hello list,
running here 3 gateways serving two communities. Nearly everything is duplicated/separated logically: fastd, bridges, routing tables, batman domains, etc.
Operating System is currently Ubuntu 14.04.
alfred: Installed: 2014.1.0-1 Candidate: 2014.1.0-1 Version table: *** 2014.1.0-1 0 500 http://apt.rfc2324.org/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status
Guess what: We have the requirement to run one alfred instance for each batman domain. What is the suggested way to achieve this?
a tangential question:
given you have a big enough hardware (since you mention ubuntu 14.04) have you considered turning it into a "hardnode" and using any kind of virtualization technology? openvz, lxc...
it would help with isolation and simplify things in the long run (including having two alfred instances)
cheers!
gui
For instance, I assume that this isn't intended by design because /etc/default/alfred in conjunction with the init script aren't multiple interface aware.
From our POV the preferred solution for this would be to patch the init script in order to support multiple interfaces by reading this from /etc/default/alfred, like:
INTERFACES="bridge_one bridge_two" BATMANIFS="bat_one bat_two"
Just to fork multiple separated processes.
Maybe this is solved elsewhere and we didn't get it, yet.
Please give us your thoughts and hopefully a solution to this issue.
Regards, Tobias Hachmer
Hallo Gui,
thanks for your reply.
On 24.07.2014 03:12, Gui Iribarren wrote:
On 23/07/14 16:23, Tobias Hachmer wrote:
Guess what: We have the requirement to run one alfred instance for each batman domain. What is the suggested way to achieve this?
a tangential question:
given you have a big enough hardware (since you mention ubuntu 14.04) have you considered turning it into a "hardnode" and using any kind of virtualization technology? openvz, lxc...
it would help with isolation and simplify things in the long run (including having two alfred instances)
Yeah, this could be an approach later. But for now our gates are either a VM or just small hardware (Atom). But I don't want to discuss this here.
It is possible to create multiple batman interfaces wich are serving different domains. Corollary, alfred has to also.
As I said, a workaround could be to just simply duplicate the init script (adjusting all relevant names like pid and so on, of course).
But there could be more communities out there which will stumble over the same issue, sooner or later. So I just wanted the developer to know, that there is such a requirement.
And, maybe, this could be achieved in a way we don't know about? Anybody here?
Greetings, Tobias
Hey Tobias,
thank you very much for stating your requirement - even if that it's not implemented yet, maybe there are people out there who want that too and can help implenting it. It shouldn't be too hard ...
As I said, a workaround could be to just simply duplicate the init script (adjusting all relevant names like pid and so on, of course).
I'd like to point out that you'd also need to add an option in alfred and its clients to duplicate the unix socket used to communicate between alfred clients and the server - currently that is hardcoded:
#define ALFRED_SOCK_PATH "/var/run/alfred.sock"
But there could be more communities out there which will stumble over the same issue, sooner or later. So I just wanted the developer to know, that there is such a requirement.
And, maybe, this could be achieved in a way we don't know about? Anybody here?
In any case, if someone wants to work on that, patches are welcome :)
Cheers, Simon
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hello Simon,
On 07/24/2014 11:01 AM, Simon Wunderlich wrote:
As I said, a workaround could be to just simply duplicate the init script (adjusting all relevant names like pid and so on, of course).
I'd like to point out that you'd also need to add an option in alfred and its clients to duplicate the unix socket used to communicate between alfred clients and the server - currently that is hardcoded:
#define ALFRED_SOCK_PATH "/var/run/alfred.sock"
Bad news, would be great if an alfred developer could make this configurable passing a socket option to the daemon.
I'm not a programmer, so would be great if someone could help us out.
Regards, Tobias
b.a.t.m.a.n@lists.open-mesh.org
-
Gui Iribarren -
Simon Wunderlich -
Tobias Hachmer