|
|
пре 1 година | |
|---|---|---|
| .. | ||
| doc | 0a62d6c556 refactor(gw): rename all gateway application name | пре 2 година |
| include | 46877e979b chore: update copyright-year | пре 2 година |
| src | 80d724c504 feat(authn): add connection expire based on authn data | пре 1 година |
| test | 80d724c504 feat(authn): add connection expire based on authn data | пре 1 година |
| .gitignore | 0a62d6c556 refactor(gw): rename all gateway application name | пре 2 година |
| README.md | 25e277bdc6 chore: fix schema desc and README.md typo | пре 2 година |
| rebar.config | 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` | пре 2 година |
The CoAP gateway implements publish, subscribe, and receive messages as standard with Publish-Subscribe Broker for the CoAP.
In EMQX 5.0, CoAP gateway can be configured and enabled through the Dashboard.
It can also be enabled via the HTTP API or emqx.conf, e.g. In emqx.conf:
gateway.coap {
mountpoint = "coap/"
connection_required = false
listeners.udp.default {
bind = "5683"
max_connections = 1024000
max_conn_rate = 1000
}
}
Note: Configuring the gateway via emqx.conf requires changes on a per-node basis, but configuring it via Dashboard or the HTTP API will take effect across the cluster.
More documentations: CoAP Gateway