![]() ![]() ![]() |
|
DarkShadow:
Bigpipe UFB on WiFi
traceroute to 12.129.222.10 (12.129.222.10), 64 hops max, 52 byte packets
1 192.168.5.254 (192.168.5.254) 4.018 ms 6.770 ms 9.151 ms
2 100.68.x.x (100.68.x.x) 8.995 ms 13.387 ms 9.391 ms
3 * * *
4 * * *
5 * * *
6 ae11-201.tkbr11.global-gateway.net.nz (122.56.118.149) 14.328 ms 9.214 ms 9.020 ms
7 ae0-10.tkbr12.global-gateway.net.nz (203.96.120.105) 5.970 ms 7.563 ms 7.050 ms
8 203.96.120.142 (203.96.120.142) 142.141 ms
xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 138.525 ms 132.728 ms
9 ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 135.080 ms
ae3-10.lebr7.global-gateway.net.nz (122.56.127.26) 135.562 ms
ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 137.842 ms
10 las-b21-link.telia.net (62.115.145.206) 149.736 ms 159.535 ms 144.787 ms
11 att-ic-153025-las-bb1.c.telia.net (80.239.193.214) 145.100 ms 152.634 ms 147.005 ms
12 cr2.la2ca.ip.att.net (12.122.129.98) 146.186 ms 147.810 ms
att-ic-153025-las-bb1.c.telia.net (80.239.193.214) 151.130 ms
13 12.123.249.73 (12.123.249.73) 140.673 ms 142.840 ms 144.774 ms
14 * 12.123.249.73 (12.123.249.73) 143.114 ms *
15 * * 12-122-254-230.attens.net (12.122.254.230) 143.640 ms
16 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 143.629 ms
206.16.68.50 (206.16.68.50) 143.478 ms
12.122.251.190 (12.122.251.190) 142.936 ms
17 * 206.16.68.50 (206.16.68.50) 145.257 ms *
18 * * *
19 * * *
20 * * *
21 * * *
traceroute to 12.129.222.10 (12.129.222.10), 64 hops max, 52 byte packets
1 192.168.5.254 (192.168.5.254) 5.252 ms 4.311 ms 2.895 ms
2 100.68.x.x (100.68.x.x) 7.299 ms 8.052 ms 10.264 ms
3 * * *
4 * * *
5 * * *
6 ae11-201.tkbr11.global-gateway.net.nz (122.56.118.149) 9.890 ms 16.936 ms 14.528 ms
7 ae0-10.tkbr12.global-gateway.net.nz (203.96.120.105) 7.769 ms 7.848 ms 9.113 ms
8 xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 135.111 ms
203.96.120.142 (203.96.120.142) 140.308 ms
xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 131.684 ms
9 ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 130.795 ms
ae3-10.lebr7.global-gateway.net.nz (122.56.127.26) 137.181 ms
ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 137.089 ms
10 las-b21-link.telia.net (62.115.145.206) 149.871 ms 142.764 ms 158.194 ms
11 att-ic-153025-las-bb1.c.telia.net (80.239.193.214) 145.715 ms 146.500 ms 151.931 ms
12 cr2.la2ca.ip.att.net (12.122.129.98) 151.680 ms 146.879 ms 151.093 ms
13 cr2.la2ca.ip.att.net (12.122.129.98) 156.409 ms
12.123.249.73 (12.123.249.73) 147.794 ms 141.686 ms
14 * * *
15 12-122-254-230.attens.net (12.122.254.230) 140.556 ms * *
16 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 144.987 ms
206.16.68.46 (206.16.68.46) 210.737 ms
mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 148.632 ms
17 * * *
18 * * *
19 * * *
20 * * *
Those are some nice tracerts.
hio77:
ctucks:
Sounds a little complicated. Right now we're using the Netcomm NF4V that Orcon supplied us with. I'm not sure what kind of VPN capabilities it has, but regardless, that's a little out of my depth as far as internet knowledge is concerned. Are there any key words / processes that you can request of your ISP to tinker with routing? or is it, like mentioned above, very out of my control?
Definitely a little bit too much for a NF4V.
I would recommend a well written email to the NOC team, include as much detail without it being simply a wall of pointless tests.
Going through Customer support is most likely to get death ears.
As I said above, your most likely not to have any positive result however.
I also wanted to ask, instead of making a new topic, how much of a difference can bad wiring affect attenuation? There's a cabinet not too far from us, and yet our downstream attenuation is 28.1db. Which, if the calculation I'm using is correct, is roughly 2km. However, the distance to the cabinet is far less than this. I'm not sure if it's just taking a bad path, or there is a problem with our wiring.
Regardless, we're going to get a master filter installed to see if that helps with anything. Hopefully the engineer that comes along can take a quick look to see if our wiring is up to scratch.
ctucks:
I also wanted to ask, instead of making a new topic, how much of a difference can bad wiring affect attenuation? There's a cabinet not too far from us, and yet our downstream attenuation is 28.1db. Which, if the calculation I'm using is correct, is roughly 2km. However, the distance to the cabinet is far less than this. I'm not sure if it's just taking a bad path, or there is a problem with our wiring.
Regardless, we're going to get a master filter installed to see if that helps with anything. Hopefully the engineer that comes along can take a quick look to see if our wiring is up to scratch.
Remember MDF layouts arent always logical in a lowest distance sense.
Bad wiring can make a massive difference.
Take my old flat, i was getting 2/3 on VDSL Due to dodgy wiring that chorus didnt want to deal with. After quite a fight in getting it resolved, i had a solid 60/10 (this was back in the 997 days when 60/10 was all you could get, that line would have easily maxed out.)
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:
ctucks:
I also wanted to ask, instead of making a new topic, how much of a difference can bad wiring affect attenuation? There's a cabinet not too far from us, and yet our downstream attenuation is 28.1db. Which, if the calculation I'm using is correct, is roughly 2km. However, the distance to the cabinet is far less than this. I'm not sure if it's just taking a bad path, or there is a problem with our wiring.
Regardless, we're going to get a master filter installed to see if that helps with anything. Hopefully the engineer that comes along can take a quick look to see if our wiring is up to scratch.
Remember MDF layouts arent always logical in a lowest distance sense.
Bad wiring can make a massive difference.
Take my old flat, i was getting 2/3 on VDSL Due to dodgy wiring that chorus didnt want to deal with. After quite a fight in getting it resolved, i had a solid 60/10 (this was back in the 997 days when 60/10 was all you could get, that line would have easily maxed out.)
find the ETP and either install a master filter with dedicated wiring to a dedicated xDSL jackpoint or disconnect all other wiring and run fresh wiring to a new xdsl jack point
Jase2985:
find the ETP and either install a master filter with dedicated wiring to a dedicated xDSL jackpoint or disconnect all other wiring and run fresh wiring to a new xdsl jack point
ctucks:
Damn, that's a huge improvement! How did you go about fixing your wiring? Or at least troubleshooting it? Was it something you did yourself? We're pretty keen to get our internet sorted out, and haven't had to go through repair procedures before.
While its something i am personally more than capable of doing, i hounded chorus for a good month or so to get it done as they were originally requested to do.
As part of my rental agreement there, i was not allowed to personally do it. i respectfully followed this request.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
|
![]() ![]() ![]() |