1dibbler-client(8) Dibbler dibbler-client(8)
2
3
4
6 dibbler-client - a portable DHCPv6 client
7
8
10 dibbler-client is a portable implementation of the DHCPv6 client. It
11 supports both stateful (i.e. IPv6 address granting) and stateless (i.e.
12 options granting) autoconfiguration. 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
18 dibbler-client [ run | start | stop | status | install | uninstall ]
19
20
22 run - starts client in the console. Client can be closed using ctrl-c.
23
24 start - starts client in daemon mode.
25
26 stop - stops running clients.
27
28 status - shows status of the client and server.
29
30 install - installs client as a service. This is not implemented yet.
31
32 uninstall - uninstall client service. This is not implemented yet.
33
34
36 Let's start with simple configuration. We want receive one IPv6 address
37 and there is only one Ethernet interface present. In that case
38 client.conf file might be completly empty. Dibbler client will request
39 for one IPv6 address on each up, running and multicast capable inter‐
40 face (except loopback).
41
42 Now some real example. We want one IPv6 address and receive DNS servers
43 and domain name. We are also not interested in the details, so debug
44 mode is disabled.
45
46 log-mode short
47 log-level 6
48 iface eth0
49 {
50 ia { }
51 option dns-server
52 option domain
53 }
54
55 Next example: we want only NIS domain and NIS server information. That
56 information should be periodicaly renewed, so we use lifetime option.
57 We don't need any addresses so stateless mode is used.
58
59 log-mode short
60 iface eth0
61 {
62 stateless
63 option nis-server
64 option nis-domain
65 option lifetime
66 }
67
68 More examples can be found in the User's Guide.
69
70
72 All files are created in the /var/lib/dibbler directory. Dibbler client
73 reads /var/lib/dibbler/client.conf file. During operation, Dibbler
74 saves various file in that directory. After reception of the DNS
75 servers or domain informations, they are added to the /etc/resolv.conf
76 file. After shutdown, that information is removed from that file.
77 Option values are stored in the option-* files. Log file is named
78 client.log.
79
80
82 This implementation aims at conformance to the following standards:
83
84 RFC 3315 DHCP for IPv6
85
86 RFC 3319 SIP options for DHCPv6
87
88 RFC 3646 DNS server options for DHCPv6
89
90 RFC 3736 Stateless DHCPv6
91
92 RFC 3898 NIS options for DHCPv6
93
94 Also options specified in following drafts are implemented:
95
96 draft-ietf-dhc-dhcpv6-opt-timeconfig-03.txt NTP and timezone options.
97
98 draft-ietf-dhc-dhcpv6-opt-lifetime-00.txt Option renewal.
99
100
102 Bugs are tracked with bugzilla, available at
103 http://klub.com.pl/bugzilla/. If you belive you have found a bug, don't
104 hesitate to report it.
105
106
108 Dibbler was developed as master thesis on the Technical University of
109 Gdansk by Tomasz Mrugalski and Marek Senderski. Currently Marek has not
110 enough free time, so this project is being developed by Tomasz Mrugal‐
111 ski. Authors can be reached at thomson@klub.com.pl and msend@o2.pl
112
113
115 There is dibbler-server(8) manual page. You are also advised to take a
116 look at project website located at http://klub.com.pl/dhcpv6/. As far
117 as authors know, this is the only Windows DHCPv6 stateful implementa‐
118 tion available. It is also one of two freely available under Linux. The
119 other Linux implementation is available at http://dhcpv6.source‐
120 forge.net, but it is rather outdated and seems not being actively
121 developed.
122
123
124
125GNU 2004-12-11 dibbler-client(8)