Firmware etc...

ProAsm

ProAsm

Expert Member
Joined
Aug 31, 2003
Messages
2,191
Reaction score
106
Location
Hilton
<b>IPWireless Modem USB Firmware:</b>

http://www.unreal.co.za/files/other/IPWP1CF4.2.1.8.exe

http://www.unreal.co.za/files/other/IPWP1CF5.0.1.60.exe

http://www.unreal.co.za/files/other/IPWP1CF5.0.1.62.exe

<b>IPWireless PCMCIA Firmware:</b>

http://www.unreal.co.za/files/other/IPWPCMCIAF4.2.2.7d.exe

<b>MySignal 5.6</b>

http://www.unreal.co.za/files/other/MySignalSetup56.zip

<b>MyWireless CD</b>

http://www.unreal.co.za/files/other/IPW_CD.zip

*** Edit ***
Just updated the URLs [:)]

<hr noshade size="1"><center><font color="blue">MyWireless Stuff</font id="blue">
<font size="1"><font color="black">The opinions expressed here are mine alone and do not necessarily reflect the opinions of my employer</font id="size1"></font id="black"></center>
 
Will the Tower information page include "firmware compatability" info in future ? i.e. which towers can handle firmware 5.x, etc. Might stop ppl from flashing unnecessarily...

Updated :
or asking when their towers are going to be upgraded to 4.2.1.8 [:)]
 
Proasm: Thank you. Would it be safe to upgrade to ver 5.0 of the firmware?

Save a horney friend........

Durban Mal Park(36) 53% sig 128k
 
Rhino, I'm sure this answer is best left to ProASM but from what I recall in previous discussions the v5 firmware is NOT ideal until the towers are upgraded to v5 as well.

And AFAIK the v5 firmware for the towers is not here yet ... (I hope ProASM can enlighten us ;-)


************************************************************
The views expressed on this site are my own and NOT those of my employer.
 
Basically from what I see there are several problems with 4.2.1.8 regarding the modem not scanning.
Its for that reason I have now also added the original 4.2.1.1
People on 4.2.1.8 will notice an improvement once their Tower is also upgraded to 4.2.1.8 although the scanning problem will still prevail.
The original 4.2.1.1 is very stable but ofcourse has the original temperature sensor problem where the modem wont switch on if its cold and also will not have the packet loss improvement that 4.2.1.8 or 5 has got and also the benifits of a Tower being on 4.2.1.8 they will not get.

However although it has not been tested as such but the 5.0.1.40 may still prove the best out the bunch as it does not have any of the problems that the other 2 have, but it may have a ping instability problem, as I said this still needs to be tested with a known Tower using 4.2.1.8

I also have 4.2.1.2 and 4.2.1.6 which I may add to the above list for people to choose and test.


<hr noshade size="1"><center><font color="blue">MyWireless Stuff</font id="blue">
<font size="1"><font color="black">The opinions expressed here are mine alone and do not necessarily reflect the opinions of my employer</font id="size1"></font id="black"></center>
 
ProAsm, do you have the release notes for each different version, so that we can see for ourselves what has changed from version to version?

My replacement modem was supplied with 4.2.1.6 which hasn't given me any problems. The packet loss is also mostly zero, so perhaps that improvement was made as early as 4.2.1.6 (the release notes would tell us). So if 4.2.1.8 has a few issues, then 4.2.1.6 might be a good version for users with problems to try.
 
JAS thanks for that information.
Ok I will make 4.2.1.6 available asap.
Regarding the release notes, they say nothing, mainly some blah blah about 3G updates which you can read on most websites.
The only one item mentioned was the fix of the temperature sensor.


<hr noshade size="1"><center><font color="blue">MyWireless Stuff</font id="blue">
<font size="1"><font color="black">The opinions expressed here are mine alone and do not necessarily reflect the opinions of my employer</font id="size1"></font id="black"></center>
 
PROASM: When you say scanning, is that the "looking for a signal" Lights running up and down sort of thing?

Save a horney friend........

Durban Mal Park(36) 53% sig 128k
 
I've been busy with a trail by fire it seems.... Is there any chance that the tower firmware upgrades could break ethernet connections ... YES ... I KNOW that sounds like BS... but I'm out of options here.....

The past couple of days I've not been able to connect with my modem using the ethernet cable (pppoe)... I switched to the USB cable and everything works fine... So I test the cable on a different modem - same tower ... no connection. I then got the cable replaced by NoWire... New cable ... same story. I'll be trying on a different tower 2morrow on my way to work BUT ... just want to try look into options at the moment...

Is anyone on 253000 Mintek 12 with ethernet cable ?


