Posts: 41
Threads: 9
Joined: Apr 2018
Reputation:
0
Hi,
I had to reflash my LM5 to be able to upgrade firmware again. This went ok. I have now the latest firmware installed.
My issue now is that I am not able to use ETS to download.
I also have an integration with Home assistant that is working one way. I am not able to expose entities to LM, but can read values from LM.
In my quest to find out what is wrong I have also powered of the HA, to ensure that this is not "holding" the connection.
My HA uses multicast to connect so this is not an issue.
Any ideas?
Posts: 4638
Threads: 24
Joined: Aug 2017
Reputation:
207
When you say latest, do you mean RC from forum or the one from openrb.com
------------------------------
Ctrl+F5
Posts: 7758
Threads: 42
Joined: Jun 2015
Reputation:
447
Are you using tunneling or multicast connection in ETS?
Posts: 7758
Threads: 42
Joined: Jun 2015
Reputation:
447
Do you have filtering set up in KNX settings? We had a report about programming issues for certain KNX devices with ETS 5.7. But it worked fine with ETS 6.
Posts: 4638
Threads: 24
Joined: Aug 2017
Reputation:
207
What if you manually put the IP and test?
------------------------------
Ctrl+F5
Posts: 4638
Threads: 24
Joined: Aug 2017
Reputation:
207
Knx settings?
------------------------------
Ctrl+F5
Posts: 7758
Threads: 42
Joined: Jun 2015
Reputation:
447
KNX settings look correct. Try installing ETS6 demo and see if it works.
The device itself being displayed in the neighbour list is a bug that will be fixed in the next firmware. It has nothing to do with the ETS connection issue.
Posts: 221
Threads: 45
Joined: Nov 2015
Reputation:
2
Would not the 172.12.30.x be "considered" a public IP and that may result in LM blocking the access to 3671? I had an issue with that, changing the IP on the network to a tested and tried IP-range worked fine.
Posts: 41
Threads: 9
Joined: Apr 2018
Reputation:
0
Thx.. It worked.
Changing the ip to conform with IP header class standard for C networks.
For my setup this was some work.
Unifi is not very happy with changing the default network ip range, so I had to create a new network site and move everything over.
Create new static leases, adopt all my Unifi devices to the new network, setup wireless networks again, restart every device that did not get new ip before lease time expire.
Update port forwardings in firewall. Setup my vpn from cabin again, update my reverse proxy config, update addresses for my NVR. Edit static dhcp on several devices.
This evening I will go over my scripts and check Sonos to match new ip-range.
At work this will be a problem, as we are running a Class A network, also several customers (municipalities) here in norway is doing the same.
Can this be a "firewall-feature" to turn of, for people who are able to put LM's behind firewall and to block 3671/tcp, in future release?
I am very fond of this gateway and was using eibd-linknx-knxweb/lua before this product came out and always loved its flexibility.
KR
Thomas
Posts: 7758
Threads: 42
Joined: Jun 2015
Reputation:
447
It will work in a class A private network range.
Posts: 7758
Threads: 42
Joined: Jun 2015
Reputation:
447
A/B/C are all supported. Your old 172.12.30.0/24 range does not belong to the B private range which is 172.16.0.0 – 172.31.255.255.
Thx for the lesson. Been using this range for at least the last 15 years, was a bit blinded..