State not properly closed on time?

[tomdiks]

In my local network I've put the inverter for the solar panels in it's own vlan with only access to internet and dns. It is perfectly able to connect to the internet and transmit data to Solax Cloud. But I've to reset it's state every day otherwise won't able to talk to Solax Cloud again. Once I've reset it's state 'let out anything from firewall host itself' the connection is reestablished.
Does anyone know how to fix this behavior?

[Fright]

can you give more details why you think that this state should have been expired?

[tomdiks]

Because of the solar inverter shuts down every day and wakes up the next morning, I'm assuming that the state should be dropped otherwise in this case it's preventing the solar inverter to properly establish a (new) connection the next day. It only makes a good connection after I've manually dropped the previous connection (state). Only then the inverter is showing up in Solax Cloud.

[Fright]

Because of the solar inverter shuts down every day and wakes up the next morning

in this case inverter and server should gracefully close tcp session. because if they not, default tcp.established timeout is set to 24H.
imho you can try to change Firewall optimization value to Aggresive in Firewall: Settings: Advanced - this will set tcp.established timeout value to 5H (there are other options, but they are somewhat more complicated imho)

[tomdiks]

Thank you for the suggestion. I’ve changed the setting into ‘aggressive’ and I’ll let you know if it helps.

[tomdiks]

Good news! Today the solar inverter got online on its own. The previous state was dropped so a new connection could be established this morning. Thanks again for this tip.

[franco]

I have one of those things in the house and the live monitoring through cloud is flaky at best. I wonder if they set out to find the worst TCP stack they could find and slapped it into these solar products?


Cheers,
Franco