Be Fucked?

friznit · Post by **friznit** » May 15th, 2008, 20:50

I've been on Bethere for about 2 months now without problems - good, fast and reliable. Last couple of days though I've started getting ~25% packet loss, which makes quite a lot of games unplayable, apart from being generally fucking annoying. Can't see anything on their webshite about serve problems...so any ideas?

London W5 area btw

Settings:

Code: Select all

Uptime:	0 days, 0:55:08
Modulation:	G.992.5 Annex A
Bandwidth (Up/Down) [kbps/kbps]:	1,295 / 6,969
Data Transferred (Sent/Received) [MB/MB]:	3.45 / 29.29
Output Power (Up/Down) [dBm]:	12.0 / 18.0
Line Attenuation (Up/Down) [dB]:	18.5 / 35.5
SN Margin (Up/Down) [dB]:	6.5 / 6.5
Vendor ID (Local/Remote):	TMMB / µ
Loss of Framing (Local/Remote):	0 / 0
Loss of Signal (Local/Remote):	0 / 0
Loss of Power (Local/Remote):	0 / 0
Loss of Link (Remote):	0
Error Seconds (Local/Remote):	2,557 / 0
FEC Errors (Up/Down):	0 / 185,070
CRC Errors (Up/Down):	10,724 / 6,724
HEC Errors (Up/Down):	6,166 / 6,341

Pinging the beeb:

Code: Select all

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:

Request timed out.
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=15ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=13ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Request timed out.
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=13ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Request timed out.
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=15ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Request timed out.
Request timed out.
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Request timed out.
Reply from 212.58.224.131: bytes=32 time=15ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123
Reply from 212.58.224.131: bytes=32 time=14ms TTL=123

Ping statistics for 212.58.224.131:
    Packets: Sent = 25, Received = 19, Lost = 6 (24% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 15ms, Average = 14ms

Post by **Dr. kitteny berk** » May 15th, 2008, 20:53

Tried restarting the router?

If you have, call them/email them, no issues here apart from the usual DNS crapness.

friznit · Post by **friznit** » May 15th, 2008, 21:00

Yeah couple of times now, no dice. Ticket sent.

Post by **Dr. kitteny berk** » May 15th, 2008, 21:03

Tis the problem with adsl2+, can go wrong easier due to stuff.

as a very, very ghetto bodge, you could try using DMT tool to horse the router to run at slower line speeds, sometimes helps a bit.

friznit · Post by **friznit** » May 15th, 2008, 21:14

Guess this might have something to do with it:

Dear members, Unfortunately there is currently an outage at our Burgh Heath exchange which is causing disruption to our broadband service. Please be assured that we are working to resolve this as soon as possible.

Post by **HereComesPete** » May 15th, 2008, 21:19

It's because hehulk got Be. His days away from space chess are now being made up for by his folding of space and time to play 28+hours per day, the internet is being saturated as a result.

Hehulk · Post by **Hehulk** » May 15th, 2008, 23:58

uh huh....

Shada · Post by **Shada** » May 16th, 2008, 0:03

HereComesPete wrote:space chess

Chickenz ego +1
HereComesPete takes 10 damage

Chickenz · Post by **Chickenz** » May 16th, 2008, 8:01

Fear · Post by **Fear** » May 16th, 2008, 14:20

God damnit, I was expecting a link to a porn site.