Version 7 (modified by Sebastien Decugis, 14 years ago) (diff)



Providing screenshots of a daemon with no human interface is quite challenging -- not to say impossible. Nevertheless, here is a series of video which show the daemon in use. Please be tolerant for the quality, creating a screencast is not so easy!

Test Application (test_app.fdx)

This first video shows the test_app extension in action. This extension is a (non-standard) ping-like application designed to test Diameter connectivity between two freeDiameter nodes. It can also be used to check routing behavior etc...

It is recommended to watch this video in HD and fullscreen.

The video shows two consoles, bottom-left and top-right. These console correspond to two Virtual Machines running on the same subnet, as follow:

Error: Failed to load processor graphviz
No macro or processor named 'graphviz' found

Here is what happens in the video:

  • (0:00 ~ 0:04) Very short explanation.
  • (0:00 ~ 0:38) Preparation of freeDiameter, using cmake.
  • (0:39 ~ 2:15) Compilation (with make).
  • (2:24 ~ 2:35) Start the daemon on both peers.
  • (2:36 ~ 3:00) Check connection status in the logs.
  • (3:00 ~ 3:50) Trig the test_app "ping" and watch the effect on the logs.
  • (3:51 ~ 4:03) Stop the daemon.

Configuration files

Please note that these files may have been updated since the time the video was created. However, the purpose of the testbed remains the same.


The following scripts are referenced in this video:

Install missing dependencies (Debian/Ubuntu), configure the source (running cmake).
Compile the sources (make), then start the daemon.
Send the USR1 signal to the daemon in a loop, to trig the test_app action.
[source:VirtualTestbed/conf/ CMakeFlags]
These are the flags passed to cmake on the command-line when preparing the source. The important ones are:
[source:VirtualTestbed/conf/ freeDiameter.conf]
The main freeDiameter configuration file. It simply indicates to load the two extensions and to connect to the server.
[source:VirtualTestbed/conf/ test_app.conf]
Configuration file for the test_app extension. It can be changed to test different routing properties for example (by changing Destination-Realm value).