New setup, incredibly unreliable

[#1]

If a device needs to rebooted which has no restart option then I would always leave a 30 seconds gap between powering up a device, giving time for any voltages to decay.

However the Hub two does have a restart option so there's no need to press the power button, the "Restart the Hub" tab is found on the Hub two's Home page. A restart would gracefully disconnect the PPP session.

This is an unusual issue, for me the next step would be to try another router, not necessarily a Hub two or as previously suggested configure a PC wired NIC for a PPPoE connection.

[#2]

I've swapped over the ethernet cable between the router and box and done a quick restart and it's behaved itself, coming back up a lot quicker. Will give it another test tomorrow as I need Internet access this evening, but for now it looks like a random cable issue. Thanks peoples.

[#3]

Screen capture of logfile (PPP filtered).

This was after the router and ONT were powered down overnight. The ONT was booted first. Once the two green lights were lit, the Hub2 was powered up.

I also thought IPV6 WAN was disabled on the Hub 2, but the 'PPP IPV6CP Send Configuration Request' still happen.

So far I've never seen a 'WAN connection WAN1_INTERNET_ETH disconnected.[ERROR_NO_CARRIER]' in my Hub2 router log (on a FTTP connection).

The other times I've seen that error is when the physical connection on a ISDN/FTTC got interrupted (testing by me - pulling the cable from the BT box or from the rear of the router). Also when I used to faff around with dial-up.

So it may be a problem with the connection between the router and the ONT (cable or the ports)?

[#4]

Just played around with the ethernet cable into the back of Hub2. Temporaily removed and reinserted.

Logfile

[#5]

---

@Baldrick1 wrote:

@Dan_the_Van 

I know that it's a long shot but my point is that if the hub boots in an unexpected way there's no knowing what would be reported.

It's just the leaving it for a time before working correctly made me think of residual voltage from the PSU holding memory in an unwanted state that's not reset on switch on which triggered my thought process.

---

A quick answer to that (if indeed an issue) is to turn off the device, then turn off at the mains; then switch the device 'on' and 'off' again - before turning the mains supply on once again, followed by the device.