(At least one) P1S doesn't support TLS for MQTT/FTP
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation, networking
Research direction
The issue names no files or tests; start by reading the repository’s current MQTT and FTP documentation and the linked open-bambu-networking issue. Reproduce the reported port and TLS behavior on the listed firmware versions, then document the confirmed support or limitations if the behavior is consistent.
Written by the indexing model from the issue text.
Description
The behavior I've observed on my P1S doesn't match what's documented in this repo. For me, both MQTT and FTP are unencrypted, on their usual unencrypted ports (that is, I need to connect to port 1883 for MQTT and 21 for FTP, both with TLS disabled).
$ nc -zv 192.168.x.x 8883
nc: connect to 192.168.x.x port 8883 (tcp) failed: Connection refused
$ nc -zv 192.168.x.x 990
nc: connect to 192.168.x.x port 990 (tcp) failed: Connection refused
$ nc -zv 192.168.x.x 1883
Connection to 192.168.x.x 1883 port [tcp/*] succeeded!
$ nc -zv 192.168.x.x 21
Connection to 192.168.x.x 21 port [tcp/*] succeeded!
$ mosquitto_sub -h 192.168.x.x -p 1883 --insecure -u bblp -P <access code> -t 'device/01Pxxxx/report'
{ status messages... }
(A bit more detail on how I came to this conclusion here).
Observed on 01.09.01.00, 01.08.02.00, and 01.07.00.00
Has anyone else seen this behavior? At this point my best theory is I somehow got a device without certs installed. I'm making this ticket mostly so anyone else with the same problem can find it. If this is a common behavior, may be worth adding to the docs here. If not, I guess I'll just call it weird and move on.
- Dominant language
- No language data
- Stars
- 684
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Doridian/OpenBambuAPI
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Doridian/OpenBambuAPI#51 · 8 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Doridian/OpenBambuAPI#10 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Doridian/OpenBambuAPI#72 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Doridian/OpenBambuAPI#56 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Doridian/OpenBambuAPI#55 · 4 comments ·
All issues in Doridian/OpenBambuAPI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
alphagov/govuk-frontend-docs#668 ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
bancolombia/scaffold-clean-architecture#1001 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
navikt/esyfo-narmesteleder#615 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 84/100
n8n-io/terraform-aws-n8n#176 ·
Maintainers usually reply within 1 day