Up and Down All Afternoon/Evening - 23rd June

[#1]

@mattsando Looking at that log - or the first 150 or so lines of it, there appears to be no network issues - it all appears to be internal, so not a Plusnet issue.

It is a bit late now - and some of this is above my pay-grade/level of experience, but maybe, if @Dan_the_Van  spots this, he may have some thoughts?

[#2]

---

@bobpullen wrote:

I have the Mesh in "Bridge" mode...

Not sure if this is information you can depend on but there's a very questionable account here of what those Tenda devices do with IP assignments when they're in bridge mode and lose contact with the external DHCP server 🤔

---

I am checking and all my clients are in the 192.168.1.x range. The Mesh doles them out in the 192.168.5.x range. SO DHCP for the Tenda Nova is definitely off.

[#3]

---

@bobpullen wrote:

Even with the wired device observation, I think there's still merit in seeing how the device network adapters are configured when in the error state: -

You can probably work out if this is happening by running 'ipconfig /all' from a Windows command line from an affected devices when the problem is present.

I will do that next time. What info is useful?

For example, right now it is this (REDACTED parts because it reveals my employer):

C:\Users\REDACTED>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : REDACTED
   Primary Dns Suffix  . . . . . . . : REDACTED.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : REDACTED.local
                                       root.local
                                       external.local
                                       perimeter.REDACTED

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 50-81-40-94-DB-AB
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b84f:ff9d:4212:e273%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.236(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 23 June 2025 07:12:46
   Lease Expires . . . . . . . . . . : 24 June 2025 20:57:53
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 206602560
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-3A-12-07-50-81-40-94-DB-AB
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Disabled

Wireless LAN adapter Local Area Connection* 1:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 52-C2-E8-CD-0A-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physical Address. . . . . . . . . : D2-C2-E8-CD-0A-1D
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Realtek RTL8822CE 802.11ac PCIe Adapter
   Physical Address. . . . . . . . . : 50-C2-E8-CD-0A-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 50-C2-E8-CD-0A-1E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Microsoft IP-HTTPS Platform Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft IP-HTTPS Platform Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd4d:3409:7acb:1002:487a:4808:4395:bb42(Preferred)
   Link-local IPv6 Address . . . . . : fe80::8b36:2900:9eee:a8dc%7(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 50331648
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-3A-12-07-50-81-40-94-DB-AB
   NetBIOS over Tcpip. . . . . . . . : Disabled

[#4]

---

@jab1 wrote:

@mattsando Looking at that log - or the first 150 or so lines of it, there appears to be no network issues - it all appears to be internal, so not a Plusnet issue.

---

Thanks. What might I expect tos ee if there was an issue?

[#5]

You say the internet is up and down - do you see the light change colour on the Hub Two?

[#6]

DHCP Server . . . . . . . . . . . : 192.168.1.1

@mattsando that doesnt look right ?

The Hub 2 should be the only DHCP server and its 192.168.1.254

What has the 192.168.1.1 address ? the Tenda mesh perhaps ?

[#7]

@MisterW 

The op has started a second thread https://community.plus.net/t5/Full-Fibre/Up-and-Down-All-Afternoon-Evening-23rd-June/td-p/2011694 

Not helpful thing to do but there is a Hub Two event log attached.

I'm out today so I have got not much time to look at it.

[#8]

@Dan_the_Van thanks, I looked briefly at that thread but didnt realise it was the same issue , doh!

From what I can see, that log is just mainly DHCP requests and assignments, there's no evidence of a PPPoE drop , and I wouldn't expect any on an FTTP connection.

Not sure I like the  IPv6 Neighbour discovery events ( but not sure if they are a problem )

I'd be starting by disconnecting the Tenda mesh. As @bobpullen said earlier, it can do strange things when it detects no other DHCP server

[#9]

@mattsando as @jab1 says above, theres nothing in that log to indicate the internet (PPPoE) connection is dropping, its all just devices renewing DHCP leases.

Can we keep all discussion of the problem in the original thread https://community.plus.net/t5/My-Router/FTTP-gt-Hub-Two-gt-DNS-Internet-does-every-night/m-p/2011711... please

[#10]

---

@MisterW wrote:

DHCP Server . . . . . . . . . . . : 192.168.1.1

@mattsando that doesnt look right ?

The Hub 2 should be the only DHCP server and its 192.168.1.254

What has the 192.168.1.1 address ? the Tenda mesh perhaps ?

---

Second this. What is at 192.168.1.1 and why does this machine think that's the location of its DHCP server?

Also, for clarity, are you extracting this information at a time the problem is evident?

[#11]

---

@Dan_the_Van wrote:

@MisterW 

The op has started a second thread https://community.plus.net/t5/Full-Fibre/Up-and-Down-All-Afternoon-Evening-23rd-June/td-p/2011694 

Not helpful thing to do but there is a Hub Two event log attached.

---

Different issues.

[#12]

---

@bobpullen wrote:

---

Second this. What is at 192.168.1.1 and why does this machine think that's the location of its DHCP server?

Also, for clarity, are you extracting this information at a time the problem is evident?

---

So here's what I've done since last night, and this morning to get back online...

I totally disconnnected the mesh, switched off all nodes and I used just the Hub Two for the evening.

Internet was awful both wired and wifi (even right in front of the router and plugged via ethernet directly into the router).

I couldn't even run a speed test, both Google's and Ookla's would error.

The internet would work very very briefly and then die again.

I hard-resetted the Hub Two. Changed only the SSID and PW.

Still, nothing. I was convinced - by your constant mentioning of it - that the Tenda Nova Mesh was the issue so i thought that removing the Mesh and going all-in with the Hub Two would work - it is a brand new router, after all.

I then removed the Hub Two entirely, and went PPPoE on the Tenda Nova Mesh and I have internet again.

So, as it stands, I have internet but I'm not holding my breath because the way that it is set up now is how it was briefly the other day and it went down again.

By competely removing the Hub Two I've been able to get back online seemingly reliably now.

[#13]

https://community.plus.net/t5/My-Router/FTTP-gt-Hub-Two-gt-DNS-Internet-does-every-night/m-p/2011711...

I've been asked to keep the discussion to this thread - even though technically they were different issues

[#14]

@mattsando 

Different issues.

Sorry, but I don't believe they are. There's no evidence from the log that the internet (PPPoE) connection is dropping, its all DHCP logs. Short of Openreach maintenance, I wouldnt expect any PPPoE drops on an FTTP connection.

The problem here is the Tenda MW5 acting as a DHCP server. Its being 'clever' because its actually providing the address of the Hub 2 (192.168.1.254) as the DNS & Default gateway, which in itself is 'odd'. 

When it decides to act as DHCP it will be overriding the manual DNS settings you made in the Hub2 and giving devices the Hub 2 (192.168.1.254) as tye DNS server.

If you really want to use the Tenda, then I suggest forgetting about the Hub 2, configure the Tenda main unit for PPPoE and connect it directly to the ONT. 

[#15]

I'm no expert, but from knowledge gained from others on here who have more knowledge, I must admit I wondered why the Hub2 needed to be involved at all - my understanding is that the Tenda can be used as a router - in fact that is what it is, the ONT acts as the modem.

EDIT @MisterW types faster than me.