Hub 2 Device Connection Problems

[#1]

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 !

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.

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.

[#2]

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.

Add tags

[#3]

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.

[#4]

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 ?

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.

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 !

[#5]

@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.

[#6]

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.

[#7]

@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.

[#8]

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 !

[#9]

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.

[#10]

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 ?

[#11]

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.