You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by "Alvaro del Castillo (Jira)" <ji...@apache.org> on 2019/11/29 16:21:00 UTC
[jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Alvaro del Castillo created PLC4X-157:
-----------------------------------------
Summary: 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
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)
Re: AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
endpoint discovery
Posted by Álvaro Del Castillo <ad...@ThingsO2.com>.
On Thu, 2019-12-05 at 17:15 +0000, Álvaro Del Castillo wrote:
> Dear Matthias,
>
> On Thu, 2019-12-05 at 16:18 +0000, Strljic, Matthias Milan wrote:
> > Hi Alvaro,
> >
> > i pushed now a potential fix for your issue. Can u verify if it
> > solves the problem?
> > This fix still uses the discovery capabilities of the Milo-Endpoint
> > because it is a quite heavy configuration. There I then replaced
> > the
> > endpoint address with the provided one and removed the discovery
> > URL.
> > So I stick with the param notation "nDiscovery" because it is still
> > using parts of the discovery and runs in a special mode which has
> > to
> > be enabled and is disables by default.
> >
> > So if u want to use it attack "nDiscovery=true" as a Get-parameter
> > like:
> > "opcua:tcp://opcua.demo-
> > this.com:51210/UA/SampleServer&nDiscovery=true"
> >
> > Try that on the Branch: PLC4X-157OPC-UADisablediscovery
> >
>
> Cool. IMHO it is better to use: discovery=false
>
> What do you think? I have commented it already on the issue but not
> sure if you could read it before the work.
I have tested it and attached the results in the JIRA issue:
https://issues.apache.org/jira/browse/PLC4X-157?focusedCommentId=16990190&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16990190
It is failing to accept:
opcua:tcp://127.0.0.1:4843?nDiscovery=true
as a valid OPC-UA URL.
Cheers!
>
> Cheers!
>
>
> > Greetings Matthias
> >
> > Matthias Strljic, M.Sc.
> >
> > Universität Stuttgart
> > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > Fertigungseinrichtungen (ISW)
> >
> > Seidenstraße 36
> > 70174 Stuttgart
> > GERMANY
> >
> > Tel: +49 711 685-84530
> > Fax: +49 711 685-74530
> >
> > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > Web: http://www.isw.uni-stuttgart.de
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Strljic, Matthias Milan <matthias.strljic@isw.uni-stuttgart.de
> > >
> > Gesendet: Thursday, December 5, 2019 9:28 AM
> > An: dev@plc4x.apache.org
> > Betreff: AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > config endpoint discovery
> >
> > Hi Alvaro,
> >
> > i am close to push this feature. But you have for me setup/example
> > server to test the issue?
> > Because my attempt would be to use the existing discovery tools to
> > generate the ApplicationDescription and then replace the host
> > address
> > with the public address or just remove included discovery urls.
> >
> > Greetings Matthias
> > Matthias Strljic, M.Sc.
> >
> > Universität Stuttgart
> > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > Fertigungseinrichtungen (ISW)
> >
> > Seidenstraße 36
> > 70174 Stuttgart
> > GERMANY
> >
> > Tel: +49 711 685-84530
> > Fax: +49 711 685-74530
> >
> > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > Web: http://www.isw.uni-stuttgart.de
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Álvaro Del Castillo <ad...@ThingsO2.com>
> > Gesendet: Thursday, December 5, 2019 7:59 AM
> > An: dev@plc4x.apache.org
> > Betreff: Re: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > config endpoint discovery
> >
> > Hi Matthias,
> >
> > On Wed, 2019-12-04 at 14:12 +0000, Strljic, Matthias Milan wrote:
> > > Ok, then i will include the typical URI style for GET-parameters
> > > like
> > > u and Chris suggests.
> >
> > So are you going to implement it? We need this fix so I can help in
> > the implementation of it or in the testing.
> >
> > Cheers!
> >
> > -- Alvaro
> >
> > > Perhaps there I try to hard to stick to the domain URL (if there
> > > is
> > > sometimes one 😃 )
> > >
> > > Greetings Matthias
> > > Matthias Strljic, M.Sc.
> > >
> > > Universität Stuttgart
> > > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > > Fertigungseinrichtungen (ISW)
> > >
> > > Seidenstraße 36
> > > 70174 Stuttgart
> > > GERMANY
> > >
> > > Tel: +49 711 685-84530
> > > Fax: +49 711 685-74530
> > >
> > > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > > Web: http://www.isw.uni-stuttgart.de
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Julian Feinauer <j....@pragmaticminds.de>
> > > Gesendet: Monday, December 2, 2019 1:42 PM
> > > An: dev@plc4x.apache.org
> > > Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > > config
> > > endpoint discovery
> > >
> > > Hi,
> > >
> > > thanks fort he fast reply Matthias.
> > > I agree with what Matthias says... I highly suggest the Camel
> > > Parameter Syntax (basically valid URI's).
> > > And yes, probably the subtype approach makes sense (this is
> > > consistent
> > > with having the physical transport layer also there for protocols
> > > that
> > > support multiple ones).
> > >
> > > Julian
> > >
> > > Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> > > matthias.strljic@isw.uni-stuttgart.de>:
> > >
> > > Hi all,
> > >
> > > For this I have a question: How should we deal with this
> > > consistently in the project?
> > >
> > > The Camel discussion about parameters/annotation is not over
> > > yet
> > > (?) and I want to avoid parameters in the URL that are not part
> > > of
> > > the
> > > domain model of the protocol.
> > > So I would solve it first as a new connection subtype.
> > > "opcua:tcp-ndiscover://145.............".
> > > But on the other hand this only makes sense if this is a
> > > real
> > > exception and would else explode in number by defined subtypes.
> > >
> > > So what do you think?
> > >
> > > Greeting
> > > Matthias Strljic, M.Sc.
> > >
> > > Universität Stuttgart
> > > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > > Fertigungseinrichtungen (ISW)
> > >
> > > Seidenstraße 36
> > > 70174 Stuttgart
> > > GERMANY
> > >
> > > Tel: +49 711 685-84530
> > > Fax: +49 711 685-74530
> > >
> > > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > > Web: http://www.isw.uni-stuttgart.de
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> > > Gesendet: Friday, November 29, 2019 5:21 PM
> > > An: dev@plc4x.apache.org
> > > Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > > config
> > > endpoint discovery
> > >
> > > Alvaro del Castillo created PLC4X-157:
> > > -----------------------------------------
> > >
> > > Summary: 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
> > >
> > >
> > > 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)
> > >
> > >
Re: AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
endpoint discovery
Posted by Álvaro Del Castillo <ad...@ThingsO2.com>.
Dear Matthias,
On Thu, 2019-12-05 at 16:18 +0000, Strljic, Matthias Milan wrote:
> Hi Alvaro,
>
> i pushed now a potential fix for your issue. Can u verify if it
> solves the problem?
> This fix still uses the discovery capabilities of the Milo-Endpoint
> because it is a quite heavy configuration. There I then replaced the
> endpoint address with the provided one and removed the discovery URL.
> So I stick with the param notation "nDiscovery" because it is still
> using parts of the discovery and runs in a special mode which has to
> be enabled and is disables by default.
>
> So if u want to use it attack "nDiscovery=true" as a Get-parameter
> like:
> "opcua:tcp://opcua.demo-
> this.com:51210/UA/SampleServer&nDiscovery=true"
>
> Try that on the Branch: PLC4X-157OPC-UADisablediscovery
>
Cool. IMHO it is better to use: discovery=false
What do you think? I have commented it already on the issue but not
sure if you could read it before the work.
Cheers!
> Greetings Matthias
>
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Strljic, Matthias Milan <ma...@isw.uni-stuttgart.de>
> Gesendet: Thursday, December 5, 2019 9:28 AM
> An: dev@plc4x.apache.org
> Betreff: AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> config endpoint discovery
>
> Hi Alvaro,
>
> i am close to push this feature. But you have for me setup/example
> server to test the issue?
> Because my attempt would be to use the existing discovery tools to
> generate the ApplicationDescription and then replace the host address
> with the public address or just remove included discovery urls.
>
> Greetings Matthias
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Álvaro Del Castillo <ad...@ThingsO2.com>
> Gesendet: Thursday, December 5, 2019 7:59 AM
> An: dev@plc4x.apache.org
> Betreff: Re: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> config endpoint discovery
>
> Hi Matthias,
>
> On Wed, 2019-12-04 at 14:12 +0000, Strljic, Matthias Milan wrote:
> > Ok, then i will include the typical URI style for GET-parameters
> > like
> > u and Chris suggests.
>
> So are you going to implement it? We need this fix so I can help in
> the implementation of it or in the testing.
>
> Cheers!
>
> -- Alvaro
>
> > Perhaps there I try to hard to stick to the domain URL (if there
> > is
> > sometimes one 😃 )
> >
> > Greetings Matthias
> > Matthias Strljic, M.Sc.
> >
> > Universität Stuttgart
> > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > Fertigungseinrichtungen (ISW)
> >
> > Seidenstraße 36
> > 70174 Stuttgart
> > GERMANY
> >
> > Tel: +49 711 685-84530
> > Fax: +49 711 685-74530
> >
> > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > Web: http://www.isw.uni-stuttgart.de
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Julian Feinauer <j....@pragmaticminds.de>
> > Gesendet: Monday, December 2, 2019 1:42 PM
> > An: dev@plc4x.apache.org
> > Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > config
> > endpoint discovery
> >
> > Hi,
> >
> > thanks fort he fast reply Matthias.
> > I agree with what Matthias says... I highly suggest the Camel
> > Parameter Syntax (basically valid URI's).
> > And yes, probably the subtype approach makes sense (this is
> > consistent
> > with having the physical transport layer also there for protocols
> > that
> > support multiple ones).
> >
> > Julian
> >
> > Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> > matthias.strljic@isw.uni-stuttgart.de>:
> >
> > Hi all,
> >
> > For this I have a question: How should we deal with this
> > consistently in the project?
> >
> > The Camel discussion about parameters/annotation is not over
> > yet
> > (?) and I want to avoid parameters in the URL that are not part of
> > the
> > domain model of the protocol.
> > So I would solve it first as a new connection subtype.
> > "opcua:tcp-ndiscover://145.............".
> > But on the other hand this only makes sense if this is a real
> > exception and would else explode in number by defined subtypes.
> >
> > So what do you think?
> >
> > Greeting
> > Matthias Strljic, M.Sc.
> >
> > Universität Stuttgart
> > Institut für Steuerungstechnik der Werkzeugmaschinen und
> > Fertigungseinrichtungen (ISW)
> >
> > Seidenstraße 36
> > 70174 Stuttgart
> > GERMANY
> >
> > Tel: +49 711 685-84530
> > Fax: +49 711 685-74530
> >
> > E-Mail: matthias.strljic@isw.uni-stuttgart.de
> > Web: http://www.isw.uni-stuttgart.de
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> > Gesendet: Friday, November 29, 2019 5:21 PM
> > An: dev@plc4x.apache.org
> > Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by
> > config
> > endpoint discovery
> >
> > Alvaro del Castillo created PLC4X-157:
> > -----------------------------------------
> >
> > Summary: 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
> >
> >
> > 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)
> >
> >
AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
endpoint discovery
Posted by "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>.
Hi Alvaro,
i pushed now a potential fix for your issue. Can u verify if it solves the problem?
This fix still uses the discovery capabilities of the Milo-Endpoint because it is a quite heavy configuration. There I then replaced the endpoint address with the provided one and removed the discovery URL.
So I stick with the param notation "nDiscovery" because it is still using parts of the discovery and runs in a special mode which has to be enabled and is disables by default.
So if u want to use it attack "nDiscovery=true" as a Get-parameter like:
"opcua:tcp://opcua.demo-this.com:51210/UA/SampleServer&nDiscovery=true"
Try that on the Branch: PLC4X-157OPC-UADisablediscovery
Greetings Matthias
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Strljic, Matthias Milan <ma...@isw.uni-stuttgart.de>
Gesendet: Thursday, December 5, 2019 9:28 AM
An: dev@plc4x.apache.org
Betreff: AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Hi Alvaro,
i am close to push this feature. But you have for me setup/example server to test the issue?
Because my attempt would be to use the existing discovery tools to generate the ApplicationDescription and then replace the host address with the public address or just remove included discovery urls.
Greetings Matthias
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Álvaro Del Castillo <ad...@ThingsO2.com>
Gesendet: Thursday, December 5, 2019 7:59 AM
An: dev@plc4x.apache.org
Betreff: Re: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Hi Matthias,
On Wed, 2019-12-04 at 14:12 +0000, Strljic, Matthias Milan wrote:
> Ok, then i will include the typical URI style for GET-parameters like
> u and Chris suggests.
So are you going to implement it? We need this fix so I can help in the implementation of it or in the testing.
Cheers!
-- Alvaro
> Perhaps there I try to hard to stick to the domain URL (if there is
> sometimes one 😃 )
>
> Greetings Matthias
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Julian Feinauer <j....@pragmaticminds.de>
> Gesendet: Monday, December 2, 2019 1:42 PM
> An: dev@plc4x.apache.org
> Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Hi,
>
> thanks fort he fast reply Matthias.
> I agree with what Matthias says... I highly suggest the Camel
> Parameter Syntax (basically valid URI's).
> And yes, probably the subtype approach makes sense (this is consistent
> with having the physical transport layer also there for protocols that
> support multiple ones).
>
> Julian
>
> Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> matthias.strljic@isw.uni-stuttgart.de>:
>
> Hi all,
>
> For this I have a question: How should we deal with this
> consistently in the project?
>
> The Camel discussion about parameters/annotation is not over yet
> (?) and I want to avoid parameters in the URL that are not part of the
> domain model of the protocol.
> So I would solve it first as a new connection subtype.
> "opcua:tcp-ndiscover://145.............".
> But on the other hand this only makes sense if this is a real
> exception and would else explode in number by defined subtypes.
>
> So what do you think?
>
> Greeting
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> Gesendet: Friday, November 29, 2019 5:21 PM
> An: dev@plc4x.apache.org
> Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Alvaro del Castillo created PLC4X-157:
> -----------------------------------------
>
> Summary: 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
>
>
> 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)
>
>
AW: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
endpoint discovery
Posted by "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>.
Hi Alvaro,
i am close to push this feature. But you have for me setup/example server to test the issue?
Because my attempt would be to use the existing discovery tools to generate the ApplicationDescription and then replace the host address with the public address or just remove included discovery urls.
Greetings Matthias
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Álvaro Del Castillo <ad...@ThingsO2.com>
Gesendet: Thursday, December 5, 2019 7:59 AM
An: dev@plc4x.apache.org
Betreff: Re: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Hi Matthias,
On Wed, 2019-12-04 at 14:12 +0000, Strljic, Matthias Milan wrote:
> Ok, then i will include the typical URI style for GET-parameters like
> u and Chris suggests.
So are you going to implement it? We need this fix so I can help in the implementation of it or in the testing.
Cheers!
-- Alvaro
> Perhaps there I try to hard to stick to the domain URL (if there is
> sometimes one 😃 )
>
> Greetings Matthias
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Julian Feinauer <j....@pragmaticminds.de>
> Gesendet: Monday, December 2, 2019 1:42 PM
> An: dev@plc4x.apache.org
> Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Hi,
>
> thanks fort he fast reply Matthias.
> I agree with what Matthias says... I highly suggest the Camel
> Parameter Syntax (basically valid URI's).
> And yes, probably the subtype approach makes sense (this is consistent
> with having the physical transport layer also there for protocols that
> support multiple ones).
>
> Julian
>
> Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> matthias.strljic@isw.uni-stuttgart.de>:
>
> Hi all,
>
> For this I have a question: How should we deal with this
> consistently in the project?
>
> The Camel discussion about parameters/annotation is not over yet
> (?) and I want to avoid parameters in the URL that are not part of the
> domain model of the protocol.
> So I would solve it first as a new connection subtype.
> "opcua:tcp-ndiscover://145.............".
> But on the other hand this only makes sense if this is a real
> exception and would else explode in number by defined subtypes.
>
> So what do you think?
>
> Greeting
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> Gesendet: Friday, November 29, 2019 5:21 PM
> An: dev@plc4x.apache.org
> Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Alvaro del Castillo created PLC4X-157:
> -----------------------------------------
>
> Summary: 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
>
>
> 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)
>
>
Re: AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
endpoint discovery
Posted by Álvaro Del Castillo <ad...@ThingsO2.com>.
Hi Matthias,
On Wed, 2019-12-04 at 14:12 +0000, Strljic, Matthias Milan wrote:
> Ok, then i will include the typical URI style for GET-parameters like
> u and Chris suggests.
So are you going to implement it? We need this fix so I can help in the
implementation of it or in the testing.
Cheers!
-- Alvaro
> Perhaps there I try to hard to stick to the domain URL (if there is
> sometimes one 😃 )
>
> Greetings Matthias
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Julian Feinauer <j....@pragmaticminds.de>
> Gesendet: Monday, December 2, 2019 1:42 PM
> An: dev@plc4x.apache.org
> Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Hi,
>
> thanks fort he fast reply Matthias.
> I agree with what Matthias says... I highly suggest the Camel
> Parameter Syntax (basically valid URI's).
> And yes, probably the subtype approach makes sense (this is
> consistent with having the physical transport layer also there for
> protocols that support multiple ones).
>
> Julian
>
> Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> matthias.strljic@isw.uni-stuttgart.de>:
>
> Hi all,
>
> For this I have a question: How should we deal with this
> consistently in the project?
>
> The Camel discussion about parameters/annotation is not over yet
> (?) and I want to avoid parameters in the URL that are not part of
> the domain model of the protocol.
> So I would solve it first as a new connection subtype.
> "opcua:tcp-ndiscover://145.............".
> But on the other hand this only makes sense if this is a real
> exception and would else explode in number by defined subtypes.
>
> So what do you think?
>
> Greeting
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> Gesendet: Friday, November 29, 2019 5:21 PM
> An: dev@plc4x.apache.org
> Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Alvaro del Castillo created PLC4X-157:
> -----------------------------------------
>
> Summary: 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
>
>
> 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)
>
>
AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Posted by "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>.
Ok, then i will include the typical URI style for GET-parameters like u and Chris suggests.
Perhaps there I try to hard to stick to the domain URL (if there is sometimes one 😃 )
Greetings Matthias
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Julian Feinauer <j....@pragmaticminds.de>
Gesendet: Monday, December 2, 2019 1:42 PM
An: dev@plc4x.apache.org
Betreff: Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Hi,
thanks fort he fast reply Matthias.
I agree with what Matthias says... I highly suggest the Camel Parameter Syntax (basically valid URI's).
And yes, probably the subtype approach makes sense (this is consistent with having the physical transport layer also there for protocols that support multiple ones).
Julian
Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>:
Hi all,
For this I have a question: How should we deal with this consistently in the project?
The Camel discussion about parameters/annotation is not over yet (?) and I want to avoid parameters in the URL that are not part of the domain model of the protocol.
So I would solve it first as a new connection subtype. "opcua:tcp-ndiscover://145.............".
But on the other hand this only makes sense if this is a real exception and would else explode in number by defined subtypes.
So what do you think?
Greeting
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Alvaro del Castillo (Jira) <ji...@apache.org>
Gesendet: Friday, November 29, 2019 5:21 PM
An: dev@plc4x.apache.org
Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Alvaro del Castillo created PLC4X-157:
-----------------------------------------
Summary: 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
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)
Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi,
thanks fort he fast reply Matthias.
I agree with what Matthias says... I highly suggest the Camel Parameter Syntax (basically valid URI's).
And yes, probably the subtype approach makes sense (this is consistent with having the physical transport layer also there for protocols that support multiple ones).
Julian
Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>:
Hi all,
For this I have a question: How should we deal with this consistently in the project?
The Camel discussion about parameters/annotation is not over yet (?) and I want to avoid parameters in the URL that are not part of the domain model of the protocol.
So I would solve it first as a new connection subtype. "opcua:tcp-ndiscover://145.............".
But on the other hand this only makes sense if this is a real exception and would else explode in number by defined subtypes.
So what do you think?
Greeting
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Alvaro del Castillo (Jira) <ji...@apache.org>
Gesendet: Friday, November 29, 2019 5:21 PM
An: dev@plc4x.apache.org
Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Alvaro del Castillo created PLC4X-157:
-----------------------------------------
Summary: 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
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)
Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Posted by Álvaro Del Castillo <ad...@ThingsO2.com>.
Dear all,
On Mon, 2019-12-02 at 12:43 +0000, Christofer Dutz wrote:
> Hi Matthias,
>
> I wouldn't like to have this handled by a new driver-name. Also do I
> think this is something quite related to the driver itself as this
> type of problem doesn't occur with other protocols (Not that I know
> of).
>
> We probably will be refactoring all drivers to:
> - IP-Based drivers simply have an IP and an optional port config
> - Serial-Based drivers simply have device uri ("/dev/s0" or "com1")
>
> Which would be pretty much similar to the existing, but the "S7"
> driver would drop the "/1/1" at the end, the AMS would lose the last
> two ".1.1" and so on and generally operate with defaults.
> If a non-default has to be used, I think it's the plan to add options
> to the string (Same way the S7 currently supports some additional
> things like to pass in the expected remote PLC type):
>
> s7://10.10.64.20:123?rack=2&slot=4
>
> or for ADS/AMS:
>
> ads://10.10.64.40?amsNetId=1.2.3.4.5.6
>
> In your proposed opc-ua case I could imagine something like this:
>
> opc-ua:typ://10.10.64.50?ndiscover=true
I find easier to understand:
opc-ua:typ://10.10.64.50?discover=false
Following this discussion, for modbus the idea for the slaveId could
be:
modbus:tcp://10.10.64.51:502?slaveId=1
Right?
I update the JIRA issue about it.
Cheers!
>
> Would that be ok for you?
>
> Chris
>
>
>
> Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <
> matthias.strljic@isw.uni-stuttgart.de>:
>
> Hi all,
>
> For this I have a question: How should we deal with this
> consistently in the project?
>
> The Camel discussion about parameters/annotation is not over yet
> (?) and I want to avoid parameters in the URL that are not part of
> the domain model of the protocol.
> So I would solve it first as a new connection subtype.
> "opcua:tcp-ndiscover://145.............".
> But on the other hand this only makes sense if this is a real
> exception and would else explode in number by defined subtypes.
>
> So what do you think?
>
> Greeting
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strljic@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -----Ursprüngliche Nachricht-----
> Von: Alvaro del Castillo (Jira) <ji...@apache.org>
> Gesendet: Friday, November 29, 2019 5:21 PM
> An: dev@plc4x.apache.org
> Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config
> endpoint discovery
>
> Alvaro del Castillo created PLC4X-157:
> -----------------------------------------
>
> Summary: 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
>
>
> 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)
>
>
Re: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Matthias,
I wouldn't like to have this handled by a new driver-name. Also do I think this is something quite related to the driver itself as this type of problem doesn't occur with other protocols (Not that I know of).
We probably will be refactoring all drivers to:
- IP-Based drivers simply have an IP and an optional port config
- Serial-Based drivers simply have device uri ("/dev/s0" or "com1")
Which would be pretty much similar to the existing, but the "S7" driver would drop the "/1/1" at the end, the AMS would lose the last two ".1.1" and so on and generally operate with defaults.
If a non-default has to be used, I think it's the plan to add options to the string (Same way the S7 currently supports some additional things like to pass in the expected remote PLC type):
s7://10.10.64.20:123?rack=2&slot=4
or for ADS/AMS:
ads://10.10.64.40?amsNetId=1.2.3.4.5.6
In your proposed opc-ua case I could imagine something like this:
opc-ua:typ://10.10.64.50?ndiscover=true
Would that be ok for you?
Chris
Am 02.12.19, 13:31 schrieb "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>:
Hi all,
For this I have a question: How should we deal with this consistently in the project?
The Camel discussion about parameters/annotation is not over yet (?) and I want to avoid parameters in the URL that are not part of the domain model of the protocol.
So I would solve it first as a new connection subtype. "opcua:tcp-ndiscover://145.............".
But on the other hand this only makes sense if this is a real exception and would else explode in number by defined subtypes.
So what do you think?
Greeting
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Alvaro del Castillo (Jira) <ji...@apache.org>
Gesendet: Friday, November 29, 2019 5:21 PM
An: dev@plc4x.apache.org
Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Alvaro del Castillo created PLC4X-157:
-----------------------------------------
Summary: 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
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)
AW: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint
discovery
Posted by "Strljic, Matthias Milan" <ma...@isw.uni-stuttgart.de>.
Hi all,
For this I have a question: How should we deal with this consistently in the project?
The Camel discussion about parameters/annotation is not over yet (?) and I want to avoid parameters in the URL that are not part of the domain model of the protocol.
So I would solve it first as a new connection subtype. "opcua:tcp-ndiscover://145.............".
But on the other hand this only makes sense if this is a real exception and would else explode in number by defined subtypes.
So what do you think?
Greeting
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strljic@isw.uni-stuttgart.de
Web: http://www.isw.uni-stuttgart.de
-----Ursprüngliche Nachricht-----
Von: Alvaro del Castillo (Jira) <ji...@apache.org>
Gesendet: Friday, November 29, 2019 5:21 PM
An: dev@plc4x.apache.org
Betreff: [jira] [Created] (PLC4X-157) OPC-UA: Disable by config endpoint discovery
Alvaro del Castillo created PLC4X-157:
-----------------------------------------
Summary: 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
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)