NodeB Upgrades - Update!

regardtv · Aug 11, 2004

Well, Sentech and audi seem to already share billing methodologies ... bill the fscked s*it out of the client ....

regardtv · Aug 11, 2004

Well,well well !

Maybe things are only looking good because of the international links being fscked so no P2P screwing the network BUT....

Over the last 3 or so hours with v5 Tower firmware and v5 client firmware I've had 0.14% packet loss ....

Have a look at the latest graphs on : http://riggerman.dyndns.org/cgi-bin/smokeping.cgi?target=SouthAfrica.STP

arf9999 · Aug 11, 2004

hmmm... but will it last?

Are you able to do some speed tests? It would be interesting to see if the packetloss is the sole reason for sh*tty speed.

-A

regardtv · Aug 11, 2004

I'm actually rather convinced that the ONLY reason things look so good is due to the fact that most people cannot P2P internationally at the moment.

At the exact time that my pings started timing out to the international sites the latency and packet loss dissapeared on local links.

This indicates to me that the tower is dropping the packets and/or the backhaul is dropping packets - BOTH bad news.

I'll try a single thread download from IS just now to check throughput...

I must say that what I'm seeing here does not instill ANY confidence.....

regardtv · Aug 11, 2004

Using the SRT (Standard Rodent Test): http://tucows.is.co.za/files4/DCPlusPlus-0.241.exe

Single threaded download during IS intenational outage:

wget http://tucows.is.co.za/files4/DCPlusPlus-0.241.exe
--12:45:26-- http://tucows.is.co.za/files4/DCPlusPlus-0.241.exe
=> `DCPlusPlus-0.241.exe'
Resolving tucows.is.co.za... 196.4.160.77
Connecting to tucows.is.co.za[196.4.160.77]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,044,011 [application/octet-stream]

100%[========================>] 2,044,011 14.73K/s ETA 00:00

12:47:59 (13.25 KB/s) - `DCPlusPlus-0.241.exe' saved [2044011/2044011]

dbnnet · Aug 11, 2004

Don't give up just yet.... I have been "given" more news:

The current ver 5.0.1.40y.firmware we all have is NOT THE CORRECT version for the upgraded NodeB.
The correct version will be made available from IPW shortly.
The new one 5.1.xxx (I think) is designed to resolve the issue.

Bay of Plenty : Signal 48% - SNL 17 - ber 71% : D-Link DI-604 - PPPoE : 8dBi Patch Antenna : Firmware 4.2.1.8

dorris · Aug 11, 2004

Well, my packetLoss has been completely resolved, I think it must have been the upgrade to the new CORE router on sunday which started the problems, and they finally resolved them.

arf9999 · Aug 11, 2004

Regardt,

I'm looking at your international pings: The UK pings seem ok, but the US ones are F!@#ed. Or am I misreading?

dbnnet · Aug 11, 2004

* UPDATE *
The NodeB Firmware was upgraded this morning on the following towers:

Horizon View - Woodmead - Killarney - Hyde Park - NorthCliff - Halfway Gardens

Bay of Plenty : Signal 48% - SNL 17 - ber 71% : D-Link DI-604 - PPPoE : 8dBi Patch Antenna : Firmware 4.2.1.8

regardtv · Aug 11, 2004

Uhm .. currently the UK one is non-operational .. will be fixed in a second or 2 ;-)

US/UK times compare quite favourably at the moment. UK times in general better - I believe this is due to the cable IS have running into Europe --- haven't been involved there for a while so my info may be stale.

Will be interesting to monitor what happens with latency now that international is back ....

I predict as p2p comes back online and people move from queued into downloading mode latency will go back up....

As to the new firmware for the clients ... pass it along ;-)

lewstherin · Aug 11, 2004

I noticed that Maui Sky Fiber has new firmware upgrades available for download as part of their dialer software:
http://www.mauiskyfiber.com/downloads/5.0.1.53_MSF_local.exe

Given that the version is 5.0.1.53, maybe its worth a try before the offical 5.1 version is made available?

Use it, don't use it [

]

Telkom needs a leash, ICASA needs some guts, and the SA consumer needs to make it happen

