{"id":14945,"date":"2025-11-07T01:31:44","date_gmt":"2025-11-07T07:31:44","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=14945"},"modified":"2026-03-27T03:01:31","modified_gmt":"2026-03-27T09:01:31","slug":"how-to-configure-network-bonding-on-debian-10-11-after-os-reload","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/how-to-configure-network-bonding-on-debian-10-11-after-os-reload\/","title":{"rendered":"How to Configure Network Bonding on Debian 10 & 11 After OS Reload"},"content":{"rendered":"\n

After reinstalling Debian\u2014whether version 10<\/strong> (Buster<\/strong>) or 11<\/strong> (Bullseye<\/strong>)\u2014one of the most common headaches is losing your network configuration. If your setup uses bonded interfaces (LACP \/ 802.3ad)<\/strong> for redundancy, the reload wipes out all those settings. The system comes up, but there\u2019s no proper connectivity until bonding is restored. This guide walks through the exact steps we follow at SupportPRO<\/strong> to bring the network back up after a reload, get the bonds working again, and make sure SSH is accessible. This process is crucial for server performance<\/strong>, high availability<\/strong>, and Linux network configuration<\/strong>.
<\/p>\n\n\n\n\n\n\n\n

Step 1: Find the Correct Interfaces<\/strong><\/h2>\n\n\n\n

Start by listing your interfaces:<\/p>\n\n\n\n

ip a<\/p>\n\n\n\n

You\u2019ll usually see something like eno1, enp9s0f0, or similar. The one with the smaller number is typically your public NIC. Make note of both interfaces that are connected to your public network \u2014 you\u2019ll need them for bonding. Identifying accurate NICs is essential for Debian network bonding configuration<\/strong>.<\/p>\n\n\n\n

Step 2: Bring Up a Temporary Network<\/strong><\/h2>\n\n\n\n

Before setting things up permanently, it\u2019s easier to create a temporary connection<\/strong> so you can install packages or fetch updates. Adjust interface names and IPs as needed for your server:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Once this is done, check if you can ping an external host (for example, 8.8.8.8). If that works, you\u2019re good to move on.<\/p>\n\n\n\n

Step 3: Update and Install Required Packages<\/strong><\/h2>\n\n\n\n

Next, refresh the package index and install a couple of tools that help with bonding:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

If this step fails, it\u2019s usually because the Debian repository URLs are outdated \u2014 that\u2019s common when working with older versions. This ensures tools like ifenslave<\/strong> required for Linux bonding setup<\/strong> work correctly.
<\/p>\n\n\n\n

Step 4: Fixing the Repository List (for Debian 10)<\/strong><\/h2>\n\n\n\n

Debian 10\u2019s repositories have moved to the archive servers. You\u2019ll need to point APT to those.
Open \/etc\/apt\/sources.list and replace the contents with:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Then run:<\/p>\n\n\n\n

apt update<\/p>\n\n\n\n

That should fix the issue and let you proceed with package installation.<\/p>\n\n\n\n

Step 5: Set Up the Bonding Configuration<\/strong><\/h2>\n\n\n\n

Now it\u2019s time to make the \u00a0bonding configuration<\/strong> permanent.
Edit the network configuration file:<\/p>\n\n\n\n

nano \/etc\/network\/interfaces<\/p>\n\n\n\n

Add or replace the content with:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Replace eno1<\/code> and eno2<\/code> with your actual interface names \u2014 check using ip a<\/code> if unsure.<\/p>\n\n\n\n

Step 6: Restart the Network<\/strong><\/h2>\n\n\n\n

To apply the configuration:<\/p>\n\n\n\n

systemctl restart network<\/p>\n\n\n\n

After restarting, your data center team will need to rebond the ports on the switch<\/strong>. Once they\u2019ve done that, the system should come back online with full internet access.
<\/p>\n\n\n\n

Step 7: Check SSH Settings<\/strong><\/h2>\n\n\n\n

If SSH isn\u2019t accessible, open \/etc\/ssh\/sshd_config<\/strong> and make sure this line is present (or uncommented):<\/p>\n\n\n\n

PermitRootLogin yes<\/p>\n\n\n\n

Then restart SSH:<\/p>\n\n\n\n

systemctl restart sshd && systemctl restart ssh<\/p>\n\n\n\n

Step 8: Verify Access and Reboot<\/strong><\/h2>\n\n\n\n

Try logging in via SSH:<\/p>\n\n\n\n

ssh root@your-server-ip<\/p>\n\n\n\n

If it connects, reboot the server once to confirm the changes persist:<\/p>\n\n\n\n

reboot<\/p>\n\n\n\n

After the reboot, your bonded interface (bond0<\/strong>) should be up and stable.<\/p>\n\n\n\n

Quick Recap<\/strong><\/h2>\n\n\n\n
Step<\/strong><\/td>Action<\/strong><\/td>Purpose<\/strong><\/td><\/tr>
1<\/td>Identify interfaces<\/td>Determine public NICs<\/td><\/tr>
2<\/td>Temporary setup<\/td>Enable short-term connectivity<\/td><\/tr>
3<\/td>Install tools<\/td>Add ifenslave and net-tools<\/td><\/tr>
4<\/td>Fix APT sources<\/td>Update repositories if needed<\/td><\/tr>
5<\/td>Configure bonding<\/a><\/td>Edit \/etc\/network\/interfaces<\/td><\/tr>
6<\/td>Restart & notify DC<\/td>Activate bonding on both ends<\/td><\/tr>
7<\/td>Enable SSH<\/td>Allow root login if blocked<\/td><\/tr>
8<\/td>Verify<\/td>Test connectivity and reboot<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

Final Thoughts<\/strong><\/h2>\n\n\n\n

Once you\u2019ve done this process a few times, it starts to feel pretty straightforward. The tricky part is just getting that temporary connection up long enough to install the right tools. After that, it\u2019s mostly about following the steps in the right order and making sure your data center rebonds the ports on their end.<\/p>\n\n\n\n

Bonding\u2019s a small task that makes a big difference. You get better uptime, load balancing, and peace of mind knowing your public network won\u2019t drop because of a single cable. We at SupportPRO<\/strong> <\/a>do this routinely for hosting providers worldwide, so if you\u2019d rather not wrestle with it yourself, we can take care of it anytime.This makes Debian network bonding<\/strong>, Linux server optimization<\/strong>, and high-availability networking<\/strong> much easier for your infrastructure.<\/p>\n\n\n\n

\n

Facing issues? <\/p>\n\n\n\n

Our technical support
engineers can solve it. <\/p>\n\n\n\n\"Contact<\/a><\/span>