topic Re: Hub 2 Device Connection Problems in My Router

Hub 2 Device Connection Problems

DLeiper — Fri, 02 Jan 2026 17:41:00 GMT

We have a Hub2 in our church and are regularly having difficulty with getting devices to connect. The system has evolved over the years and has numerous devices connected. Some are allocated static IPs. I am still trying to build a picture of what all there is, but information is limited and not all devices are listed in the routers DHCP table. I had thought TP-Link powerline wifi extenders were acting as DHCP servers so have disabled these where I could. However two were V1.0 units which have limited configuratios options so planned to replace them today. I have also been trying to allocate static IPs to all of them. Once done, I reset the router to find:

1) The newly allocated fixed IPs had changed !

3) The two wifi extenders although not showing on the router were actually allocated IPs (visible on the WiFi Analyzer app) and connected to the internet.

Any clues as to what's going ? Thanks in anticipation.

Re: Hub 2 Device Connection Problems

PhilipHeyes — Sat, 03 Jan 2026 11:57:26 GMT

1) The newly allocated fixed IPs had changed !

How did you allocate the IPs & in what IP range ?
i.e. Genuine Static IP or Reserved IP to MAC on the Hub 2

What has been done to ensure the Hub 2 DHCP server does not issue IPs that clash with the static IPs ?

2) My laptop would not connect to the internet or router configuration page, though accessing this through my phone, I could see it was actually connected. Looking back on the router log, I also saw that it had been given 4 different IPs within an hour, prior to the router reset.

Check the laptop has an IP and Gateway address that matches the Hub 2's IP range.

If the IP is in the right range, is there an IP clash with one or more static IP device(s) ?

If the laptop has an IP in the 169.xxx.xxx.xxx range it has failed to get a DHCP IP from the Hub 2,
and will not connect to the Hub 2.

3) The two wifi extenders although not showing on the router were actually allocated IPs (visible on the WiFi Analyzer app) and connected to the internet.

On these I prefer DHCP disabled and Wi-Fi AP Isolation disabled to avoid Double NAT issues on the repeated Wi-Fi.

Allocated IPs as in they have genuine Static IPs which is common for Wi-Fi Access Points.

Perhaps don't show in the Hub 2 connected devices because they have not been allocated a DHCP IP by the Hub 2.

Re: Hub 2 Device Connection Problems

DLeiper — Tue, 06 Jan 2026 19:50:35 GMT

Thankyou very much for your questions and suggestions. Apologies for the delayed response.

1) The newly allocated fixed IPs had changed !
How did you allocate the IPs & in what IP range ? i.e. Genuine Static IP or Reserved IP to MAC on the Hub 2

What has been done to ensure the Hub 2 DHCP server does not issue IPs that clash with the static IPs ?

In this latest attempt, I used the "Always use this IP address" in the router and set them outside the DHCP range (which is set to 64 to 199). If I used using Genuine Static IP , would they not change ?

I guess the Hub 2 DHCP server would not issue IPs that clash with those static IPs ?

I am quite sure they were.

If the IP is in the right range, is there an IP clash with one or more static IP device(s) ?

Surely the router would not issue an IP already reserved ?

If the laptop has an IP in the 169.xxx.xxx.xxx range it has failed to get a DHCP IP from the Hub 2,
and will not connect to the Hub 2.

3) The two wifi extenders although not showing on the router were actually allocated IPs (visible on the WiFi Analyzer app) and connected to the internet.
On these I prefer DHCP disabled and Wi-Fi AP Isolation disabled to avoid Double NAT issues on the repeated Wi-Fi.
Allocated IPs as in they have genuine Static IPs which is common for Wi-Fi Access Points.
Perhaps don't show in the Hub 2 connected devices because they have not been allocated a DHCP IP by the Hub 2.

On the extenders the DHCP has been disabled. I can't see any option to disable Wi-Fi AP Isolation. I am also thinking the IP were allocated by some other device, but it's proving difficult to find !

Re: Hub 2 Device Connection Problems

Dan_the_Van — Wed, 07 Jan 2026 08:49:57 GMT

@DLeiper

Hub Two default settings

The Hub network range is 192.168.1.0/24 (that will be mask 255.255.255.0)

The Hub's IP Address is 192.168.1.254 - this is the default gateway and DNS IP Address for all devices

The default IP DHCP pool is 192.168.1.64 to 192.168.1.253

There is no option for the Hub to pre assign an IP Address to device MAC Address, you use "always us this IP Address" after the device connects.

I believe the "always us this IP Address" should be for setting a device to use an IP within the DHCP pool. The DHCP server randomly assign IP Addresses to devices.

Device set with a static IP Address should be within the 192.168.1.to 192.168.1.63 range.

I would check the laptop WiFi network card properties for 'use randomised MAC address'. The network card will create a new MAC address for each WiFi network it has connected to.

You would need back to back routers for Double NAT, devices assigned an IP Address on the same network would not be double NAT.

What are the powerline and wireless access point / extenders you are using?

