HotLoop Flow 2.9.1 release notes
HotLoop Flow 2.9.1 lets the modbus-server node listen on one VLAN’s interface, so one Flow can run a server on each VLAN of a port at the same address and port.
What’s new
Section titled “What’s new”modbus-servertakes a network interface. The listening socket is bound to the interface (SO_BINDTODEVICE) before it listens, so two servers on192.168.1.9:10502on two VLANs no longer collide. The setting is the same as on every client: the node’s own Network interface, elseFLOW_NETWORK_INTERFACEin its tab’s environment variables. With neither, it listens as it always did, and two servers on one address and port still collide, now with an error that says each needs an interface.
What changed
Section titled “What changed”- Unset, it behaves as the upstream does. NOTICE and
HOTLOOP_PATCH.txtsay what changed.
New settings
Section titled “New settings”None beyond the Network interface field on modbus-server. The chart value bindToInterface.netRaw and the host-network requirement from 2.9.0 apply to it as they do to the clients.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.9.1 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. A flow that sets no interface behaves exactly as it did on 2.9.0.
Image: ghcr.io/hotloop-io/hotloop-flow:2.9.1, linux/amd64 first, with arm64 following in 2.9.2. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.9.1/README.md