problem with reconnection after redeployment about node-red-contrib-ads-client HOT 4 OPEN

It seems, that the client does not send the propper FIN bit to the Server

This is the tcpdump, when I press the deploy button in Node-Red. For the connection close the client should send the FIN bit to the server, and not the FIN-ACK, to close the connection.

10:07:53.376115 IP (tos 0x0, ttl 128, id 29256, offset 0, flags [DF], proto TCP (6), length 82) 192.168.2.3.48898 > 192.168.2.10.45599: Flags [P.], cksum 0xdab1 (correct), seq 1961:2003, ack 1778, win 8208, length 42 10:07:53.389961 IP (tos 0x0, ttl 64, id 43242, offset 0, flags [DF], proto TCP (6), length 82) 192.168.2.10.45599 > 192.168.2.3.48898: Flags [P.], cksum 0xeab6 (correct), seq 1778:1820, ack 2003, win 993, length 42 10:07:53.392146 IP (tos 0x0, ttl 128, id 29257, offset 0, flags [DF], proto TCP (6), length 82) 192.168.2.3.48898 > 192.168.2.10.45599: Flags [P.], cksum 0xd95d (correct), seq 2003:2045, ack 1820, win 8208, length 42 10:07:53.403457 IP (tos 0x0, ttl 64, id 43243, offset 0, flags [DF], proto TCP (6), length 40) **192.168.2.10.45599 > 192.168.2.3.48898: Flags [F.]**, cksum 0x0893 (correct), seq 1820, ack 2045, win 993, length 0 10:07:53.404140 IP (tos 0x0, ttl 128, id 29258, offset 0, flags [DF], proto TCP (6), length 40) **192.168.2.3.48898 > 192.168.2.10.45599: Flags [.]**, cksum 0xec63 (correct), seq 2045, ack 1821, win 8208, length 0 10:07:53.404316 IP (tos 0x0, ttl 128, id 29259, offset 0, flags [DF], proto TCP (6), length 40) **192.168.2.3.48898 > 192.168.2.10.45599: Flags [F.]**, cksum 0xec62 (correct), seq 2045, ack 1821, win 8208, length 0 10:07:53.404405 IP (tos 0x0, ttl 64, id 43244, offset 0, flags [DF], proto TCP (6), length 40) **192.168.2.10.45599 > 192.168.2.3.48898: Flags [.]**, cksum 0x0892 (correct), seq 1821, ack 2046, win 993, length 0 10:07:54.201757 IP (tos 0x0, ttl 64, id 30368, offset 0, flags [DF], proto TCP (6), length 60) 10.89.8.10.33901 > 192.168.2.3.48898: Flags [S], cksum 0x10a4 (correct), seq 2558094520, win 29200, options [mss 1460,sackOK,TS val 1916286308 ecr 0,nop,wscale 6], length 0 10:07:55.239178 IP (tos 0x0, ttl 64, id 30369, offset 0, flags [DF], proto TCP (6), length 60) 10.89.8.10.33901 > 192.168.2.3.48898: Flags [S], cksum 0x0c96 (correct), seq 2558094520, win 29200, options [mss 1460,sackOK,TS val 1916287346 ecr 0,nop,wscale 6], length 0

from node-red-contrib-ads-client.

Found the Problem!

With my Hardware (Advantech ICR32xx) I use a VPN Connection to the LTE-Router. So when the connection to the client 192.168.2.10 will be closed, the ADS-router trys to connect to the vpn adress 10.89.8.10 --> this blocks then the connection for the client 192.168.2.10..

from node-red-contrib-ads-client.

Hi! Sorry I didn't got time to look into this, luckily you sorted it out. Thanks for letting me know!

from node-red-contrib-ads-client.

I have found the Problem, but is there also a solution for that? At the moment I just restart the openvpn1 client of my router, that the connection will be interrupted and the ads-client connects to the IP, which is configured at the node.

It should never happen, that the connection will be established with the openvpn1 IP adress if a local IP is configured?!

Thank you!

from node-red-contrib-ads-client.