[Dibbler] Multiple Relays Problem

Tomasz Mrugalski thomson at klub.com.pl
Tue Apr 23 16:55:02 CEST 2013


On 23.04.2013 08:19, Jean-Jacques Sarton wrote:
> Hi,
> 
> The line for which you have an error contain:
>  pool 2a00:d90:1ab:616:biff::/80
> The letter i may be the reason.
It is.

Also, a couple of random comments:

> Am 20.04.2013 11:41, schrieb Axel Dahlberg:
>> I havin trouble in enable multiple relays. I saw this post from 2009 and we
>> have the same setup.
>> http://klub.com.pl/lists/dibbler/2009-November/000297.html
A LOT has changed in the code since 2009. In particular, recently the
support for relay has been cleaned up. Linkaddr field from RELAY-FORW is
now properly supported. This has been working for some time (added after
0.8.3 was published, so it is git only for now, until 0.8.4 is
published), but was never clearly documented. I just pushed updated
User's Guide to the git repo. The basic principle is quite easy.

You just add:

subnet prefix/length

to you relay definition and server will try to do interface-id matching
first. If that fails, it will try to do a match based on linkaddr field.
That's what the subnet definition is for.

>> Also unicast is only able to be set once in one relay{}. Is it
>> possible to make all of the relays listen to the same unicast
>> address?

Finally, I think you misunderstood the concept of unicast. Normally all
communication towards the server (from clients or from relays) is done
using multicast, unless explicitly configured otherwise. It is possible
to configure server to listen on a specific unicast address in addition
to the multicast. This is done on a per server basis and you specify it
only once. Once enabled, it opens up a new socket and server will
process all incoming traffic to that address, so you can say that it
applies to all your relays (and clients that happen to support unicast
traffic). It doesn't make sense to repeat the same unicast twice or more.

If you want your relays to send data to that unicast address rather than
to the default multicast, you need to add in the global section of your
server.conf:

unicast address-configured-on-your-server

and then configure your relays to send out traffic to that address.

As said before, the git code supports subnet definitions. It also has
significantly improved relay selection routines. I'm eager to hear from
you if it worked for you.

Cheers,
Tomek



>>
>>                         server
>>                        +------+
>> link1------relay1--    |      |
>>                     \  |      |
>> link2------relay2---int1      |
>>                     /  |      |
>> link3------relay3--    |      |
>>                        +------+
>>
>> My configuration look like this:
>> # Prefix Delegation Config
>> # Logging level range: 1(Emergency)-8(Debug)
>> log-level 8
>> # Don't log full date
>> log-mode short
>> # set preference of this server to 0 (higher = more prefered)
>> preference 0
>> iface relay1
>> {
>>     relay eth1
>>     unicast 2a00:d90:1ab:babe::2
>>     #Customer 1 id
>>     interface-id "KUND1:KUND_1_CPE"
>>     t1 1000
>>     t2 2000
>>     prefered-lifetime 3600
>>     valid-lifetime 7200
>>     pd-class
>>     {
>>         pd-pool 2a00:d90:1ab:ba00::/56
>>         pd-length 64
>>     }
>>     class
>>     {
>>         pool 2a00:d90:1ab:616:b00b::/80
>>     }
>> #provide DNS server location to the clients
>>     option dns-server 2001:4860:4860::8888,2001:4860:4860::8844
>> #provide their domain name
>>     option domain kund1.com
>> }
>> iface relay2
>> {
>>     relay eth1
>>     #unicast 2a00:d90:1ab:babe::2 *###Only works on one place in the config*
>>     #Customer 2 id
>>     interface-id "KUND2:KUND_2_CPE"
>>     t1 1000
>>     t2 2000
>>     prefered-lifetime 3600
>>     valid-lifetime 7200
>>     pd-class
>>     {
>>         pd-pool 2a00:d90:1ab:ff00::/56
>>         pd-length 64
>>     }
>>     class
>>     {
>>         pool 2a00:d90:1ab:616:biff::/80    *###### Gets an error here*
>>     }
>> #provide DNS server location to the clients
>>     option dns-server 2001:4860:4860::8888,2001:4860:4860::8844
>> #provide their domain name
>>     option domain kund2.com
>> }
>>
>> To the question:
>> at relay2 class dibbler conplains at pool 2a00.....
>> "*34:11 Server Critical  Config parse error: line 59, unexpected [2] token."
>> *
>>
>> root at sth-dgc-lab-exjobbdhcp:/etc/dibbler# dibbler-server run
>> | Dibbler - a portable DHCPv6, version 0.8.3 (SERVER, Linux port)
>> | Authors : Tomasz Mrugalski<thomson(at)klub.com.pl>,Marek
>> Senderski<msend(at)o2.pl>
>> | Licence : GNU GPL v2 only. Developed at Gdansk University of Technology.
>> | Homepage: http://klub.com.pl/dhcpv6/
>> 2013.04.19 16:34:11 Server Notice    My pid (2968) is stored in
>> /var/lib/dibbler/server.pid
>> 2013.04.19 16:34:11 Server Notice    Detected iface eth1/3,
>> MAC=00:14:5e:de:0c:a0.
>> 2013.04.19 16:34:11 Server Notice    Detected iface eth0/2,
>> MAC=00:14:5e:de:0c:9e.
>> 2013.04.19 16:34:11 Server Notice    Detected iface lo/1,
>> MAC=00:00:00:00:00:00.
>> 2013.04.19 16:34:11 Server Notice    Parsing /etc/dibbler/server.conf
>> config file...
>> 34:11 Server Debug     PD: Client will receive /64 prefixes (T1=1000..1000,
>> T2=2000..2000).
>> 34:11 Server Debug     PD: Pool 2a00:d90:1ab:ba00:: -
>> 2a00:d90:1ab:baff:ffff:ffff:ffff:ffff, pool length: 56.
>> 34:11 Server Debug     PD: Up to 256 prefixes may be assigned.
>> 34:11 Server Debug     0 per-client configurations (exceptions) added.
>> 34:11 Server Debug     PD: Client will receive /64 prefixes (T1=1000..1000,
>> T2=2000..2000).
>> 34:11 Server Debug     PD: Pool 2a00:d90:1ab:ff00:: -
>> 2a00:d90:1ab:ffff:ffff:ffff:ffff:ffff, pool length: 56.
>> 34:11 Server Debug     PD: Up to 256 prefixes may be assigned.
>> *34:11 Server Critical  Config parse error: line 59, unexpected [2] token.*
>> 34:11 Server Debug     Parsing /etc/dibbler/server.conf done.
>> 34:11 Server Critical  Fatal error during config parsing.
>> 34:11 Server Critical  Fatal error during CfgMgr initialization.
>>
>>
>> Thanks in advanced!



More information about the Dibbler mailing list