You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "Alvaro del Castillo (Jira)" <ji...@apache.org> on 2019/12/16 10:30:00 UTC
[jira] [Resolved] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
[ https://issues.apache.org/jira/browse/PLC4X-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alvaro del Castillo resolved PLC4X-157.
---------------------------------------
Fix Version/s: 0.6.0
Resolution: Fixed
> 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
> Fix For: 0.6.0
>
>
> 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)