As a last resort I'm going have to drive to PTA NoWire to test my setup - NoWire Village walk is rather useless as they don't have coverage and therefore CANNOT test the units.

R

************************************************************
The views expressed on this site are my own and NOT those of my employer.
 
OOOH ... Here's an interesting one ....

1) downgrade to 4.2.1.1 via USB
2) Connect ethernet and reboot modem.
* Still cannot connect to network*
3) Upgrade to 4.2.1.8 via ETHERNET cable
4) Reboot modem
***MODEM CONNECTS TO NETWORK - NO PROBLEMS ***

Hope this helps anyone else that gets bitten with this LOOOOVELY bug...

R

************************************************************
The views expressed on this site are my own and NOT those of my employer.
 
Update
-------

2 modem reboots later and I'm back to USB connection only. Advice ... anyone ?

************************************************************
The views expressed on this site are my own and NOT those of my employer.
 
As to error message .. The modem software tells me hardware error or network refused connection ... strange errors....

Have now made a direct contact attempt to IPWireless.

R

************************************************************
The views expressed on this site are my own and NOT those of my employer.
 
Hi ProAsm.
I have done a test with the following info:

Can you please let me know what you think about it?

Josandre.

Hostname:
IP address: 66.18.86.14

--------------------------------------------------------------------------------

Resolve/Reverse Lookup:66.18.86.14 resolved to myw-stp-66-18-86-14.sentechsa.netDNS Query Results:myw-stp-66-18-86-14.sentechsa.net. 10800 IN A 66.18.86.14sentechsa.net. 1734 IN NS ns2.mailgate.net.sentechsa.net. 1734 IN NS ns1.mailgate.net.ns1.mailgate.net. 123708 IN A 196.38.110.1ns2.mailgate.net. 123708 IN A 196.38.110.2WWWhois Results:Connecting to whois.crsnic.net...NOT FOUND: No match for myw-stp-66-18-86-14.sentechsa.net
Whois Server Version 1.3

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

No match for "MYW-STP-66-18-86-14.SENTECHSA.NET".

&gt;&gt;&gt; Last update of whois database: Wed, 9 Jun 2004 08:17:22 EDT &lt;&lt;&lt;

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
IP Whois Results:Connecting to whois.arin.net...
OrgName: InfoSat (Pty) Ltd
OrgID: IFST
Address: 160 Jan Smuts Avenue, Rosebank
Address: Johannesburg, Gauteng 2196
City:
StateProv:
PostalCode:
Country: ZA

ReferralServer: rwhois://rwhois.infosat.net:4321

NetRange: 66.18.64.0 - 66.18.95.255
CIDR: 66.18.64.0/19
NetName: INFOSAT12-ZA
NetHandle: NET-66-18-64-0-1
Parent: NET-66-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.MAILGATE.NET
NameServer: NS2.MAILGATE.NET
Comment:
RegDate: 2002-11-22
Updated: 2004-01-15

TechHandle: AR756-ARIN
TechName: Roussos, Angelo
TechPhone: +27 11 721 3800
TechEmail: [email protected]

OrgTechHandle: AR756-ARIN
OrgTechName: Roussos, Angelo
OrgTechPhone: +27 11 721 3800
OrgTechEmail: [email protected]

# ARIN WHOIS database, last updated 2004-06-08 22:38
# Enter ? for additional hints on searching ARIN's WHOIS database.
Checking Port 80...Port 80 does not appear to be open.Ping Results:PING 66.18.86.14 (66.18.86.14) 56(84) bytes of data.
64 bytes from 66.18.86.14: icmp_seq=1 ttl=111 time=993 ms
64 bytes from 66.18.86.14: icmp_seq=2 ttl=111 time=468 ms
64 bytes from 66.18.86.14: icmp_seq=3 ttl=111 time=542 ms
64 bytes from 66.18.86.14: icmp_seq=4 ttl=111 time=583 ms
64 bytes from 66.18.86.14: icmp_seq=5 ttl=111 time=597 ms

