mbusd:did not bind to specific interface
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
mbusd
Maintainer
Marcin Jurkowski
OpenWrt Version
24.10.3
OpenWrt Target/Subtarget
ath79/generic
Steps to Reproduce
Use i.e. any dumb ap with 3 VLANs.
one interface unmanaged,
2 interfaces with static ip's i.e. 192.168.1.33/24 & 192.168.2.33/24
install mbusd
configure with additional option "address 192.168.2.33"
Actual Behaviour
The original mbusd package provides option "A" to specify a address of the interface, to which mbusd will bind.
This is especially useful when running some VLANs on the same device.
The openwrt init script for mbusd did not provide this option. Even if you define "option address 192.168.x.x" in /etc/config/mbusd this option is ignored and mbusd is bind to all interfaces with IP's defined.
So please add the "A" option to config and init script.
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 by locating the mbusd package's init script and configuration handling for /etc/config/mbusd. Check how the requested address setting is translated into the daemon arguments, then verify with multiple VLAN interfaces that mbusd binds only to the configured address.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100