Netgear D7000 VDSL modem/router

[glenimp617]

which one do i need for sky fibre?

I have money burning a hole in my pocket this morning

 

[glenimp617]

sorry for all the questions

I do like the look of the AC87U, but since it's not a VDSL router will I still need the sky hub? even if I use asuswrt?

 

[michty_me]

The AC87U should still work. You just remove the sky router and plug it into the openreach modem. I've used the N-56U, N-66U, AC68U all this way before.

 

[glenimp617]

The AC87U should still work. You just remove the sky router and plug it into the openreach modem. I've used the N-56U, N-66U, AC68U all this way before.

Thanks mate, that's pretty much what I'm finding out

Merlin firmware seems a must to install

That's £150 gone

 

[michty_me]

Thanks mate, that's pretty much what I'm finding out

Merlin firmware seems a must to install

That's £150 gone

Let us know how you get on. May have been worth holding off until Friday to see if there was any black friday deals.

Also a bit cheaper here. I always check this site before a purchase.

http://www.hotukdeals.com/deals/asu...outer-ac-2400-dual-band-139-49-currys-2322626

 

[michty_me]

Also I found this which may help you in the setup.

https://www.avforums.com/threads/how-to-replace-sky-sr102-with-another-router-sky-fibre.1939217/

 

[pdes]

That's good.

I've just put together a new tool for getting all of the details from a sky router, you'll not need it now, but if you see someone who needs help it's available over on the Skyuser forum.

I took a trip over to SkyUser but couldn't see your tool!

I am registering some very regular and consistent bursts of FEC errors which has a detrimental effect on my SNR (as you would expect!). As part of the analysis and to eliminate the D7000, I would like to see whether the FEC errors are the same on the SR102. Will the tool show this?

Thanks

 

[glenimp617]

Let us know how you get on. May have been worth holding off until Friday to see if there was any black friday deals.

Also a bit cheaper here. I always check this site before a purchase.

http://www.hotukdeals.com/deals/asu...outer-ac-2400-dual-band-139-49-currys-2322626

Thanks to everyone for the help

I found a local store which had stock so I went after work and bought it the hotukdeals voucher had expired but thanks for the link anyway

Prior to plugging it in I read some threads and people went on about having to run various things in hex, and entering telnet commands etc etc

Basically I plugged it in, uploaded the latest merlin, entered my sky username and password and bang! connected straight away

OMG! this thing is awesome

Streaming 1080p xbox one over wifi two floors up, silky smooth with zero lag. It can also remotely power on the xbox when I'm outside the network (ie: mobile 3g) which could come in handy for a little xbox playing at work

 

[michty_me]

Thanks to everyone for the help

I found a local store which had stock so I went after work and bought it the hotukdeals voucher had expired but thanks for the link anyway

Prior to plugging it in I read some threads and people went on about having to run various things in hex, and entering telnet commands etc etc

Basically I plugged it in, uploaded the latest merlin, entered my sky username and password and bang! connected straight away

OMG! this thing is awesome

Streaming 1080p xbox one over wifi two floors up, silky smooth with zero lag. It can also remotely power on the xbox when I'm outside the network (ie: mobile 3g) which could come in handy for a little xbox playing at work

Glad to hear you got it setup OK then. It should do you well compared to the old one. Just avoid asus' attempts at a dual box.

 

[michty_me]

Just had another total lockup of the D7000. I had just hit around 23 days uptime this time. A switch off for 30 mins and back on again and all seems well for now. Gained another 1Mb on the DS too.

 

[marjohn56]

Just had another total lockup of the D7000. I had just hit around 23 days uptime this time. A switch off for 30 mins and back on again and all seems well for now. Gained another 1Mb on the DS too.

I'm contacting Netgear on Monday, mine has now developed another problem, even though now it's only acting as a wireless router. Several times a day it just freezes for a minute or two then away it goes again. I bought a cheap nasty chinese 1200AC router for £45 to put in place of the D7000 to prove it was the D7000, so far it's working fine and I've not had the problem again, so it's on to Netgear.

 

[Logsi]

The D7800 seems to be keeping a better Noise Margin, it does drop but does recover somewhat.

