[Dibbler] Dibbler 0.8.4 Release Candidate 1
dieter.busch at gmail.com
Sun Apr 28 18:20:49 CEST 2013
thank you for your fast answer.
What I intent to do is the following (and there I'm a little bit lost
because of the description in the manual):
Client 1 ---
... ------- Rel.1_a --
Client n --- \
-- Rel.1_1 --
Client 1 --- / |
\ / |
... ------- Rel.1_b -- |
Client n --- |
Client 1 --- |
... ------- Rel.2_a -- |
/ \ |
Client n --- \ |
-- Rel.2_1 --
Client 1 --- /
... ------- Rel.2_b --
Client n ---
Rel.1 and Rel.2 shall have different address pools, independant of the
Rel.N_x (may be a LDRA, nobody cares).
From my point of view a config should look like:
From my point of view I do not really "need" the customer facing relays
here, but I'm not sure if it would work this way. This would mean, that
the server facing relays address pool can somehow be "inherited" from
the customer facing relays. All configuration (except some specific
stuff is needed) will be relying on the server facing relay.
If I have to ad the customer facing relays (only one example) I would
configure - assuming that configuration is inherited from the server
In my actual setup (based on 0.8.3) I had to install two dibbler
servers, one for each branch on different VMs - or at least I didn't
manage to configure dibbler in the correct way. Btw. I included the
LDRAs in the config and assigned address pools at this level.
Unfortunately I'm in a lab setup using one LDRA connected to two relays....
----------------- old posts following ----------------------
I have a question on a documetation detail. I am going to deploy dibbler
with cascaded relays (one of them will be an LDRA) and I find the
5.3.9 Example 9: Cascade 2 relays
> This particular piece of documentation is a bit old. It is still valid,
> though. You can define the whole chain of relays, but since 0.8.4RC1 it
> should be sufficient to define only the relay closest to the client.
> You may also look at section 5.3.8. There are 3 different ways to
> specify interface-id: as 32 bit unsigned integer (as in the example you
> cited), as a text string or as a hex value of arbitrary length.
> Depending on how interface-id is configured on your relay, one of them
> may be easier for you.
> If your relay sets linkaddr field in RELAY-FORW (it should), then you
> can use subnet declaration, so the server will pick the right interface
> based on address, rather than interface-id. This is explained in section
> I don't remember if there are special actions needed for LDRA. I haven't
> read that RFC and haven't coded anything for its support (if anything is
> Hope that helps,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dibbler