--- 66.18.86.14 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4030ms
rtt min/avg/max/mdev = 468.373/637.097/993.823/183.918 ms
Traceroute Results: 1 63-217-30-94.sdsl.cais.net (63.217.30.94) 0.362 ms 0.272 ms 0.351 ms
2 uunet.pos1-2.cr02.frf02.pccwbtn.net (63.218.15.10) 120.133 ms 121.660 ms 118.247 ms
3 so-0-2-0.TR2.FFT1.ALTER.NET (146.188.6.113) 118.510 ms 121.330 ms 119.317 ms
4 so-1-0-0.TR1.LND2.ALTER.NET (146.188.8.181) 131.347 ms 132.923 ms 133.796 ms
5 so-5-0-0.XR2.LND2.ALTER.NET (146.188.7.229) 113.166 ms 110.493 ms 109.088 ms
6 pos3-0.cr2.lnd5.gbb.uk.uu.net (158.43.233.245) 130.755 ms 131.921 ms 134.828 ms
7 fe8-0-0.gw13.lnd5.gbb.uk.uu.net (158.43.157.141) 307.492 ms 272.284 ms 200.207 ms
8 Internet-Solutions-gw.customer.ALTER.NET (146.188.58.162) 131.696 ms 130.921 ms 130.727 ms
9 168.209.247.158 (168.209.247.158) 131.955 ms 166.990 ms 136.036 ms
10 168.209.100.30 (168.209.100.30) 106.991 ms 106.027 ms 106.373 ms
11 168.209.0.85 (168.209.0.85) 352.866 ms 353.281 ms 353.254 ms
12 isl.nmszone.is.co.za (196.26.0.3) 360.302 ms 353.089 ms 354.833 ms
13 168.209.18.62 (168.209.18.62) 353.093 ms 353.225 ms 352.402 ms
14 gige-0-0-21.rtr-core4-stp.infosat.net (66.18.65.222) 357.949 ms 359.175 ms 360.633 ms
15 66.18.65.105 (66.18.65.105) 368.591 ms 366.862 ms 364.882 ms
16 myw-stp-66-18-86-14.sentechsa.net (66.18.86.14) 653.761 ms 584.994 ms 695.771 ms







Related Links:

SG Broadband Tools
SG TCP/IP Analyzer
SG Security Scanner &gt; Scanned Ports &gt; Commonly Open Ports
SG Speed Test
SG Network Tools
SG Bits/Bytes Conversion Calculator
Buy Broadband
 
Somewhere between 4.2.1.2 and 4.2.1.6 they also changed the startup behavior of the modem. When power was applied, 4.2.1.2 would startup completely (i.e. switch on, self test, scan, lock onto tower, and then be fully functional), whereas 4.2.1.6 switches on, flashes all its lights, and then goes to sleep with only the red power light on. You then have to press the button to start the modem properly.
 
mmm thanks JAS, so basically 4.2.1.6 has the same problem as 4.2.1.8 and I was hoping that 4.2.1.6 would be better but obviously not.
So as things stand atm its a tossup between 4.2.1.1 which is stable all round except for bad packet loss and 5.0.1.40 which is good all round except has very shaky pings due to the NodeB firmware mismatch.
In my case I will stick to 4.2.1.1 unless the packetloss problem has been fixed in 4.2.1.2 which I will check out asap.

Josandre, your problem is way outa my scope, maybe TheRoDent can comment on that lot [:)]


<hr noshade size="1"><center><font color="blue">MyWireless Stuff</font id="blue">
<font size="1"><font color="black">The opinions expressed here are mine alone and do not necessarily reflect the opinions of my employer</font id="size1"></font id="black"></center>
 
He He.

Thank ProAsm.

I think that TheRoDent are too busy to fight with Sentech. I hope he will get a chance to have a look.

Thanks
 
Once you press the button with 4.2.1.6 it scans without any problems. I understood from other postings that people with 4.2.1.8 were not able to get it to scan at all, even after pressing the button. This new POR (Power-On Reset) behavior seems to be by design, rather than a bug, although I cannot think why they would want it like this. The old POR behavior was much more suitable for unattended operation, where the modem needs to startup completely after a long power outrage. Has 5.0.1.40 gone back to the old POR behavior? Let us know what you find with the packetloss on 4.2.1.2.
 
Well im on 4.2.1.8 on ethernet and connecting to the new Rosebank tower ( so should also be on 4.2.1.8 ) and everything is running very well.

Pings are avereging 93ms to www.sentech.co.za down from about 130ms before upgrade

Ethernet connects first time everytime, this was not the case before the upgrade, used to take 2 or 3 attempts

The modem power on behaves as explained by others where the button must basically be pressed twice
 
Added 4.2.1.2b - 4.2.1.6 - PCMCIA 4.2.2.7d
Can someone possibly test the 4.2.1.2b and see if it has the packetloss fix in it.

JAS, yes the Power-On Reset is now by design but not popular.

<hr noshade size="1"><center><font color="blue">MyWireless Stuff</font id="blue">
<font size="1"><font color="black">The opinions expressed here are mine alone and do not necessarily reflect the opinions of my employer</font id="size1"></font id="black"></center>
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X