- Added MD5 support for sysop identification. MD2 is still usable until
  every terminal software does not support MD5.

- Temporary files (.$$$), which are used by the DOS gateway wasn't deleted.
  Fixed. Tks G3RTU.

- Linux version now supports calls from the F6FBB's client programs (either
  xfbbC or xfbbX). DxNet uses by default the port 3287, excepy if it has
  been set differently with the -p switch (ie dxnet -p3290).

  A new version of xfbbC (in beta test), based on ncurses, has been made by
  F6FBB. I also wrote a client for windows 95/98/nt.

  You can still continue to use DxNet exactly as before anyway. You have
  nothing to do for that.

  Thanks a lot to Jean-Paul (F6FBB) for his help.

- Added xfbb? client to the linux distribution package.

- Fixed a compilation error in MEDIT.CPP (linux version). Tks SP9UMX.

- The symbol # can be use in .CFG file to put comments.

- Added a DxNet cluster loop filter. Most of us must to be faced with
  cluster loops. This new feature should help a bit.

  The loop filter is disabled by default. Enter the sysop command
  ' SET/LFilter on ' to enable it.

  Rules are saved in ~/script/<callsign>.lf, where callsign is the
  adjacent cluster callsign - WITHOUT ssid - you want to enable the
  loop filter with.

  The format of the fields are closed to the .CFG ones :

  [in]
  # Incoming protocol messages section
  <cmd>	  <hops>   <call-list>
  ...
  [out]
  # Outgoing protocol messages section
  <cmd>   <hops>   <call-list>
  ...
  [reject]
  # Neighbourgs reject section
  <call>  [dx-hops[ann-hops[wwv-hops]]]

  [in] and [out] section
  ----------------------
  <cmd>       : one the the following command : DX, Annoucement, WWV
  <hops>      : hop count value (from 0 to 99)
  <call-list> : callsign list which the rule must be applied for. If
		there is more than one callsign, they must be separated by
		a colon (:).
		You put here the cluster callsigns which the protocols
		are ORIGINATED from. It is not necessary a neighbourg, it
		can even be a cluster very far away !

  In example, assume the following cluster configuration :

  F5MZN -> PI5EHV
  F5MZN -> F6KBF -> F5GHV -> F6KIF -> LX0PRG

  F5MZN wants to forward, say, both DX and ANNOUCEMENT informations from
  F6KBF, F5GHV, and F6KIF to PI5EHV (with a hop count of 10), as well as
  WWV informations from both F6KBF and F5GVH, and to reject anything else.

  The .lf file could be similar to the following :

  --- PI5EHV.LF ---
  [in]
  # Nothing to do

  [out]
  *	0	*			# reject everything
  dx	10	F*			# but dx info from French clusters,
  a	10	F*		        # announces
  wwv	10	F6KBF:F5GHV		# and WWV, from F6KBF & F5GVH only

  [REJECT]
  # Nothing to do



  [reject] section
  ----------------
  This section is used to specify the *NEIGHBOUR* protocols you want to
  reject. The whole protocols coming from a specified neighbour cluster
  station won't be forwarded, except the DX/ANN/WWV ones (depending of the
  settings).

  <call>     : neighbour callsign
  [dx-hops]  : hop-counts assigned to the DX protocols (PC11)
  [ann-hops] : hop-counts assigned to the ANNOUNCEMENTS protocols (PC12)
  [wwv-hops] : hop-counts assigned to the WWV protocols (PC23)

  Default value for [dx-hops], [ann-hops], [wwv-hops] is 0.

  For example, assume I want to reject the whole protocols which are coming
  from my adjacent cluster station K1XX to F6KBF-3 :

  --- F6KBF.LF ---
  [REJECT]
  K1XX

  [IN]
  # Nothing to do

  [OUT]
  # Nothing to do

  Ultimate example !
  ------------------
  Assume the following rules for F6KBF-3 :
  . Reject everything from K1XX but :
	Prot	Hops
	DX	10
	ANN	5
	WWV	0
  . Forward DX/ANN protocols coming from any french cluster with a maximum
    hop-counts of 10
  . Forward WWV protocols coming from any french cluster with a maximum
    hop-counts of 5
  . Forward any other DX/ANN/WWV protocols with a maximum hop-counts
    of 1
  . Reject any DX/ANN/WWV protocols coming from, say, Belgium.

  --- F6KBF.LF ---
  [REJECT]
  K1XX	10 5  0

  [OUT]
  *	 1	*
  *	 0	ON*
  dx	 10	F*
  ann	 10	F*
  wwv	 5	F*

  * VERY IMPORTANT *
  ------------------
  Take care using the loop filter feature if you don't want to be blamed by
  other sysops if something is wrong in your settings !!! You need to know
  exactly what you are doing ! BTW, this would be used by experienced sysop
  ONLY.

  Remark : the .lf files are read each time a protocol is to be forwarded.
  It means that you don't need to either disconnect/connect the adjacent
  cluster or to restart dxnet to get modifications effective.

