Step‑by‑Step Ethernet Bridge Configuration Tool Tutorial (Windows & Linux)

This tutorial walks through configuring an Ethernet bridge on both Windows and Linux using common tools. It assumes you want to link two or more network interfaces so devices on each interface share a single broadcast domain (useful for VMs, network segmentation, or extending LAN segments). Steps include preparing interfaces, creating the bridge, assigning IP settings, and testing connectivity.

Prerequisites

• Administrator (Windows) or root/sudo access (Linux).
• Two or more Ethernet interfaces available and not managed by other services.
• Backup of current network settings (so you can revert if needed).

Linux: Create an Ethernet Bridge (using iproute2 / networkd / NetworkManager)

These instructions use iproute2 and systemd-networkd where noted. Adjust for your distro (Debian/Ubuntu, CentOS/RHEL, Fedora).

1) Identify interfaces

1. List interfaces:

   Code
   Copy CodeCopied
   ip link show 

2. Note interface names to bridge (e.g., eth0, eth1 or enp3s0, enp4s0).

2) Stop services that manage interfaces (if needed)

• If NetworkManager or other network services auto-manage interfaces, either use their configuration method or temporarily bring interfaces down:

  Code
  Copy CodeCopied
  sudo nmcli device set eth0 managed no sudo nmcli device set eth1 managed no sudo ip link set eth0 down sudo ip link set eth1 down 

3) Create the bridge and add interfaces

1. Create bridge:

   Code
   Copy CodeCopied
   sudo ip link add name br0 type bridge 

2. Add member interfaces:

   Code
   Copy CodeCopied
   sudo ip link set eth0 master br0 sudo ip link set eth1 master br0 

3. Bring up bridge and member interfaces:

   Code
   Copy CodeCopied
   sudo ip link set br0 up sudo ip link set eth0 up sudo ip link set eth1 up 

4) Assign IP to bridge

• For DHCP:

  Code
  Copy CodeCopied
  sudo dhclient br0 

• For static IPv4:

  Code
  Copy CodeCopied
  sudo ip addr add 192.168.1.⁄24 dev br0 sudo ip route add default via 192.168.1.1 

5) Persist configuration

• systemd-networkd example:

  • /etc/systemd/network/10-br0.netdev

    Code
    Copy CodeCopied
    [NetDev] Name=br0 Kind=bridge 

  • /etc/systemd/network/10-br0.network

    Code
    Copy CodeCopied
    [Match] Name=br0[Network] DHCP=yes 

  • /etc/systemd/network/10-eth0.network and 10-eth1.network set to:

    Code
    Copy CodeCopied
    [Match] Name=eth0
    
     
    [Network] Bridge=br0 

  • Restart:

    Code
    Copy CodeCopied
    sudo systemctl restart systemd-networkd 

• NetworkManager: use nmcli or GUI to create a bridge connection, add slave interfaces, and set IPv4 settings.

6) Verify

Code
Copy CodeCopied
bridge link ip addr show br0 ip route ping -c 3 8.8.8.8 

Windows: Create an Ethernet Bridge (GUI and PowerShell)

Windows can create a network bridge in the GUI or via PowerShell (Windows ⁄₁₁ / Server).

1) Prepare interfaces

• Ensure Ethernet adapters are enabled and not used for other special services (Internet Connection Sharing, Hyper-V virtual switch).

2) GUI method

1. Open Control Panel > Network and Internet > Network Connections (or run ncpa.cpl).
2. Select two or more network adapters (Ctrl+click).
3. Right-click one selection and choose “Bridge Connections”.
4. Windows creates “Network Bridge”. Set IPv4/IPv6 on the bridge adapter by right-clicking it > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties.

3) PowerShell method

• Create bridge using WMI (requires administrative privileges):

  Code
  Copy CodeCopied
  # List adapters Get-NetAdapter
  
   
  Example: create bridge using New-NetSwitchTeam isn’t for bridging; Windows lacks a direct native cmdlet for bridging.
   
  Use PowerShell to invoke WMI:
   
  \(adapters = Get-WmiObject -Class Win32_NetworkAdapter | Where-Object { \).NetEnabled -eq \(true -and (\).Name -match ‘Ethernet’) }
   
  Select specific adapters by Index or Name, then:
   
  $bridge = (Get-WmiObject -List Win32NetworkAdapter).CreateBridge() # Note: CreateBridge() may not be present; fallback to GUI for reliability. 

• Practical note: GUI is the most reliable built-in method for consumer Windows. For servers, consider Hyper-V virtual switches or third-party tools.

4) Configure IP on bridge

• After creation, open bridge adapter properties and set DHCP or static IP as needed.

5) Verify

• In PowerShell:

  Code
   ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
  Get-NetAdapter -Name “Network Bridge” Get-NetIPConfiguration -InterfaceAlias “Network Bridge” Test-NetConnection -ComputerName 8.8.8.8 

Troubleshooting

• No connectivity: ensure member NICs are up and not blocked by drivers or VLAN settings.
• Duplicate IPs: assign IP only to bridge, not to member interfaces.
• Windows bridge missing option: adapter drivers or services (like ICS) may prevent bridging; disable conflicting features.
• Virtualization: if using Hyper-V or other hypervisors, use virtual switch features instead of a host bridge.

Security and Best Practices

• Avoid bridging interfaces that connect to untrusted networks without firewalling.
• Keep firmware and drivers updated.
• For predictable behavior, manage bridging through your system’s network manager rather than ad-hoc ip commands for persistent setups.

Quick checklist

1. Identify interfaces.
2. Stop auto-management if needed.
3. Create bridge and add interfaces.
4. Assign IP to bridge.
5. Persist configuration across reboots.
6. Test connectivity.

If you want, I can produce distro-specific config files (Debian/Ubuntu netplan, CentOS NetworkManager keyfiles) or a PowerShell script for a specific Windows version.