public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] alfred - one gateway - multiple interfaces
Date: Thu, 24 Jul 2014 11:01:30 +0200	[thread overview]
Message-ID: <201407241101.34652.sw@simonwunderlich.de> (raw)
In-Reply-To: <88409a9ed363089a1dfc08d0baa9dea5@hachmer.de>

[-- Attachment #1: Type: Text/Plain, Size: 1001 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-07-24  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 19:23 [B.A.T.M.A.N.] alfred - one gateway - multiple interfaces Tobias Hachmer
2014-07-24  1:12 ` Gui Iribarren
2014-07-24  4:40   ` Tobias Hachmer
2014-07-24  9:01     ` Simon Wunderlich [this message]
2014-07-24 17:46       ` Tobias Hachmer
  -- strict thread matches above, loose matches on Subject: below --
2014-07-24  8:50 Treasach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201407241101.34652.sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox