LINUX PPPOE V6 服务器搭建测试_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
LINUX PPPOE V6 服务器搭建测试
上传于|0|0|文档简介
&&讲解如何在DEBIAN上搭建一个PPPOE V6 的SERVER,以及如何分到地址,软件如何安装等,非常完整,配以详细的注释,浅显易懂,值得收藏
阅读已结束，如果下载本文需要使用0下载券
想免费下载更多文档？
定制HR最喜欢的简历
下载文档到电脑，查找使用更方便
还剩4页未读，继续阅读
定制HR最喜欢的简历
你可能喜欢此次IPV6服务器配置主要使用Linux软件来实；Dibbler实现DHCPV6的功能；RADVD实现IPV6路由功能；一，在Linux系统上安装这两个软件；开启IPV6路由转发：；#vim/etc/sysctl.conf；添加下面一行信息；net.ipv6.conf.all.forwar；radvd安装起来比较简单，通过在线安装就可以成；#yuminsta
此次IPV6服务器配置主要使用Linux软件来实现IPV6 DHCP功能和IPV6 路由器功能。
Dibbler实现DHCPV6的功能。
RADVD实现IPV6路由功能。
一，在Linux系统上安装这两个软件。
开启IPV6路由转发：
#vim /etc/sysctl.conf
添加下面一行信息
net.ipv6.conf.all.forwarding=1
radvd安装起来比较简单，通过在线安装就可以成功安装。
#yum install radvd
dibbler安装起来稍微有点麻烦，需要自己编译安装，其实如果熟悉了安装起来也是很方便的，下面我说下我安装的过程：
先去官方网站下载最新的dibbler源码包，一般是以.tar.gz结尾的文件。
我下载的是dibbler-0.8.1.tar.gz，下载完以后就是先解压#tar -xzvf dibbler-0.8.1.tar.gz
解压完你会看到dibbler-0.8.1这样一个文件夹。
进入文件夹，然后就是编译安装了，安装之前请确认你的linux系统已经安装好了编译环境，一般就是gcc gcc-c++ kernel-headers make等软件环境。
dibbler-0.8.1文件夹内已经有Makefile文件了，可以直接：
#make install
进行安装，但是这样dibbler会安装到默认的文件夹内。
我为了以后卸载方便，帮dibbler软件指定了一个安装的目录：
#./configure --prefix=/opt/dibbler-0.8.1 （此命令可以配置将dibbler安装到/opt/dibbler-0.8.1文件夹内）
#make install
如果没有出现异常，dibbler已经成功安装你的电脑上了，但是还有后续一些小的地方需要改动。
为了以后适用方便，建立dibbler的软链接。
#ln -s /opt/dibbler-0.8.1/sbin/dibbler-* /usr/local/sbin/
#ln -s /opt/dibbler-0.8.1/etc/ /etc/dibbler
二，修改配置文件
（1） 修改/etc/radvd.conf配置文件内容
radvd.conf基本内容如下：
interface eth0
AdvOtherConfigF
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
prefix 2001:db8:1:0::/64
AdvRouterA
radvd.conf参数说明（根据自己的理解说明，不保证完全正确，仅供参考）
参考上海电信研究院IPV6环境抓包修改radvd.conf配置文件如下：
interface eth0
AdvManagedF
AdvDefaultLifetime 1800;
AdvRetransTimer 1000;
AdvOtherConfigF
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvSourceLLA
AdvLinkMTU 1500;
# prefix 2001:db8:1:0::/64
AdvRouterA
************************************************
INTERFACE SPECIFIC OPTIONS(接口参数选项）：
************************************************
IgnoreIfMissing on|off
配置该参数，使radvd在启动时，忽略不存在的接口参数，比如，配置文件里面配置了接口ppp0，但是ppp0在radvd启动的时候不存在，默认情况下，radvd会报错，无法启动；配置该参数值为on后，虽然ppp0不存在，但是radvd仍然可以成功启动。这个参数对动态的接口参数比较有用。
参数默认为off。
AdvSendAdvert on|off
该参数表示radvd是否定期发送路由通告消息和回应路由请求消息。
参数默认为off
UnicastOnly on|off
该参数表示接口类型仅支持单播。
参数默认为off
MaxRtrAdvInterval seconds
该参数表示radvd定期发送路由通告消息的最大间隔时间，以秒为单位。参数数值必须不小于4s，并且不大于1800s。
参数默认为600s
MinRtrAdvInterval seconds
该参数表示radvd定期发送路由通告消息的足迹小间隔时间，以秒为单位。参数数值必须比小于3s,并且不大于0.75*MaxRtrAdvInterval
参数默认为0.33*MaxRtrAdvInterval
MinDelayBetweenRAs seconds
该参数表示radvd允许的从接口发送多播路由通告消息的最小时间，以秒为单位。 参数默认为3
AdvManagedFlag on|off
如果配置该参数为on，路由通告消息里面的M标记将变为1，主机将通过有状态自动配置协议（DHCPV6）配置IP地址和其它信息。
参数默认为off
AdvOtherConfigFlag on|off
如果配置该参数为on,路由通告消息里面的O标记将变为1，主机将通过有状态自动配置协议（DHCPV6）配置除IP地址以外的其它信息。
参数默认为off
AdvLinkMTU integer
MTU选项用来在链路MTU不是明确的情况下确保链路上的所有节点使用相同的MTU。如果该参数的值不为0，那么参数的值必须不小于1280，并且不大于当前链路允许的最大MTU（以太网允许的最大MTU为1500）
参数默认为0
AdvReachableTime milliseconds
该参数用来侦测邻居不可达的时间，以毫秒为单位。最长不超过3，600，000毫秒（1小时），如果值为0，表示该路由器没有特别指定参数值。
参数默认为0
AdvRetransTimer milliseconds
该参数表示邻居请求消息重传的时间，用来进行地址解析和邻居不可达侦测，如果值为0，表示该路由器没有特别指定参数值。
参数默认为0
AdvCurHopLimit integer
该参数表示路由的跳数限制，如果值为0，表示该路由器没有特别指定参数值。 参数默认为64
AdvDefaultLifetime seconds
该参数表示连接默认路由的生存时间。最大可以达到18.2小时。如果生存时间为0，表示该路由器不是一个默认路由器，并且不应该出现在默认路由器列表里面。
参数值要么为0，要么在MaxRtrAdvInterval和9000秒直接。
参数默认为3*MaxRtrAdvInterval(最小为1秒）
AdvDefaultPreference low|medium|high
该参数表示连接的默认路由器的优先级，可选的值有&low&,&medium&,&high&
参数默认为medium
AdvSourceLLAddress on|off
如果配置该参数，外发的接口链路地址将包括在RA消息里面。
参数默认为on
AdvHomeAgentFlag on|off
如果设置该参数为on，表示该路由器可以充当移动IPV6家庭代理，并且，MinRtrAdvInterval和MaxRtrAdvInterval将使用移动IPV6指定的最小的限制。
参数默认为off
AdvHomeAgentInfo on|off
如果配置该参数为on,路由通告消息里面将包括Home Agent Information 选项（移动IPV6规定），并且如果要启用该参数，AdvHomeAgentFlag必须为on。
参数默认为off
HomeAgentLifetime seconds
该参数表示路由器提供移动IPV6 Home Agent 服务的时间，参数值不能设为0。参数的最大值为65520秒（18.2小时）。如果AdvHomeAgentInfo没有开启，将忽略该参数。 参数默认为AdvDefaultLifetime
HomeAgentPreference integer
该参数表示Home Agent的优先级，参数值大于0表示更好的Home Agent,参数值小于0表示不是很好的Home Agent。如果AdvHomeAgentInfo没有开启，将忽略该参数。
参数默认为0
AdvMobRtrSupportFlag on|off
如果配置该参数为on，表示Home Agent支持移动路由器注册。如果要开启该选项，必须先开启AdvHomeAgentInfo。
参数默认为off
AdvIntervalOpt on|off
如果配置该选项为on，路由通告消息里面将包括Advertisement Interval Option。并且，MinRtrAdvInterval和MaxRtrAdvInterval将使用移动IPV6指定的最小的限制。
通告时间间隔依赖于MaxRtrAdvInterval参数的配置，除非参数的值小于200ms，通常，路由间隔时间等于MaxAdvRtrInterval+20ms
参数默认为off
************************************************
PREFIX SPECIFIC OPTIONS(前缀参数选项）：
************************************************
AdvOnLink on|off
如果配置该选项为on，表示这个前缀可以用于在链确定，这意味着此前缀可以用来确定一个地址是否在链；如果配置该选项为off，通告信息里面将没有这个前缀的连接状态信息。 参数默认为on
AdvAutonomous on|off
如果配置该选项为on,表示这个前缀可以用来进行地址自动配置。
参数默认为on
AdvRouterAddr on|off
如果该选项为on，表示接口将使用地址代替前缀发送，这是移动IPV6的要求。并且，MinRtrAdvInterval和MaxRtrAdvInterval将使用移动IPV6指定的最小的限制。 参数默认为off
AdvValidLifetime seconds|infinity
该参数表示前缀可以用来确定一个地址是否在链的有效时间。infinity表示无穷大的时间（即所有的值都为1（0xffffffff))。
备注：如果一个已经存在的前缀的AdvValidLifetime小于2个小时，客户端应该忽略它。
三亿文库包含各类专业文献、外语学习资料、生活休闲娱乐、各类资格考试、行业资料、39IPv6服务器配置笔记等内容。　
　IPV6笔记 11页 1下载券 IPV6笔记 12页 1下载券 IPv6服务器配置笔记 14页 1...IPv6 支持地址范围 ipv4 : 2 的 32 次方 ipv6:2 的 128 次方 global 地址... 　版本: IPV4,IPV6 2. 标识符、标志、片偏移: 一段数据太长会被切片,然后通过...服务器响应客户机的 DHCPDISCOVER 报文,并向客户机提供各种的配置参数 DHCP-... 　路由交换笔记_计算机硬件及网络_IT/计算机_专业资料。...通 常用来放置服务器、数据库等设备 防火墙(firewall...IPv6、VPN 11、组播、广播流量必须使用 ACL 明确... 　为主流服务器操作系统配置Ipv6_专业资料。为主流服务器操作系统配置Ipv6IPv4 技术在网络发展中起到了巨大的作用, 不过随着时间的流逝它无论在网络地址的提供、 服务... 　IPv6服务器配置笔记 14页 1下载券 ipv6笔记 暂无评价 22页 3下载券 ipv6学习...过渡方式丰富多彩:从 IPV4 过渡到 IPV6 的方式很多 CISCO 12.2(2)T 及更高... 　FTP在客户端与服务器的内部建立两条TCP连接,一条是控制连接,端口号为21;另一...B、IPv6使用更小的路由表 C、IPv6增加了增强的组播 D、IPv6加入了对自动配置(... 　Linux运维笔记_计算机软件及应用_IT/计算机_专业资料...IPV6INIT=no USERCTL=no DNS1=10.10.5.12 6)...你自己服务器的网卡,不同的服务器 以及配置下和我... 　第五天 网络配置和文件服务器_电脑基础知识_IT/计算机_专业资料。补充: IP地址: Ipv4 tcp udp 2*32 Ipv6 网络通讯协议 用户数据报协议 常见网络端口: 20 21 ... 　到不同的VLAN,使用 VMPS(VLAN管理策略服务器)完成 ...网络笔记 大型企业网络笔记 二、配置命令 配置命令 ...1985--IPv4; 2029--IPv6 1985--IPv4; 1985--...DHCPv6: Dibbler - a portable DHCPv6
Dibbler is a portable DHCPv6 implementation. It supports stateful (i.e. IPv6 address granting and IPv6 prefix delegation) as well
as stateless (i.e. option granting) autoconfiguration for IPv6. Currently Linux 2.4 or later and Windows XP or later
are supported. It features easy to use install packages (Clickable
Windows installer and RPM and DEB packages for Linux) and extensive documentation (both for users as
well as developers). Dibbler is developed under
licence. It means that it is free for all, including commercial usage.
This project was started in 2003 as master thesis by Tomasz Mrugalski and
Marek Senderski of
on . This project is named Dibbler (after famous CMOT Dibbler from fantastic
Discworld series by Terry Pratchett). If you are interested in porting it to other systems/architectures,
for info and guidelines.
Please do not contact author directly and instead use mailing lists for discussion or bugzilla for bug reports.
Contact author directly only if discussing security issues or other confidential matters.
Documentation
Supported architectures and systems:
, x86 (experimental)
, x86 (experimental)
Experimental support means that this architecture lacks confirmation
by users that everything is fully functional or there are known
deficiencies.
If you have successfuly run Dibbler on onther architectures or systems, let me know so I can update
this list. If you would like to have Dibbler running on some other architecture not mentioned above,
and you are ready to provide me access to such hardware, let me know.
Already got feedback from:
Czech Republic
United States
Switzerland
United Kingdom
Philippines
Bosnia and Herzegovina
New Zealand
Costa Rica
If you use Dibbler and live in a country not listed above,
let me know so I can update this list.
Dibbler is part of the following Linux distributions:
: Dibbler 1.0.1 has been released.
It contains a number of bug fixes that were already released
in the 1.0.1 Release Candidate 1 and several new fixes.
One of them may have security implications, so upgrade
is strongly encouraged.
: The second Release Candidate for Dibbler 1.0.0 has been released.
Due to other obligations, 1.0.0RC1 was available for a very long time
and I never had a chance to release 1.0.0 final. In the mean time, quite
a few of fixes and small features were added (Changelog mentions 35 items,
but I'm sure some of them were not listed). So formally this is a second
RC, but it contains unexpectedly large changes for an RC. Keep that in
mind. This time I expect the delay between RC and final to be much shorter
(couple weeks).
Couple changes worth mentioning:
dibbler client now configures received prefix with /128, not /64. This
will likely raise some eyebrows, but that how DHCPv6 is supposed to work.
Please see
for extra details.
There are reports that Reconfigure messages are sent to the wrong address
if the client connected via relays. See .
There are reports that Dibbler has problems on Ubuntu 14.04. That was
traced to a Linux kernel issue and is fixed in 3.15.2. See
Windows port improved, now using Visual Studio 2013 Express.
Issue tracker on github has been disabled. It was awkward to use both
bugzilla and github.
See CHANGELOG for a complete list of changes. If you find bugs, please report
If you need help or want to share your thoughts, take a look at one
of two mailing lists:
. Please do not contact
author directly, unless you want to report security issues or discuss
confidential matters.
: Dibbler 1.0.0 Release Candidate 1 has been released!
This version is being released today to celebrate 10th anniversary
of the DHCPv6 protocol. The RFC3315 that defines it was published exactly
10 years ago - on 30th July of 2003.
According to the author's knowledge, Dibbler is currently the only
implementation that implements every feature mentioned in the RFC3315.
Please note that feature complete doe-)
This release brings in all outstanding RFC3315 features that used to
be missing in previous releases. In particular:
Reconfigure support. Server is now able to load database, check it against
existing configuration and send reconfigure to clients that have
configuration out of date. Clients are able to accept incoming reconfigure
messages and initiate reconfiguration.
Reconfigure-key authentication. Server is now able to generate
reconfigure-key when responding to clients and later use that key to
sign reconfigure messages. Clients are able to store received key and
later confirm that incoming reconfigure message is properly signed.
Delayed authentication - clients and server are able to leverage
pre-configured keys to sign later parts of the messages exchange.
Dibbler authentication - it is a rewritten mechanism used in earlier
versions. It has number of advantages compared to delayed
authentication, but has a number of advantages over it. First, it
secures the whole transmission, including initial SOLICIT
message. Second, it offers much stronger digests: HMAC-MD5, HMAC-SHA1,
HMAC-SHA224, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512. As this is
Dibbler specific extension, it is not expected to inter-operate with
any other implementations. Third, it does not require to maintain
strict client DUID-key-id bindings on the server side, as clients send
ID of the key they used to protect their transmissions.
Replay detection - both client and server can now detect whether
receiving message is a new one or it is replayed by attacker.
Client is now able to act according to received M(managed) and O(Other
configuration options) in Router Advertisements, if configured to
Server and client now checks database against changes in the network
interfaces and tries to update it if possible. That should be helpful
if you happen to lost and recreated an interface (e.g. broken ppp
connection).
: Dibbler 0.8.4 has been released.
There is no single major new feature, just a lot of bug fixes:
34 bug fixes, tweaks and small improvements since 0.8.3.
Vendor class and User class methods are now implemented.
Relay support has been rewritten. It is now possible to select subnet
based on interface-id or value of linkaddr field set by the relay.
Client classification has been improved and now can be used to
differentiate between 2 or more classes, e.g. docsis3.0 and eRouter
in cable networks.
Confirm support has been cleaned. Daemon mode no
longer has issues when reading from socket descriptor 0.
The database format has changed a bit. It now stores interface names,
not just interface indexes. That is helpful in cases your interfaces
has changed, e.g. when your ppp0 interface went down and was
recreated with different ifindex. Opening up old database should be
seamless, but make sure you make a backup before migrating to 0.8.4.
Dibbler server no longer does by default destination address filtering
against the addresses sockets are bound to. If that bothers you,
because on your OS you see the same incoming packet being received over
two sockets, please use --enable-dst-addr-check in configure phase.
: Dibbler 0.8.4 Release Candidate 1 has been released.
There is no single major new feature, just a lot of bug fixes.
In particular, relay support has been rewritten. It is now possible to select
subnet based on interface-id or value of linkaddr field set by the relay.
Client classification has been improved and now can be used to differentiate
between 2 or more classes, e.g. docsis3.0 and eRouter in cable networks.
Confirm support has been cleaned. Daemon mode no longer has issues when reading
from socket descriptor 0.
See CHANGELOG for a complete list of changes.
: Dibbler 0.8.3 has been released.
The biggest feature is a rewritten address and prefix allocation engine. Both
follow the same algorithm now. It is possible to reserve specific address
and/or prefix for a given host. The host can be referenced by DUID, remote-id
or link-local address. Both in-pool and out-of-pool reservations are now
supported.
Support for DDNS is now significantly improved. Secure DNS Updates using TSIG
are now supported. Many, many bugs were fixed and the FQDN handling code is now
much more robust.
The code now compiles on Solaris 11. It is not yet fully usable, and there are
outstanding problems with link-layer address detection, but it is better than
Script execution is now improved as well. It is called when receiving stateless
configuration (after receiving reply to INF-REQUEST) and extra options (like
FQDN and vendor-specific info) are now properly passed.
See CHANGELOG for a complete list of changes.
: Dibbler 0.8.1 Release Candidate 1 is released. This release introduces
number of useful additions, new features and the usual bug fixes. In particular,
the highlights of this release are:
Support for routing configuration was added. Yes, you read that correctly.
Recent draft draft-ietf-mif-dhcpv6-route-option defines provisioning mechanism
that delivers routing information over DHCPv6. Although this implementation is
not entirely complete (there are certain limitations, see User's Guide), it is very usable.
This feature was tested with excellent
implementation and is interoperable. You may want to read
for additional information.
Script support is rewritten. Client can call a script every time it receives a
message and pass all received options as environment variables. That is very
convenient way to extend client with custom actions. This feature is going to
be further expanded in upcoming releases.
Server is now able to run scripts, too. That is convenient if you need your
server to execute custom actions. One notable example is a routing reconfiguration
after prefix was delegated to a client.
Added support for FreeBSD, NetBSD and OpenBSD. Mac OS X support is now also
significantly improved. To achieve this level of portability, build system
was completely rewritten and is now using automake and autoconf tools.
You can now use ./configure script to enable or disable various parameters.
Makefile modification is no longer necessary.
DNS Update can now be performed over UDP, TCP or both (try over UDP and if it fails,
try TCP). Configurable timeout for DNS Updates added.
Significant update in prefix delegation support. Server will now remember previously
assigned prefixes and will try to assign the same prefix to returning client.
Support for DS-Lite tunnels configuration added (RFC6334)
Rather large User's Guide documentation update
Fixed mis-aligned memory reads on ARMv5 architecture
Added support for unittests using googletests. Number of tests is small now,
but is expected to grow.
: Dibbler source has been moved to GIT repository at github.
:Dibbler 0.8.0 has been released. That is a new release after long time. Dibbler development just resumed.
: I got my first mac! Yay! After figuring out how to do anything useful without insert,
delete, pgup and pgdown, I think I was able to fix many problem with Mac OS port. I'm able to run both
client and server on my mac. If you have Mac hardware available, please Get the latest code from SVN
and give it a try.
: I'm happy to announce that my 7 year struggle to complete my Ph.D. is finally
over. It appears that I will finally have some time to reinvigorate Dibbler. There are many
things happening lately in DHCP world, so it seems I'll be busy in the near future. In the
mean time, Dibbler became quite outdated. Please send a note to the mailing list regarding
missing features that you find the most urgent to develop.Cheers, Tomasz Mrugalski, Ph.D.
: Good news, everyone! After a year and a half, I finally
found some time to wrap everything that was slowly going around, packed and
released 0.8.0 Release Candidate 1. The major changes include support for
Windows 7 and Mac OS (both experimental), support for CONFIRM, client and
server will reload their databases during boot, Linux console now can be
colorful, support for bunch of experimental stuff added. Finally, there's
large code refactoring taking place, so let's hope that everything is working...
Feature List
Server discovery and address assignment (SOLICIT, ADVERTISE, REQUEST and REPLY
messages) - This is a most common case: client discovers servers available in the local network,
then asks for an address (and possibly additional options like DNS configuration), which is granted
by a server.
Best server selection - when client detects more than one server available (by receiving more than
one ADVERTISE message), it chooses the best one and remembers remaining ones as a backup.
Relay support - In a larger network, which contains several Ethernet segments and/or wireless
areas, sometimes centrally located DHCPv6 server might not be directly reachable. In such cace,
additional proxies, so called relays, might be deployed to relay communication between clients and
a remote server. Dibbler server supports indirect communication with clients via relays. Standalone,
lightweight relay implementation is also available. Clients are capable of talking to the server
directly or via relays.
Leasequery - From the sysadmin's perspective, it is often beneficial to check which address
has been assigned to a specific client or who got a specific address. To do so, it is possible to query
server for such information. There is a special type of DHCPv6 entity called requestor that performs such queries
and parses server's answers.
Address renewal - After receiving address from a server, client might be instructed to renew its
address at regular intervals. Client periodically sends RENEW messege to a server, which granted
its address. In case of communication failure, client is also able to attempt emergency address
renewal (i.e. it sends REBIND message to any server).
Unicast communication - if specific conditions are met, client could send messages directly to a
server's unicast address, so additional servers does not need to process those messages. It also
improves effciency, as all nodes present in LAN segment receive multicast packets.
Duplicate address detection - Client is able to detect and properly handle faulty situation, when
server grants an address which is illegaly used by some other host. It will inform server of such
circumstances (using DECLINE message), and request another address. Server will mark this
address as used by unknown host, and will assign another address to a client.
Power failure/crash support - After client recovers from a crash or a power failure, it still can have
valid addresses assigned. In such circumstances, client uses CONFIRM message, to config if those
addresses are still valid.
Normal and temporary addresses - Depending on its purpose, client can be configured to ask for
normal (IA NA option) or temporary (IA TA option). Although use of temporary addresses is
rather uncommon, both dibbler server and client support it.
Hint system - Client can be configured to send various parameters and addresses in the REQUEST
message. It will be treated as a hint by the server. If such hint is valid, it will be granted for this
Server caching - Server can cache granted addresses, so the same client will receive the same address
each time it asks. Size of this cache can be configured.
Stateless mode - Client can be configured to not ask for any addresses, but the configuration
options only. In such case, when no addresses are granted, such configuration is called stateless
(INFORMATION-REQUEST message is used instead of normal REQUEST).
Rapid Commit - Sometimes it is desirable to quicken configuration process. If both client and server
are configured to use rapid commit, address assignment procedure can be shortened to 2 messages,
instead of usual 4. Major advantage is lesser network usage and quicker client startup time.
Also following extensions are supported:
DNS Servers - During normal operation, almost all hosts require constant use of the DNS servers.
It is necessary for event basic operations, like web surfing. DHCPv6 client can ask for information
about DNS servers and DHCPv6 server will provide necessary information.
Domain Name - Client might be interested in obtaining information about its domain. Properly
configured domain allow reference to a different hosts in the same domain using hostname only, not
the full domain name, e.g.
with properly configured domain can refer to another
host in the same domain by using 'bob' only, instead of full name .
NTP Servers - To prevent clock misconfiguration and drift, NTP protocol can be used to synchronize
clocks. However, to successful use it, location of near NTP servers must be known. Dibbler
is able to configure this information.
Time Zone - To avoid time-related ambiguation, each host should have timezone set properly.
Dibbler is able to pass this parameter to all clients, who request it.
SIP Servers - Session Initiation Protocol (SIP) is commonly used in VoIP solutions. One of the
necessary information is SIP server addresses. This information can be passed to the clients.
SIP Domain Name - SIP domain name is another important parameter of the VoIP capable nodes.
This parameter can be passed to all clients, who ask for it.
NIS, NIS+ Server - Network Information Service is a protocol for sharing authentication parameters
between multiple Unix or Linux nodes. Both NIS and NIS+ server adresses can be passed to the
NIS, NIS+ Domain Name - NIS or NIS+ domain name is another necessary parameter for NIS or
NIS+. It can be obtained from the DHCPv6 server to all clients, who require it.
Option Renewal Mechanism (Lifetime option) - All of the options mentioned on this list can be
refreshed periodically. This might be handy if one of those parameters change.
Dynamic DNS Updates - Server can assign a fully qualified domain name for a client. To make such
name useful, DNS servers must be informed that such name is bound to a specific IPv6 address.
This procedure is called DNS Update. There are two kinds of the DNS Updates: forward and
reverse. First is used to translate domain name to an address. The second one is used to obtain full
domain name of a known address.
Prefix Delegation - Server can delegate a prefix to a client. That feature is intended to be used
mainly by routers, which obtain prefixes from an upper level router. Client after receiving prefix, will
generate smaller prefixes for each available interface.
Download: stable
Here's newest stable version. If you need, for some reason, older releases, you can find them
directory.
<tr class="tbl">
Sources written in C/C++. You can compile them yourself, if you likeWindows XP/2003/Vista/7/8 version.Windows XP/2003/Vista/7/8 version.today (git)Documentation for Dibbler: User's Guidetoday (git)Documentation for Dibbler: Developer's GuideRelease CandidateLinux binary version. This distribution model is no longer supported. Please download sources and compile them. But before you use this, check if there is no package for your Linux distro.Windows NT/2000 version. It is considered experimental.
Following links are static (i.e. updated rarely or never in a manual manner)
<tr class="tbl">
<tr class="tbl">
Presnetation about DHCPv6 and Dibbler in particular.
<tr class="tbl">
All newest files are available there. Use sourceforge if download .pl
is too slow.
<tr class="tbl">
Linux Distro packages
Stable version for Linux. Includes server, client, relay and User's Guide. See CHANGELOG for details.
<tr class="tbl">
Linux non-x86
Dibbler 0.4.0 is available in the ,
which supports various non-x86 architectures.
<tr class="tbl">
Wireless router LinkSys WRT54G
Dibbler 0.7.1 has been ported to embedded devices, e.g. wireless router Linksys WRT54G. Currently
there is an ongoing work to update OpenWRT's repositories with updated 0.7.1 version.
<tr class="tbl">
Article #1 about Dibbler
This is an article about Dibbler. It was published on the
conference,
held in Zagreb, Croatia. My presentation is also included.
<tr class="tbl">
Article #2 about Dibbler
Another article about Dibbler. This one describes DNS Update issues and some authentication related topics.
It was published on the
conference,
held in Gdansk, Poland. My presentation is also included.
Download: development version
Sources can also be downloaded from GIT repository:
git clone git:///tomaszmrugalski/dibbler.git
You can also browse source directly with your web browser: .
Old sources can also be downloaded from SVN. These sources are outdated and keep around only for several
students that are doing their master theses. They can compare changes here. Everyone should migrate to GIT.
If you really have a reason to use this old version, please use following command to download SVN sources:
svn checkout .pl/var/svn/dibbler/trunk
Short-term goals (aka TODO)
is a bug tracking system. It
allows to report, assign and deal with bugs in a convinient manner. It can also be
used to request new features. It is called enhancement. Take a look at bugs with
severity (&Sev& column) set to &enh&. You can define what are you
looking for by hand, or use one of the links on the side panel.
Long-term goals (aka Roadmap)
There's list of features, which I would like to include someday. In
some far, distant, not so sure future. I'm really busy person, sorry.
In parenthesis there are estimated versions, where this feature will
be implemented.
(0.4.0) RELAY AGENT support [done]
(0.5.0-RC1) temporary addresses support (IA_TA option) [done]
(0.5.0-RC1) DNS updates (FQDN option) [done]
(0.6.0-RC1) Prefix Delegation [done]
(0.7.0) Leasequery (RFC5007)
(0.7.0) Authentication [done]
(0.7.1-CVS)crash/power outage recovery (CONFIRM message)[done]
(0.8.0) Mac OS X port
(0.8.1RC1) DNS Updates over UDP
(0.8.1RC1) FreeBSD/NetBSD/OpenBSD port
(0.8.1RC1) Routing configuration (draft-mif-dhcpv6-route-option)
(0.8.3RC1) Proper lease expiration support (with external script support)
(0.8.3RC1) DNS Update security (TSIG)
(0.9.0) Better client reservation (subscriber-id, relay-id link address)
(0.9.0) Better client classification support (DUID, link address, relay-id etc.)
(0.9.0) RECONFIGURE support
(0.9.0) Universal new option definition (with external script support)
(1.0.0) Remaining RFC3315 features
Bulk leasequery
DOCSIS 3.0 options
(under consideration) Minimal client for embedded devices
(under consideration) allow DB storage in a real database (PostgreSQL probably)
DHCPv6 Failover (once the draft becomes solid enough)
If you are thinking about joining or contributing to the dibbler project, you may want
to see this
Looking for sponsor
During Dibbler development, I have encountered several problems with equipment availability.
This project has no budget and I develop everything in my home. I have several computers,
so I can build basic configuration. However, I don't have any fancy hardware, so I can't
verify any of the more advanced setups.
Another issue that I have encountered is a lack of access to non-x86 architectures. I would
like to develop Dibbler versions for other architectures, eg. 64-bit or Mac. So, if you
are a well prospering company and you find Dibbler useful, consider supporting open
source development and donating some of your equipment.
In further Dibbler development, access to the following equipment would be useful:
An Intel 64-bit box
A MAC capable of running Mac OS X
Sun Sparc with Sun OS supporting IPv6
A Cisco router capable of running DHCPv6 relay
a LinkSys Wireless router WRT54G (which already supports Dibbler)
A PDA with a network interface
Any other uncommon hardware which would be able to run Dibbler
Mailing lists
USERS: Mailing list was created to support Dibbler users. Feel free to discuss any topic
related to Dibbler or DHCPv6 in general. You can also ask for help here.
If you want to subscribe, please send mail with subject &subscribe& to
You will receive confirmation request shortly. You can also
using www browser. There are
available.
DEVELOPERS: Second list is dedicated to free exchange of thoughts between people
engaged in the Dibbler development. Sadly, this list will be even more desolated then the previous one.
If you want to subscribe, please send mail with subject &subscribe& to
You will receive confirmation request shortly. You can also
using www browser. There are
Requirements
This implementation is developed using tools listed below. It may,
of course, work with newer/older versions. Even with other
compilers. Marek Senderski developed WinXP version using microsoft
Visual C++
and 2008 editions. Bison++ has been merged into CVS, so there should
be no more problems with obtaining bison++. Note that bison++ is available
distribution. In parenthesis is version which has been used to develop Dibbler.
It will work for sure, but there's pretty good chance that other versions
will work, too. Here's the list:
gcc (2.95 to 4.7.2)
g++ (2.95 to 4.7.2)
flex (2.5.35 or later)
bison++ (1.21.9, sources included in git)
libxml2 (with pkg-config in Linux)
To generate Windows installer, a cool
tool was used. Dibbler User's Guide was written in LaTeX, Dibbler Developer's Guide was generated
Older versions
All versions are stored in the
directory.
Take note that they are kept for archeological/sentimental purposes only. Please use latest version only.
(inactive)
Your IP address is 220.177.198.53.