The connection I have above constantly toggles between connected and faulted and is generally unusable.
The reported error is:
io.netty.channel.AbstractChannel$AnnotatedNoRouteToHostException: No route to host: /172.16.0.244:4840
Caused by: java.net.NoRouteToHostException: No route to host
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:336)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:339)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:784)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:732)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:658)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base/java.lang.Thread.run(Unknown Source)
Configuration of endpoint as follows:
Haven’t been able to see a certificate to trust yet as I did in UaExpert.
Using Ignition Maker 8.3.3 on a Raspberry Pi 5.
You just don’t have a network route to this host available.
How did you get this hostname? Type it in manually or go through discovery?
What IP, subnet, etc… does the Pi have?
The device is 172.16.0.244 and the pi is 172.16.0.245
Network /24
As it happens the device is a soft dPAC running in docker on the same Raspberry Pi.
I don’t know why there’s the leading forward slash on the no route to host.
Comms must work somehow, it shows connected before it drops.
The hostname was typed in manually.
I think that it briefly shows connected is actually just a UI bug.
Is Ignition also in Docker, or running on the host?
Unless you’ve done some special networking setup you’ve left out, then you need to be connecting to this container at “localhost:4840” instead, and hopefully you started it with 4840 on the host forwarded to 4840 in the container (-p 4840:4840).
I believe 4840 is forwarded to the container. I can access it as opc.tcp://172.16.0.244:4840 from another computer with UaExpert as an OPC UA client.
This is partial config in UaExpert:
With that configuration, I am able to connect once I accept certificate errors.
To answer the question about the networking setup, part of the EAE dPAC deployment does have me creating a separate IP address for that docker container, so the dPAC is .244 and ignition is .245
If you go through the discovery process in Ignition can you reach it at either opc.tcp://localhost:4840 or opc.tcp://172.16.0.2:4840 (assuming 172.16.0.2 is the IP of the bridge in docker)?
If that doesn't work you're going to have to share actual details about how the docker container/networking are set up.
