• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WAP Configure

Status
Not open for further replies.
I have an ethernet port in my loft where wifi is not so great. I'm looking to create a WAP using a

TP Link WA801ND

Maybe I've looked at too many tutorials on how to best achieve this, but now find myself confused.

I want simply to improve wifi in my loft so it's similar to what I get closer to my Plusnet Hup One router on the ground floor.

I don't want a new network, just to extend my existing plusnet wifi reach to the loft.

Should I be setting TP Link as a WAP or Client mode? I've seen configs for both.

Can it be that house wandering users will automatically change to the strongest signal source depending where they are in the property?

Bit lost with all the various settings and options etc.

I imagine this is quite straight forward to somebody with networking knowledge, but that's not my strong point.

Any help and /or advice gratefully appreciated.

Dave
 
you already have an Ethernet port in the loft, which is a great start.
assuming that port goes down to the ground floor router, plug the TP-Link into that ethernet port using the PoE port on the back of it and set it up as a WAP.
you could then either create a new wireless network name and password, or create one with the same name and password as already in use downstairs. meshing the two networks together would give you a seamless connection as people move around.

or you could not wire it up and instead go through the setup wizard and have it search for your current wifi network and extend it that way. but you need to be well within the current wifi radius coverage and it sounds like you aren't.
 
Thanks for the options. I won't use PoE, I'll use the included power adaptor. Ethernet port does arrive at router via a switch. Does it make any difference whether it's connected to the switch or is it best to connect directly to router ports?
The second option you mention implies the TP Link would search for an existing wifi signal and extend it that way. Wouldn't that be a weaker path and be the same as inefficient wifi extender / repeater packages? In the loft I receive about 60% of the signal received on the ground floor where the router is. I'm hoping to achieve much the same signal strength in loft with WAP.
 
switch is fine. in dummy terms, think of a switch like a double adapter for a power cord.
yes, my second option is not my personal preference, but an option none the less.
as to signal strength, don't forget, devices connected to the WAP will probably get high %'s, like >90 as it's the signal from those devices to the WAP being shown. the second option replies on the strength between the WAP and the router's wireless network - and that's the Achilles' heal in that option.
 
switch is fine. in dummy terms, think of a switch like a double adapter for a power cord.
yes, my second option is not my personal preference, but an option none the less.
as to signal strength, don't forget, devices connected to the WAP will probably get high %'s, like >90 as it's the signal from those devices to the WAP being shown. the second option replies on the strength between the WAP and the router's wireless network - and that's the Achilles' heal in that option.
Yes, definitely option one. Haven't received the WAP unit yet, just trying to plan ahead. When I get it up and running I'll let you know how it goes. I dare say there'll be some more configuration questions. Thanks again for your advice.
 
there will be no more questions.
you'll plug it in, run the setup wizard, it'll do all the heavy lifting and POW, you'll have your new wifi network upstairs.
that's the theory anyway - and things always follow that path don't they?! :)
 
there will be no more questions.
you'll plug it in, run the setup wizard, it'll do all the heavy lifting and POW, you'll have your new wifi network upstairs.
that's the theory anyway - and things always follow that path don't they?! :)
This is the case for some I read. If so, you'll be amongst the first to know. I admire your optimism.
 
Thought you might be mildly interested how it all went. Firstly, updated firmware on AP which was a faf given that TP Link's fw update is in a global mess - chat with tech support pointed me to the latest stable fw. Couldn't decide whether to use same ssid and security or create a second ssid for loft. A helpful youtube vid looked at both scenarios and I opted for the double ssid meaning roamers would have to change connection depending on where they were in the property. At least they'd know which one they were connected to and change if required. My only issue is that I can't access the AP config page using the AP ip.
It all works apart from this, I'm a bit lost with the ip assigning question re static and dynamic. andip address ranges etc. I'm sure it could be fine tuned. All in all though, not a bad day's work for a network novice.
 
depending on how you set it up, the IP of the new TP-Link should still be the advertised one it came with.

so if downstairs is on say the IP range of 10.1.1.nnn and the new upstairs router is 192.168.0.nnn then devices connected to downstairs will get 10.1.1.nnn addresses and the TP-Link will issue 192.168.0.nnn ones.

what error do you get when you try to type in the TP-Links address into a browser?
 
Thanks for your comments. That's what I need, very simple stuff - this is not my thing by some way.
If I try accessing TP link unit using its default ip address of 192.168.0.254 I receive a "timed out" and "cannot reach" browser message.
My main router can still be accessed by it's default ip of 192.168.1.254
These two IPs are very close it would seem - do I need to make changes.
Both SSIDs are both working, as I mentioned, but no access to TP unit.
 
