dibbler-relay(8)

1dibbler-relay(8)                    Dibbler                   dibbler-relay(8)
2
3
4

NAME

6       dibbler-relay - a portable DHCPv6 relay
7
8

DESCRIPTION

10       dibbler-relay  is a portable implementation of the DHCPv6 relay. DHCPv6
11       relays are proxies, which allow one  server  to  support  links,  which
12       server  is  not  directly  connected  to. There are ports available for
13       Linux 2.4/2.6 systems as well as MS  Windows  XP  and  2003.  They  are
14       freely available under GNU GPL version 2 (or later) license.
15
16

SYNOPSIS

18       dibbler-relay [ run | start | stop | status ]
19
20

OPTIONS

22       run - starts relay in the console. Relay can be closed using ctrl-c.
23
24       start - starts relay in daemon mode.
25
26       stop - stops running relay.
27
28       status - shows status of the relay.
29
30

EXAMPLES

32       Relay forwards DHCPv6 messages between interfaces. Messages from client
33       are encapsulated and forwarded as  RELAY_FORW  messages.  Replies  from
34       server  are  received  as RELAY_REPL message. After decapsulation, they
35       are being sent back to clients.
36
37       It is vital to inform server, where this relayed message was  received.
38       DHCPv6  does  this  using  interface-id option. This identifier must be
39       unique. Otherwise relays will get confused when they will receive reply
40       from server. Note that this id does not need to be alligned with system
41       interface id (ifindex). Think about it as "ethernet segment identifier"
42       if  you  are  using  Ethernet network or as "bss identifier" if you are
43       using 802.11 network.
44
45       Let's assume this case: relay has 2 interfaces: eth0 and eth1.  Clients
46       are  located  on  the  eth1  network. Relay should receive data on that
47       interface using well-known ALL_DHCP_RELAYS_AND_SERVER multicast address
48       (ff02::1:2).  Relay also listens on its global address 2000::123. Pack‐
49       ets received on the eth1 should be forwarded  on  the  eth0  interface,
50       also using multicast address:
51
52       log-level 8
53       log-mode short
54
55       iface eth0 {
56         server multicast yes
57       }
58
59       iface eth1 {
60         client multicast yes
61         client unicast 2000::123
62         interface-id 1000
63       }
64
65       Here  is  another  exmaple. This time messages should be forwarded from
66       eth1 and eth3 to the eth0 interface (using multicast) and to  the  eth2
67       interface  (using server's global address 2000::546). Also clients must
68       use multicasts (the default approach):
69
70       iface eth0 {
71         server multicast yes
72       }
73
74       iface eth2 {
75         server unicast 2000::456
76       }
77
78       iface eth1 {
79         client multicast yes
80         interface-id 1000
81       }
82
83       iface eth3 {
84         client multicast yes
85         interface-id 1001
86       }
87
88

FILES

90       All files are created in the /var/lib/dibbler directory. During  opera‐
91       tion, Dibbler saves various file in that directory. Dibbler relay reads
92       /etc/dibbler/relay.conf file. Log file is named client.log.
93
94

STANDARDS

96       This implementation aims at conformance to the following standards:
97
98       RFC 3315 DHCP for IPv6
99
100       RFC 3736 Stateless DHCPv6
101
102

BUGS

104       Bugs     are     tracked     with      bugzilla,      available      at
105       http://klub.com.pl/bugzilla/. If you belive you have found a bug, don't
106       hesitate to report it.
107
108

AUTHOR

110       Dibbler was developed as master thesis on the Technical  University  of
111       Gdansk by Tomasz Mrugalski and Marek Senderski. Currently Marek has not
112       enough free time, so this project is being developed by Tomasz  Mrugal‐
113       ski. Author can be reached at thomson@klub.com.pl.
114
115