You seem to be saying ISPs/CPs should not have any information about what speed a customer's line is running at and whether or not it is connected. Including LLU where the DSLAM/MSAN belongs to them.

Uh?

(Edit - re PPP session, as this is established at the CP kit hiding it from them could be difficult, and their not monitoring it would seems to be a very odd approach).

Edited by RobertoS (Tue 09-Apr-13 09:05:05)

You also seem to be saying it should be compulsory for all IP addresses to be static.

Uh?

no, they can do what they want.

But I consider a more modern approach to dynamic ips is where they have a lease eg. as on virgin media and on sky. In that approach they generally dont change for short outages such as a resync event.

Given the ipv4 shortage now, it can never be compulsory.

In reply to a post by tommy45:

I am quite suprised that no one has so far suggested asking the ISP to manually set the target margins, and disable DLM as ISP's can now and also make sure the IP profile is set up and correct for the sync afterwards do this with BT wholesale adsl2 + products, Saves the all the faffing around waiting for this and that to maybe happen ect ect, and runing a risk of ending up with a call out bill from BT

Problem is we don't really know much about the OP's home wiring, she states early on in this thread that she doesn't have a NTE5 and presumably has the micro filter/router connected to a phone socket. So requesting the ISP to manually set the target margins etc. may indeed be one approach but personally I would rather check initially that the feed from an external junction box (?) to the phone socket (?) is in sound condition (e.g. no corrosion, a twisted pair, etc.) and that there are not any other unfiltered extensions or star wiring issues before proceeding any further...

Thanks to everyone for their input/help.

My OH has checked the wiring and this has now been ' sorted' , if you get my drift.
There was an improvement in my connection as you can see from my stats below:


System Up Time 3 days 04:31:01
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 43184 54840 0 83 683 22:17:51
LAN 100M/Full 790023 795198 0 7394 1278 22:17:52
WLAN 11M/54M 339488 117237 0 780 44 3 days 04:31:01

ADSL Link Downstream Upstream
Connection Speed 13976 kbps 1243 kbps
Line Attenuation 20.0 db 10.0 db
Noise Margin 9.00 db 5.5 db

Maybe the previous socket had become faulty ??? Still no where near the sync of 18000 Kbps I had before this all started back in February.

Unfortunately, I had another loss of 'IP address' last night after being connected for over 9 hrs or so - red light on router for approx. 45 mins until just pressed 'reconnect' in the Router status section. No drop in synch, no drop to zero noise margins, noise etc have been recorded by RouterStats- everything remained unchanged. From this I presume I'm right to say that I was still connected to the exchange?? Bearing in mind my ISP comments re the previous losses of the IP address, I'm not too sure if they will take any notice of this latest episode, let alone take any notice of the RouterStats info. Surely two routers cannot both be faulty??

I have got a new Netgear router which I will be connecting at the weekend just in case!! It will be interesting to see if the same losses if IP address continue??

We will see

Edited by deleted (Thu 11-Apr-13 19:46:25)

Is RouterStats showing the downstream noise margin to fluctuate by a considerable amount or is it fairly stable at about 9dB? In other words, for example, after dark does it reduce to around 6dB then return to around 9dB during daylight hours, or fluctuate erratically by 3dB or more at anytime, or remain within 1dB of 9dB throughout a full 24 hour period?

In amswer to your query, I can confirm that the downstream noise margin does not fluctuate wildy. It remains fairly stable around 9 dB (9.1 to 8.8 dB) with no drastic deviations at all. Unfortunately I don't run RouterStats 24 hrs but it has been operational up to 21.00 - 21.30 hrs so has operated in the 'dark' nighttime hrs.

Thanks

I suspect that the 9dB SNRM and improved speed was due to a resync after "My OH has checked the wiring and this has now been ' sorted'" and the SNRM may now be gradually lowering and which also does appear to be very stable

See how you get on with the new Netgear router at the weekend and when that is booted and sync'd to the exchange hopefully you may see the downstream SNRM at 6dB and your sync speed back to it's previous ~18000Kbps level. The loss of PPP link events will hopefully also be considerably reduced.

Good luck

New Netgear router has been up and running since last Sunday. My connection was slightly faster than previous at over 14.6 Mbs. Unfortunately it dropped the connection on Mon (noise upstream) but has been stable ever since. I've decided to sit it out for a couple of weeks and see what happens. Have noted what has been said previously and will wait the 14+ days to see if my SNRM gets lowered. So far it has not, can't help wondering if my connection speed has been 'banded'?? Previously, the DLM automatically kicked in adjusting the SNR/speed up/down as necessary. Will just have to be patient I suppose!! I have told my ISP that I'll be back if nothing changes as I do feel my connection is under-performing.

Listed below are my most recent stats:

System Up Time 190:42:43
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 832668 1186211 0 223 1958 168:17:38
LAN1 100M/Full 2220317 1769152 0 2252 400 190:40:36
LAN2 Link down
LAN3 100M/Full
LAN4 Link down
WLAN 145M 963015 391981 0 1238 64 190:02:35

ADSL Link Downstream Upstream
Link Rate 14383 Kbps 1043 Kbps
Line Attenuation 17.5 dB 10.8 dB
Noise Margin 10.3 dB 9.8 dB

Let's wait and see

In some respects your stats are worst: previous downstream attenuation reported by the router was 20dB, now you are only seeing an increase of ~400Kbps with an attenuation of 17.5dB. The difference in attenuation figures may be due to the way differing routers "see" the loop loss though.

Upstream noise margin has increased so a drop in upstream sync speed is the result although the attenuation is very similar to that previously reported by the other router.

I would say that you still have a problem with line, not serious but sufficient to reduce your sync speeds, particularly the downstream significantly. A 17.5db downstream attenuation should ideally with a 6dB noise margin give you a sync speed of 20000Kbps or more on ADSL2+.

Perhaps the next step might be to have a NTE5 master socket fitted together with the phone wire from a junction box (?) to the master NTE5 being inspected and replaced if necessary. Then you will be able to check your connection speeds etc. from a test socket and if there is no improvement then an OR engineer could check your line from the test socket to the exchange, however if your sync speed stays at around 14 to 15Mbps and the DSL doesn't drop frequently then an ISP may be very reluctant to book an engineer.