openwrt / openwrt/packages

netifd proto bonding: cannot create bond without IP/netmask

Open
#16,779 14 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Hi, I've tried to create a bond without an IP/netmask to add it as a slave of a bridge.
For example I want to bond port1 and port2 of my router and make a bridge between the bond, port3 and port4.
The bond is set as "active-backup" to provide redundancy.
This allows me to use the OpenWrt router as an "adapter" to connect non-bonding-aware devices to an existing redundant/high availability network setup with two switches where all other nodes are bonding-aware.

But from what I have seen, this protocol (and the luci-proto) requires an Ip and netmask. I also tried deleting the ip and netmask from config file, restarted network service and no bond is created.

I know it is possible to make bonds without an IP/netmask and use them as slaves in a bridge in Linux, I've been doing this on OpenSUSE (also works on Debian) for a while. A IP-less bond can also be used as a target to create VLANs over the bond.

Is there something I can change in the protocol script to just make it ignore the need for IP/netmask and build the bond anwyay?

maintainer (of the bonding proto): @he-ma

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the netifd bonding protocol and luci-proto configuration paths described in the issue, then reproduce a bond configuration with the IP and netmask removed. Done means an IP-less active-backup bond is created and can serve as a bridge slave or VLAN target without requiring an IP/netmask.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.