[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freediameter-help
Subject:    [Help] Error-Message content: 'No suitable candidate to route the message to'
From:       marko.stojakovic () amres ! ac ! rs (=?UTF-8?Q?Marko_Stojakovi=C4=87?=)
Date:       2012-09-20 11:00:49
Message-ID: 011201cd971f$314e2e40$93ea8ac0$ () amres ! ac ! rs
[Download RAW message or body]

Sebastien,

 

I am not sure if I can control advertized applications in radiator, but I will check.

 

Thank you very much!

 

 

Best regards,

Marko Stojakovic

 

 

From: Sebastien Decugis [mailto:sdecugis at freediameter.net] 
Sent: Wednesday, September 19, 2012 10:57 PM
To: Support for the freeDiameter implementation.
Cc: Marko Stojakovi?
Subject: Re: [Help] Error-Message content: 'No suitable candidate to route the \
message to'

 

Hi Marko,

It seems your radiator server is only advertizing support for applications 1 and 3 \
during the CER/CEA exchange; therefore the converted Diameter EAP message \
(application 5) cannot be routed to this peer.  Can you control the advertized \
applications in radiator?

Best regards,
Sebastien.





Le 2012/09/19 18:21, Marko Stojakovi? a ?crit :

Hello,

 

 

I have a problem with relaying Diameter authentication requests from Freediameter to \
Radiator server that is configured as a Diameter-to-Radius gateway.

 

Here are the server names and explanations:

server1.rcub.rs (192.168.13.10) : Freediameter configured as a radius-to-diameter \
gateway

server2.amres.rs (192.168.13.11) : Radiator server, configured as a \
diameter-to-radius gateway

 

The idea is to use eapol_test on the server1 to generate EAP-TLS Radius \
authentication request (with username marko at amres.rs) and send it to localhost.

Then, the Freediameter should convert this request to Diameter protocol and relay it \
to server2; 

 

Step1: When I start the servers I see that the Diameter connection is established ? \
on Freediameter (server1) the message is:

 

         | tid:Receiver (20) SCTP/noTLS)        09/18/12,13:40:49.286447        in \
fd_sctp_recvmeta@/tmp/freeDiameter/libfdcore/sctp.c:1230

         |  Received 60b data on socket 20 (stream ignored)

         | tid:PSM/server2.amres.rs     09/18/12,13:40:49.286475        in \
p_psm_th@/tmp/freeDiameter/libfdcore/p_psm.c:429

         |  'STATE_OPEN'        <-- 'FDEVP_CNX_MSG_RECV'        (0x839c270,60)  \
'server2.amres.rs'

Received 60b from 'server2.amres.rs' (STATE_OPEN)

Logged: 09/18/12,13:40:49.286501

 

The whole message from ?freeDiameterd ?c freediameter.conf -ddd? is in the attachment \
(state_open.txt).

 

Step2: Then, when I use eapol_test to send radius message to Freediameter for \
converting it to diameter and relaying, the Freediameter brakes. This is the message \
I get: 

 

[auth.rgwx]   Error-Message content: 'No suitable candidate to route the message to'

 

The whole message from ?freeDiameterd ?c freediameter.conf -ddd? is in the attachment \
(Aborted.txt).

 

Also I am sending freediameter.conf and rgw.conf in attach.

 

Could you help me with this problem?

 

 

Best regards, 

Marko Stojakovic

 






_______________________________________________
Help mailing list
Help at freediameter.net
http://lists.freediameter.net/cgi-bin/mailman/listinfo/help

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freediameter.net/pipermail/help/attachments/20120920/8abdece1/attachment-0001.html>



[prev in list] [next in list] [prev in thread] [next in thread]