-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need Support to Configure xk6 Diameter with DTLS using SCTP #17
Comments
You can enable TLS/SCTP using this example configuration: let client = diam.Client({
requestTimeout: "50ms",
enableWatchdog: false,
authApplicationId: [app.ChargingControl],
vendorSpecificApplicationId: [
{
authApplicationId: app.ChargingControl,
vendorId: vendor.TGPP,
}
],
capabilityExchange: {
vendorId: 35838,
},
transportProtocol: "sctp",
tls: {
enable: true,
},
}) |
Thanks @lwlee2608 for the response will try this and update. |
@lwlee2608 I am using freediameter server version 1.2.1. I am seeing following error in the server:
Below is configuration I made based on the above suggestion:
Not sure its a problem with the server or the data that client is sending from xk6-diameter. |
I have not used FreeDiameter, so I am unable to help you with that. However, I tested xk6-diameter with this diameter server. |
Sure Thanks @lwlee2608. The main reason I am sticking with freediameter is that it supports applications like SIP, 3GPP, NAS, EAP etc to test. The server that you have shared above can it be used to test all these Diameter applications or Is this a custom server only for testing basic diameter flows. If we don't have support for this applications now in both client and server do we have any plans to add these later both from client and server perspective. |
I was following this link to test diameter protocol: GitHub - MATRIXXSoftware/xk6-diameter: A k6 extension for Diameter protocol 1
I was able to make it work for non TLS with TCP. I want to configure xk6 Diameter with DTLS using SCTP. Do we have any sample config or any help link which mentions all this in detail.
The text was updated successfully, but these errors were encountered: