Tower Maintenance

[Luke7777]

Just a heads up...

MyWireless Scheduled Maintenance: 04, 05, 06 and 07 April 2006

Maintenance will be performed on the following MyWireless towers from 04:00 to 06:00. MyWireless customers may not be able to connect during this period.

04 April: Menlopark, Mintek
05 April: Hyde Park, Lamontagne, Nelspruit Steiltes, Nelspruit Boston
06 April: Northcliff, Woodmead, Fourways
07 April: Aasvoelkop, Rosebank, Elardus Park

 

[bHOLDher]

Luke, I wanned to tell you, it seems as if the tower maintenance might have been a firmware upgrade. I upgraded my modem's firmware to 5.0.1.68m a month or two ago, and today the minimum ping (After testing for veeeeeeeeeery long) was 54ms (previously 88ms).. I only started getting that pings after I flashed my modem , or uhhh upgraded my modem's firmware.

But, of course the new firmware doesnt sort out any problems, it just improves pings (relatively speaking), -- the pings still vary between 54 and 1100+ms.

The 54ms is just there to show you what the network is capable of.

 

[Luke7777]

Quick ping to Sentech shows improvement. Modem firmware still on 5.0.1.60

Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of d

Reply from 66.18.65.124: bytes=32 time=100ms TTL=250
Reply from 66.18.65.124: bytes=32 time=176ms TTL=250
Reply from 66.18.65.124: bytes=32 time=120ms TTL=250
Reply from 66.18.65.124: bytes=32 time=356ms TTL=250
Reply from 66.18.65.124: bytes=32 time=133ms TTL=250
Reply from 66.18.65.124: bytes=32 time=139ms TTL=250
Reply from 66.18.65.124: bytes=32 time=173ms TTL=250
Reply from 66.18.65.124: bytes=32 time=131ms TTL=250
Reply from 66.18.65.124: bytes=32 time=1078ms TTL=250
Reply from 66.18.65.124: bytes=32 time=153ms TTL=250
Reply from 66.18.65.124: bytes=32 time=132ms TTL=250
Reply from 66.18.65.124: bytes=32 time=152ms TTL=250
Reply from 66.18.65.124: bytes=32 time=216ms TTL=250
Reply from 66.18.65.124: bytes=32 time=272ms TTL=250
Reply from 66.18.65.124: bytes=32 time=685ms TTL=250
Reply from 66.18.65.124: bytes=32 time=226ms TTL=250
Request timed out.
Reply from 66.18.65.124: bytes=32 time=215ms TTL=250
Reply from 66.18.65.124: bytes=32 time=253ms TTL=250
Reply from 66.18.65.124: bytes=32 time=252ms TTL=250

Ping statistics for 66.18.65.124:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 100ms, Maximum = 1078ms, Average = 261ms

 

[ProAsm]

Luke is that the new or old modem.
Pinging from the NodeB on the Tower to 66.18.65.124 is a constant 16 ms so it shows you how far the air interface has to go still.
It would be interesting to know the difference between the 2 modems using the same version firmware, from the same PC from the same location.

 

[JayT]

Old modem using firmware 5.0.1.68m

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

Reply from 66.18.65.124 : bytes=32 : time=157 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=138 ms
Reply from 66.18.65.124 : bytes=32 : time=138 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=137 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=217 ms
Reply from 66.18.65.124 : bytes=32 : time=139 ms
Reply from 66.18.65.124 : bytes=32 : time=138 ms
Reply from 66.18.65.124 : bytes=32 : time=137 ms
Reply from 66.18.65.124 : bytes=32 : time=138 ms
Reply from 66.18.65.124 : bytes=32 : time=137 ms
Reply from 66.18.65.124 : bytes=32 : time=138 ms
Min=137 : Max=217 : Ave=144 ms : Packetloss = 0%

 

[bHOLDher]

ProAsm, so you ping from the tower to 66.18.65.124 and it gives you 16ms???? Why on earth are we getting totally inconsistent pings anything from 60ms to 3000+sec? Are the towers getting busy? Or would you rather not say?

Luke's pings look pretty good (relatively speaking). It gets a bit worse during the day, although today its been better, Avg 450-500ms, instead of Avg 600-800ms.

Im convinced the 68m firmware improve pings even more.

ProAsm, my friend has a new modem and says that performance is pretty good for him. Have you noticed any performance difference between the old and new modem, or heard that anyone else saying something like that?

 

[Luke7777]