You are free to use your preferred router with plusnet, for Full Fibre (FTTP) it would connected directly to the ONT for Part Fibre (copper wire to property/ FTTC) the Hub Two can be configured to be a modem only device.

If there is any function you'd like to check on the Hub two let me know as I have a test device.

Re: Hub 2 Device Connection Problems

DLeiper — Wed, 07 Jan 2026 20:42:42 GMT

Thanks Dan.

Our Hub DHCP range has been configured to be from 192.168.1.64 to 192.168.1.199

The range 192.168.1.200 to 253 has been allocated for various AV devices by a contractor.

I am trying to give static IP addresses to other fixed / permanent devices in the building eg office computer, printer, WiFi extenders, etc and leave the 64 to 199 range for folk coming and going. With the WiFi extenders (mainly TP-Link TL-WPA4220 units with a TL-PA4010 and also a TL-WA860RE), once they are connected, they can be configured in the device itself with a static IP address. I am using something in the range 1 to 63 or where there are gaps in the 200 to 253 range. I am thinking this is better than doing it in the router, as they seem to have got lost when the router is reset ?

We have had another day of guest's laptops connecting to the wifi, but then not being able to access the internet.

Also my phone and two new TL-WPA4220 units being given IP addresses of 192.168.0.100 !! Where has that come from ? It's not even a default IP address for these units. After 5 - 10 minutes they eventually got IPs in the 64 to 199 range.

Thanks for the offer to check any function on the Hub2, but I'm not sure what I should check to find why various devices are intermittently connecting but not getting internet access or if some other device is allocating IP addresses.

Re: Hub 2 Device Connection Problems

Dan_the_Van — Thu, 08 Jan 2026 08:13:44 GMT

@DLeiper

TL-WPA4220 units being given IP addresses of 192.168.0.100

That is the out of the box IP Address range for every WPA4220 if I recall correctly DHCP is set to Auto. You need to change it to your preferred choice or use these settings as seen in a browser

(I use 192.168.10.0/24 network so ignore)

I would make sure the WPA4220 DHCP server is set to OFF like my mine is.

With the DHCP server set to Auto - if there is a break of connection of the Powerline network to the Hub the WPA DHCP server will start to allocate IP Addresses, which would result in device connection to the WPA being allocated a wrong network range IP, this would result in "No Internet detected"

In general the hub DHCP IP Addresses allocation to a devices is sticky with the device rarely changing it IP Address, so provided you can accept the allocation there should be no need to fix it using the My Network Devices GUI.

If ON I would also consider turning off DHCP server on the TL-WA860RE as you only need one per network.

What name have you given the WiFi access points?

You might like to consider taking a Backup of the Hub config.

Re: Hub 2 Device Connection Problems

DLeiper — Thu, 08 Jan 2026 09:27:37 GMT

Thanks Dan.

I could only find info saying the default IP address was 192.168.0.1, not 192.168.0.100. So still wondering.

You recalled correctly, DHCP is set to Auto, but I have configured them all to Off straight away. Same with the TL-WA860RE. It seems the new devices take a wee while to get an IP address from the Hub. The Hub has been regularly switched off and then on again (for emergency lighting tests), so maybe that's why any static IP addresses set by the router are getting lost ? I will see if setting them in the devices is more reliable.

Still not sure why my phone got allocated 192.168.0.101 though ?

The access points all have the same WiFi name as the Hub.

Yes, a backup would be a good idea !

Re: Hub 2 Device Connection Problems

Dan_the_Van — Thu, 08 Jan 2026 10:23:29 GMT

To make the IP Address stable, maybe set them both WPA and WA locally with an static IP Address.

I manage my WPA4220 using the tpPLC app, there is a Windows (downloaded from TP-Link) and Android/Apple app (available through the relevant app store) version

For both applications you can manage the WiFi settings, setup the powerline network security, check the connection speed between the powerline adapters. The overall Ethernet speed is restricted to 100 Mbps as they only support 10/100 Mbps connections.

I have no issues with mine using the same WiFi name as the main router.

Re: Hub 2 Device Connection Problems

DLeiper — Sat, 10 Jan 2026 20:37:48 GMT

So today I tried to connect my laptop at the far end of the building, where I know it will need to use one of the TP-Link powerline extenders. It connects to the wifi, but fails to connect to the internet. I check the router on my phone and find my laptop listed with an IP address 169.254.175.211. I understand this is "a self-assigned Automatic Private IP Address which means my device is unable to communicate with a DHCP server (usually my router) to obtain a proper network address."
But why ? Especially when my phone connects ?

Re: Hub 2 Device Connection Problems

Dan_the_Van — Sun, 11 Jan 2026 07:59:24 GMT

Using the tpPLC app can you see all the powerline adapters listed/displayed?

The android app this is what I see; I just have two devices, but more would displayed if I had them

The tpPLC desktop version. Using the desktop version you can connect directly to the powerline adapter ethernet port.

If not I would suggest going through the pairing process to all the devices to make sure they are on the same powerline network, it maybe easier to pair them together when are a situated close to each other.

