On Mon, Aug 28, 2017 at 01:09:17PM -0300, R0me0 *** wrote: > This is snapshot from today: > > Aug 28 16:05:25 rpibsd Tor[54551]: Bootstrapped 50%: Loading relay > descriptors > urtwn0: device timeout > Aug 28 16:05:30 rpibsd /bsd: urtwn0: device timeout
This again works fine here without device timeout messages: $ tail /var/log/messages Aug 28 15:47:19 carberry Tor[69953]: Bootstrapped 56%: Loading relay descriptors Aug 28 15:47:21 carberry Tor[69953]: Bootstrapped 63%: Loading relay descriptors Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 68%: Loading relay descriptors Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 75%: Loading relay descriptors Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 80%: Connecting to the Tor network Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 85%: Finishing handshake with first hop Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 90%: Establishing a Tor circuit Aug 28 15:47:24 carberry Tor[69953]: Tor has successfully opened a circuit. Looks like client functionality is working. Aug 28 15:47:24 carberry Tor[69953]: Bootstrapped 100%: Done $ date Mon Aug 28 18:31:52 CEST 2017 Ping test has been running fine as well: 9851 packets transmitted, 9828 packets received, 3 duplicates, 0.2% packet loss round-trip min/avg/max/std-dev = 2.759/114.881/3848.698/1285.292 ms I am not convinced that the urtwn driver is part of your problem. Unless you can show convincing evidence that it's a driver problem I am not going to spend more time on this. Have you already tried using this urtwn device in another machine? I suspect it will work just fine. It seems your hardware is not behaving as expected. Have you already tried using a different electrical power supply for your rpi3?