Pro, old modem April 2004 firmware 5.0.1.60. Patch antenna inhouse. 300m directly west of the tower. Anyone in Pta with a new modem is welcome to contact me for a "plug&play" session and old modem, new firmware....maybe bHOLDher and myself can setup the last one. Will a properly placed outdoor antenna improve the pings/latency (can't remember and too lazy to search the forum) If so, I'll cast an evil eye in bdt's direction for possible assistance. Note : just taking a stroll outside with laptop, modem and patch antenna pointing at the tower, I can double my signal strength and up the SNL quite a bit too. Never done anything for me speed and stability wise, so I couldn't be bothered

 

[TheRoDent]

This is not a tower firmware upgrade.

 

[bHOLDher]

Hehehe, maybe the tower maintenace had nothing to do with the improved pings!

Lets just say its MAGIC!

 

[Luke7777]

Will a properly placed outdoor antenna improve the pings/latency (can't remember and too lazy to search the forum) If so, I'll cast an evil eye in bdt's direction for possible assistance. Note : just taking a stroll outside with laptop, modem and patch antenna pointing at the tower, I can double my signal strength and up the SNL quite a bit too. Never done anything for me speed and stability wise, so I couldn't be bothered

I'm still open for suggestions and still too lazy

 

[bHOLDher]

Will a properly placed outdoor antenna improve the pings/latency (can't remember and too lazy to search the forum)

I personally feel that the problem is not with the SNL, that is not the biggest problem. Theoretically a better SNL will give you better pings because there is more data and less errors going through.

I vaguely remember a few posts (hehe years ago) from people saying that after installing a dish, the pings got a lot better and fixed up connections that would drop, and improved speed.

On the other hand I have a SNL of 3 (bounced signal) at home [ - very stable connection], and my pings are on average better than on Menlo tower with a SNL of 17.

Home min ping = 52ms, avg 150 - 200ms. On Menlo (during day) min ping = 62, avg 350-400.

So, I think it would not be worth the money, I believe that the real problem is high contention ratios, and maybe a few other problems too.

Then again, there is only one way to find out.

 

[ProAsm]

ProAsm, so you ping from the tower to 66.18.65.124 and it gives you 16ms???? Why on earth are we getting totally inconsistent pings anything from 60ms to 3000+sec? Are the towers getting busy? Or would you rather not say?

The problem is the air interface between the modem and the tower.
This is currently being worked on with regard to the firmware and we are getting somewhere although the fluctuations are still bad.
For VOIP to work well we need a consistant 120 ms or better.

Regarding the new modems, I have never used one yet and only saw one when I went on the IPWireless course.
Theoretically they should be a lot better but only time will tell.
The new modems are split into 3 sections (audio, video and general) whereas the old modems only have a general channel.
The dedicated channels of the new modem dont currently work as the Tower hardware is different but will upgrade in due course.

 

[bHOLDher]

Ahh, cool, thanks ProAsm, thats very interesting!

 

[bHOLDher]

I just had to post this, its probably the best that I have even seen it.

Pinging 66.18.65.105 with 32 bytes of data:

Reply from 66.18.65.105: bytes=32 time=189ms TTL=253
Reply from 66.18.65.105: bytes=32 time=68ms TTL=253
Reply from 66.18.65.105: bytes=32 time=98ms TTL=253
Reply from 66.18.65.105: bytes=32 time=77ms TTL=253
Reply from 66.18.65.105: bytes=32 time=83ms TTL=253
Reply from 66.18.65.105: bytes=32 time=81ms TTL=253
Reply from 66.18.65.105: bytes=32 time=91ms TTL=253
Reply from 66.18.65.105: bytes=32 time=59ms TTL=253
Reply from 66.18.65.105: bytes=32 time=68ms TTL=253
Reply from 66.18.65.105: bytes=32 time=66ms TTL=253
Reply from 66.18.65.105: bytes=32 time=53ms TTL=253
Reply from 66.18.65.105: bytes=32 time=71ms TTL=253
Reply from 66.18.65.105: bytes=32 time=129ms TTL=253
Reply from 66.18.65.105: bytes=32 time=88ms TTL=253
Reply from 66.18.65.105: bytes=32 time=227ms TTL=253
Reply from 66.18.65.105: bytes=32 time=186ms TTL=253
Reply from 66.18.65.105: bytes=32 time=85ms TTL=253
Reply from 66.18.65.105: bytes=32 time=123ms TTL=253
Reply from 66.18.65.105: bytes=32 time=62ms TTL=253
Reply from 66.18.65.105: bytes=32 time=61ms TTL=253
Reply from 66.18.65.105: bytes=32 time=71ms TTL=253
Reply from 66.18.65.105: bytes=32 time=58ms TTL=253
Reply from 66.18.65.105: bytes=32 time=68ms TTL=253
Reply from 66.18.65.105: bytes=32 time=67ms TTL=253
Reply from 66.18.65.105: bytes=32 time=64ms TTL=253
Reply from 66.18.65.105: bytes=32 time=71ms TTL=253
Reply from 66.18.65.105: bytes=32 time=69ms TTL=253
Reply from 66.18.65.105: bytes=32 time=68ms TTL=253
Reply from 66.18.65.105: bytes=32 time=77ms TTL=253
Reply from 66.18.65.105: bytes=32 time=84ms TTL=253
Reply from 66.18.65.105: bytes=32 time=63ms TTL=253
Reply from 66.18.65.105: bytes=32 time=61ms TTL=253
Reply from 66.18.65.105: bytes=32 time=71ms TTL=253
Reply from 66.18.65.105: bytes=32 time=131ms TTL=253
Reply from 66.18.65.105: bytes=32 time=197ms TTL=253
Reply from 66.18.65.105: bytes=32 time=135ms TTL=253
Reply from 66.18.65.105: bytes=32 time=74ms TTL=253
Reply from 66.18.65.105: bytes=32 time=52ms TTL=253
Reply from 66.18.65.105: bytes=32 time=70ms TTL=253
Reply from 66.18.65.105: bytes=32 time=80ms TTL=253

Ping statistics for 66.18.65.105:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 227ms, Average = 89ms

 

[Luke7777]

hmmm, speak for yourself...

Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of da

Reply from 66.18.65.124: bytes=32 time=290ms TTL=250
Reply from 66.18.65.124: bytes=32 time=225ms TTL=250
Reply from 66.18.65.124: bytes=32 time=238ms TTL=250
Reply from 66.18.65.124: bytes=32 time=165ms TTL=250
Reply from 66.18.65.124: bytes=32 time=198ms TTL=250
Reply from 66.18.65.124: bytes=32 time=160ms TTL=250
Reply from 66.18.65.124: bytes=32 time=202ms TTL=250
Reply from 66.18.65.124: bytes=32 time=229ms TTL=250
Reply from 66.18.65.124: bytes=32 time=225ms TTL=250
Request timed out.
Reply from 66.18.65.124: bytes=32 time=255ms TTL=250
Request timed out.
Reply from 66.18.65.124: bytes=32 time=199ms TTL=250
Reply from 66.18.65.124: bytes=32 time=333ms TTL=250
Reply from 66.18.65.124: bytes=32 time=156ms TTL=250
Reply from 66.18.65.124: bytes=32 time=454ms TTL=250
Reply from 66.18.65.124: bytes=32 time=236ms TTL=250
Reply from 66.18.65.124: bytes=32 time=95ms TTL=250
Reply from 66.18.65.124: bytes=32 time=138ms TTL=250
Reply from 66.18.65.124: bytes=32 time=303ms TTL=250

Ping statistics for 66.18.65.124:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 454ms, Average = 227ms

and 1 min later

Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of

Reply from 66.18.65.124: bytes=32 time=164ms TTL=250
Reply from 66.18.65.124: bytes=32 time=151ms TTL=250
Reply from 66.18.65.124: bytes=32 time=278ms TTL=250
Reply from 66.18.65.124: bytes=32 time=230ms TTL=250
Reply from 66.18.65.124: bytes=32 time=333ms TTL=250
Reply from 66.18.65.124: bytes=32 time=131ms TTL=250
Reply from 66.18.65.124: bytes=32 time=213ms TTL=250
Reply from 66.18.65.124: bytes=32 time=133ms TTL=250
Reply from 66.18.65.124: bytes=32 time=232ms TTL=250
Reply from 66.18.65.124: bytes=32 time=152ms TTL=250
Reply from 66.18.65.124: bytes=32 time=353ms TTL=250
Reply from 66.18.65.124: bytes=32 time=112ms TTL=250
Reply from 66.18.65.124: bytes=32 time=196ms TTL=250
Reply from 66.18.65.124: bytes=32 time=95ms TTL=250
Reply from 66.18.65.124: bytes=32 time=96ms TTL=250
Reply from 66.18.65.124: bytes=32 time=153ms TTL=250
Reply from 66.18.65.124: bytes=32 time=212ms TTL=250
Reply from 66.18.65.124: bytes=32 time=289ms TTL=250
Reply from 66.18.65.124: bytes=32 time=93ms TTL=250
Reply from 66.18.65.124: bytes=32 time=196ms TTL=250

Ping statistics for 66.18.65.124:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 353ms, Average = 190ms

It's the (lack of) consistency that annoys me, but yes, looks like the max has decreased a bit

 

[bHOLDher]

Well, Im impressed with the Menlo tower today!!! (At least for this time of day)

Ping statistics for 66.18.65.105:
Packets: Sent = 159, Received = 159, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 532ms, Average = 187ms

(When I first logged the call, the average was 700-900ms...)

The consistency is MUCH better, but still not as good as Horizon tower (posted above).

But, what will it look like during lunch time?

And now:

Ping statistics for 66.18.65.105:
Packets: Sent = 488, Received = 488, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 1078ms, Average = 204ms