My only problem i'm having with it though is the flakey 5GHz wireless. The D7000 was solid but the 5GHz band is getting timeouts when pinging websites and it's quite annoying as it just does not have the immediacy of loading like the D7000 did.

Ping has started…

PING bbc.co.uk (212.58.244.20): 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=50 time=22.012 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=50 time=21.506 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=50 time=22.061 ms
64 bytes from 212.58.244.20: icmp_seq=3 ttl=50 time=21.288 ms
64 bytes from 212.58.244.20: icmp_seq=4 ttl=50 time=22.397 ms
64 bytes from 212.58.244.20: icmp_seq=5 ttl=50 time=37.168 ms
64 bytes from 212.58.244.20: icmp_seq=6 ttl=50 time=55.909 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 212.58.244.20: icmp_seq=9 ttl=50 time=22.195 ms
64 bytes from 212.58.244.20: icmp_seq=10 ttl=50 time=21.825 ms
64 bytes from 212.58.244.20: icmp_seq=11 ttl=50 time=22.331 ms
64 bytes from 212.58.244.20: icmp_seq=12 ttl=50 time=21.649 ms
64 bytes from 212.58.244.20: icmp_seq=13 ttl=50 time=21.746 ms
64 bytes from 212.58.244.20: icmp_seq=14 ttl=50 time=22.951 ms
64 bytes from 212.58.244.20: icmp_seq=15 ttl=50 time=32.490 ms
64 bytes from 212.58.244.20: icmp_seq=16 ttl=50 time=52.596 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
64 bytes from 212.58.244.20: icmp_seq=21 ttl=50 time=21.853 ms

The latency fluctuates also...

I'm changing channels to see if this helps but it doesn't thus far.

EDIT - Unplugged the iDect cordless phone next to the router and thought it may have solved it...2 minutes later...

Ping has started…

PING bbc.co.uk (212.58.244.20): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 212.58.244.20: icmp_seq=1 ttl=50 time=248.474 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 212.58.244.20: icmp_seq=4 ttl=50 time=21.381 ms
64 bytes from 212.58.244.20: icmp_seq=5 ttl=50 time=23.886 ms
64 bytes from 212.58.244.20: icmp_seq=6 ttl=50 time=47.589 ms
64 bytes from 212.58.244.20: icmp_seq=7 ttl=50 time=66.451 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 212.58.244.20: icmp_seq=13 ttl=50 time=21.534 ms
64 bytes from 212.58.244.20: icmp_seq=14 ttl=50 time=24.424 ms
64 bytes from 212.58.244.20: icmp_seq=15 ttl=50 time=48.026 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
64 bytes from 212.58.244.20: icmp_seq=19 ttl=50 time=19.611 ms
64 bytes from 212.58.244.20: icmp_seq=20 ttl=50 time=21.343 ms
64 bytes from 212.58.244.20: icmp_seq=21 ttl=50 time=21.283 ms
64 bytes from 212.58.244.20: icmp_seq=22 ttl=50 time=21.853 ms
64 bytes from 212.58.244.20: icmp_seq=23 ttl=50 time=25.568 ms
64 bytes from 212.58.244.20: icmp_seq=24 ttl=50 time=45.214 ms
64 bytes from 212.58.244.20: icmp_seq=25 ttl=50 time=68.594 ms
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
64 bytes from 212.58.244.20: icmp_seq=29 ttl=50 time=21.497 ms
64 bytes from 212.58.244.20: icmp_seq=30 ttl=50 time=21.013 ms

 

[marjohn56]

I've just been looking at the Netgear community forum, seems a lot of people are having exactly the same problem I am now getting which is the sudden loss of data being passed. All the lights appear normal, you can connect to the wifi but no data is passed on wifi or Lan ports, DSL stays connected. For some like myself this corrects itself afer a couple of minutes others have reset the D7000 and it comes back. From what I am reading it appears to be a hardware issue, could turn out to expensive for Netgear if the boards have to be replaced. I dont think the D7800 will have this issue as it's a different chipset.

