Router to Switch With Access Point

it sounds like you want to configure the TP-Link in Client mode

Hi, thanks for trying to help. I have tried every mode including client mode. Not a single mode allows you to access the wi-fi key of the router. If you scan it will pick up the BT router but doesn't give an option to enter the wi-fi key. I've come to the conclusion of it just being a cheap access point. One of the images on the TP-Link box shows the access point plugged into a game console for wireless mode. But I Can't even see how that will work as you cant connect to the router.
Thanks for trying to help though, it's much appreciated.


Regards,
KCorbishley

If I understood the manual right, you select Client Mode, click SSID, and then Search. Select you wireless network and hit Save.

After rebooting it seems you go to Security and enter the password key for the wifi

I would assume if you used the search option on that same page, you would be given the opportunity to specify the security settings.

A word of caution is in order. This device is using WDS, NOT universal bridging. Universal bridging relies on wifi certified protocols (B/G/N) to establish the link between the bridge and the remote AP (just like the wireless USB/PCI adapter in your desktop/laptop). Because WDS is not a wifi standard, incompatibilities are very common. As a general rule, your best hope for having WDS work is to make sure you use hardware from the same manufacturer. Even then, manufacturers have been known to change their implementations and create their own incompatibilities. For these reasons, WDS has fallen out of favor over the years and “universal” bridging has become much more prevalent.

The TL-WA701ND manual is very misleading in this regarding. It uses terminology like “universal repeater”, WDS enabled/disabled, etc., when in fact, you’re ALWAYS using WDS. To understand why requires a minor lesson in WDS.

The most common WDS difference (leading to incompatibility, but not necessarily the only one) is the addressing in the WDS header. The WDS header contains several addresses relevant to WLAN and ethernet frames (it’s these addresses that allow the APs to communicate and pass ethernet frames). Again, WDS isn’t a wifi standard, so to even talk of a standard or correct implementation is a misnomer. So let’s talk in terms of behavior. It’s generally agreed that a “well behaved” WDS implementation uses four (4) address fields in the WDS header. Some “less well behaved” WDS implementations only use three (3) address fields (the developers recognized that one of the addresses wasn’t absolutely necessary for WDS to work, so they eliminated it… that’s what happens when you don’t have standards!).

So what’s this all mean? When configuring your client (or repeater) bridge, you’ll notice that you have the option to enabled or disabled WDS. This is misleading. You’re ALWAYS using WDS. When WDS is enabled, it just means they’ll use the “four (4) addresses” implementation. But if WDS is disabled, they’ll use the “three (3) addresses” implementation. In either case, it’s still WDS. What makes it “universal” in the minds of TP-Link engineers is the assumption that this is the only possible incompatibility, and if you simply try one or the other, WDS will work w/ any other WDS enabled device, even those from other manufacturers.

And there’s the rub. As long as you have no standards, the possibility of other incompatibilities remains. Some may be so subtle that you might not notice it immediately. You may get connected initially, but then have dropped or otherwise unreliable connections.

For these reasons, I always worry when someone is relying on WDS. It can lead to endless headaches, esp. across manufacturers. Don’t be surprised if it still doesn’t work, even if you get past the wireless security issue. TP-Link seems to be one of the few manufacturers that have attempted to address this problem by creating what is more properly termed “universal WDS”. The only time I recommend WDS is when you know w/ 100% certainty that it’s compatible (e.g., same device (ideal), same manufacturer, same third-party firmware (dd-wrt, tomato, etc.)).