Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 207
    • Merge Requests 207
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #12319

Closed
Open
Opened Jan 16, 2021 by Lars Rönnbäck@Roenbaeck

ifupdown-ng does not run ifenslave

After upgrading from 3.11 to 3.13.0 networking no longer worked. My interface, bond0, came up without errors but the server was unreachable. Logging in locally and digging around I saw that: /sys/class/net/bond0/bonding/slaves was empty. Running the following two commands by hand solves the problem and the network starts working:

ifenslave bond0 eth0
ifenslave bond0 eth1

It seems to me that this should be managed automatically by ifupdown-ng. I did some extensive searching, trying to figure out if the syntax of /etc/network/interfaces has changed, but could not figure out if it had. The admin guide for ifupdown-ng on their own github page did not provide further help.

For reference, my interfaces file looks as follows, which worked fine before the upgrade:

auto lo
iface lo inet loopback

auto bond0
iface bond0 inet dhcp
        bond-slaves eth0 eth1
        hostname nas
        bond-mode 2
Edited Jan 16, 2021 by Lars Rönnbäck
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/aports#12319