pbr: custom proto tunnels can't be used
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
pbr
Maintainer
Stan Grishin
OpenWrt Version
24.10.2
OpenWrt Target/Subtarget
ramips/mt7621
Steps to Reproduce
- Add interface with custom tunneling proto, e.g. amneziawg (from other sources)
- Execute
ubus -S call luci.pbr getInterfacescommand. - Observe that there is no added amneziawg interface in the list of supported interface for PBR
Actual Behaviour
/etc/init.d/pbr contains some code to determine the supported interfaces types. This method is hardcoded and doesn't allow to add custom protocol types.
It would be cool if script contains some sort of hook which can be used to install additional criteria by other packages providing custom tunneling protos.
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
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 with /etc/init.d/pbr and the interface detection used by ubus -S call luci.pbr getInterfaces. Trace how supported interface types are determined, then define a hook that other packages can use to register custom tunneling protocols. Done means an added amneziawg interface appears in the supported interface list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100