|
Re: Possible Bug in VMNG300 firmware?
One of the things ignition told me was to check the frequency rather than the id as the id is cosmetic and can change even tho you on the same channel still. So if you can remember the frequency of the lower utilised channel and compare it to the one on the vmng300 you will know if it is different or not.
The last month or so I was on the superhub VM activated a 2nd upstream channel so I had channels 7 and 8, 7 was significantly lower utilised than 8 and yet the superhub 9 times out of 10 picked 8, my logic was that the superhub scans from top down (not other way) so unless there is a issue connecting to 8 then 7 wont get picked. Hence my trick of artifically reducing the signal to 8 by half removing the cable so 7 gets picked. A short time before I got the vmng300 the channel 7 changed to a docsis2 channel which looks like it merged in the channel 8 as well so the 2 smaller width channels merged into a single big width channel. As the last week or so on the superhub it seemed to keep picking channel 7. This has carried on to the vmng300 now I always get channel 7 and I did check the frequency which is the same as the channel 7 was on the superhub. So for me its either.
1 - still 2 channels but VM stopped the round robin and forced customers onto specific channels.
2 - is only 1 channel now its docsis2.
3 - as you say the vmng300 is acting odd, but its worth saying whenever I plugin my superhub it always gets channel 7 now as well. you should be able to do same test if your superhub is still activated.
|