When is 2.32e going to full release?

[ricke17]

Logically, it shouldn't but the devices I have configured with a static IP do show up.

[killsta]

Do you mean the devices you've set up with a static IP via DHCP? If so, that would make sense is well, as DHCP is providing them with an IP when requested, albeit the same one every time. If you've set up a static IP directly on the device, the router's DHCP isn't assigning anything, so it wouldn't appear in the list?

That is how I would understand it anyway!

[ricke17]

Do you mean the devices you've set up with a static IP via DHCP? If so, that would make sense is well, as DHCP is providing them with an IP when requested, albeit the same one every time. If you've set up a static IP directly on the device, the router's DHCP isn't assigning anything, so it wouldn't appear in the list?

That is how I would understand it anyway!

No - I have set up a static IP for my WD Cloud NAS via the user interface of the billion via my laptop. This is because sometimes the IP changes and screws up my laptop trying to find it to add/remove movies etc. My other NAS had the option to assign a static IP via its web interface and I done this for the same reasons.

Other than using an app to scan for connected devices to the Billion there seems to be no other way to see whats connected to the Billion other than via the DHCP listings.

I hope that makes sense.

[killsta]

Do you mean the devices you've set up with a static IP via DHCP? If so, that would make sense is well, as DHCP is providing them with an IP when requested, albeit the same one every time. If you've set up a static IP directly on the device, the router's DHCP isn't assigning anything, so it wouldn't appear in the list?

That is how I would understand it anyway!

No - I have set up a static IP for my WD Cloud NAS via the user interface of the billion via my laptop. This is because sometimes the IP changes and screws up my laptop trying to find it to add/remove movies etc. My other NAS had the option to assign a static IP via its web interface and I done this for the same reasons.

Other than using an app to scan for connected devices to the Billion there seems to be no other way to see whats connected to the Billion other than via the DHCP listings.

I hope that makes sense.

Ah, ok - so you have assigned a static IP via DHCP. Are you sure there isn't also a static IP set in the WD GUI? That would stop it requesting an IP from DHCP on the billion (and thus appearing in the list most likely) - if not try rebooting the NAS to force it to request a new IP, which might update the list.

I assign about 10 static IPs via DHCP and all of mine appear in the list, so it could be an intermittent bug I suppose, I'll keep monitoring mine to see if it loses any.

[ricke17]

Do you mean the devices you've set up with a static IP via DHCP? If so, that would make sense is well, as DHCP is providing them with an IP when requested, albeit the same one every time. If you've set up a static IP directly on the device, the router's DHCP isn't assigning anything, so it wouldn't appear in the list?

That is how I would understand it anyway!

No - I have set up a static IP for my WD Cloud NAS via the user interface of the billion via my laptop. This is because sometimes the IP changes and screws up my laptop trying to find it to add/remove movies etc. My other NAS had the option to assign a static IP via its web interface and I done this for the same reasons.

Other than using an app to scan for connected devices to the Billion there seems to be no other way to see whats connected to the Billion other than via the DHCP listings.

I hope that makes sense.

Ah, ok - so you have assigned a static IP via DHCP. Are you sure there isn't also a static IP set in the WD GUI? That would stop it requesting an IP from DHCP on the billion (and thus appearing in the list most likely) - if not try rebooting the NAS to force it to request a new IP, which might update the list.

I assign about 10 static IPs via DHCP and all of mine appear in the list, so it could be an intermittent bug I suppose, I'll keep monitoring mine to see if it loses any.

This is how I set the static IP up (whether it is DHCP or not - not too technically minded sorry!).

Configuration - then I add it on the Host Label section

[killsta]

Yes that is the way I do it - seems odd your devices aren't all appearing, if they don't appear after a device reboot then I'd suspect it could be an intermittent bug.

[ricke17]

Yes that is the way I do it - seems odd your devices aren't all appearing, if they don't appear after a device reboot then I'd suspect it could be an intermittent bug.

Everything works ok - just that the device I configured the static IP on the actual NAS device itself doesn't show up on the Billion web userface - but it's no biggie.

[killsta]

Yes that is the way I do it - seems odd your devices aren't all appearing, if they don't appear after a device reboot then I'd suspect it could be an intermittent bug.

Everything works ok - just that the device I configured the static IP on the actual NAS device itself doesn't show up on the Billion web userface - but it's no biggie.

Bet it's not as annoying as your router rebooting itself at 10pm every night...

[ricke17]

Yes that is the way I do it - seems odd your devices aren't all appearing, if they don't appear after a device reboot then I'd suspect it could be an intermittent bug.

Everything works ok - just that the device I configured the static IP on the actual NAS device itself doesn't show up on the Billion web userface - but it's no biggie.

Bet it's not as annoying as your router rebooting itself at 10pm every night...

That's weird and could kick in DLM too - have you checked this part of the config: Advanced Setup - Management - auto reboot?

[killsta]

I have - it's disabled. It's only occurred since the latest firmware, however I did do a factory reset then restore from a backup. I've enabled auto reboot then disabled it again just incase it was somehow enabled, but if it does it again tonight I'll have to do a factory reset and see if that sorts it. Failing that it'll be back to 2.32d...