From sdecugis at freediameter.net  Mon Nov 30 01:56:42 2020
From: sdecugis at freediameter.net (sdecugis)
Date: Sun, 29 Nov 2020 16:56:42 -0000
Subject: [Help]
 =?utf-8?q?=E2=80=8F_=E2=80=8F_Same_realm_for_two_different?=
 =?utf-8?q?_DiameterIdentity?=
In-Reply-To: <AM0PR07MB5714A8E34803C68FDB93B557D2F60@AM0PR07MB5714.eurprd07.prod.outlook.com>
Message-ID: <20201129164852.7B5F43140D65@sd-126148.dedibox.fr>

Ok, clear. Then you should be able to do that with the rt_default extension, adding a score to your server1. It will behave as you need, I think.BR,SebastienSent from my Galaxy
-------- Original message --------From: Eyal Savion <eyalsavion at hotmail.com> Date: 11/30/20  00:34  (GMT+08:00) To: Sebastien Decugis <sdecugis at gmail.com> Cc: Sebastien Decugis <sdecugis at freediameter.net>, dev at freediameter.net, "Support for the freeDiameter implementation." <help at freediameter.net> Subject: Re:‏ ‏ Same realm for two different DiameterIdentity 











Hi Seb,
I meant one server is the a primary and the second is for redundent, both of them should be up and be connected but the Diameter messages will be routed for the primary as long as it up.


Thanks,
Eyal





מאת: Sebastien Decugis <sdecugis at gmail.com>
‏‏נשלח: יום ראשון 29 נובמבר 2020 16:25
‏‏אל: Eyal Savion <eyalsavion at hotmail.com>
עותק: Sebastien Decugis <sdecugis at freediameter.net>; dev at freediameter.net <dev at freediameter.net>; Support for the freeDiameter implementation. <help at freediameter.net>
‏‏נושא: Re: ‏ Same realm for two different DiameterIdentity
 


Hi Eyal,


If both servers are redundant, what s the issue that messages are load balanced between them when they are both up?


BR,
Seb



On Mon, Nov 30, 2020, 00:08 Eyal Savion <eyalsavion at hotmail.com> wrote:
















Hi Seb,


Thanks for your answer - I didn't notice your email at noon time but here we are.

I will be more clear and I will add my comment with
red color


You have a realm with two servers, for example server1.realmA.net and server2.realmA.net 
 (TRUE).



From a third peer, lets call it client.realmB.net,
 you want to be connected to both servers , but for a specific message, you want to route always to server1 (never to server2) (not exactly I will explain - the both servers are used as redundancy, the
 client client.realmB.net is connected
 to each one of them by the ConnectPeer parameter in the config file (after CER/CEA WDR/WDA). The two  messages should be routed  only for one server as long as it is up.  If the  server1.realmA.net will
 go down all the traffic will go through the server2.realmA.net).


 but this message only contains Destination-Realm = realmA.net but it cannot contain a Destination-Host ( TRUE
 - there is one message without Destination-Host
 and  the other is with Destination-Host,
but it doesn't relevant for routing them to the servers).
  )



I am assuming both servers support the Diameter application of your message, so from freeDiameter point of view on the client side, they are both suitable for routing the message by default.
Without any routing extension loaded there, there is no guarantee of which of the two servers will receive the message. (TRUE -  I saw by WireShark that sometimes
 the message goes via server1.realmA.net and
 sometimes via server2.realmA.net ). 



Just to mention the servers are DRA - Diameter Routing Agent (and I have another question here : is it possible to change the client/server and my freeDiameter will be server and the two DRA will be client ?)


Please update me If regarding my comments something else should be done, otherwise  I will follow your advice regarding  routing extension. I will do it and
 I will check the doc/rt_ereg.conf.sample file preliminary.


Seb thank you very much .







מאת: Sebastien Decugis <sdecugis at gmail.com>
‏‏נשלח: יום ראשון 29 נובמבר 2020 11:48
‏‏אל: Eyal Savion <eyalsavion at hotmail.com>
עותק: 
sdecugis at freediameter.net <sdecugis at freediameter.net>;
dev at freediameter.net <dev at freediameter.net>; Support for the freeDiameter implementation. <help at freediameter.net>
‏‏נושא: Re: Same realm for two different DiameterIdentity
 



Hello Eyal,


First of all, let me rephrase the situation I understand from your mail to make sure I don t misunderstand something:


You have a realm with two servers, for example 
server1.realmA.net and 
server2.realmA.net


From a third peer, let s call it 
client.realmB.net, you want to be connected to both servers, but for a specific message, you want to route always to server1 (never to server2) but this message only contains Destination-Realm = realmA.net but it cannot contain a Destination-Host.


Is this the correct understanding ?


I am assuming both servers support the Diameter application of your message, so from freeDiameter point of view on the client side, they are both suitable for routing the message by default.
Without any routing extension loaded there, there is no guarantee of which of the two servers will receive the message.


You can change this behavior on the 
client.realmB.net machine by loading a routing extension (rt_*.fdx files) that will influence how the routing decisions will be made. There are some default extensions that can cover already quite a large number of scenarios, and if not sufficient, you
 can probably add one more extension to implement exactly what you need, these extensions are pretty simple. From what you described, I think rt_ereg.fdx may be suitable, you can see some details in doc/rt_ereg.conf.sample file.


Let me know if I misunderstood your question, or if this is not clear.


Best regards,
Seb






Le mar. 24 nov. 2020 à 18:42, Eyal Savion <eyalsavion at hotmail.com> a écrit :





Dear   Sebastian and freeDiameter team



Please kindly advise what is provided or what should be done to distinguish routing diameter messages between two diameter Identities, which have the same realm but own different Identity (the host is different).
  The issue is that for a certain diameter message I must send only the destination-realm (without the destination-host).
I did configure two different ConnectPeer but for this case,  which the destination-host is messing at the diameter message , the FD doesn't route everytime  the diameter message to the right address.
Is there any way to get some direction/hint what to change at the open source to be available to send everytime the diameter message to the right address.


Thanks in advance,
Eyal



 


















-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listsint.freediameter.net/pipermail/help/attachments/20201129/3a1b4429/attachment.html>