bottom line, if it's working, let it be.
but of course we all love tinkering, and personally, I'd be playing with it to 'fix' it.
one day you will need to get into the menu of the TP-Link unit, so why not fiddle while you have no pressures.

I'd be having separate IP families for the two routers.
leave downstairs on the 192.168.1.nnn range.
but plug the TP-Link straight into your PC, that way your PC and TP-Link will be on the same address class, then go to a browser and type in 192.168.0.254, that should get you into the menu structure of the loft router.

change its IP to (let's go for) 10.1.1.1, subnet of 255.255.255.0 and gateway of 192.168.1.254, DNS1 of 192.168.1.254 and leave DNS2 blank.
there may not be a DNS2 and they may be called primary and secondary.
when you save all that, you'll probably get a warning that you are about to lose your IP address.
that's cool as you are on 192.168.1.... but about to tell the router to go to 10.1.1...... so save, exit and reboot the PC (the TP-Link should auto reboot).
then go back into the TP-Link menu via 10.1.1.1 to see you still can.
then plug it back into the wall, reconnect you PC to it (cable or wireless) and check the connection, there should be a Status or similar page that tells you download speeds and such in the menu system of the TP-Link.

basically all we told the loft router was to issue addresses starting at 10.1.1.nnn but to get the internet off 192.168.1.254 (downstairs router).

hopefully that works and makes sense.
if it fails you can always press the reset button on the TP-Link and start from scratch like you did initially.
 
bottom line, if it's working, let it be.
but of course we all love tinkering, and personally, I'd be playing with it to 'fix' it.
one day you will need to get into the menu of the TP-Link unit, so why not fiddle while you have no pressures.

I'd be having separate IP families for the two routers.
leave downstairs on the 192.168.1.nnn range.
but plug the TP-Link straight into your PC, that way your PC and TP-Link will be on the same address class, then go to a browser and type in 192.168.0.254, that should get you into the menu structure of the loft router.

change its IP to (let's go for) 10.1.1.1, subnet of 255.255.255.0 and gateway of 192.168.1.254, DNS1 of 192.168.1.254 and leave DNS2 blank.
there may not be a DNS2 and they may be called primary and secondary.
when you save all that, you'll probably get a warning that you are about to lose your IP address.
that's cool as you are on 192.168.1.... but about to tell the router to go to 10.1.1...... so save, exit and reboot the PC (the TP-Link should auto reboot).
then go back into the TP-Link menu via 10.1.1.1 to see you still can.
then plug it back into the wall, reconnect you PC to it (cable or wireless) and check the connection, there should be a Status or similar page that tells you download speeds and such in the menu system of the TP-Link.

basically all we told the loft router was to issue addresses starting at 10.1.1.nnn but to get the internet off 192.168.1.254 (downstairs router).

hopefully that works and makes sense.
if it fails you can always press the reset button on the TP-Link and start from scratch like you did initially.
Thanks for this detailed guide. I shall proceed with it and report back. I agree - it is working so will leave for now until I have time to put your plan into action.
I read that others with this model have experienced the same issue of not being able to access the AP after it has been setup and running and having to revert back to a reset and connecting directly to PC via LAN and default AP ip. This doesn't sound right and allows no path for tweaks or alterations without starting from scratch. I also read that many folk are forced into changing IP protocols on their PCs when dealing with these issues. Glad to think I'm not in that area.
Thanks again. I'll let you know how it goes in due course.
Dave
 
sounds like a plan.

the Mods will chime in soon and indicate whether you have any updates on the matter, sounds like you're going to leave it for now and dive back in at some later date.
if so, for now, reply back that you are happy this thread can be closed - you can always open another one down the track.
or, if you think you'll want to get your hands wet in a couple of days, let them know you would like it left opened. :thumbsup:
 
dsmail has asked that the thread be left open for a few days and was advised of the following;

We cannot leave threads open indefinitely and for the following reason/s, forum procedure is to ask for an update when a thread remains unanswered for three days, if still no answer after a further two days a second update request is post along with notice that the thread will be closed if not replied to within 48hrs, we have to have such a procedure to keep the forums in order as some folk will start threads on five or six forums and then abandon all but one of them.

Genuine people such as dsmail unfortunately suffer because of the selfish attitude of those that think that it is acceptable to abuse the free help we offer.
 
  • Like
Reactions: dsmail
Status
Not open for further replies.