Forum Home
Press F1
 
Thread ID: 140193 2015-09-01 22:50:00 VDSL Slow - Chorus tech booked Sam Bos (12456) Press F1
Post ID Timestamp Content User
1407749 2015-09-02 04:02:00 They are excellent modems. :)

Got one here...but yeah get a splitter installed for sure.

6728
wratterus (105)
1407750 2015-09-02 05:02:00 What firmware version is on the DV130? The original release firmware for NZ was almost unusable on the Chorus network, and the first 'fix' firmware was solid but very, very slow in my experience.

As to master splitters - almost necessary if you have multiple jacks, older wiring, multiple devices on the line etc. If you have relatively new/good condition wiring with nothing else using the line, it's really a negligible difference.
inphinity (7274)
1407751 2015-09-02 10:03:00 Firmware version is 3.7.8

Update - someone from Chorus came round this afternoon (while I was out so I still didn't get a chance to hit him up about a master filter and a dedicated line). Anyway apparently he fixed some wiring in the junction box outside the house, speeds are looking a lot better now. However now there seems to be a lot of difference between the modem (currently saying 29.4Mbps) and running the speedtest.net on my Ipad and laptop (both getting around 20-22Mbps) - is this normal? Or is there something goin on in the router that's slowing it down?
Sam Bos (12456)
1407752 2015-09-02 21:18:00 That's about right for wifi. inphinity (7274)
1407753 2015-09-02 22:10:00 Yeah, there are a lot of factors that can affect wireless performance - we might be able to improve it a bit - do you want to try troubleshooting that? ;)

Could you also post a screenshot of the line stats page in the modem?

Like this - under diagnostics.

6729
wratterus (105)
1407754 2015-09-03 03:00:00 Just adding to what the other said, DV130 is a *good* router, very solid. As you've now found, house wiring plays an insanely large part in good vs bad speeds. When signing up customers I _always_ include wiring for a dedicated jackpoint, there's absolutely no good reason not to.

If you're getting ~90% of your sync speeds, that counts as 'acceptable'. The question you now have to find the answer for: Is the problem my WiFi performance or my ISP throttling me?
Chilling_Silence (9)
1407755 2015-09-03 11:06:00 Ok I've attached a screenshot of the diagnostics.

Also, one other problem I'm having - I'm using the Netgear (a D6200) for the Wifi network, it is hooked up to the Draytek via one of the Netgear's LAN ports. When I was setting up the Netgear (via routerlogin.net, I disabled the DHCP server on it, then plugged it into the Draytek and we were able to get on the network/internet etc. But ever since hooking the Netgear up to the Draytek, I can no longer access the Netgear's dashboard (neither from routerlogin.net or via its IP address).

At first I thought perhaps it's an IP address conflict (the Netgear and Draytek both used the same default IP, and I hadn't changed either of them). So just now I reset the Netgear, set it up from scratch again and changed the IP. I was able to access it fine until I plugged it into the Draytek again, now it still won't give me access to the dashboard via routerlogin.net or via the new IP address. Can anyone point out what I'm doing wrong?

Thanks for all your help everyone :)
Sam Bos (12456)
1407756 2015-09-03 12:04:00 Correction - the default IP's aren't the same - Draytek is 192.168.1.1, Netgear is 192.168.0.1 - still giving me the same problem though. Also now if I try to change the IP on the Netgear at all, I lose access to its dashboard until I do a factory reset, even when connected directly to one of the LAN ports. Doing my head in! Sam Bos (12456)
1407757 2015-09-03 22:11:00 Those line stats looks good.

downloads.snappernet.co.nz %20Configuration.pdf

Those are the instructions for putting the DV130 into bridge mode with a VDSL connection.

If you reset the Netgear again, and set it up in PPPoE mode (with the Draytek plugged into the WAN port) you should be good. Leave the IP on default (assuming that is 192.168.0.1). Chill may be able to give some more detailed info around that, it's not something I do very often, but in this case it's the ideal way to set it up.

I would scrap all the 'setup genie' crap. Just browse to the IP and configure it manually.

I'm not much of a fan of those routers to be honest, but it should be sweet for this setup. iPad should be able to work on 5GHz, and on full signal strength you should get very close to the same speed as Ethernet.
wratterus (105)
1407758 2015-10-24 00:58:00 Those line stats looks good.

downloads.snappernet.co.nz %20Configuration.pdf

Those are the instructions for putting the DV130 into bridge mode with a VDSL connection.

If you reset the Netgear again, and set it up in PPPoE mode (with the Draytek plugged into the WAN port) you should be good. Leave the IP on default (assuming that is 192.168.0.1). Chill may be able to give some more detailed info around that, it's not something I do very often, but in this case it's the ideal way to set it up.

I would scrap all the 'setup genie' crap. Just browse to the IP and configure it manually.

I'm not much of a fan of those routers to be honest, but it should be sweet for this setup. iPad should be able to work on 5GHz, and on full signal strength you should get very close to the same speed as Ethernet.

Ok I finally got round to trying this, but I just cannot get it to work.

I tried to follow those instructions from SnapperNet:
Step 1: Configuring the VLAN ID - no problems here.
Step 2: Disable PPPoE/PPPoA client - works but it disables the VLAN Tag Insertion in Step 1, so I have to go back and enable that again.
Step 3: Setup the bridge - no problems here. But then at the bottom of the page it says "Set up a PPPoE client on the LAN side of the DV130 with your ISP credentials...." - the problem here is that there is nothing about that in the LAN settings on the router. The only place where you can set up a PPPoE client with ISP credentials is in the Internet settings - but I have just disabled that in Step 2 - so it makes no sense at all.

So I ended up basically keeping the settings I already had (that was the only way I could keep it connected to the Internet - if I followed the SnapperNet instructions it wouldn't connect. So the only thing I ended up changing was disabling the DHCP server on the modem.


Unplugged the modem from my PC, then reset the Netgear router to factory, and plugged it in to the PC. Logged on, changed Wifi settings to my own (SSID, password etc). Note at this stage, the DHCP on the Netgear router is still disabled. I then changed it's IP to my own personalised one. To my surprise, after applying that, I was able to login again afterwards (which previously I hadn't been able to do - as I'd mentioned a couple of posts earlier). I then enabled the DHCP server on the Netgear, after which I was unable to login to it again.

Anyway, I unplugged it from my PC, then plugged the modem into the WAN port on the router. No network access at all. I tried plugging it into one of the LAN ports on the router. Was able to establish a local connection but still no internet. So I gave up and just decided to reload the settings on both. The Netgear I knew I would have to do another factory reset just to be able to login again. But now even the modem wouldn't let me login, so I had to do a factory reset on that too.

So now they're both back on the settings I was using before (as how I mentioned in post #17), not ideal but it's the only way that I can get it to work.

If anyone can provide some clear-cut instructions on getting this to work I would be very grateful!
Sam Bos (12456)
1 2 3