F5F Stay Refreshed Power Users Networks Yes, you can configure your router to act as an expander or bridge for another device.

Yes, you can configure your router to act as an expander or bridge for another device.

Yes, you can configure your router to act as an expander or bridge for another device.

A
awincent
Junior Member
24
08-09-2016, 06:40 AM
#1
Hi, I have a TP-Link Archer C5 as my main router at home, and an ASUS DSL-AC55U connected right after it in my room. The TP-Link gives weak 5GHz signal on my side, so I’m using it for internet. My phone, smart TV, printer, and dad’s PC (which will become a NAS) are all wired to the TP-Link via Ethernet. I’m wondering if it’s possible to merge these two routers into one network and still access the wired devices from both simultaneously.
A
awincent
08-09-2016, 06:40 AM #1

Hi, I have a TP-Link Archer C5 as my main router at home, and an ASUS DSL-AC55U connected right after it in my room. The TP-Link gives weak 5GHz signal on my side, so I’m using it for internet. My phone, smart TV, printer, and dad’s PC (which will become a NAS) are all wired to the TP-Link via Ethernet. I’m wondering if it’s possible to merge these two routers into one network and still access the wired devices from both simultaneously.

Q
Qandii
Member
233
08-27-2016, 12:58 PM
#2
You can't really set up a single SSID easily as they won't work in tandem. Best to have two separate wifi networks. On the Asus, turn its DHCP server off and give it an IP address one higher than the TP-Link (or lower if the TP-Link is .254) so that it doesn't clash but you can still talk to it. (you might want to talk to it to manage its wifi access list or something) What then happens is that your PC and phone connect to the Asus, but it just passes through the DHCP requests. The TP-Link responds with IP addresses and advertises itself as the next hop to the outside world.
Q
Qandii
08-27-2016, 12:58 PM #2

You can't really set up a single SSID easily as they won't work in tandem. Best to have two separate wifi networks. On the Asus, turn its DHCP server off and give it an IP address one higher than the TP-Link (or lower if the TP-Link is .254) so that it doesn't clash but you can still talk to it. (you might want to talk to it to manage its wifi access list or something) What then happens is that your PC and phone connect to the Asus, but it just passes through the DHCP requests. The TP-Link responds with IP addresses and advertises itself as the next hop to the outside world.

S
SoloElite
Junior Member
5
08-29-2016, 03:43 AM
#3
Hey! Thanks for your helpful advice. There seems to be a bit of a problem. Even though the DHCP on ASUS is turned off and it has a static IP from TP-Link, ASUS still creates its own subnet. As a result, devices linked to ASUS appear in the TP-Link console with IPs from TP-Link, but my Windows PC can't locate the TP-Link devices and the Sonos speaker isn't showing up on my phone. My main goals are: 1) Get access to the storage on my dad's PC, 2) Connect the network printer on my PC to TP-Link, and 3) Improve Wi-Fi coverage in my living area. Goal 1 and 2 can be solved by connecting the upstream cable to ASUS and using it as a switch. Goal 3 is more challenging since both routers support WDS Bridge and static routing—could that help? I'm also considering replacing ASUS with TP-Link, which is newer and has a 5GHz antenna. I'll look into it tomorrow.
S
SoloElite
08-29-2016, 03:43 AM #3

Hey! Thanks for your helpful advice. There seems to be a bit of a problem. Even though the DHCP on ASUS is turned off and it has a static IP from TP-Link, ASUS still creates its own subnet. As a result, devices linked to ASUS appear in the TP-Link console with IPs from TP-Link, but my Windows PC can't locate the TP-Link devices and the Sonos speaker isn't showing up on my phone. My main goals are: 1) Get access to the storage on my dad's PC, 2) Connect the network printer on my PC to TP-Link, and 3) Improve Wi-Fi coverage in my living area. Goal 1 and 2 can be solved by connecting the upstream cable to ASUS and using it as a switch. Goal 3 is more challenging since both routers support WDS Bridge and static routing—could that help? I'm also considering replacing ASUS with TP-Link, which is newer and has a 5GHz antenna. I'll look into it tomorrow.

