[jira] [Commented] (PLC4X-157) OPC-UA: Disable by config endpoint discovery

["Alvaro del Castillo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PLC4X-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988534#comment-16988534 ] 

Alvaro del Castillo commented on PLC4X-157:
-------------------------------------------

According to:

[https://mail-archives.apache.org/mod_mbox/plc4x-dev/201912.mbox/browser]

the proposal is to add the param to the protocol URL:
{noformat}
opc-ua:typ://10.10.64.50?ndiscover=true{noformat}
I would prefer:
{noformat}
opc-ua:typ://10.10.64.50?discover=false{noformat}

> 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)