IP Banded...Again

I have a 8mg profile and this marks the third time I have been banded down.

Last December I was down to 256k and again this past March. I guess I should be happy that I'm amazingly at 1144k but this is getting tiresome.

I guess this situation needs to be resolved with Orange's 'amazing' customer service. Goodbye week of internet.

Strangely enough according to the logs I my internet has disconnected at around the same time for the past three days. I haven't even been home when they occurred so perhaps it is a faulty line.

Anyways here are some details.
ADSL Firmware Version 3.4.4.0.0.1
Modem Status Connected
DownStream Connection Speed 1144 Kbps
UpStream Connection Speed 967 Kbps
VPI 0
VCI 38

ADSL Link Downstream Upstream
Connection Speed 1144 Kbps 967 Kbps
Line Attenuation 30.4 dB 16.4 dB
Noise Margin 32.5 dB 9.6 dB

Here is my BTW Performance Test

1. Best Effort Test: -provides background information.

Download Speed
0.9 Mbps

0 Mbps 1 Mbps
Max Achievable Speed

Download speedachieved during the test was - 0.9 Mbps
For your connection, the acceptable range of speeds is 0.4 Mbps-1 Mbps.
IP Profile for your line is - 1.01 Mbps

2. Upstream Test: -provides background information.

Upload Speed
0.15 Mbps

0 Mbps 0.83 Mbps
Max Achievable Speed

Upload speed achieved during the test was - 0.15Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps

Speed test and IP Profile are no use to you. It's your Sync Speed that is being held down by this unnecessarily high:

In reply to a post by MachoRick:

Noise Margin 32.5 dB 9.6 dB

Orange are prone to doing that. You need to get on to their Fault management Team to release your Target NM.

Thanks.

I'll ring them up.

It's all well and good getting the profile reset, but what you REALLY need EE to address/resolve is WHY it keeps being banded.

Yeah it is very strange. For a couple of months it will be great and then all of a sudden. My road has been getting a lot of road works so I don't know if that has anything to do with it or just random interference or what.

I woke up this morning after leaving everything untouched to see that my connection had only been up for 2 hours. This time however my WAN and LAN was also reset (it had been at 600+ hours of continued connection). My upstream had also increased from 876 to 1000 something. Hopefully it is starting to stabilize. Will continue to monitor.

In reply to a post by MachoRick:

My upstream had also increased from 876 to 1000 something.

Due to switch from Interleaved to Fast Path.

Does this mean my connection could improve or is it simply an AM vs PM occurrence?

Neither! I mean only what I said.

If you can get the full router stats from your Netgear, I think, via TELNET you will see what I mean.

Okay, gotcha.

Will check when I get home tonight. Thanks.

Got home and checked my log. I have pasted it below:

