I had one line connected no problems at all. When nDSL was released in Jan, I jumped on it.
It appears to be a hue mistake, since then I am having voice quality issues, and cannot "switch" between calls. Xnet helpdesk get me to monitor it for a few days, give them times and dates of the calls that were doing it.
Did all that, xnet said "We'll ring you back when the tech team have had a look" a week went by, rang xnet back again, "oh, the tech team couldn't find anything wrong, its a fault with your hardware"
So I complained again, and again, now they say some packets are being lost, and for me to do a trace route. Downloaded the program, pinging google.co.nz results:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 3412 | 3412 | 0 | 1 | 343 | 0 |
| ip-58-28-15-31.wxnz.net - 0 | 3412 | 3412 | 46 | 53 | 438 | 47 |
| ip-58-28-13-83.wxnz.net - 0 | 3412 | 3412 | 46 | 51 | 2031 | 47 |
| ge-0-0-0-akl-core1.wxnz.net - 1 | 3412 | 3383 | 46 | 52 | 547 | 62 |
| Gi9-1.gw1.AKL1.asianetcom.net - 0 | 3412 | 3412 | 46 | 51 | 562 | 47 |
| po8-3.gw1.sjc1.asianetcom.net - 0 | 3412 | 3412 | 170 | 176 | 1483 | 172 |
| 74.125.49.97 - 0 | 3412 | 3412 | 171 | 192 | 1062 | 188 |
| 216.239.46.192 - 0 | 3412 | 3412 | 201 | 207 | 984 | 203 |
| 66.249.95.212 - 0 | 3412 | 3412 | 248 | 270 | 2217 | 266 |
| 72.14.238.137 - 1 | 3412 | 3411 | 233 | 250 | 2124 | 234 |
| 216.239.48.68 - 0 | 3412 | 3412 | 233 | 268 | 2045 | 1220 |
| 72.14.236.200 - 1 | 3412 | 3411 | 233 | 273 | 1186 | 282 |
| 216.239.48.190 - 1 | 3412 | 3402 | 264 | 279 | 2061 | 266 |
| od-in-f104.google.com - 1 | 3411 | 3402 | 264 | 279 | 1983 | 282 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
From this I read 1% loss at od-in-f104.google.com, 216.239.48.190, 72.14.236.200, 72.14.238.137 and ge-0-0-0-akl-core1.wxnz.net
Pinging 58.28.20.150:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 2487 | 2486 | 0 | 4 | 188 | 0 |
| ip-58-28-15-31.wxnz.net - 0 | 2487 | 2487 | 46 | 58 | 578 | 63 |
| ip-58-28-13-83.wxnz.net - 0 | 2487 | 2487 | 46 | 55 | 578 | 47 |
| ge-0-0-0-akl-core3.wxnz.net - 1 | 2487 | 2486 | 46 | 55 | 594 | 47 |
| pan.wxnz.net - 1 | 2487 | 2482 | 46 | 57 | 578 | 47 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
From this I read 1% loss at 192.168.1.1, ge-0-0-0-akl-core3.wxnz.net and pan.wxnz.net.
To which I got told "oh its something to do with your lan, see 1% loss at your end"
Do I get the feeling Xnet are trying to blame my hardware rather than looking into actually fixing the problem?
They ignored my comment "When I had just the one line there were no issues"