Ports
| IP address | Port | Protocol | Payload | Reply from the server |
|---|---|---|---|---|
164.30.75.205 | 41300 | UDP | Any | Only with ECHO |
164.30.75.205 | 41300 | CoAP | Any method, any path, any payload; Block1 for large payloads | 2.04 Changed, with ECHO 2.05 Content |
164.30.75.205 | 12400 | TCP | Any | Only with ECHO |
164.30.75.205 | 12400 | HTTP/1.1 | Any method, any path, any body | 204 No Content, with ECHO 200 OK |
164.30.75.205 | 41300 | DTLS 1.2 (PSK) | UDP or CoAP inside DTLS, as above | As for UDP and CoAP, encrypted |
164.30.75.205 | 12400 | TLS 1.2 (PSK) | TCP or HTTP inside TLS, as above | As for TCP and HTTP, encrypted |
164.30.75.205 | 15683 | LwM2M 1.0 / 1.1 (CoAP) | Register your LwM2M client, see LwM2M | LwM2M server: registration, read, write, observe |
164.30.75.205 | 5783 | LwM2M bootstrap (CoAP) | Bootstrap-Request of your LwM2M client, see bootstrap | The account of the LwM2M server on port 15683 |
164.30.75.205 | 15684 | LwM2M over DTLS 1.2 (PSK) | As on 15683, encrypted; key identity = endpoint name, see LwM2M | As on 15683, encrypted |
164.30.75.205 | 5784 | LwM2M bootstrap over DTLS 1.2 (PSK) | Bootstrap-Request with the key of the endpoint | The DTLS account of the LwM2M server on port 15684 |
All protocols of a port share it. The server recognises the protocol from your message: a DTLS or TLS handshake starts an encrypted session, a valid CoAP request is answered as CoAP, a connection that starts with an HTTP request is answered as HTTP. Everything else is plain UDP or TCP. Inside DTLS and TLS the same rules apply to your decrypted data.