Sat, 2000-01-01 00:00:31 - Upnp set event: redirecting port from 32255 to 192.168.0.2:32255 protocol TCP for: uTorrent (TCP)
Sat, 2000-01-01 00:00:31 - UPnP set event: removing redirect rule port, port:32255 protocol:TCP
Sat, 2000-01-01 00:00:31 - Upnp set event: redirecting port from 32255 to 192.168.0.2:32255 protocol TCP for: uTorrent (TCP)
Sat, 2000-01-01 00:00:38 - DHCP IP: 192.168.0.3 to MAC address 30:85:A9:60:3C:2B
Sat, 2000-01-01 00:01:09 - DHCP IP: 192.168.0.4 to MAC address AC:72:89:89:A7:3D
Sat, 2000-01-01 00:01:15 - Initialize LCP.
Sat, 2000-01-01 00:01:15 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:15 - LCP down.
Sat, 2000-01-01 00:01:18 - [Internet disconnected]
Sat, 2000-01-01 00:01:19 - Initialize LCP.
Sat, 2000-01-01 00:01:19 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:20 - CHAP authentication success
Sat, 2000-01-01 00:01:20 - [Internet connected] IP address 2.27.77.208
Sat, 2000-01-01 00:01:27 - Send out NTP request to time-g.netgear.com
Mon, 2013-04-29 15:12:55 - Receive NTP Reply from time-g.netgear.com
Mon, 2013-04-29 15:12:57 - Upnp set event: redirecting port from 62369 to 192.168.0.2:62369 protocol UDP for: Teredo
Mon, 2013-04-29 15:12:57 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:13:00 - DHCP IP: 192.168.0.4 to MAC address AC:72:89:89:A7:3D
Mon, 2013-04-29 15:13:34 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:13:59 - UDP Packet - Source:208.78.158.71,56065 Destination:2.27.77.208,63834 - [DOS]
Mon, 2013-04-29 15:13:59 - UDP Packet - Source:208.78.158.72,56055 Destination:2.27.77.208,63834 - [DOS]
Mon, 2013-04-29 15:14:50 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:19:33 - DHCP IP: 192.168.0.5 to MAC address A4:C0:E1:02:5A:3A
Mon, 2013-04-29 15:11:27 - Router start up
Mon, 2013-04-29 15:27:13 - DHCP IP: 192.168.0.4 to MAC address AC:72:89:89:A7:3D
Mon, 2013-04-29 15:27:22 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:31:49 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:31:59 - UPnP set event: removing redirect rule port, port:0 protocol:TCP
Mon, 2013-04-29 15:31:59 - Upnp set event: redirecting port from 32255 to 192.168.0.2:32255 protocol TCP for: uTorrent (TCP)
Mon, 2013-04-29 15:31:59 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:31:59 - Upnp set event: redirecting port from 32255 to 192.168.0.2:32255 protocol UDP for: uTorrent (UDP)
Mon, 2013-04-29 15:31:59 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 15:54:40 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:03:18 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:14:19 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:23:57 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:32:17 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:32:50 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:37:16 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:37:53 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:39:05 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:43:27 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:44:01 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:44:35 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:45:07 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:48:09 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:49:20 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:51:03 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:54:47 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:55:21 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 16:55:28 - Administrator login successful - IP:192.168.0.2
Mon, 2013-04-29 16:55:52 - UPnP set event:AddPortMapping from source 192.168.0.2







Apparently the millennium just happened?

Thought I would post here to see if anyone has any experience with this type of log?

So what's the problem with it? It all looks normal.

Most routers start with some "zero" date when they boot up, until the get the true date from a time server (NTP).

Oh I see, wasn't sure if that was normal or not.

A bit more excitement from 5pm this evening with some disconnects. Not really sure what happened there.

on, 2013-04-29 17:01:13 - Administrator login successful - IP:192.168.0.2
Mon, 2013-04-29 17:01:42 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:02:25 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:02:56 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:03:31 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:04:06 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:04:47 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:05:29 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:08:29 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:09:05 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:09:49 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:10:24 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:10:59 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:11:18 - UPnP set event: removing redirect rule port, port:32255 protocol:TCP
Mon, 2013-04-29 17:11:18 - UPnP set event: removing redirect rule port, port:32255 protocol:UDP
Mon, 2013-04-29 17:11:23 - Administrator login successful - IP:192.168.0.2
Mon, 2013-04-29 17:11:30 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:12:03 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:12:43 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:13:16 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:13:52 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:14:26 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:14:59 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:15:32 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:16:11 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:16:47 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:17:27 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:18:02 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:18:35 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:19:20 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:20:04 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:20:08 - LCP down.
Mon, 2013-04-29 17:20:11 - [Internet disconnected]
Mon, 2013-04-29 17:20:48 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:21:04 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:21:20 - UPnP set event:AddPortMapping from source 192.168.0.2
Mon, 2013-04-29 17:21:52 - UPnP set event: removing redirect rule port, port:55771 protocol:UDP
Mon, 2013-04-29 17:21:52 - UPnP set event:DeletePortMapping from source 192.168.0.2
Mon, 2013-04-29 17:23:20 - [Internet disconnected]
Mon, 2013-04-29 17:23:20 - Initialize LCP.
Mon, 2013-04-29 17:23:20 - LCP is allowed to come up.
Mon, 2013-04-29 17:23:20 - CHAP authentication success
Mon, 2013-04-29 17:23:20 - UPnP set event: removing redirect rule port, port:21828 protocol:
Mon, 2013-04-29 17:23:21 - [Internet connected] IP address 2.25.220.3




