FTTP > Hub Two > DNS - Internet ‘does’ every night

[#1]

---

@bobpullen wrote:

---

---

I'm expecting a problem to be identified/fixed, or alternatively those ranges quarantined until it is. Either way, as soon as it's 'safe' to, I'll remove the static IP assignment.

---

Thanks again. An update: still working perfectly.

[#2]

Right, core network issue identified and hopefully fixed.

@mattsando - I've removed the temporary IP from your connection so it will change the next time your hub is rebooted, hopefully without any return to the problems you've been suffering (at least since yesterday!).

[#3]

Thanks. Rebooting now. I’ll give it a good hour and report back. Finger’s crossed.

[#4]

Fantastic @bobpullen, that seems to have solved it. I’ll obviously be back to advise if it is not working again but it does seem solid and stable again.

I’m going to leave any changes to the network for a while before adding back the switches and mesh. I’m leaving it simple with just the Hub Two for now. When I do add them back, I’ll do so one at a time so that I can easily trouble-shoot where the issues may lay - if there are any.

Thank you for your patience and help. Very much appreciated!

[#5]

I've added 1 switch back into the mix and I'll leave it 24 hours before adding the next one.

Still up and stable.

I have 2 more switches to add that I will do one by one.

After that, I will re-add the Tenda Nova MW5 in Bridge Mode from the Hub Two - H2 acting as PPPoE/router.

I'll leave it like that for a good week or so.

If that continues to work as expected, then I think I'lll leave the whole things as it is.

[#6]

@bobpullen 

Definitely an issue with the Tenda Nova MW5 when in Bridge Mode with the Hub Two as the PPPoE Router.

I had it set up like this:

ONT  >wired>  Hub Two  >wired>  Tenda Main Node in Bridge Mode  >wired>  3 x Nodes  >wifi>  Clients

ONT  >wired>  Hub Two  >wired>  Tenda Main Node in Bridge Mode  >wired>  Switch  >wired>  Clients & Switch >wired>  Clients & Switch 

As I brought the 3 Nodes back into the mix (wired backhaul), the internet dropped for the whole house.

I didn't do any further trouble-shooting because I have a house trying to work but I had planned to keep the Hub Two out of the mix eventually anyway but this just forced my hand. So now it's like this:

ONT  >wired>  Tenda Nova MW5 Main Node  >wired>  3 x Satellite Nodes >WiFi>  

ONT  >wired>  TNMW5 Main Node  >wired>  'Main' Switch & Clients   >wired>  2 x Switches & Clients

[#7]

@mattsando so is the configuration now without the Hub 2 i.e the main MW5 connected directly to the ONT and doing the PPPoE ?

[#8]

---

@MisterW wrote:

@mattsando so is the configuration now without the Hub 2

---

Yes, I suppose I should have done a crude text diagram! Hang on a sec...

ONT  >wired>  Tenda Nova MW5 Main Node  >wired>  3 x Satellite Nodes  >WiFi>

ONT  >wired>  TNMW5 Main Node  >wired>  'Main' Switch & Clients   >wired>  2 x Switches & Clients

This is how I've basically also had it for 5-6 years prior to getting FTTP. When I was FTTC, I had this and it was rock-solid and never needed any maintenance. Fingers crossed I get the same now...!

Phone Line   >wired>  Huawei HG612 Modem  >wired>  Tenda Nova MW5 Main Node  >wired>  3 x Satellite Nodes  >WiFi>

Phone Line  >wired>  Huawei HG612 Modem  >wired>  TNMW5 Main Node  >wired>  'Main' Switch & Clients   >wired>  2 x Switches & Clients

[#9]

This is how I've basically also had it for 5-6 years prior to getting FTTP. When I was FTTC, I had this and it was rock-solid and never needed any maintenance. Fingers crossed I get the same now...!

In that case it ought to be the same, effectively you're just replacing the HG612 with the ONT.

What's caused the problems was the issue with the IP range you got allocated to when moved to FTTP, that's now been resolved so let's hope its all plain sailing from here...

[#10]

---

@MisterW wrote:

What's caused the problems was the issue with the IP range you got allocated to when moved to FTTP, that's now been resolved so let's hope its all plain sailing from here...

---

@bobpullen wrote:

Right, core network issue identified and hopefully fixed.

@mattsando - I've removed the temporary IP from your connection so it will change the next time your hub is rebooted, hopefully without any return to the problems you've been suffering (at least since yesterday!).

AIU...

• Following the move to FTTP this was found to be broken
• @bobpullen providing a temporary static IP address mitigated the issue
• The core network issue was addressed
• The temporary static IP address was removed

... and now there's difficulty again?

• The the difficulty being experienced the same as before or something else?
• If the experience is the same - are there similar residual core network issues?

[#11]

.. and now there's difficulty again?

ICBW but i don't believe there is 

[#12]

> and now there's difficulty again?

>The the difficulty being experienced the same as before or something else?

>If the experience is the same - are there similar residual core network issues?

No, so the issue I had today was not the same as prior to today. I think I know what the issue today was but, as it was the middle of the work day, I needed to get back online quickly so I didn’t have time to diagnose it. I think the issue was that the MW5 tries to act as DHCP Server even though it is in Bridge mode and should not be acting as DHCP Server. The fact that it happened as soon as I introduced a single mesh node suggests that there was conflict of IP addresses at that point.

However… My intention was always to remove the Hub Two entirely but this issue forced my hand.

All working fine again now

[#13]

I have a TP-Link OneMesh device under Network settings it has 

Having this set to the default of Auto caused me no end of issues, if the mesh unit didn't see a active DHCP server it would use the local to the device DHCP server, I always turn it off now.

[#14]

---

@Dan_the_Van wrote:

if the mesh unit didn't see a active DHCP server it would use the local to the device DHCP server, I always turn it off now.

---

I suspect that could be my issue. The only way to test it is to return my config back to the way it was prior, to force the internet to go down. I can't for the foreseeable, but I might be able to do it in a few weeks just because I'm curious to confirm it either way.

Someone posted a link where someone else had had a conversation with tenda, and Tenda confirmed that (if the Main Node didn't see an active DHCP Server) the Main Node will spark its own DHCP Server into life - even when in Bridge Mode (when DHCP should be off).

When in Bridge Mode, you can not access a whole host of settings in the Tenda Nova's Main Node's GUI.

I suspect that this is what the Main Node is doing, and then there's one or two conflicts.

[#15]

A thought

using a PC with a static IP Address (configured on the PC through network properties) turn off the Tenda DHCP server before changing to 'bridge mode' to see if that helps.

Much of the configuring should be achievable without a internet connection.

You might of said before, it's a long thread but why do you want to use the Hub two with Access Points rather than using the Tenda as a router?