- Fixed (again) a bug in the CluLink protocol (message numbers higher to 127
  wasn't interpreted). Tks F6KBF and F5GHV.

- Added the local conference feature. Command : CONFerence

- Added the cluster-wide conference feature. Command : CONFerence/Full
  Protocols PC13 PC14 PC15 are now supported by dxnet, as well as the
  CluLink 140 (=PC13), 141 (=PC14) and 142 (=PC15).

- Dxnet might crash when CONF was defined in the .CFG file. Fixed.

- Added new sysop command : SET/MONitor. This allows to switch ON or OFF
  the monitoring mode.

  Syntax : SET/MONitor ON | OFF

- Added a monitor-like feature under linux.

  Only the frames between DxNet and a station which is connected to are
  monitored. The others are not. Use one the xfbb client to show the
  monitor.

  The "monitor" client feature displays the PC frames.
  The "all channels" client feature displays the users frames.

- Fixed a TALK problem : it was impossible to send a talk to a cluster
  station. Tks PA3EZL, IK5ZUK and IZ8CCW.

- Known bug : both PA3EZL and IK5ZUK reported that if a sysop who is in
  sysop mode issues a rcmd/cluster_neighbour <command> ALSO the OTHER
  CONNECTED SYSOP gets the output from cluster_neighbour. I don't know how
  to fix this problem because the protocol don't carry who requested
  the remote command. This is why the reply are sent to every sysops.

- Changed format of the file ~dxnet/system/bin/users.bin, which has also
  changed its name : ~dxnet/system/bin/userscfg.bin

  DxNet will convert it to the new format automaticaly the first time
  you run this version. You have nothing to do.

- New user command : SET/FILTER

	SET/FILTER <band|all|vlf|hf|vhf|uhf|shf|all|ssb|cw|rtty> <...> ...

  This command is used to maintain what DX announcements are allowed for
  each user.

  DxFiltering is done by the user. Filtering may be done by mode (CW, SBB
  or RTTY), and band : 2km, 160m, 80m, ..., 1cm, 6mm.

  Some special properties are available :

  VLF = 2km
  HF  = 160m 80m 40m 30m 20m 17m 15m 12m 10m
  VHF = 6m 4m 2m 135cm
  UHF = 70cm 34cm 23cm 13cm
  SHF = 5cm 3cm 1cm 6mm (even if I know that neither 1cm not 6mm are SHF ...)

  all = all bands, all modes

  If you precede the property with an exclamation mark (!), it removes the
  property from the filter.

  Examples :

  Assuming that the filter feature is disable, if you issue the following
  command sequence :
  SET/FILTER HF SSB	 : You'll receive only HF spots in SSB segment
  SET/FILTER !80m	 : 80m meters spots will be rejected
  SET/FILTER VHF UHF SHF : Add VHF, UHF and SHF bands to the filter

  If you want to receive VHF, UHF and SHF bands only :
  SET/FILTER VHF UHF SHF     or     SET/FILTER ALL !VLF !HF

  SET/FILTER with no argument shows the current filter status.

- Added a new data file in ~/dxnet/system : mode.dat

  This file contains the frequency range, mode per mode. It is designed
  to serve for the DX announcement filtering feature.

- New user command : SHow/Filter

  This command shows the current DX announcement filter status for the
  user.

- New user command : SET/NOFilter

  This command disables any DX announcement filters. All spots will be sent
  to the user.

- Fixed a BEEP/NOBEEP problem with the TALK messages.

- Fixed a bug in WWV/DX merge request (PC25/26/27). Tks PA3EZL.

- Fixed the 'language undefined' error message in remote/commands replies.

- DxNet now displays the here/nohere information for the dxcluster station
  also, as well as the conference/full flag (*).

- Added user commands : SET/DX_announcements and SET/NODx_annoucements.
  These commands allow a user to anable or disable the display of DX
  annoucements. If the user disconnects and reconnects, DX announcements
  will be re-enabled.

- Added user commands : SET/Annoucements and SET/NOAnnouncements.
  These commands allow a user to anable or disable the display of
  annoucements. If the user disconnects and reconnects, Announcements
  will be re-enabled.

- Fixed some problem with SH/DX <frequency>. Tks F8BJI.

- CLX always need 2 characters in the time field of the WWV protocol
  messages, even if only one is needed. Done. Tks PA3EAS and PA3EZL.

- Fixed a problem which sometimes occured during the initialization
  sequence

- Merged DX and WWV informations are now sent to the local users.