K
KylianMaas
Junior Member
4
08-29-2016, 04:09 AM
#4
You've got the trick here that you're physically connecting the units by cable, so I'm not sure whether trying to engage WDS bridge might cause an issue unless you pull the cable. I've never used it personally. The Sonos not showing up on the phone would make me investigate whether there is a DMZ at play. Particularly when using a guest network, routers automatically forbid wi-fi devices from seeing anything other than the internet. You say that the Asus has a static IP from the TP-Link? Static is programmed directly into the unit itself... unless you've made a DHCP reservation for the Asus via MAC address or something. It sounds as if the Asus is still not configured quite right. Ideally, the aim is to get the Asus to be as dumb as possible, with its own SSID, so as far as the TP-Link is concerned, any device connected via the Asus appears to be a LAN device. Try the usual ping and traceroute to see what's happening to the packets. Apologies, but it sounds like there's a configuration issue going on, that I'd only be able to work out if I was there with you. Otherwise I'm reduced to rough guessing.
K
KylianMaas
08-29-2016, 04:09 AM #4

You've got the trick here that you're physically connecting the units by cable, so I'm not sure whether trying to engage WDS bridge might cause an issue unless you pull the cable. I've never used it personally. The Sonos not showing up on the phone would make me investigate whether there is a DMZ at play. Particularly when using a guest network, routers automatically forbid wi-fi devices from seeing anything other than the internet. You say that the Asus has a static IP from the TP-Link? Static is programmed directly into the unit itself... unless you've made a DHCP reservation for the Asus via MAC address or something. It sounds as if the Asus is still not configured quite right. Ideally, the aim is to get the Asus to be as dumb as possible, with its own SSID, so as far as the TP-Link is concerned, any device connected via the Asus appears to be a LAN device. Try the usual ping and traceroute to see what's happening to the packets. Apologies, but it sounds like there's a configuration issue going on, that I'd only be able to work out if I was there with you. Otherwise I'm reduced to rough guessing.

M
Mini_Knight
Junior Member
20
08-29-2016, 05:15 AM
#5
Just a brief reminder... I assume you're linking the TP-Link to one of the yellow network ports? If it's connected to the blue port, that could cause issues since the blue port on the Asus is a WAN port, and the Asus might treat the TP-Link as a WAN device needing routing. Make sure both your PC and the TP-Link are on the yellow network ports on the Asus.
M
Mini_Knight
08-29-2016, 05:15 AM #5

Just a brief reminder... I assume you're linking the TP-Link to one of the yellow network ports? If it's connected to the blue port, that could cause issues since the blue port on the Asus is a WAN port, and the Asus might treat the TP-Link as a WAN device needing routing. Make sure both your PC and the TP-Link are on the yellow network ports on the Asus.

S
soldier_craft
Member
242
08-29-2016, 09:45 AM
#6
Explanation of the port and WAN situation. If the TP-Link is linked to the blue WAN port, the Asus functions as a firewall between the devices, believing the TP-Link is the internet. This behavior creates issues. When the TP-Link connects to the yellow port, it operates as a flat network, allowing everything to communicate freely without the Asus firewall obstructing the connection.
S
soldier_craft
08-29-2016, 09:45 AM #6

Explanation of the port and WAN situation. If the TP-Link is linked to the blue WAN port, the Asus functions as a firewall between the devices, believing the TP-Link is the internet. This behavior creates issues. When the TP-Link connects to the yellow port, it operates as a flat network, allowing everything to communicate freely without the Asus firewall obstructing the connection.

M
MeggaFAGG0T
Member
58
08-31-2016, 10:18 AM
#7
This setup shows how devices connect: Internet → wired adapter → TP-Link → ASUS → PC. If WDS is enabled, it lets you share the same network name across all devices and let them communicate. If not, check your Sonos and phone IP addresses to see if your PC can reach them.
M
MeggaFAGG0T
08-31-2016, 10:18 AM #7

This setup shows how devices connect: Internet → wired adapter → TP-Link → ASUS → PC. If WDS is enabled, it lets you share the same network name across all devices and let them communicate. If not, check your Sonos and phone IP addresses to see if your PC can reach them.

