All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Not committed (merge conflicts...):
net/radsecproxy/distinfo
The following distfiles could not be fetched (fetched conditionally?):
./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch
- Add LICENSE= 2-clause-bsd
- Drop PKG_DESTDIR_SUPPORT=
- Add SUBST_CLASSES to edit Makefile for PREFIX
- Add SUBST_CLASSES to edit dhisd.h and README for VARVASE and PREFIX
- Add SPECIAL_PERMS to set mode 0700 owner root onto executables
(pkgsrc/DESCR)
- Add pointer to ${PREFIX}/share/doc/dhisd/README for info
(pkgsrc/patches/patch-aa)
- Removed
(upstream)
- Update 5.1 to 5.5
-----------------
On dhisd-5.5
The server no longer requires a 5.4 client to have rport=0
in order to reply to the sending port. This releases a small
issue that broke 5.4 clients with servers <= 5.3.
As of this version, if the client's version is 5.4 or higher,
the server always replies to the sending UDP port and disregards
rport. 5.5. clients however continue to fill in rport in order
to be compatible with <= 5.3 servers.
On dhisd-5.4:
The modular architecture has been dropped and the modules and
engines are no longer part of dhisd. Instead dhisd is again
a DNS only updating daemon without engines; the extra functionality
provided by previous engines can however still be replicated with
OnCmd and OffCmd scripts on a per-host basis.
The default configuration directory is now /usr/local/etc
The default binaries directory is now /usr/local/sbin
It is now possible to put all configuration parameters under a
config file; the default is /usr/local/etc/dhisd.conf
The pid file default location moved to /var/run/dhis/dhisd.pid
The log file default location moved to /var/log/dhis/dhisd.log
The server can now be bound to a specific IP address with either
the BindAddr config option or the -b command line option.
Multiple options have been added and are now possible with the
command line (dhisd -h) and the config file.
The server now binds to a UDP port (58800 by default) and sends
UDP messages from that port; in previous versions dhisd sent
UDP messages from a random port even though it listened on port 58000.
In addition to the database text file (specified by the -d option
or the DBFile config option), dhisd can now use a MySQL database
instead to achieve the same purpose of the dhis.db file. See
README and INSTALL for details.
This version of the server is compatible with NAT friendly 5.4 clients.
On dhisd-5.3:
Corrected bug that caused improper handling of comment character (;)
in the database file.
On dhisd-5.2:
Documentation Updates
By the means of a DHIS client a host which is assigned a dynamic
IP address (either from its ISP or from DHCP) is able to communicate
with a DHIS server in order to advertise its newly acquired IP
address.
The DHIS server (permanently online) listens to UDP messages from
its clients and authenticates these against its knowledge of keys.
When authentication is successful the DHIS server updates one or
more databases with the newly received IP address for the given
client.
The server then keeps sending, every period of time, check requests
to each of its connected clients. These need to be acknowledged.
If not the server will consider, on an individual basis, that the
client has disconnected and will
again update the databases to an offline state.
Alternativelly the server may receive an OFFLINE_REQ packet from
the client, in which case the DNS record is updated at once and
the online state droped.