If you have a DSL connection, make sure you do not use the WAN port (next to the DC power port) as that is only used for an upstream modem or Full Fibre ONT.

Re: Hub 2 Device Connection Problems

DLeiper — Thu, 15 Jan 2026 17:59:18 GMT

Thanks Dan for the suggestion to use the tp App. I have used this to set up the powerline adapters and check they connect.

However today's problem was encountered while myself and a colleague were 2m from the Hub 2 (!) so nothing to do with the adapters. Again, our laptops connect to wifi, but the connection states "no internet". My phone does connect, including to the internet and the Hub 2, where I can see my laptop has the same IP address 169.254.175.211 as before, indicating it is unable to communicate with a DHCP server. I swiched on and off the laptop wifi several times, but no change, put it to sleep for 10 minutes, but no luck.

So I am reaching the conclusion the router is faulty, unless there is another explanation ?

Re: Hub 2 Device Connection Problems

Dan_the_Van — Thu, 15 Jan 2026 18:30:53 GMT

@DLeiper

Can you use this link https://maclookup.app/

Using the MAC address of the PC, does it report the manufacturer of the network card or it being a random MAC Address also know as hardware address.

If a random hardware address you might be be able to refresh it so it changes.

Windows key:- enter text "use random hardware address"

Edit: - There will be an option to turn off use random hardware address if you so wish to

If it is the true MAC Address, then I would give the PC a static IP Address using network properties.

Re: Hub 2 Device Connection Problems

mystreet1 — Thu, 15 Jan 2026 18:33:39 GMT

Had this once on a laptop. Fixed it by removing the hardware in device manager, then rebooted the machine which found new hardware, installed the drivers, reconnected back to network.

Re: Hub 2 Device Connection Problems

DLeiper — Thu, 15 Jan 2026 20:15:08 GMT

The router shows the same mac address for my laptop everytime and I'd like to leave it that way. The router should allocate an IP address to it. I could make it static, but it's not just me, various other users have the same problem. We shouldn't have to allocate static IPs for every laptop that wants to connect, that's what the DHCP is for isn't it ? That might be a work around, but the problem would remain for any new user.

Re: Hub 2 Device Connection Problems

DLeiper — Thu, 15 Jan 2026 20:18:37 GMT

Thanks, but as I said to Dan, there are numerous people with the same problem, so I think it's a router issue and it's impractical to do it for all laptops. So looking for router solutions please.

Re: Hub 2 Device Connection Problems

Dan_the_Van — Thu, 15 Jan 2026 20:43:39 GMT

Can you export the event log and attach it to a post please, location
>Home >Advanced settings >Technical log >Eventlog
The export is a CSV file
Thanks

Re: Hub 2 Device Connection Problems

DLeiper — Thu, 15 Jan 2026 21:11:01 GMT

As requested, attached is the event log from 14:30. I hope that's enough to see what's going on at the time I tried to connect, around 14:47 The screenshot I posted earlier was taken at 14:54.

Re: Hub 2 Device Connection Problems

Dan_the_Van — Fri, 16 Jan 2026 09:02:53 GMT

For what it is worth the laptop MAC Address is not randomised.

My thinking is the laptop is not making a DHCP request, not clear why.

Some diagnosis is required, assuming it is a windows PC, using the same laptop as previously with MAC Address e0:d4:e8:96:0a:00

Open a CMD prompt in Administrator mode - Windows key -> enter text "cmd" select 'Run as administrator'

Try these commands, they force the PC to make a DHCP request.

ipconfig /release - press Enter

ipconfig /renew - press Enter

It will be interesting to see if this works or reports an error.

Another thought, your DHCP pool only has 135 devices (64 to 199), are all the IP Addresses used?. From what I recall the Hub two does not appear to released unused IP Addresses. With many visitors you could soon use up the DHCP pool.

The following will need to be performed on a laptop as the Hub GUI does not work correctly on mobile/table device.

Could you try deleting some Disconnected devices from the Hub ->Home -->Advanced settings --->My devices

--->Select Disconnected devices drop down. Then click on remove.

With option of setting the Hub Two to bridge mode (modem only), if your budget allows maybe consider purchasing a router which has a more flexible DHCP server and more suited to your requirements with the option of a Guest Network..

Re: Hub 2 Device Connection Problems

Anonymous — Fri, 16 Jan 2026 22:39:16 GMT

"From what I recall the Hub two does not appear to released unused IP Addresses."

That is also my recollection/experience.

Re: Hub 2 Device Connection Problems

Dan_the_Van — Mon, 19 Jan 2026 16:19:02 GMT

@DLeiper

From what I can make out the cause of the 169.254.x.x IP Addresses was connecting a PC to a network without an active DHCP server, the network could be either wired of wireless.

I have powered up my Hub two and confirmed the above.

Hopefully you can resolve the issue by removing the PC from the My Devices list on the Hub,

It is not possible to delete with an Active connection, so make sure the devices WiFi is off and/or disconnect any ethernet cable

On the Hub navigate ->Home -->Advanced settings --->My devices ---> Filter for "Show Disconnected" devices drop down. Click on remove.