Can't connect two freeDiameter nodes

[Pichon Julien]

Hello,

I am facing a problem with freeDiameter, I was trying to setup an architecture
in order to run the test_app application.

So I have two virtual machines, one named server.diameter.home, an another one
named client.diameter.home. I create the certificates as mentioned here: http://www.freediameter.net/trac/wiki/Documentation#TLS.

I am lauching the two daemon on each machines like here: http://www.freediameter.net/trac/wiki/TBSimple.

Each daemon is launched sucessfully, but when they fail connecting together.

I put the config files for freeDiameter & the test app of each node.

[Pichon Julien]

Log of the server

[Pichon Julien]

Log of the client

[Pichon Julien]

config file of the server

[Pichon Julien]

config file of the test_app for the server

[Pichon Julien]

config file of the test_app for the client

[Pichon Julien]

config file of the client

[Sebastien Decugis]

Hello Julien,

Thank you for your detailed report.

In your server log, the following line appears:

No address available to connect to peer 'client.diameter.home', aborting

It seems that there is a DNS resolution problem aon your server, and it results in the daemon going crazy.

I am accepting the bug and I will fix the behavior of the daemon in this situation. Anyway, I think that if you fix your DNS resolution on the server, it should allow you to connect the peers properly and go on with your experiments.

Best regards,
Sebastien.

[Alexandre Westfahl]

Sebastien,

SOmething strange in his problem is that /etc/hosts is correctly configured. He can make "hostname" command and ping hostname.
Do you use resolve domain name through DNS in fD?

Alexandre

[Sebastien Decugis]

I fixed a first problem: the flag

TLS_old_method;

from your configuration was not taken into account. Starting from commit 372, well, actually 373, the daemon should try to connect to the correct port and start TLS after initial capabilities exchange.

I will now check why there is no Host-IP-Address AVP in the CER, which seems to be the real reason why the server is discarding it.

About the DNS or /etc/hosts, freeDiameter is using the getaddrinfo interface which should behave as expected. I am not sure why the address is not retrieved correctly by the daemon. The addresses in the range 127.x.x.x and 224~255.x.x.x are rejected, but 172.x.x.x should be just fine.

I will provide more information later, hopefully a fix :)

[Sebastien Decugis]

Hello again,

The problem should be completely fixed with 378. I recommend upgrading to latest revision since a couple of additional bugfixes have been committed.

Please reopen the ticket if you still have this problem with newer source code!

Best regards,
Sebastien.