and an updated router status
System Up Time 02:51:01
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 9568 11195 0 932 3364 00:39:09
LAN 10M/100M 556757 798530 0 8801 43818 02:50:41
WLAN 11M/54M/150M 22698 7632 0 326 59 02:50:45

ADSL Link Downstream Upstream
Connection Speed 1144 Kbps 1211 Kbps
Line Attenuation 30.4 dB 16.3 dB
Noise Margin 30.6 dB 6.3 dB

In reply to a post by XRaySpeX:

In reply to a post by MachoRick:

My upstream had also increased from 876 to 1000 something.

Due to switch from Interleaved to Fast Path.

Not so! My great upstream speed 1243 (Kbps) has returned on interleaved path without any intervention from me.
My downstream has decreased though, but I don�t mind that, it�s the high upstream speed that gives me a stable connection for running BBC iPlayer ect.

ADSL Status
This page shows information about your ADSL connection if applicable.
Status
Configured Current
Line Status --- SHOWTIME
Link Type --- Interleaved Path
Operation Mode Automatic G992.5(ADSL2+)

Data Rate Information
Stream Type Actual Data Rate
Upstream 1243 (Kbps.)
Downstream 9722 (Kbps.)

Defect/Failure Indication
Operation Data Upstream Downstream
Noise Margin 5.5 dB 6.8 dB
Line Attenuation 15.7 dB 29.0 dB

Indicator Name Near End Indicator Far End Indicator
Output Power 12.5 dBm 0.0 dBm
Fast Path FEC Correction NA NA
Interleaved Path FEC Correction 13138 0
Fast Path CRC Error NA NA
Interleaved Path CRC Error 6 0
Loss of Signal Defect 0 0
Fast Path HEC Error STR NA NA
Interleaved Path HEC Error 14 0
Error Seconds 6 0
Statistics
Received Cells 440838
Transmitted Cells 42919

With regard to your downstream sync are you saying that interleaving has reduced the speed from 13377Kbps to 9722Kbps?

I said that 876K implies Interleaved, not that Interleaved implies 876K. There's a name for this fallacy but I can't think of it at the mo'.

In reply to a post by 4M2:

With regard to your downstream sync are you saying that interleaving has reduced the speed from 13377Kbps to 9722Kbps?

I am saying I am not so concerned with the downstream more the upstream.

On interleaved path my upstream speed reduced to 888 (Kbps) and at times BBC iPlayer would not run. Now the upstream has increased to 1243 (Kbps) my connection is stable and I am now able to run BBC iPlayer without any problems, even though the downstream has decreased to 9722 (Kbps).

My previous stats when I had the upstream problem...
ADSL Status
This page shows information about your ADSL connection if applicable.
Status
Configured Current
Line Status --- SHOWTIME
Link Type --- Interleaved Path
Operation Mode Automatic G992.5(ADSL2+)

Data Rate Information
Stream Type Actual Data Rate
Upstream 888 (Kbps.)
Downstream 13365 (Kbps.)

Defect/Failure Indication
Operation Data Upstream Downstream
Noise Margin 16.3 dB 4.9 dB
Line Attenuation 15.6 dB 29.5 dB

Indicator Name Near End Indicator Far End Indicator
Output Power 12.3 dBm 0.0 dBm
Fast Path FEC Correction NA NA
Interleaved Path FEC Correction 99715081 1447
Fast Path CRC Error NA NA
Interleaved Path CRC Error 766246 103394
Loss of Signal Defect 0 0
Fast Path HEC Error STR NA NA
Interleaved Path HEC Error 643861 35596
Error Seconds 12013 12360
Statistics
Received Cells 1149350
Transmitted Cells 240726

Looks as if it was the upstream SNRM that was holding back your upstream sync speed previously, i.e. was 16.3dB now 5.5dB, since both stats show interleaving.

Possibly noise was affecting the line causing issues with iPlayer and now adjustments have been made to the downstream sync speed (reduced power?) to relieve that issue and also as a consequence the upstream SNRM has reduced hence increasing the upstream speed.

Perhaps interleaving, as such, had little or no influence on the iPlayer problem?

You are confusing cause with effect.

You line was unstable with the previous stats probably due to the low Down NM and high # of ESs; nowt to do with the low upstream sync which hardly comes into play with streaming which is predominantly downstream.