-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
receiveServiceResponse returns BADCONNECTIONCLOSED #2562
Comments
Which Server and Client are you using? |
I am using the open62541 library in the current development state (+ some logs) and the machine we are trying to connect is a Siemens SINUMERIK 840D SL. You will find attached the wireshark dump. We can read the error 0x80AB0000 (UA_STATUSCODE_BADINVALIDARGUMENT) after the "OpenSecureChannel" request. I guess this is due to the certificate? |
The server returns an error message with BADINVALIDARGUMENT. To decrypt the packages, you could try setting the key in wireshark if you have access to it. |
I followed this link to decrypt https://support.citrix.com/article/CTX116557 We couldn't find the logs on the server either... Really hard to debug I hope we will find something. |
Ah, my mistake. I thought wireshark had a feature to decrypt OPCUA traffic. Apparently not. You can try using the scapy plugin i wrote for opcua to decrypt the packet. See this file for some hints on how to use it. |
Unfortunately I'm not comfortable at all with this tool. I have 3 files .pcapng, .der and .pem (actually a forth one which is also a .pem) so I should have everything but in the example the method reading .pcapng (read_pcap) returns the variable "pc" that is not used. So I'm enclosing the files here if by chance you can try something fast but on our side we will focus more on the server logs if we can finally find / enable some. |
I have the same problem as you。the server is Siemens SINUMERIK 840D SL which is is successfully connected by the software "UA Expert".. have you solved the problem???? Thank you in advance |
I do not have any problems with the newest version. |
thank you very much for you replying . I use this library in arm, may i use your version to connect my server? thank you in advance!!
…------------------ 原始邮件 ------------------
发件人: "open62541/open62541" <[email protected]>;
发送时间: 2020年10月21日(星期三) 下午2:35
收件人: "open62541/open62541"<[email protected]>;
抄送: "仲夏夜之梦"<[email protected]>;"Comment"<[email protected]>;
主题: Re: [open62541/open62541] receiveServiceResponse returns BADCONNECTIONCLOSED (#2562)
I have the same problem as you。the server is Siemens SINUMERIK 840D SL which is is successfully connected by the software "UA Expert".. have you solved the problem???? Thank you in advance
I do not have any problems with the newest version.
I have a tip for you: Use the certificate generated by UaExpert to establish the connection. This way you can rule out that there is a problem with the certificate you generated. And don't make the same mistake as I did here. If the UaExpert certificate works, you can try to generate one yourself that meets the requirements.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I have the same problem as you。the server i try to connect is Siemens SINUMERIK 840D SL which is is successfully connected by the software "UA Expert".. have you solved the problem???? Thank you in advance |
Description
I am trying to connect a machine with a certificate and a login / password but the error BADCONNECTIONCLOSED (0x80AE0000) is returned by the function "receiveServiceResponse" in "openSecureChannel".
Some logs are attached below so that you will see the different steps involved in the connection. How can I debug further? Is it possible that it comes from a configuration problem around the certificate?
What is interesting is that our program, using the development version of open62541, is already working for other machines and the machine we are trying to connect is successfully connected by the software "UA Expert".
Logs
The text was updated successfully, but these errors were encountered: