Hi,

Long overdue cleanup of the website done today:

• removed the references to the source code here, the development happens now in github (link at the top).
• idem for the ticket system, please use github.
• added a link to a book that explains both Diameter protocol and freeDiameter, for more details for those who are interested.

The mailing-list is not active anymore, please use github tickets instead. Thanks !

Finally after many requests, it is done ! The code is moving to github platform here: ​https://github.com/freeDiameter/freeDiameter

All future code updates and releases will be done there, as well as future announcements. Please refer to that URL for further updates.

Thank you !

Version 1.5.0 wis now tagged in the repository. The source code of this release can directly be downloaded using this link: ​​​​​http://www.freediameter.net/hg/freeDiameter/archive/1.5.0.tar.gz.

This release contains numerous improvements from great contributors; thanks a lot to Thomas and Luke for your continuous work on this stack !

As the number of changes is quite long, I invite you to read from the changelog file directly here: ​http://www.freediameter.net/hg/freeDiameter/file/1.5.0/contrib/debian/changelog

We also got our first security advisory CVE-2020-6098 / TALOS-2020-1030 which is fixed in this release. Thanks a lot for the researchers who contacted me before releasing the description and gave me enough time to push a fix.

Thank you for your interest in freeDiameter !

The freeDiameter team.

Version 1.4.0 was tagged in the repository a few months ago. The source code of this release can directly be downloaded using this link: ​​​​http://www.freediameter.net/hg/freeDiameter/archive/1.4.0.tar.gz.

This new version comes with quite a number of changes:

• New API: fd_fifo_set_max to change the capacity of a queue.
• New configuration stanza for Relays: ProcessingPeersPattern? and ProcessingPeersMinimum?
• New configuration stanza for scalability: RoutingInThreads? and RoutingOutThreads?
• some coding style cleanups
• Improvements on rt_load_balance algorithm
• Improvements on logging & locking behaviors
• More tolerant to invalid messages and answers.
• Improvements on shutdown behaviors.
• test_ccload: new extension: generates random Credit-Control-Requests and counts how many are answered/give an error/get no answer. Start it with SIGUSR2, stop it with a second SIGUSR2. Statistics are printed on exit.
• test_cc: new extension. Automatically replies to Credit-Control-Requests. Copies minimally necessary data from the Request.
• Fixed testcnx failing due to expired CA certificate

Thanks a lot to the contributors who continue to work and improve this stack!

Thank you for your interest in freeDiameter !

The freeDiameter team.

Version 1.3.2 has been tagged in the repository. The source code of this release can directly be downloaded using this link: ​​​http://www.freediameter.net/hg/freeDiameter/archive/1.3.2.tar.gz.

This new version adds better compilation compatibility with a wider range of system versions and improvements to the whitelist extension (acl_wl).

Note: 1.3.1 was exactly the same as 1.3.0 but fixes a version number problem only...

Thank you for your interest in freeDiameter !

The freeDiameter team.

A new book about the Diameter protocol was just published:

​Diameter: New Generation AAA Protocol - Design, Practice, and Applications

The reason to mention it here: this book discusses about freeDiameter in particular, and comes with a pre-built virtual machine image that contains a ready-for-use freeDiameter environment. Quite a good starting point for any freeDiameter enthusiast.

Version 1.3.0 was tagged in the repository. The source code of this release can directly be downloaded using this link: ​​http://www.freediameter.net/hg/freeDiameter/archive/1.3.0.tar.gz.

Many thanks to Thomas Klausner for his contribution of several important extensions.

Thank you for your interest in freeDiameter The freeDiameter team.

Hi,

You may have noticed that the domain was down for a while; the primary server has actually physically relocated to a new home... And it took some time to get all back online!

Let us know if you experience any issue now that the server is back...

Apology for the inconvenience~ Sebastien