n0-computer / n0-computer/dumbpipe
Invalid tickets from listen-tcp?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 782
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Hello, thanks for this interesting sounding tool.
Alas I appear to be too dumb for the pipe. I have a local development webserver running on port 80. If I run: dumbpipe listen-tcp --host localhost:80 I get a ticket. So far so good.
https://ticket.iroh.computer/ suggests this ticket, along with all the others I've created, is invalid.
I cannot connect on another device using dumbpipe connect-tcp --addr 0.0.0.0:80 <key>, I get the following error:
error: invalid value '...' for '<TICKET>': wrong prefix, expected node
v0.28.0, Ubuntu 24.04, installed via cargo.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the report with dumbpipe listen-tcp --host localhost:80, then try the resulting ticket at ticket.iroh.computer and with dumbpipe connect-tcp --addr 0.0.0.0:80 <key>. Trace why the generated ticket has the wrong prefix for the connect command; done means tickets from listen-tcp are accepted and the connection works on another device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100