Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 16 17 [18] 19 20 ... 22

Author Topic: FTTC woes  (Read 64402 times)

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #255 on: July 21, 2015, 12:02:52 PM »

This engineer's tests passed and so as is becoming a pattern, he couldn't really do anything :no:

We now have an unhacked HG612 though! ;D
Logged

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: FTTC woes
« Reply #256 on: July 21, 2015, 12:03:29 PM »

On upstream as well as downstream

Is that important?
Yes, it means your upstream will benefit from G.INP too, making your connection faster and more stable.
Logged

spudgun

  • Reg Member
  • ***
  • Posts: 143
Re: FTTC woes
« Reply #257 on: July 21, 2015, 12:34:37 PM »

Upstream G.INP is turned off by default now though
Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #258 on: July 21, 2015, 12:36:20 PM »

Oh well mine was definitely turned on.
Logged

spudgun

  • Reg Member
  • ***
  • Posts: 143
Re: FTTC woes
« Reply #259 on: July 21, 2015, 12:40:53 PM »

By default, downstream G.INP is on and upstream G.INP is off - this explains why you were asked about it in the thread earlier. It would be a surprise if you are G.INP enabled on both the upstream and downstream
Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #260 on: July 21, 2015, 12:43:34 PM »

54 on the downstream and 42 on the upstream :)
Logged

spudgun

  • Reg Member
  • ***
  • Posts: 143
Re: FTTC woes
« Reply #261 on: July 21, 2015, 12:49:31 PM »

I hope that it helps with stability for you as having read through the many pages of this thread it isn't 100% conclusive that there is a fault (probably why the engineers have been of little help) and you may just have a crappy line.

I know first hand how disappointing it can be when a line doesn't live up to expectations, and hopefully the FTTP on demand prices will come down to realistic levels soon so that you can have some guaranteed performance :)
Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #262 on: July 21, 2015, 01:47:46 PM »

Well if I have a crappy line I'm sure with enough pressure OR will eventually change it all! :)
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4898
Re: FTTC woes
« Reply #263 on: July 21, 2015, 05:12:23 PM »

Was the engineer able to tell you the distance from your Master Socket to the cabinet via his/her JDSU ?
Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #264 on: July 21, 2015, 05:13:26 PM »

My JDSU says 850m.
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: FTTC woes
« Reply #265 on: July 21, 2015, 05:19:14 PM »

By default, downstream G.INP is on and upstream G.INP is off - this explains why you were asked about it in the thread earlier. It would be a surprise if you are G.INP enabled on both the upstream and downstream

There have been recent reports of some users who had initially G.INP Mk1 applied (DS & US), then having US G.INP removed (Mk 2) & very recently having it applied to US again (Mk 3?).

I didn't realise that AlecR was still using SP10.
It seems that was finally updated (probably to SP08) to allow G.INP, but his new SP06 modem needs unlocking in order to see the stats.


I believe that G.INP can actually be active on SP06 HG12s.
If I'm not mistaken, WWWombat, for example, has G.INP active on his SP06 HG612.



Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #266 on: July 21, 2015, 05:25:01 PM »

I went live with FTTC in June, the cabinet had only been alive for a week or so. I believe I was the first line on the cabinet to be enabled.

I have never had G.INP and I don't believe the cabinet ever did either.

This morning my connection dropped and G.INP had been enabled. I could see this because my HG612 (purchased from eBay) had been hacked and was running (I am fairly sure) the B030SP08 firmware from Howlingwolf.

Looking at the INP levels on MyDSLWebStats, we can see 54.00 for the downstream and 42.00 for the upstream. So it looks like I have it on both - this is not supposed to happen is it?

The Openreach engineer today replaced that hacked modem with another HG612 ("...to make it look like I've done something...") which, from looking at the bottom, is running SP06 firmware. I believe my hacked HG612 was originally running SP10 firmware.

Do I need to do anything now? I'm going to put the Billion 8800NL (replacement) back on in a day or so anyway probably as I miss being able to see the stats :(
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: FTTC woes
« Reply #267 on: July 21, 2015, 05:25:52 PM »

My JDSU says 850m.

You have your own JDSU?

Can we see some photos/screenshots of its stats?

Does it have the TDR function that might identify line 'faults' (& their location)?

Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4898
Re: FTTC woes
« Reply #268 on: July 21, 2015, 05:29:57 PM »

My JDSU says 850m.

Your on a long line then your current stats on MDWS looks ok and a sync of 40000kbps is nothing to sniffed at.

Clould you recap on what the issue is again as your thread is quite large.
Logged

GigabitEthernet

  • Kitizen
  • ****
  • Posts: 2243
Re: FTTC woes
« Reply #269 on: July 21, 2015, 05:30:24 PM »

You have your own JDSU?

Yes, it's an ex-Openreach JDSU by the looks of it.

Can we see some photos/screenshots of its stats?

I would take some but I've already had at least four connection drops today so I'd rather not upset DLM any further today :)

Does it have the TDR function that might identify line 'faults' (& their location)?

I don't know how to access that nor how to use it :(
Logged
Pages: 1 ... 16 17 [18] 19 20 ... 22