6 | | ---- |
7 | | |
8 | | === Simple testbed: two peers connected === |
9 | | |
10 | | This first video shows the [wiki:test_app.fdx 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... |
11 | | |
12 | | It is recommended to watch this video in HD and fullscreen. |
13 | | [[Embed(youtube=FQwPBncbIxQ&hd=1,w=660,h=525)]] |
14 | | |
15 | | The video shows two consoles, bottom-left and top-right. These console correspond to two Virtual Machines running on the same subnet, as follow: |
16 | | {{{ |
17 | | #!graphviz |
18 | | graph G { |
19 | | graph [bgcolor="#E8E8E8C8"]; |
20 | | rankdir = "LR" |
21 | | node [shape=box]; |
22 | | edge [color=blue]; |
23 | | cli [ |
24 | | label="cli.simple.testbed.aaa" |
25 | | URL="#cli.simple.testbed.aaa" |
26 | | ] |
27 | | serv [ |
28 | | label="serv.simple.testbed.aaa" |
29 | | URL="#serv.simple.testbed.aaa" |
30 | | ] |
31 | | cli -- serv [label=Diameter]; |
32 | | } |
33 | | }}} |
34 | | |
35 | | Here is what happens in the video: |
36 | | * (0:00 ~ 0:04) Very short explanation. |
37 | | * (0:00 ~ 0:38) Preparation of freeDiameter, using cmake. |
38 | | * (0:39 ~ 2:15) Compilation (with make). |
39 | | * (2:24 ~ 2:35) Start the daemon on both peers. |
40 | | * (2:36 ~ 3:00) Check connection status in the logs. |
41 | | * (3:00 ~ 3:50) Trig the {{{test_app}}} "ping" and watch the effect on the logs. |
42 | | * (3:51 ~ 4:03) Stop the daemon. |
43 | | |
44 | | ==== Configuration files ==== |
45 | | |
46 | | 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. |
47 | | |
48 | | ===== Scripts ===== |
49 | | The following scripts are referenced in this video: |
50 | | [source:VirtualTestbed/scripts/freeDiameter-install.sh freeDiameter-install.sh]:: |
51 | | Install missing dependencies (!Debian/Ubuntu), configure the source (running {{{cmake}}}). |
52 | | |
53 | | [source:VirtualTestbed/scripts/freeDiameter-run.sh freeDiameter-run.sh]:: |
54 | | Compile the sources ({{{make}}}), then start the daemon. |
55 | | |
56 | | [source:VirtualTestbed/scripts/freeDiameter-trig.sh freeDiameter-trig.sh]:: |
57 | | Send the USR1 signal to the daemon in a loop, to trig the {{{test_app}}} action. |
58 | | |
59 | | ===== cli.simple.testbed.aaa ===== |
60 | | |
61 | | These are the configuration files for freeDiameter on the client: |
62 | | [source:VirtualTestbed/conf/cli.simple.testbed.aaa/freeDiameter/CMakeFlags CMakeFlags]:: |
63 | | The flags passed to {{{cmake}}} (on the command-line) when preparing the source. The noticeable ones are: |
64 | | * {{{-DBUILD_TEST_APP:BOOL=ON}}} : compile the [wiki:test_app.fdx] extension. |
65 | | * {{{-DBUILD_DBG_MONITOR:BOOL=ON}}} : compile the [wiki:dbg_monitor.fdx] extension. |
66 | | |
67 | | [source:VirtualTestbed/conf/cli.simple.testbed.aaa/freeDiameter/freeDiameter.conf freeDiameter.conf]:: |
68 | | The main freeDiameter configuration file. It simply indicates to load the two extensions and to connect to the server. |
69 | | |
70 | | [source:VirtualTestbed/conf/cli.simple.testbed.aaa/freeDiameter/test_app.conf test_app.conf]:: |
71 | | Configuration file for the test_app extension. It can be changed to test different routing properties for example (by changing Destination-Realm value). |
72 | | |
73 | | ===== serv.simple.testbed.aaa ===== |
74 | | |
75 | | The server uses these files: [source:VirtualTestbed/conf/serv.simple.testbed.aaa/freeDiameter/CMakeFlags CMakeFlags], [source:VirtualTestbed/conf/serv.simple.testbed.aaa/freeDiameter/freeDiameter.conf freeDiameter.conf], and [source:VirtualTestbed/conf/serv.simple.testbed.aaa/freeDiameter/test_app.conf test_app.conf]. They are very similar to the client's one, so see previous section for explanations. |
| 5 | [TBSimple Simple Testbed]:: |
| 6 | This video shows two peers exchanging a Diameter message. |