Rich,
But I believe that the connections are always initiated by the Cloud Connector.
This is what I thought too. But this wouldn’t explain why I see refuse immediately after request from outside.
My understanding now is the following (can be very wrong though):
- my client initiates connection to the cloud for creating the tunnel
- within this tunnel, external element initiates connections back to my OH
This would be logical explanation how to trigger from e.g. Google home switch off of my lights (Google Home → Cloud [myopenhab.org] ----- over the tunnel ----> my own OH instance → item switch off request)
This in turn suggests there is some setting somewhere allowing/disallowing these internal requests (within the tunnel which is always initiated one way by my OH instance)
In my network setting I just specified my OH primary address with the netmask - 192.168.1.23/24 (the hint in line below in the PaperUI suggests however the whole subnet, I don’t know whether I should change it…)
then all the rest is default i.e.
- use IPv6 if available (ON)
- no broadcast address
- single IP address per interface (OFF)
I installed OH using apt (about 1.5-2y ago so that’s why I was thinking that maybe I missed something important during installation and forgot about it).
I don’t use any iptables for traffic filtering
sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
more /var/lib/openhab2/config/org/eclipse/smarthome/network.config
primaryAddress=“192.168.1.23/24”
service.pid=“org.eclipse.smarthome.network”
some threads however suggest that the primary address should be the network (e.g. this one: Parameter setting org.eclipse.smarthome.network - #9 by lubeda) but this is a bit counterintuitive. What do you have set there?