I have 2 network connected set top boxes and although they both have the same issue I'll just concentrate on one so as to not complicate the issue.
The STB in question is a Dreambox which some may of heard of, for those who haven't the Dreambox is a very versatile and capable satellite/cable receiver and network streamer, the OS is Enigma2 which sits on top of a light version of debian linux.
It has a 10/100/1000 MBit/s compatible Gigabit Ethernet Interface probably Broadcom, the CPU is Broadcom mips.
So I get my shiny new AC87U installed latest Merlin, set a manually assigned IP for the STB and everything is dandy, all STB network functions working as they should.
It's not until i reboot the STB the problem manifests, when it comes to the point during boot where I assume the STB tries to connect to the network it actually halts the booting and won't progress !
The only way to fully boot the STB is to remove the network cable and reconnect it after it has successfully booted after which the network functions as it should.
I've just updated to Merlins 378.50_beta1 hoping the issue would go away but it hasn't.
No such issues with my previous Netgear R7000 router, can anyone throw any light on this as it's driving me crazy ?
Thanks
The STB in question is a Dreambox which some may of heard of, for those who haven't the Dreambox is a very versatile and capable satellite/cable receiver and network streamer, the OS is Enigma2 which sits on top of a light version of debian linux.
It has a 10/100/1000 MBit/s compatible Gigabit Ethernet Interface probably Broadcom, the CPU is Broadcom mips.
So I get my shiny new AC87U installed latest Merlin, set a manually assigned IP for the STB and everything is dandy, all STB network functions working as they should.
It's not until i reboot the STB the problem manifests, when it comes to the point during boot where I assume the STB tries to connect to the network it actually halts the booting and won't progress !
The only way to fully boot the STB is to remove the network cable and reconnect it after it has successfully booted after which the network functions as it should.
I've just updated to Merlins 378.50_beta1 hoping the issue would go away but it hasn't.
No such issues with my previous Netgear R7000 router, can anyone throw any light on this as it's driving me crazy ?
Thanks