jabilmplane

But why API for calling a RPC still exists? I mean `sr_rpc_send`. If it is ignored, there is no need to keep it in the API and in examples provided...

Hi, I have exactly the same issue. I started the call-home procedure when port 4334 was not opened on the client side and got following logs continuously printed: ``` [INF]:...

One more note. In the netstat output there are duplicated items (client's ip address is 192.168.111.3) : ``` engineer@sub6:~$ netstat -a | grep 192.168.111.8 tcp 0 1 192.168.111.8:44910 192.168.111.3:4334 SYN_SENT...

@michalvasko I did some investigation and found that the root cause is similar to the one I mentioned. It is almost the same code but in the different place: end...

Correct, I use pretty old version. But I have checked diff between recent devel and code looks pretty similar.

`[ERR]: LN: Could not set TCP_NODELAY socket option (Bad file descriptor).` is printed when port 4334 is disabled on the client's side

@michalvasko, you are right. It seems to work properly on the latest devel. ``` [INF]: LN: Trying to connect via IPv4 to 192.168.0.107:4334. [INF]: LN: Timed out after 5s (Operation...

It is possible to configure some rules using "iptables" linux tool. In my configuration, if I remove rules for port 4334, any connection to this port will be dropped. But...