babeld: unable to specify bridge as interface
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 396
- Forks
- 452
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 2
Description
It is not possible to use a bridge as an interface in babeld (when configured using UCI).
A simple
config interface 'wan'
will resolve wan to the first interface of that bridge (in my case eth0) as opposed to br-wan. This, obviously, breaks in funny ways.
The sample UCI config states to use the full interface name instead to avoid this mess, like this:
config interface 'br-wan'
Well, that doesn't work either. A dash is not allowed by UCI in section names.
Can we restructure the config to make ifname an option of the configuration section?
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
Start by tracing how the UCI interface section resolves a named bridge to its underlying interface. Check the existing sample UCI configuration and the handling of interface names such as br-wan. Done means a bridge can be configured through UCI without being reduced to eth0, while existing interface configuration continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100