Ethernet works not WiFi

Trojan Horse

Trojan Horse

Trojan Horse

Associate
Joined
27 Jul 2012
Posts
1,705
I'm trying to get my TP Link WR1043 router (bought a few day ago) to work as a wireless repeater. It is currently connected to my main TP Link WD-9980 through the Powerlink. The ethernet from modem to router is connected to the WR1043 blue WAN internet slot.

My ethernet cable from WR1043 to PC works but not my WiFi.

The WR1043 is currently bridging the main wifi but have tried to do it manually as a seperate SSID and pass and that doesn't work. It just connects and says limited connectivity and won't connect to either router or modem web page. My iPhone doesn't connect at all to the WR1043 it just says connecting forever.

This was happening on my old spare plusnet router so thought buying the TP link would fix it but it hasnt. What could be wrong?

Also sometimes on ethernet I have to reboot the Router so that the connection works.
 
I think your problem is the WR1043 is still set up as a router and not a bridge/ap.

If you're in the WAN socket and you are connecting LAN side of it then you will be handed an IP (as the router will be DHCP'ing and NAT'ing) and this will be the problem.

Set the WR1043 up with a LAN IP out of the DHCP range of the main router and connect to the LAN ports, not the WAN. Set wireless up as you like.
 
You need to connect the routers through the LAN ports on both routers. Turn DHCP off on one router. You need to setup your DHCP pool range say 192.168.1.2 - 192.168.1.252 and have the second routers ip address outside of that range so say 192.168.1.253. Then make sure the channels don't clash so have them either 1,5,11.
 
Steveocee said:
Something still sounds wrong. It may work but is it working as well as it should or in the right way?
Click to expand...

Yep it broke after like an hour. I did it properly via LAN port not WAN and used a seperate DHCP range. Seems to work great. :)

Only problem is now I cannot access second router IP even though I set it to something different to original router. I am using an app on my phone called Fing to scan and find local IP of devices but I have only 1 ip for my router and the second one has been wiped off the mark?
 
Assuming you do have a wired connection to the second router (even if it is a Powerline connection)...

According to TP-Link's website there isn't a dedicated AP mode so it needs to be done manually.

  1. Set the second router's management IP to match your subnet. Choose a value that isn't in the primary router's DHCP range.
  2. Disable the second router's DHCP server. The primary router will handle this.
  3. Configure the wireless settings; this will usually be identical to the primary router except for the wireless channel.
  4. Connect the two routers together LAN-to-LAN.
 
Really you want 1 big IP range rather than one for your main router and one for the second.

If you main router is 192.168.1.1 and it gives out 1.50-1.254 on DHCP, set your second router to 1.2, turn off its DHCP and firewall and give it a default gateway of 1.1 (adjust these ips to suit you)

You're then creating 1 big LAN rather than a 2 tiered LAN which isn't needed.
 
Steveocee said:
Really you want 1 big IP range rather than one for your main router and one for the second.

If you main router is 192.168.1.1 and it gives out 1.50-1.254 on DHCP, set your second router to 1.2, turn off its DHCP and firewall and give it a default gateway of 1.1 (adjust these ips to suit you)

You're then creating 1 big LAN rather than a 2 tiered LAN which isn't needed.
Click to expand...

Right now it works as it is 192.168.1.1-.50

second router is .51-199

dont need to fath about as doubt i will ever get as many as 20 clients on it. it works if it doesnt ill change something but for now i am satisfied hahha
 
You've asked for advice, people are giving you it, and you're ignoring it.

You've already "got it working" once before then came back 2 hours later saying something messed up.

Again, what you've "got working" is an overly complicated network configuration that could result in confusing complications down the line.

It really sounds like you're only missing one step, and that's disabling the DHCP server on your WR1043 - it doesn't need to be there.
 
RoyMi6 said:
You've asked for advice, people are giving you it, and you're ignoring it.

You've already "got it working" once before then came back 2 hours later saying something messed up.

Again, what you've "got working" is an overly complicated network configuration that could result in confusing complications down the line.

It really sounds like you're only missing one step, and that's disabling the DHCP server on your WR1043 - it doesn't need to be there.
Click to expand...

cool
 
I agree with the post above you only need DHCP on one router. Having two doing with just cause clashes between them and most likely drop outs of service. Turn it off on the second router and make sure wifi channels are at least 5 apart.
 
You must log in or register to reply here.
Back
Top Bottom