Zoltan Papp 2dec016201 Fix/always on boot (#1062) ...

In case of 'always-on' feature has switched on, after the reboot the service do not start properly in all cases.
If the device is in offline state (no internet connection) the auth login steps will fail and the service will stop.
For the auth steps make no sense in this case because if the OS start the service we do not have option for
the user interaction.

2023-08-11 11:51:39 +02:00

..

conn_status_test.go

Use the conn state of peer on proper way (#717)

2023-03-03 19:49:18 +01:00

conn_status.go

Use the conn state of peer on proper way (#717)

2023-03-03 19:49:18 +01:00

conn_test.go

Wg ebpf proxy (#911)

2023-07-26 14:00:47 +02:00

conn.go

Wg ebpf proxy (#911)

2023-07-26 14:00:47 +02:00

env_config.go

Add force relay conn env var for debug purpose (#904)

2023-05-29 13:50:40 +02:00

error_test.go

Test conn (#199)

2022-01-21 13:52:19 +01:00

error.go

Test conn (#199)

2022-01-21 13:52:19 +01:00

listener.go

Add OnDisconnecting service callback (#767)

2023-03-29 10:39:54 +02:00

notifier_test.go

Update calculate server state (#796)

2023-04-10 18:22:25 +02:00

notifier.go

Fix/always on boot (#1062)

2023-08-11 11:51:39 +02:00

status_test.go

Reduce the peer status notifications (#956)

2023-06-19 11:20:34 +02:00

status.go

After add listener automatically trigger peer list change event (#1044)

2023-08-04 14:14:08 +02:00

stdnet_android.go

Bind implementation (#779)

2023-04-13 17:00:01 +02:00

stdnet.go

Bind implementation (#779)

2023-04-13 17:00:01 +02:00