Hi,
The client often loses the connection.
I'm using a server on a Raspberry Pi 3. Pings from client to server are not lost.
How can I fix it?
Wed Jun 19 15:21:29 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:26:29 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:26:29 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:31:29 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:31:29 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:31:47 2019 user.info vhusbdchpi3[532]: Device 114 [0529:0001] UNBOUND from connection 17
Wed Jun 19 15:31:48 2019 user.info vhusbdchpi3[532]: Connection 17 successfully removed (reason:timeout)
Wed Jun 19 15:32:24 2019 user.info vhusbdchpi3[532]: 192.168.21.29 connected as connection 24
Wed Jun 19 15:36:29 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:36:29 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:41:29 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:41:29 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:46:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:46:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:51:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:51:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 15:56:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 15:56:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 16:00:15 2019 user.info vhusbdchpi3[532]: Connection 24 successfully removed (reason:timeout)
Wed Jun 19 16:01:01 2019 user.info vhusbdchpi3[532]: 192.168.21.29 connected as connection 25
Wed Jun 19 16:01:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 16:01:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 16:01:40 2019 user.info vhusbdchpi3[532]: Connection 25 successfully removed (reason:timeout)
Wed Jun 19 16:02:57 2019 user.info vhusbdchpi3[532]: 192.168.21.29 connected as connection 26
Wed Jun 19 16:06:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 16:06:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 16:11:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 16:11:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 16:16:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
Wed Jun 19 16:16:30 2019 daemon.notice netifd: lan (576): udhcpc: lease of 192.168.21.206 obtained, lease time 600
Wed Jun 19 16:21:30 2019 daemon.notice netifd: lan (576): udhcpc: sending renew to 192.168.21.2
.
Dont use wifi on the pi3, use ethernet instead, or use a decent dual 2T2R board like the gl-mt300nv2
I use ethernet.
I use ethernet.
I'm using ethernet. Can I
I'm using ethernet. Can I increase the timeout?
.
Are you using it over a VPN or plain ethernet? If you are getting issues like this over plain ethernet i think there is some hardware problem with your pi or network.
.
plain ethernet
.
I think there is some hardware issue.
I am also experiencing this.
I am also experiencing this. I have a pi 3b+ wired via ethernet. Would using a VPN eliminate these dropouts?
/
What is your latency graph looking like? Right click on the USB server in the client and select Properties -> (Latency)