You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,13 +37,15 @@ The actual probe code that runs inside a docker container on the device is autom
37
37
38
38
## Accessing the probe
39
39
40
-
For security reasons there is no way to get shell access of a running probe. But for debugging purposes you can connect to it via SSH to get the logs of the software probe. To connect:
40
+
For security reasons there is no way to get shell access of a running probe. But for debugging purposes you can connect to it via SSH to get the container logs of the software probe. To connect:
41
41
42
42
1. Login into your router's web UI and check the list of connected devices. You should be able to spot the globalping hardware probe in the list.
4. You can now see the log output of the docker container running the software probe on your device.
46
46
47
+
To access firmware logs (only really useful to firmware devs/firmware debug), repeat the above steps but with "devlogs" instead of "logs" as the user
48
+
47
49
## Security
48
50
49
51
In addition to the [security features of the software probe](https://github.com/jsdelivr/globalping-probe#security) these are the extra safe guards we used to make the hardware device as secure as possible:
0 commit comments