TP-Link Repeater Problem
 

Evening all,

Recently had virgin media installed, and the superhub does not cover the entire house so bought the TL-WA701ND.

I want to use this in universal repeater mode so that the rooms at the back of the house can access the superhub.

I installed this, and after a day of fiddling with settings thought I had it connected.

192.168.0.1 is superhub

192.168.0.254 is TP-Link

However, the TP-link keeps dropping signal and when digging the superhub is registering the ip address of the TP-Link as the same as my laptop.

The superhub has DHCP active and the TP-Link has it deactive.

Any assistance would be great as the family are getting annoyed at constant internet outages!

Re: TP-Link Repeater Problem
 

I also changed the IP address range in the superhub to 192.168.0.2 to 192.168.0.200 as someone suggested that the static ip of the repeater should be OUTSIDE of this range. Is this correct? Even so the repeater still had the same ip as my laptop. Is this normal??

Re: TP-Link Repeater Problem
 

IMO you would be better off putting the superhub in modem mode and connecting a proper wireless router. Is it too late to return your access point in exchange for a router?

The superhub is well known for it's wireless shortcomings.

Re: TP-Link Repeater Problem
 

I am not able to change the hardware.

Is there noone that can help?

Re: TP-Link Repeater Problem
 

Added screenshot
http://i218.photobucket.com/albums/c...r/6e86dbf7.png

This shows that I have reserved an ip address for the repeater, yet it still uses another one, which happens to be the same as mine.

---------- Post added at 20:20 ---------- Previous post was at 20:04 ----------

http://i218.photobucket.com/albums/c...r/67cb27fe.png

Re: TP-Link Repeater Problem
 

Personally, I'd set the static IP address in the TP-Link web interface rather than relying on the Superhub's DHCP to dish it out the correct address. Would certainly work around the issue.

Paul

Re: TP-Link Repeater Problem
 

Certainly doesn't work around the issue as that is how it was setup in the first place which led to the problems I am now getting.

Re: TP-Link Repeater Problem
 

I have the TL-WA901N and I'm using that configured statically, not with a superhub but it does work. Are you using the LAN or using the WDS?

Re: TP-Link Repeater Problem
 

It is wireless

Re: TP-Link Repeater Problem
 

Have you updated the firmware? If it's a V1 then you can get the firmware here, looks like there have been some issues with the repeater mode. Updating to the latest firmware may resolve your issue.

Paul

Re: TP-Link Repeater Problem
 

Firmware is 3.12.6 Build 110210 Rel.37112n

Re: TP-Link Repeater Problem
 

Can you post the config screens from the access point? Ideally the Wireless -> Wireless Settings, Wireless->Wireless Security and Network pages. Would also be useful to see the wireless settings from the Superhub. Have you tried it with encryption turned off just in case?

Re: TP-Link Repeater Problem
 

I tried installing an older firmware to see if that worked and now I cannot access the ap at all.

---------- Post added at 15:10 ---------- Previous post was at 13:41 ----------

http://i218.photobucket.com/albums/c...r/9f4abcb6.png

http://i218.photobucket.com/albums/c...r/22aebad3.png

http://i218.photobucket.com/albums/c...r/71055119.png

Re: TP-Link Repeater Problem
 

Not a huge issue but the Gateway on the repeater should be set to 192.168.0.1 (i.e. the Superhub). You also need to ensure that the encryption settings are identical on both the Superhub and the repeater. Does it see the Superhub's SSID when you click survey?

Re: TP-Link Repeater Problem
 

It has produced the same results with both gateway entries.

The encryption settings are identical.

And yes it does see the superhubs SSID and the mac address is shown in the above screenshot.

Re: TP-Link Repeater Problem
 

It says in the info page that if you select Dynamic IP the DHCP server in the repeater will not run. As you are seeing two devices with the same IP it means you must have two DHCP servers running. Change type to Dynamic and see if that fixes things up.

Don't get confused between the GUI IP for configuring it and the IP it is operating on in your Superhub subnet - I think (but don't know) that they are probably different and probably will not even be in the same subnet.