Navigation


Opened 12 years ago

Closed 12 years ago

#4 closed defect (fixed)

Can't connect two freeDiameter nodes

Reported by: Pichon Julien Owned by: Sebastien Decugis
Priority: major Milestone:
Component: framework Version:
Keywords: Cc:
Blocked By: Blocking:

Description

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.

Attachments (6)

log_server (25.1 KB) - added by Pichon Julien 12 years ago.
Log of the server
log_client (24.1 KB) - added by Pichon Julien 12 years ago.
Log of the client
fD_server.conf (385 bytes) - added by Pichon Julien 12 years ago.
config file of the server
test_app_server.conf (15 bytes) - added by Pichon Julien 12 years ago.
config file of the test_app for the server
test_app_client.conf (81 bytes) - added by Pichon Julien 12 years ago.
config file of the test_app for the client
fD_client.conf (385 bytes) - added by Pichon Julien 12 years ago.
config file of the client

Download all attachments as: .zip

Change History (10)

Changed 12 years ago by Pichon Julien

Attachment: log_server added

Log of the server

Changed 12 years ago by Pichon Julien

Attachment: log_client added

Log of the client

Changed 12 years ago by Pichon Julien

Attachment: fD_server.conf added

config file of the server

Changed 12 years ago by Pichon Julien

Attachment: test_app_server.conf added

config file of the test_app for the server

Changed 12 years ago by Pichon Julien

Attachment: test_app_client.conf added

config file of the test_app for the client

Changed 12 years ago by Pichon Julien

Attachment: fD_client.conf added

config file of the client

comment:1 Changed 12 years ago by Sebastien Decugis

Owner: changed from Administrator to Sebastien Decugis
Status: newaccepted

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.

comment:2 Changed 12 years ago by 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

comment:3 Changed 12 years ago by 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 :)

Last edited 12 years ago by Sebastien Decugis (previous) (diff)

comment:4 Changed 12 years ago by Sebastien Decugis

Resolution: fixed
Status: acceptedclosed

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.

Note: See TracTickets for help on using tickets.