[jira] [Comment Edited] (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=16990190#comment-16990190 ] 

Alvaro del Castillo edited comment on PLC4X-157 at 12/6/19 9:57 PM:
--------------------------------------------------------------------

Ok, I will try now the fix. As the OPC-UA server I will launch in a docker image.
{code:java}
[docker]$ docker run -p 4843:4843 mcr.microsoft.com/iotedge/opc-plc -ut --pn 4843 
{code}
This server will be inside a docker and it will use the docker image networking config.  If you try to discover the endpoints, it will provide internal IP address that can not be accessed outside the docker image. So it is the ideal scenario for testing the "discover=false" feature.

 


was (Author: acs):
Ok, I will try now the fix. As the OPC-UA server I will launch in a docker image.
{code:java}
docker run mcr.microsoft.com/iotedge/opc-plc -ut --pn 4843{code}
This server will be inside a docker and it will use the docker image networking config.  If you try to discover the endpoints, it will provide internal IP address that can not be accessed outside the docker image. So it is the ideal scenario for testing the "discover=false" feature.

 

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