Software version 4.7.5.1.83.8.237.2.2 : No devices showing on the network map

[#1]

My Hub One updated to Software version 4.7.5.1.83.8.237.2.2  last night.

Now the Network "Map" is missing all the devices (and yes I've done a refresh). My laptop is connected via wireless and the Youview Box is also connected via a wired connection (Youview Box is connected to the internet)

It also looks like the DMZ has stopped working.

For various reasons I do not use the DHCP server on the router.

I have rebooted the router to see if it fixed the issue - it didn't

[#2]

We'll try and replicate this and get a bug raised if necessary. It definitely worked before the update, yes? Any other non-default config i should know about? I'm assuming you've tried restarting the Hub?

[#3]

Yes it was all working perfectly before the update. I've got a pingable device in the DMZ so I can monitor the network.

I restarted it and it just got worse - port forwarding stopped working totally.

I've done a factory reset and restored the config I backed up yesterday and port forwarding now seems to be working but the DMZ seems to be dead.

Only device being seen on the network now is the media server :

I used to be able to see all the devices on the network. I suspect the DMZ isn't working because it doesn't know about the device so it can't route to it.

[#4]

Do connected devices have their IPs assigned statically, or are you using another DHCP server?

[#5]

Other devices are dynamically assigned from another DHCP server but on very long lifespans.  192.168.0.1 is the only hard coded IP address on the network apart from the Router (192.168.0.66) and another wireless access point (192.168.0.67) and the device in the DMZ. (192.168.0.10).

I suspect the port forwarding stopped when I rebooted it because its all based on named devices (using the MAC address) and if it can't discover the devices I guess it can't know how to forward to them. Rebooting would have flushed any tables held in memory.

[#6]

So it was still all "broken" when I got home tonight but now its sort  of working. Although it shows my laptop and my mobile phone as not connected when they are.

And the device in the DMZ is now reachable

[#7]

It's still all over the place - not showing any wifi devices even though I know there are at least 3 devices connected to it, but it's showing the second hub (Fluffy) as connected although it has now lost the You-View box in the bedroom.

The text version on the front page shows a different list:

@bobpullen - any update on this? Is it possible to rollback to the previous (stock) version of the router firmware as that didn't exhibit this problem.

[#8]

@bobpullen or anyone?

Router restarted this morning - no devices showed on the home network page, none of the port forwarding worked any more, DMZ doesn't work.

Got port forwarding working by changing it all to IP addresses but the DMZ needs to use a name that you set up from the Home Network Page.... and the DMZ wont work if that device doesn't appear on the Home Network Page.

I either need a fix for this or I need the stock firmware re-installing and the router taken out of the update list as there is obviously something fundamentally broken with this version.

Edited to add : Couple of devices have shown up now. Interestingly although it doesn't see anything on Lan Port 2 it can work out that it has a Gbit capable device connected to it...  Right now I've got the following devices connected:

• Music Laptop
• Second wireless access point (Fluffy)
• Main server (debussy)
• YouView Box (living room)
• YouView Box (bedroom) - connected via Fluffy
• My Laptop (Via Wireless)
• Works Phone (Via Wireless)
• My Phone (Via Wireless)

All of which are working fine

[#9]

@SteveA, apologies for the silence. I've not forgotten about this one, I've been a bit stacked with other stuff this week though.
There is a way we can revert you to a previous build, however the version immediately before the current one has a bit of a nasty PPP connectivity bug. Our options therefore are to try a very early build, that may have some other since-fixed bugs, or give a version that's currently in testing a shot. I'll aim to reach out to you next week to sort.

[#10]

@bobpullen - thanks for the update.

If you need any more information from me then please let me know.

If a back up configuration file for the router would help then I can let you have one.

[#11]

Just to add a "me too" on this one, as I came on the board looking for this particular issue.

My device showing:  Plusnet Hub One | Software version 4.7.5.1.83.8.237.2.2 | Last updated 23/03/18

According to the Devices page, I'm viewing it via telepathy!

Port forwarding is definitely broken too. I noticed while I was out that I couldn't connect to my VPN hosted on my Raspberry Pi.

[#12]

You can "Fix" port forwarding by changing them all to use IP addresses - which is fine as long as they are either static or on very long leases.  It's not nice but it gets round the immediate issue. 

[#13]

Thanks, that must be a new option as when I originally configured it, I could only assign them to a discovered and named device. The option for a user-defined IP address wasn't there.

Strangely though, my devices have all come back, and my port forwarding is currently working, even though I've not touched anything since my posting earlier.

[#14]

They come back, and then some of them will vanish again, usually when they vanish off the Network diagram port forwarding keeps working... until the router reboots.

[#15]

Thanks Steve. I've changed the F/W rule to point to the static IP of the device instead.

Like I said, I didn't have that option when I originally configured it, but to my knowledge, the Firmware update on the 23rd is the first I'd had since getting the router back in November. It had always shown a last updated date of 'Never' (or similiar - off the top my head). 

I'll keep an eye on the thread too, might be useful. Appreciate the heads up about the port forwarding.