graphprotocol / graphprotocol/graph-node
Bind server to IPv6 as well as IPv4
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Do you want to request a feature or report a bug?
Mostly a feature, but sort of a bug. The server currently only binds to IPv4, so it's hard to run in IPv6 environments without something like socat. In let addr = SocketAddrV4::new(Ipv4Addr::new(0, 0, 0, 0), port);
What is the current behavior?
The server binds to IPv4 only.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
N/A
What is the expected behavior?
It should bind to IPv6 as well.
Contributor guide
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
Start in server/http/src/server.rs around the SocketAddrV4 construction at line 76 and trace how the server creates its listening socket. Determine how IPv6 should be included while preserving the current IPv4 behavior. Done means the server binds successfully in IPv6 environments as well as IPv4 environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100