Skip to content

Commit c98e904

Browse files
Update README.md (#38)
Add user devlogs info
1 parent 01bced9 commit c98e904

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,13 +37,15 @@ The actual probe code that runs inside a docker container on the device is autom
3737

3838
## Accessing the probe
3939

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:
4141

4242
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.
4343
2. Get the IP address of the probe
4444
3. Login via ssh `ssh logs@IP_ADDRESS` e.g. `ssh [email protected]`
4545
4. You can now see the log output of the docker container running the software probe on your device.
4646

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+
4749
## Security
4850

4951
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

Comments
 (0)