[
https://issues.apache.org/jira/browse/PLC4X-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991842#comment-16991842
]
Alvaro del Castillo edited comment on PLC4X-157 at 12/16/19 10:28 AM:
----------------------------------------------------------------------
[~nalim2] you are totally right that this option is for broken opc-ua servers.
And maybe I have not understand correctly the "nDiscovery" param. I have
interpreted it as "notDiscovery" and for me this name has two problems: you
need to understand that "n" is for "not" and that it is the negative logic what
you are defined. But maybe you have in mind other interpretation. Just trying
to understand you fully so it is easier to work together :)
was (Author: acs):
[~nalim2]you are totally right that this option is for broken opc-ua servers.
And maybe I have not understand correctly the "nDiscovery" param. I have
interpreted it as "notDiscovery" and for me this name has two problems: you
need to understand that "n" is for "not" and that it is the negative logic what
you are defined. But maybe you have in mind other interpretation. Just trying
to understand you fully so it is easier to work together :)
> OPC-UA: Disable by config endpoint discovery
> --------------------------------------------
>
> Key: PLC4X-157
> URL: https://issues.apache.org/jira/browse/PLC4X-157
> Project: Apache PLC4X
> Issue Type: Improvement
> Components: Driver-OPC-UA
> Reporter: Alvaro del Castillo
> Priority: Major
> Labels: device, network
>
> Some real world devices like the [https://iqunet.com/server-and-data/]
> includes as the OPC-UA server the FreeOPCUA server running inside a docker.
> When you discover the endpoints, the IPs advertised are the internal ones in
> the docker container, so you can not access these endpoint from the network.
> It is an issue in the device, but for those cases, just using directly the
> public IP in which the OPC-UA server is listening as the endpoint is the only
> solution.
> For PLC4x to work in those cases, a config option must be available to
> disable the endpoint discovering and just connect to the endpoint build with
> the public IP.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