regardtv · Aug 11, 2004

don't use that version .. it's only for the 1D models ... I'm sure I posted about that somewhere ....

I must be losing my mind

kickass72za · Aug 11, 2004

What models do we have???

regardtv · Aug 11, 2004

1C ... and the Maui Sky Fibre only has 4.2.1.8b for the 1C models

regardtv · Aug 11, 2004

Ok, now that the international links are back up I'm noticed the following....

1) Latency jump by about 50ms
2) Packetloss went from <1% to >4.5%

This is seeming very tower specific....I'm not liking this

Somehow I don't think that a change in the client firmware is going to make a change there... I'd love to be proven wrong by Sentech ...

mrbob · Aug 11, 2004

128k package on Tower 116 (Brixton )

Pinging www.sentech.co.za [66.18.65.115] with 32 bytes of data:
-blahblahblah

-

Ping statistics for 66.18.65.115:
Packets: Sent = 20, Received = 12, Lost = 8 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 1255ms, Average = 552ms

Pings I'd say are pretty useless, my speeds are still as lame as ever; they are a bit better than yesterday but it's always so tough to tell. I'm downloading the new firmware from ProAsm at just under 3Kb/s , it's a small improvement but it's still useless. Still it is good to know that something is being done, when I read that sentech were doing a "Major software upgrade" I assumed they were installing a new version of Solitaire for the Orcs behind helpdesk to play.

Will post once I've installed the new firmware .. wow download has actually moved up to 4.15K/s and seems to be holding round there... WOOHOO I'm getting dial-up speeds baby! *feels the power of "broadband"*

mrbob · Aug 11, 2004

downloading the same file again, this time at 6Kb/s , pretty cool... almost a 40k connection.. though not quite. Pings are also better

Pinging www.sentech.co.za [66.18.65.115] with 32 bytes of data:

Ping statistics for 66.18.65.115:
Packets: Sent = 20, Received = 12, Lost = 8 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 1255ms, Average = 552ms

arf9999 · Aug 11, 2004

beat this:
esolving host 'www.sentech.co.za'
Pinging [66.18.65.115] x 10 with 32 bytes of data

Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=229 ms
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=189 ms
Min=189 : Max=229 : Ave=209 ms : Packetloss = 80%

A new record!!

MW128, Tower 60(Northpark Plaza), Signal:16%,S-N-L: 7, BER: 45%

dorris · Aug 11, 2004

I've just about had enough of this sh1tty packetloss problem, does anybody know what the router maintenance on sunday was and on what router.
This packetLoss is not being caused by firmware, its not specific to towers, and packet loss is terrible by
gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65.106]
So, that leads to a conclusion, packets are getting lost over microwave links, or at that router, since maintenance was done on sunday to a router, and thats when everything started, MY FINGERS POINTING STRAIGHT AT THE ROUTER.
ps, has anybody logged a ticket about the PL, what was said about it??
I know I should do it, but I'm too lazy currently to speak to those ORCS

Robone · Aug 11, 2004

I am so glad the managed to upgrade Northcliff (tower 60) to day.

I am now the proud user of a high packet loss system.

We should run a contest to see who can get the highest packet loss today.

Rules: You must keep your antenna pointing at the right tower, and try not to hard to actually use your internet connection.

Anyway, mine are:
esolving host 'www.sentech.co.za'
Pinging [66.18.65.115] x 4 with 32 bytes of data

Reply from 66.18.65.115 : bytes=32 : time=1281 ms
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=261 ms
Min=261 : Max=1281 : Ave=771 ms : Packetloss = 50%

Resolving host 'www.sentech.co.za'
Pinging [66.18.65.115] x 4 with 32 bytes of data

Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=211 ms
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Min=211 : Max=211 : Ave=211 ms : Packetloss = 75%

Not bad hey. Beat that.

NodeB Upgrades - Update!

Expert Member

Expert Member

MyBroadband Member

Expert Member

Expert Member

Senior Member

Well-Known Member

MyBroadband Member

Senior Member

Expert Member

Senior Member

Expert Member

Well-Known Member

Expert Member

Expert Member

Active Member

Active Member

MyBroadband Member

Well-Known Member

Senior Member