We'd like to remind Forumites to please avoid political debate on the Forum... Read More »
We're aware that some users are experiencing technical issues which the team are working to resolve. See the Community Noticeboard for more info. Thank you for your patience.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
Extending Wifi Woes
Options
Comments
-
not the routers it is a range extender
https://www.amazon.co.uk/Universal-Extender-Broadband-Ethernet-TL-WA850RE/dp/B00AHXXJVW/ref=sr_1_3?ie=UTF8&qid=1520874260&sr=8-3&keywords=tp+link+wifi+extender0 -
In theory the only issue for not having DHCP is on the remote router TPlink1 so it should get it's IP from TPlink2, I have tried that and with relay and with none at all.
You don't need DHCP to assign IP addresses -- just give the TPLink devices fixed IPs. You'll need to do this on the Sky router as well as the TPLink devices themselves.
Then, you just need DHCP running on the Sky router to automatically assign IPs to other devices on the network.0 -
Although a static IP is not a practical solution on laptop as connects to numerous wireless networks on different subnets, I figured it might help me diagnose what is going wrong.You don't need DHCP to assign IP addresses -- just give the TPLink devices fixed IPs. You'll need to do this on the Sky router as well as the TPLink devices themselves.
Then, you just need DHCP running on the Sky router to automatically assign IPs to other devices on the network.
I did explain that the TPlinks have their own IP's
I am not about to change the Sky config as it issues IP's in it's locale.
I did explain that static IP for laptops is not a practical solution, whilst I can do it for diagnostic purposes the user is not technical, a static IP would not work if they went to Costa and signed on to a hotspot or a plethora of other places if they did not have IP set to get automatically.
Besides the Wireless Bridge works as designed, if I set DCHP on TPLink2 it will deliver it's range of IP's to wireless devices connecting to TPLink1. It is just a dumb setup to force the bridge to have to use same IP subnet.
So if TPlink2 can see the Sky Router on the Status page it then it becomes a routing issue.
I am experimenting with setting on TPLink2 that is wired to Sky router.
It previously worked on Dynamic setting.
It will not let me set a Static Wan (more TPLink rules it seems) I am documenting all of these as no matter what I do I get an error of one sort or another (either with the subnet I use or the gateway).
It does not pick up the Wan connection from the Sky Router, it shows it is there on the status page but will not connect to it and the test option fails too
My feeling is that it worked before as I did all the setup with standalone devices but when the IP lease expired it would not renew, otherwise how come it worked for a month.
Either that or some setting has been changed on Sky Router but I have not touched it so any change must have been made by Sky. I know some ISP's do not like seeing devices downstream and can block Mac addresses if they are minded to. TBH can't see Sky doing this.0
This discussion has been closed.
Confirm your email address to Create Threads and Reply

Categories
- All Categories
- 350.9K Banking & Borrowing
- 253.1K Reduce Debt & Boost Income
- 453.5K Spending & Discounts
- 243.9K Work, Benefits & Business
- 598.7K Mortgages, Homes & Bills
- 176.9K Life & Family
- 257.1K Travel & Transport
- 1.5M Hobbies & Leisure
- 16.1K Discuss & Feedback
- 37.6K Read-Only Boards