August-13th-2018, 09:54 AM
Hi Afet,
first of glad to hear that netPI and the internet connectivity is working as expected now.
Using Modbus TCP in a container makes no problems. There is nothing to be changed. Node-RED, respectively node.js underneath will send TCP/IP traffic (MQTT or Modbus) to the IP destination addressed and Linux will based on the subnetworks automatically route traffic to the right interface ... if it is Wifi or LAN doen't matter for the app.
To the DHCP problem: you say you "put the system in use". Can you please tell which the three parameters IP address, gateway and subnet mask you enter in this case for LAN and Wifi. And then I understood you change the LAN settings again to "another" value range and ... then independent of what you enter DHCP is enabled by netPI software by mistake? Is my understanding correct?
Thx
Armin
first of glad to hear that netPI and the internet connectivity is working as expected now.
Using Modbus TCP in a container makes no problems. There is nothing to be changed. Node-RED, respectively node.js underneath will send TCP/IP traffic (MQTT or Modbus) to the IP destination addressed and Linux will based on the subnetworks automatically route traffic to the right interface ... if it is Wifi or LAN doen't matter for the app.
To the DHCP problem: you say you "put the system in use". Can you please tell which the three parameters IP address, gateway and subnet mask you enter in this case for LAN and Wifi. And then I understood you change the LAN settings again to "another" value range and ... then independent of what you enter DHCP is enabled by netPI software by mistake? Is my understanding correct?
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)