Also just notciced on MDSLWS that the DLM profile monitor has now gone from around 23.35 to 23.97, it's now getting more data sent to it, far fewer packets are being lost and this is using a cheap and nasty chinese wifi 1200AC router, but it's not dropping any packets.

 

[Logsi]

Just checked wired to be sure...

Ping has started…

PING bbc.co.uk (212.58.244.20): 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=50 time=18.295 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=50 time=18.389 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=50 time=18.237 ms
64 bytes from 212.58.244.20: icmp_seq=3 ttl=50 time=18.464 ms
64 bytes from 212.58.244.20: icmp_seq=4 ttl=50 time=18.439 ms
64 bytes from 212.58.244.20: icmp_seq=5 ttl=50 time=18.056 ms
64 bytes from 212.58.244.20: icmp_seq=6 ttl=50 time=18.165 ms
64 bytes from 212.58.244.20: icmp_seq=7 ttl=50 time=18.712 ms
64 bytes from 212.58.244.20: icmp_seq=8 ttl=50 time=18.050 ms
64 bytes from 212.58.244.20: icmp_seq=9 ttl=50 time=18.313 ms

--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.050/18.312/18.712/0.192 ms

That's fine...looks like this may be going back. Just checked 2.4GHz and that's sporadic packet loss also. The D7000 was SOLID as a rock with its wireless...

 

[marjohn56]

To be honest, I am a bit dissapointed, for what it cost I was expecting at least reliability. Whatever, even if Netgear replace it it will not be going back online as a modem, the OR modem is rock solid and never misses a beat. The PC Engines/pfSense unit is perfect for my neeeds and all I really need now is a good Wifi access point. In saying that the cheapo one is doing the job without any issues so I may leave things as they are, it's all working and reliable, what more do I need.

 

[Logsi]

So i know I'm not being dense here. What other settings can affect wireless performance and timeouts? I've changed the channel even though there isn't any other wireless devices around.

Pinging the router is painful to see;

Ping has started…

PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=40.982 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=60.089 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.952 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=19.654 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=39.996 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=60.311 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=3.898 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=100.242 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=16.461 ms
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=50.952 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=20.283 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=105.988 ms
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=79.659 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=4.373 ms

 

[marjohn56]

Not really, off its OK on 2.4G but the issue is not on 5G then its either the router or your wifi device. As it was OK on the d7000 it would suggest that the latter is OK.

 

[Logsi]

Not really, off its OK on 2.4G but the issue is not on 5G then its either the router or your wifi device. As it was OK on the d7000 it would suggest that the latter is OK.

Been doing some further testing and 2.4GHz is also poor with timeouts and is similar to 5Ghz. Tried with multiple different wireless devices and they all share the same behaviour.

Just unplugged for 30 minutes and now it's back to normal. Somethings odd so will see how long it takes to go screwy again...

Might have to end up getting the OR modem out again and just getting a different router instead if this continues. Wonder if firmware updates will fix this, currently on the latest. 1.0.0.44.

 

[marjohn56]

Fair chance that firmware would fix it, just depends how long you are prepared to wait. Have you looked at the Netgear community site to see if anyone else is experiencing the same problems? I think if I had not wanted to down the pfsense route, I would have probably got an Asus RT-AC87 and flashed it with Merlin, and stuck with the OR modem.

 

[Logsi]

Downgraded the firmware to the previous one to see if this fixes the wireless issues I'm having. It was fine last night but this morning it's gone back to the timeout mess. Downgraded to 1.0.0.40 but an interesting tidbit is that when i initially had the router and even now with this firmware it doesn't automatically find 1.0.0.44 and i manually had to find and upload it.

Annoyingly since downgrading router has dropped my sync rate by 4 meg.Thanks DLM.

Got a return request now though and will see what happens when i get home tonight and tomorrow morning.

EDIT- Thinking about it...when pinging the router it's around 4ms...this seems very high when I'm sitting 2 meters away from it...checking another router at work now and it pings at 0.4ms to my phone...something doesn't seem right. Would this be a hardware fault...i've made sure the antennas are secured multiple times...

EDIT 2 - Just copped a Asus AC-87u on a lightning deal so will ship this one back regardless now, enjoy the saving and see how i get on with the OR and that. I just really wanted to have a single unit.