Cable Forum - View Single Post

Chrysalis · 31-05-2011, 19:54

ok I finished playing.

Was harder to do and I also failed.

On the vmng300 if removing the cable it seems it eithers works with normal power levels or doesnt work, I couldnt get it to be partially connected at reduced power levels. The numerous recconections were all on the same channel.

When I tried on the superhub because of bridge mode I had the same problem I had with the vmng300 in that I couldnt keep refreshing the page to check the channel status as I had to keep doing dhcp renew's on the router to keep been able to connect to the GUI, the superhub had an additional problem because of this I couldnt relogin after a dhcp renew due to a ghosted session and the superhub restriction of one login at a time. Nevertherless I did about 10 attempts and all same channel.

So I am stuck with this jitter now until VM do another upgrade.

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=11ms TTL=252
Reply from 194.168.4.100: bytes=32 time=9ms TTL=252
Reply from 194.168.4.100: bytes=32 time=22ms TTL=252
Reply from 194.168.4.100: bytes=32 time=25ms TTL=252
Reply from 194.168.4.100: bytes=32 time=12ms TTL=252
Reply from 194.168.4.100: bytes=32 time=11ms TTL=252
Reply from 194.168.4.100: bytes=32 time=9ms TTL=252
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=11ms TTL=252
Reply from 194.168.4.100: bytes=32 time=21ms TTL=252

Ping statistics for 194.168.4.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 25ms, Average = 13ms

It was only 2-3 weeks or so back when ignition signed up and I posted on his thread I had much better then that to the same ip.

31-05-2011, 19:54	#58
Chrysalis cf.mega poster Join Date: Sep 2003 Posts: 12,048	Re: Possible Bug in VMNG300 firmware? ok I finished playing. Was harder to do and I also failed. On the vmng300 if removing the cable it seems it eithers works with normal power levels or doesnt work, I couldnt get it to be partially connected at reduced power levels. The numerous recconections were all on the same channel. When I tried on the superhub because of bridge mode I had the same problem I had with the vmng300 in that I couldnt keep refreshing the page to check the channel status as I had to keep doing dhcp renew's on the router to keep been able to connect to the GUI, the superhub had an additional problem because of this I couldnt relogin after a dhcp renew due to a ghosted session and the superhub restriction of one login at a time. Nevertherless I did about 10 attempts and all same channel. So I am stuck with this jitter now until VM do another upgrade. Pinging 194.168.4.100 with 32 bytes of data: Reply from 194.168.4.100: bytes=32 time=11ms TTL=252 Reply from 194.168.4.100: bytes=32 time=9ms TTL=252 Reply from 194.168.4.100: bytes=32 time=22ms TTL=252 Reply from 194.168.4.100: bytes=32 time=25ms TTL=252 Reply from 194.168.4.100: bytes=32 time=12ms TTL=252 Reply from 194.168.4.100: bytes=32 time=11ms TTL=252 Reply from 194.168.4.100: bytes=32 time=9ms TTL=252 Reply from 194.168.4.100: bytes=32 time=8ms TTL=252 Reply from 194.168.4.100: bytes=32 time=11ms TTL=252 Reply from 194.168.4.100: bytes=32 time=21ms TTL=252 Ping statistics for 194.168.4.100: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 25ms, Average = 13ms It was only 2-3 weeks or so back when ignition signed up and I posted on his thread I had much better then that to the same ip.