T
tacgun
Member
70
08-31-2016, 03:56 PM
#8
Since your ASUS is wired, WDS isn't necessary. It connects two WiFi links when they aren't linked by a physical cable. The ASUS shouldn't be able to create its own network if the DHCP Server is turned off. You might have accidentally disabled the DHCP Client. Make sure to turn off the DHCP Server, ensure the main router connection uses an ASUS LAN port, and stick with a dedicated SSID for your ASUS so you can identify the network your devices connect to. Most devices struggle with roaming and may get stuck on the strongest signal initially.
T
tacgun
08-31-2016, 03:56 PM #8

Since your ASUS is wired, WDS isn't necessary. It connects two WiFi links when they aren't linked by a physical cable. The ASUS shouldn't be able to create its own network if the DHCP Server is turned off. You might have accidentally disabled the DHCP Client. Make sure to turn off the DHCP Server, ensure the main router connection uses an ASUS LAN port, and stick with a dedicated SSID for your ASUS so you can identify the network your devices connect to. Most devices struggle with roaming and may get stuck on the strongest signal initially.

B
Back2Blaze
Member
204
09-01-2016, 09:51 PM
#9
The setup doesn<|pad|>'s mention no Ethernet connection between the routers, which explains why we need to confirm the network layout. To prevent the ASUS from creating its own network, it should operate in bridge mode. Turning off DHCP might enable this behavior. If not in bridge mode, DHCP requests could fail, leaving new devices without IP addresses. For consistency, ensure the ASUS and TP-Link share the same network segment—either assign static IPs per port or allow the TP-Link to assign DHCP addresses and add them to reservations. Using separate SSIDs helps guarantee you connect to the intended device.
B
Back2Blaze
09-01-2016, 09:51 PM #9

The setup doesn<|pad|>'s mention no Ethernet connection between the routers, which explains why we need to confirm the network layout. To prevent the ASUS from creating its own network, it should operate in bridge mode. Turning off DHCP might enable this behavior. If not in bridge mode, DHCP requests could fail, leaving new devices without IP addresses. For consistency, ensure the ASUS and TP-Link share the same network segment—either assign static IPs per port or allow the TP-Link to assign DHCP addresses and add them to reservations. Using separate SSIDs helps guarantee you connect to the intended device.

W
WhiteLimon
Junior Member
38
09-02-2016, 12:27 AM
#10
Thanks for your feedback. I value all the suggestions you shared. The configuration seemed to follow a straightforward path, but my expectations were unclear. I was assuming the WDS mode would enhance the ASUS's capabilities, yet I realized it might require more precise setup on the TP-Link side. My initial thought about disabling the firewall was misguided; I should have focused more on network adjustments.

During the process, I encountered issues with SSID bridging and WPA2 compatibility. The TP-Link's DHCP server was disabled, which affected connectivity. I ended up testing the setup in my bedroom and noticed mixed results—5GHz devices worked well, while wired connections struggled. The lack of guest networks and the discrete bands added complexity.

I’m considering whether the 5GHz signal in my room is the main hurdle. If that’s the case, upgrading to a different router might be necessary. I’m also curious about DHCP reservations and whether they can resolve the connectivity problems. Overall, it’s been a challenging but informative experience.
W
WhiteLimon
09-02-2016, 12:27 AM #10

Thanks for your feedback. I value all the suggestions you shared. The configuration seemed to follow a straightforward path, but my expectations were unclear. I was assuming the WDS mode would enhance the ASUS's capabilities, yet I realized it might require more precise setup on the TP-Link side. My initial thought about disabling the firewall was misguided; I should have focused more on network adjustments.

During the process, I encountered issues with SSID bridging and WPA2 compatibility. The TP-Link's DHCP server was disabled, which affected connectivity. I ended up testing the setup in my bedroom and noticed mixed results—5GHz devices worked well, while wired connections struggled. The lack of guest networks and the discrete bands added complexity.

I’m considering whether the 5GHz signal in my room is the main hurdle. If that’s the case, upgrading to a different router might be necessary. I’m also curious about DHCP reservations and whether they can resolve the connectivity problems. Overall, it’s been a challenging but informative experience.