Upstream attenuation halved?

[gymno]

Many thanks for your input snadge.
This attenuation thing certainly is a head scratcher, but already you've found more info on it than i could after hours of searching.

I checked my pings at 11pm last night & they were/are back to normal, so the hike lasted less than 48hrs.

Something's definitely going on with my line though, as my WAN uptime indicates i had a re-sync at 5:55 a.m. this morning. System uptime remains unchanged so wasn't a power cut. I guess it could be DLM but would expect that to re-sync around 3 a.m. Plus i have the same stats as before, complete with the 8.0db upstream attenuation, so i doubt it.

TBH, the only thing that's actually annoying me at the mo is the routers really slow GUI.
I know it's something that every user (apart from me, apparently) seems to have always had, but it only started after i DMZ'd my ps3.

Is it normal for it to slow down after making just 1 little change like that?

Also, i disabled UPNP on the ps3, thinking it could only interfere with the DMZ settings. Does anyone know if there's a general consensus this? Probably a noob question, but i assume UPNP needs to be left enabled on the router?

[snadge]

unfamiliar with PS3 etc, I dont even know what DMZ is or means?-?-?-? lol

BUT , having googled it I now know, your basically manually assigning an IP to the PS3 and putting that IP into DMZ in router which allows open access to it - bit like opening a port on a firewall I suppose..?!?

if the routers GUI is slow after connecting your PS3 then it sounds like the settings maybe incorrect or there is a lot of traffic to/from router/s3 as your trying to access it

[NilSatisOptimum]

I too have wobbly up attenuation, between 18db-33db and anything in between to date, 29db after re-sync today , SNR always bang on 10 and pumps out 800kbps!

[gymno]

So after 3 days with my pings back to the 24ms i've always been used to, i now have this

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=43.9 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=51.5 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=45.9 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=48.9 ms

5 seconds later & it's this:

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=28.0 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=33.2 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=25.4 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=26.9 ms.

Could it really be a backhaul problem?

[gymno]

OMG.
I've never had anything like this before

PING 173.194.34.166 (173.194.34.166): 56 data bytes
56 bytes from 173.194.34.166: icmp_seq=0 ttl=58 time=118.3 ms
56 bytes from 173.194.34.166: icmp_seq=1 ttl=58 time=124.3 ms
56 bytes from 173.194.34.166: icmp_seq=2 ttl=58 time=118.2 ms
56 bytes from 173.194.34.166: icmp_seq=3 ttl=58 time=130.8 ms

That was google.com.
It's the same at bbc.co.uk aswell now. 97ms - 117ms

ADSL Link Downstream Upstream
Connection Speed 19999*kbps 1175*kbps
Line Attenuation 23.0*dB 8.0*dB
Noise Margin 6.7*dB 9.4*dB

- - - Updated - - -

[gymno]

LOL

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=113.4 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=429496595.1 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=120.6 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=121.2 ms

--- 212.58.241.131 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 113.4/55.1/429496595.1 ms

Where did it get the avg 55.1 from?
Do i have a faulty router?
Has anyone ever seen anything like this?

In the last 3 months, i've managed to get 16 good days out of my broadband.
I honestly don't know what to do now

[Isitme]

Something wrong with the arithmetic somewhere -
Minimum 113.4
Maximum 429496595.1
Average 55.1 ?????
Maybe it was so fed up it could not be bothered calculating it.

It looks like even after all you have gone through there is still a fault on your line

[gymno]

Back to this now

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=24.4 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=25.4 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=24.9 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=25.2 ms

--- 212.58.241.131 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 24.4/24.9/25.4 ms

I'll have to give sky a call tomorrow *sigh*

Any advice before i do?
I've no pc here, just my ps3 so can't provide traceroutes or talk to them about hops etc.
(i prefer a crisp lager anyway)
Can CST do things like ping my ip address & look for bottlenecks or anything?
Without a pc, i can see this one being a bit tricky...

[Isitme]

I honestly don't know how accurate this is or if it will help, but might want to try this site - Networktools: Reverse IP Lookup, Whois, Ping, RBL Check, DNS Records, Traceroute, Host information

[gymno]

Thanks isitme.
Unfortunately, i was advised by flamey on the sky forum many moons ago that reverse trace takes a different route & so shouldn't be used for that kind of thing.

Still, i've been going to a similar site though, just to be nosy, whenever i've had an ip change:
Traceroute, Ping, Domain Name Server (DNS) Lookup, WHOIS

I'll post the results from both sites when i get the chance.
Cheers.