Consider adding an ethernet layer platform interface
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Currently, our platform interface has an IP-level interface to the outside world: https://github.com/MSRSSP/litebox/blob/b90d32dc976ca8553fdedef708f7bc843173ce8c/litebox/src/platform/mod.rs#L206-L221
We might wish to consider (esp for Linux-based platform scenarios, to possibly skip tun) introducing an ethernet-level interface to the platform. We can then support configuration at the LiteBox layer that allows for the platform to say whether they wish to be an Ethernet-level or an IP-level platform, with the TCP/IP stack automatically configuring itself at the right layer.
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 by reading litebox/src/platform/mod.rs around lines 206-221 to understand the existing IP-level platform interface. Then determine the scope and API needed for selecting Ethernet-level or IP-level platforms and for configuring the TCP/IP stack accordingly. Done would require an agreed design and implementation plan; the issue names no tests or concrete acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100