Title
q
quaint-policeman-41984
10/07/2022, 3:23 PMIt happens on 21.02 and 22.03
m
most-rain-82770
10/07/2022, 3:25 PMcan you provide steps to reproduce? As it sounds like it works sometimes would need to isolate
q
quaint-policeman-41984
10/07/2022, 3:27 PMJust restarting the system, i will make some test in 30 minutes
m
most-rain-82770
10/07/2022, 3:28 PMthanks sounds good
anything yet?
q
quaint-policeman-41984
10/07/2022, 4:52 PMSorry, i'm updating it to the latest version 0.16.1
No problems on debian installs
I'm going back to 0.16.0 to test the problem i mentioned before
m
most-rain-82770
10/07/2022, 5:37 PMok
q
quaint-policeman-41984
10/07/2022, 5:44 PMWell the first thing, when you stop netclient (/etc/init.d/netclient stop) the wireguard tunnel is still up
You can see in the logs that it successful stops
[netclient] 2022-10-07 17:42:59 [daemon.go-74] Daemon(): shutting down netclient daemon
[netclient] 2022-10-07 17:42:59 [mqpublish.go-41] Checkin(): checkin routine closed
[netclient] 2022-10-07 17:42:59 [daemon.go-201] messageQueue(): shutting down message queue for server xxx
[netclient] 2022-10-07 17:42:59 [daemon.go-76] Daemon(): shutdown completeCant reproduce when the tunnel does not start, i see that wireguard is started but no peers are created
Will trace the error when it happens again
After a power lose when openwrt 22.03 turn on the tunnel is not working
[netclient] 2016-01-21 08:50:20 [daemon.go-49] Daemon(): netclient daemon started -- version: v0.16.0
[netclient] 2016-01-21 08:50:20 [clientconfig.go-23] UpdateClientConfig(): checking for netclient updates...
[netclient] 2016-01-21 08:50:20 [clientconfig.go-52] UpdateClientConfig(): finished updates
[netclient] 2016-01-21 08:50:20 [daemon.go-93] startGoRoutines(): initializing network home
[netclient] 2016-01-21 08:50:20 [daemon.go-108] startGoRoutines(): started daemon for server xxx
[netclient] 2016-01-21 08:50:40 [mqpublish.go-32] Checkin(): starting checkin goroutine
[netclient] 2016-01-21 08:50:40 [daemon.go-193] messageQueue(): network: home netclient message queue started for server: xxx
[netclient] 2016-01-21 08:50:40 [mqpublish.go-56] checkin(): checkin with server(s) for all networks
[netclient] 2016-01-21 08:51:10 [daemon.go-302] setupMQTT(): unable to connect to broker, retrying ...[netclient] 2016-01-21 08:51:30 [mqpublish.go-75] checkin(): error encountered checking public ip addresses: public address not found
[netclient] 2016-01-21 08:51:30 [daemon.go-309] setupMQTT(): could not connect to broker xxx nslookup failed for broker ... check dns records
[netclient] 2016-01-21 08:52:00 [mqpublish.go-255] publish(): could not connect to broker at xxx
[netclient] 2016-01-21 08:52:00 [mqpublish.go-152] Hello(): Network: home error publishing ping, connection timeout
[netclient] 2016-01-21 08:52:00 [mqpublish.go-153] Hello(): running pull on home to reconnect
[netclient] 2016-01-21 08:52:00 [mqpublish.go-156] Hello(): could not run pull on home, error: Post "https://xxx/api/nodes/adm/home/authenticate": dial tcp: lookup xxx on [::1]:53: server misbehaving
[netclient] 2022-10-08 11:18:31 [daemon.go-155] setSubscriptions(): subscribed to node updates for node Pueblo update/home/yyy
[netclient] 2022-10-08 11:18:31 [daemon.go-160] setSubscriptions(): subscribed to peer updates for node Pueblo peers/home/yyy
[netclient] 2022-10-08 11:19:14 [mqpublish.go-56] checkin(): checkin with server(s) for all networks
[netclient] 2022-10-08 11:19:15 [mqpublish.go-159] Hello(): checkin for home completeNo peers listed on wireguard, but seems to be started
m
most-rain-82770
10/10/2022, 6:50 PMstill started?
q
quaint-policeman-41984
10/10/2022, 7:12 PMYou mean if the netclient process stops/dies? No, it continues spamming the hello and checkin