A bridged connection lets two networks act like one, so devices on different networks can talk to each other as if they're on the same wire
When you bridge a connection, you're creating a single logical network from two separate physical networks. The bridge device — usually your router or a computer running bridge software — sits between the two networks and forwards traffic between them. Devices on one side see devices on the other side as local neighbors, not as distant computers on the internet.
This is different from a standard router setup, where the router separates networks and controls what passes between them. A bridge is transparent: it doesn't change addresses, doesn't filter traffic the way a router does, and doesn't create a boundary. If you have a wired network in one room and a wired network in another, bridging them makes them function as a single network.
Key Takeaways
- A bridge connects two separate networks so devices on each side can communicate directly without a router translating between them.
- Bridging is useful when you have two wired segments in different locations and want them to behave as one continuous network.
- Most home setups do not need bridging; a standard router handles network separation and connection adequately.
- Bridging requires either a dedicated bridge device or bridge software running on a computer, and both networks must use the same protocol and address scheme.
How a bridge differs from a router
A router creates a boundary between networks. It has an inside (LAN) and an outside (WAN), and it translates addresses so devices on the inside can reach the outside. A bridge has no inside or outside — it straightforward extends the network.
When your computer sends a packet to a printer on a routed network, the router rewrites the packet's address information so the printer knows where to send the reply. On a bridged network, the packet travels unchanged. The printer sees the computer's real address and replies directly. This matters for certain older protocols and for devices that expect to be on the same physical segment.
Routers also filter traffic by default: they block incoming connections unless you set up port forwarding. Bridges do not filter. Everything on one side can reach everything on the other side, which is why bridges are rarely used on networks that connect to the internet.
When you actually need a bridge
Most home and small office networks do not need bridging. A single router with multiple wired ports or a combination of wired and wireless devices works fine for typical use.
You might need a bridge if you have two separate wired network segments in different parts of a building and you want them to function as one. For example, if you have network equipment in a basement and network equipment in an upstairs closet, and you want devices in both locations to see each other without going through a router, a bridge connects them. The bridge device sits between the two segments and forwards frames (the raw data packets) between them.
Bridging also appears in some specialized setups: connecting two office buildings with a dedicated fiber line, extending a network through a wireless link (wireless bridge), or combining multiple network segments in a data center. These are not typical home scenarios.
How to set up a bridge with hardware
A hardware bridge is a device with at least two network ports. You connect one port to the first network segment and the other port to the second segment. The bridge learns which devices are on each side and forwards traffic between them.
Most modern routers can operate in bridge mode. You would connect the router's WAN port to your main network and its LAN ports to the segment you want to extend. The router then forwards traffic between the two without creating a separate network. Check your router's manual for bridge mode settings — the exact steps vary by manufacturer.
Some network switches can also bridge, though this is less common in consumer equipment. Enterprise-grade switches often have bridging built in. If you need a dedicated bridge device and do not have one, you can use an old computer with two network cards and bridge software, though this is uncommon in modern setups.
How to set up a bridge with software
Windows, macOS, and Linux all support software bridging. You run bridge software on a computer with at least two network connections — typically one wired port and one wireless port, or two wired ports.
On Windows, you can bridge connections through the Network Connections control panel. Select the two connections you want to bridge, right-click, and choose "Bridge Connections." Windows then treats them as a single network. On macOS, you use System Preferences > Network and configure bridge settings there. On Linux, you use command-line tools like brctl or network configuration files, depending on your distribution.
Software bridging works, but it ties up a computer to do the job. That computer must stay powered on and connected for the bridge to function. For most situations, a hardware bridge or a router in bridge mode is simpler and more reliable.
Bridging and IP addresses
On a bridged network, all devices share the same IP address range. If your main network uses 192.168.1.0 to 192.168.1.255, devices on the bridged segment also use that same range. There is no separate subnet.
This is why bridging only works when both segments use the same protocol (both IPv4 or both IPv6) and the same address scheme. If one segment uses 192.168.1.0 and the other uses 10.0.0.0, you cannot bridge them — you would need a router to translate between the two.
When you set up a bridge, make sure your DHCP server (the device that assigns IP addresses) is configured to serve the entire bridged network. If you have two separate DHCP servers, one on each segment, they will conflict. Usually, you keep one DHCP server and let it serve both sides of the bridge.
Security considerations with bridges
Because a bridge does not filter traffic, it offers no protection between the two segments it connects. Any device on one side can reach any device on the other side without restriction. If one segment is compromised, the other is when ready exposed.
For this reason, bridges are not used to connect networks with different security requirements. You would never bridge a guest network to your main network, or bridge an untrusted segment to a trusted one. Use a router with firewall rules instead.
If you are bridging two segments within your own network — say, two parts of your office — this is usually acceptable. But if either segment connects to the internet or to an untrusted network, do not bridge. Use a router to maintain a security boundary.
Frequently Asked Questions
Can I bridge a wired network and a wireless network?
Yes. A wireless bridge device connects to your wired network on one side and broadcasts a wireless signal on the other. Devices connect to the wireless side and appear on the wired network. This is common for extending a network to areas where running cable is difficult.
What happens if I bridge two networks with different IP ranges?
The bridge will not work as intended. Devices on one side will not be able to reach devices on the other side because they are on different subnets. You need a router to translate between different IP ranges, not a bridge.
Is bridging the same as creating a mesh network?
No. A mesh network uses wireless repeaters that talk to each other to extend coverage. A bridge connects two separate networks. They serve different purposes and use different technology.
Can I use a bridge to connect my home network to the internet?
No. A bridge does not provide internet access or security filtering. You need a router to connect to the internet. A bridge only connects two local networks to each other.
Do I lose speed when I use a bridge?
A hardware bridge adds minimal delay. A software bridge running on a computer may reduce speed slightly because the computer has to process every packet. For most uses, the difference is not noticeable, but a dedicated hardware bridge is faster.