| Author |
 Topic  |
|
|
beluczywo
Member
USA
5 Posts |
 Posted - 04/18/2002 : 9:57:48 PM
|
Allright all, here's my best hack yet.
I have completely cured the "works for 5 minutes then locks the router" problem with the SpeedStream 2623 Wireless router.
Thanks to those on the board whose own hacking gave me the idea. After calling Socket (who were very nice, but it's really not their problem, and Siemens SpeedStream who basically said "too bad, it works with our stuff so you're stuck with it", I was about to look for new routers. I really wanted the print server function included in the speedstream and the only other brand to offer it was "SMC". So I got this brilliant idea:
I made the educated guess that the SMC 5435 and SpeedStream were the SAME unit (same case, same light positions, same entry screens). So, I downloaded the latest SMC firmware from here (use the 5435 stuff):
[URL=http://www.smc.com/index.cfm?action=products_downloads&productCode=SMC7004AWBR&prod_id=63]http://www.smc.com/index.cfm?action=products_downloads&productCode=SMC7004AWBR&prod_id=63[/URL]
I went to the tools menu, updated firmware.
Note: SpeedStream's default address is 192.168.254.254 and SMC's is 192.168.2.1 -- the best bet is to hard set your TCPIP on 1 computer to an address in the 192.168.2.xxx range.
After the router reboots, go to 192.168.2.1. You may get the message relating to the recovery boot loader. If so, just select the file a second time and do an update again.
Now, switch your TCPIP back to DHCP and you are good to go. The update even leaves all of your settings alone -- WEP key, MAC filtering, etc.
It works great!!!!! No more lockups, don't have to return any crap, figured something out myself to pass on to Socket and SpeedStream. By the way, SMC is about 10 revs past SpeedStream and SpeedStream has "no beta drivers being tested".
Enjoy, I am!
See this from the readme in SMC's file:
v1.41.004: 03/13/2002
1. modified app_tunnel_cfg.c for special applications does not work properly. 2002/01/28
2. modified default SNTP server 2002/01/30
3. modified bpalogin file structure connectedprog and disconnectedprog array size to 16,
because system NV space not enough. User need to Factory reset. 02/07/2002
4. add appletalk to snds driver
5. support 45100B CPU
v1.41.003 : 01/25/2002
1. Remove the PPPOE:3COM from web page.
2. Fix the some web site can not access through PPPOE or modem.
3. Enable AppleTalk bridge betweem wireless and LAN.
v1.41.002 :
1. modify nat_cfg_appfilter.c, app_tunnel_hook.c, alias_db.c to fix the probelm
that port scanner detect 113 port closed
v1.41.001 :
=> 1. modified protocol_sntp & core_sntp_cfg for new UI to compatible with old UI
2. fix alias.c does not discount MSS of ppp1 & ppp0
v1.41.000 :
=> 1. Add BigPond page and functions.
2. Wireless AP firmware version update to 1.1.1
3. Add PPPOE:3Com
v1.40.014 :
=> 1. Include Dial-up,PPPoE MTU settings.
2. Ability to use the "Virtual Server" and "Special APs" at the same time.
3. Include the ability to connect to a non-standard port.
v1.40.013 :
=> 1. fix apps_tunnel run out of resource problem.
V1.40.012:
=> 1. Solve bug that specail application can accept port > 65535 in public port
V1.40.011: 12/06/2001
=> 1.Add non-standard ftp port config
V1.40.010 : 12/06/2001
=> 1. Add virtual server loop back
v1.40.009 : 12/04/2001
=> 1. Modify http_API.c to solve that "Status" page show "Disconnected"
when connecting BigPond.
v1.40.008 : 11/23/2001
=> 1. Modify nat_cfg_AppFilter.c to add BigPond port (5050) in port filter list.
It solve that gateway can not connect BigPond server.
V1.40.007:
=> 1.Add BigPond mode to wan need add apps_bpalogin module, core_bpalogin_cfg,
core_dns_cfg, need modify apps_conf.c, dhcpc_cfg.c, ip_bootup.c, wan_fsm.c,
wan_fsm-ping.c, apps_test.c, nat_cfg_Appfilter.c
2.Otter still not add web and web_src in v1.40.007
V1.40.006:
=> 1. modified tcpOptionParse() of alias.c to fix under PPPoE mode, POP3 can not work.
V1.40.005:
=> 1. Modify and add files for MS CHAP II compatible
Note: Those who want to download v1.40.005 or upper version MUST download "Arm7H"
for two files modified(ppp.h, chap.h).
V1.40.004: 11/05/2001
=> 1. Fix the default PPPOE idle time to 0. (because wrong copy in v1.40.001)
V1.40.003:
=> 1. Fix the potential dead lock in wan state.
V1.40.002:
=> 1. Fix PPPOE will hang up in ARM9 platfrom, but ARM7 will not.
Anyway we also fix in ARM7.
V1.40.001: 11/01/2001
=> 1. Fix IPSec multiple connection for Nortel VPN.
2. Panda adds PPPOE auto backup.
3. Morgan changes httpd to close connection at TIME_WAIT state.
And add code to kernel_sup.c to support this feature.
4. Wenbin changes Modem interface (ppp0) MTU to be 1480 and checks
if MRU value given by ISP server is greater than 1500.
5. NE2000.c add nop function and output put delay for WAN driver.
In order to solve ftp linkage problem.
V1.20.002: 10/29/2001
=> 1. Morgan modified app_tunnel_cfg.c & app_tunnel_hook.c for
when playing MSN game zone, 2nd player can NOT play immediately
after 1st player play over.
=> 2. Morgan, solve when modem connected, then "connect" PPPoE, LAN driver
can NOT receive any incoming packet, but no data abort.
=> 3. Morgan, solve default DNS setting shows 0.0.0.0 (should be empty).
V1.20: 10/12/2001
=> 1. Eaton modified wan_mdm.c for modem connecting speed problem.
2. Jeny fixed user login twice problem.
3. Jeny modified tool_update page SMC website redirect address.
4. Roger modified minimun DHCP packet lenth restriction to 252,
and computation of DHCP t1, t2 from lease time.
Brian D Luczywo |
|
|
johnd
Mobility Advocate
USA
1602 Posts |
Posted - 04/19/2002 : 09:32:36 AM
|
Brian,
Thank you for the OUTSTANDING news and the informative post. I will be sure to pass it along to the Socket Technical Support Team so they can refer other users to your hard work.
I think you have provided an example of how Socket users are very valuable in helping other Socket customers. With your help and working in an environment that Socket does not have, you were able to come up with a resolution to a problem.
Thanks again!!
Regards,
John Doub
Director, Empowering Mobility Program(TM)
Wireless Advocate
-----
Socket Communications
www.socketcom.com/emp
johnd@socketcom.com |
 |
|
|
sfhub
Senior Member
24 Posts |
Posted - 04/19/2002 : 10:45:33 AM
|
beluczywo,
It's great that this solution worked for you.
To provide a little background:
It can get a little confusing because SMC makes 2
versions of the AWBR that differ only in part #.
The original AWBR 750.5312 was OEMd from
AMIT (www.amit.com.tw) and uses 1.94x firmware.
It is not compatible (as you noted) with
the Speedstream 2623.
The newer AWBR (part #750.5435) is OEMd from Accton
(www.acton.com) and uses the WindRiver VxWorks micro-kernel.
Firmware is number 1.41.xxx. It is a complete different
product that AWBR v1. Apparently this is the version
that the Siemens/Speedstream is related to.
Ironically over on DSLReports, users are doing the
opposite and using the Speedstream firmware
on their SMC AWBRv2 to fix a hanging problem with
the router (related to DHCP renew problems with
ISP)
The first caveat is you might be introducing this
new hanging problem onto your router by using the SMC
firmware. I'd like to stress this problem is completely
unrelated to the Socket Wireless hanging problem. If it
works, great, don't change it, but for new people they
should be aware of this before switching.
Second caveat is some people have complained that their
router became useless after changing from SMC to Speedstream
firmware. There doesn't seem to be any specifics about
this (and it may or may not be relevant since your solution
is changing firmware in the opposite direction). It could
easily be as simple as someone not realizing the default IP
address of the router changes between the two firmwares, but
based on the comments on DSLReports, it looks like the unit
is really broken (user used the serial port to try to config
unit and tried hard reset)
Third caveat is Siemens includes both boot and
runtime flash ROM code while the SMC only provides
runtime code. This may or may not be relevant to why some
units may break.
Having said all that, it does appear that some units will take
the upgrade without any problem. There are examples of people
using the firmware of the other unit in both directions.
I've included the relevant postings at DSLReports which you
should review before deciding to go ahead with the firmware
change.
Siemens Speedstream 2623 firmware for 7004AWBR?
http://www.dslreports.com/forum/remark,2787901~root=smc~mode=flat
Beware of Siemens firmware for 5435 7004AWBR
http://www.dslreports.com/forum/remark,3018004~root=smc~mode=flat
7004AWBR and Siemens Speedstream -Encryption?-
http://www.dslreports.com/forum/remark,2978526~root=smc~mode=flat
|
|
|
|
johnd
Mobility Advocate
USA
1602 Posts |
Posted - 04/19/2002 : 11:00:15 AM
|
sfhub,
Welcome to the forum and thank you for the feedback as well.
Regards,
John Doub
Director, Empowering Mobility Program(TM)
Wireless Advocate
-----
Socket Communications
www.socketcom.com/emp
johnd@socketcom.com |
|
|
|
beluczywo
Member
USA
5 Posts |
Posted - 04/19/2002 : 12:23:42 PM
|
sfhub:
Thank you for the heads up on the possible dhcp renew problem.
I used to have that problem with both my Belkin router (non-wireless) and with the SpeedStream when @Home was my ISP. My SpeedStream was about 2 weeks old when @Home went out of business and during that 2 weeks I was beating my head against the wall. The only cure was to hard code my assigned ip address (@Home used "permanent", but "renewed" ip addressing).
When Insightbb took over and signed up with AT&T, the problem mysteriously went away completely and has never reappeared. So at least in my case, even when my SpeedStream was on rev. 1.20.002 it had issues with some ISP setups, but I have to believe it was related to @Home's not-quite-dhcp, not-quite-permanent setup.
I will definitely keep an eye out for a recurrence and greatly appreciate the warning. It is always good to have a clue BEFORE the problem manifests. Thanks for sharing your knowledge.
Brian D Luczywo |
|
|
|
Keev
New Member
1 Posts |
Posted - 05/16/2002 : 6:18:32 PM
|
Brian, your suggestion of trying the SMC v1.41 firmware on the SS 2623 worked brilliantly. I was about to return my SS 2623, after having to reset it every five minutes... all the problems you mentioned. I just had to download the new firmware file, and upgrade.. that's it. Now I'm posting via my wireless connection. The SMC firmware also seems much faster. The change log you posted tells a lot of the story.. Anyways, thanks again, you saved me lots of time and trouble.
Kevyn
quote:
originally posted by beluczywo:
Allright all, here's my best hack yet.
I have completely cured the "works for 5 minutes then locks the router" problem with the SpeedStream 2623 Wireless router.
Thanks to those on the board whose own hacking gave me the idea. After calling Socket (who were very nice, but it's really not their problem, and Siemens SpeedStream who basically said "too bad, it works with our stuff so you're stuck with it", I was about to look for new routers. I really wanted the print server function included in the speedstream and the only other brand to offer it was "SMC". So I got this brilliant idea:
I made the educated guess that the SMC 5435 and SpeedStream were the SAME unit (same case, same light positions, same entry screens). So, I downloaded the latest SMC firmware from here (use the 5435 stuff):
[URL=http://www.smc.com/index.cfm?action=products_downloads&productCode=SMC7004AWBR&prod_id=63]http://www.smc.com/index.cfm?action=products_downloads&productCode=SMC7004AWBR&prod_id=63[/URL]
I went to the tools menu, updated firmware.
Note: SpeedStream's default address is 192.168.254.254 and SMC's is 192.168.2.1 -- the best bet is to hard set your TCPIP on 1 computer to an address in the 192.168.2.xxx range.
|
|
|
|
Algester
Senior Member
Australia
14 Posts |
Posted - 05/18/2002 : 4:42:28 PM
|
I recently acquired a Speedstream 2623 wireless router and did have it working as delivered.
I thought would be good idea to update the firmware to the SMC one as per above. Particularly as the SMC firmware had setup screen for BPA (Bigpond Aust ISP).
It flashed perfectly and was able to connect as previously. But had some performance issues, was a bit patchy needing to do refreshes quite often, a number of sites I couldn't access at all etc.
So decided that may as well go back to the previous 1.2 Spreedstream version of the firmware. Thats when my problems started. It flashed OK but am now unable to log onto the router.
I've tried using different addresses (eg 192.168.254.254 and 192.168.2.1) but no luck to date.
Originally the default address for the Spreedstream 1.2 firmware was 192.168.254.254 and this was also the case after I had updated to the SMC firmware. I thought that it should have changed to the SMC default of 192.168.2.1 but this was not the case.
I've tried the reset button, turning off etc but still having trouble logging onto the router.
Would be grateful if anybody had any suggestions as to what I can try next and if further information is required please let me know.
|
|
|
|
sfhub
Senior Member
24 Posts |
Posted - 05/23/2002 : 2:32:49 PM
|
quote:
Would be grateful if anybody had any suggestions as to what I can try next and if further information is required please let me know.
If your unit comes with a serial port that can be used as a console, try using that to access the unit (some SMC units do, but I don't know about Speedstream). Other than that, your best bet is probably to return the unit for warranty replacement.
|
|
|
|
Algester
Senior Member
Australia
14 Posts |
Posted - 05/25/2002 : 12:42:48 AM
|
Thanks sfhub, I'll give that a go. Bit of a beginner at this but presume that I can telnet to the hub?
|
|
|
|
tolle
New Member
2 Posts |
Posted - 06/04/2002 : 4:38:15 PM
|
I contacted tech support about this issue today and they said a new firmware version will be out in a month or so. They did admit it sounded like their problem and apologized. My case number with them is 88685. I encourage everyone to call and report this problem to help encourage them to fix it with the next firmware release, don't forget to get your case number. I gave the tech the URL to this thread and he read it while we were on the phone, he found it interesting.
The socket card works far better than what I expected. I use it at work and home. I work at a University and bounce from access point to access point. I can easily move between 12 access points in a 15 minute walk and it never misses a beat. At home I go to the back of my neighbor's house across the street and it still works. 300+ feet through two houses is pretty darn good, I do have the router installed on the second floor of my house so maybe that helps.
Socket, please keep hounding Siemens about their firmware glitch.
Thanks,
Troy
|
|
|
|
mwmiller87
New Member
USA
4 Posts |
Posted - 06/24/2002 : 7:21:55 PM
|
quote:
Allright all, here's my best hack yet.
I have completely cured the "works for 5 minutes then locks the router" problem with the SpeedStream 2623 Wireless router.....
Hi Brian -
I have the same setup: Socket + 2623 and have not yet succeeded in connecting the Pocket PC to anything (other PCs on the home net are fine with each other). Please fill me in since I come late to the thread: what exactly have been the "router problems" people are experiencing. At this point, should I just return the Speedstream? The combination should pick up IE at least, but does not Netrunner cannot find shared folders, etc.
Any and all info welcome.. Thanks....
|
|
|
|
mwmiller87
New Member
USA
4 Posts |
Posted - 06/29/2002 : 5:53:16 PM
|
Brian, Johnd -
Having had the same frustrating experience with the SpeedStream 2623 not getting along with the Socket, I updated the thing with the SMC firmware (the 1.41.xx series as you suggested John). Now I can't hit the router at all, using their own address--192.168.2.1. Can't get to the old SpeedStream manager either of course. Is there something I should have done, or still can do, to get myself back into the router interface? Does the firmware work over a different channel, or different ESSID? I don't know...I'm really stuck, and about to toss the 2623 and get something that's proven to work with the Socket...but that's a nice chunk of money down the drain! Any ideas, before I throw in the towel?
Mitchell
mwmiller87@hotmail.com
|
|
|
|
Algester
Senior Member
Australia
14 Posts |
Posted - 07/01/2002 : 12:37:50 AM
|
Hope you do find an answer and if you do please post here. I had similiar problems as noted above. I ended up going out and getting another wireless router, obviously different make. At the end of the day I recognise it was probably my own fault in changing the firmware but it wasn't working correctly and needed to do something. And sitting here in Australia trying to get the 2623 fixed when I bought it on a trip to USA is near impossible.
|
|
|
|
dl
New Member
1 Posts |
|
|
mwmiller87
New Member
USA
4 Posts |
Posted - 07/12/2002 : 06:37:10 AM
|
| Concerning use of SMC firmware...has anyone found a way to deploy VPN over a home wireless LAN using the Barricade firmware (or Speedstream 2623 for that matter)? I find no reference to it in the SMC User Guide...other than the statement that VPN support at some level exists. |
|
|
|
tolle
New Member
2 Posts |
Posted - 07/14/2002 : 10:51:31 AM
|
Well the wireless part still locks up with the latest firmware. Can anyone confirm this update works for them in low power mode?
It still doesn't lock up if I disable all Socket power savings.
|
|
|
|
gaffgaff
New Member
1 Posts |
Posted - 09/02/2002 : 1:23:41 PM
|
This fix works wonderfully. Thank you so much for the hack. I have a speedstream router and it worked fine with my 3 older dell 4800lt network cards. However, when I tried adding new 802.11b cards to the network, they would get dropped after five minutes and the only way to get them back on was to reboot the router. This fix worked great and now Im finally able to use my router properly.
|
|
|
|
Bob S
Member
8 Posts |
Posted - 09/20/2002 : 07:32:54 AM
|
Another believer!
My 2623 system worked perfectly w/ Linksys WPC11 in a Dell running NT4, until I added my Ipaq 3955 w/ Socket WLan card; then within about 5 minutes the router would lock up and my Dell would lose connection, and not be recognized until I reset the router. I played with settings for days with no improvement. Efficient's answer was that "They did not support Windows CE".
Finally decided to risk the firmware change 2 weeks ago and have not SINGLE problem since!
|
|
|
|
nickon17
New Member
3 Posts |
Posted - 01/26/2004 : 1:43:15 PM
|
| If your firmware failed, try this. Open up the unit, and take out the wireless nic card. Its just a standard nic that will work in your laptop. If you use it in your laptop use the Acer Warplink WS8-P driver. But anyways, take out the card, and power on the router. Everything will work then! I have not tested it with the nic back in yet though. |
|
|
| |
Topic |
|
Topic Locked
