 digiblurGot Sipura?Premium
join:2002-06-03
Louisiana
1 edit | New WRT54G Firmware - Built in TX mW selection! No more having to the ping hack everytime you reboot the WRT54G. This one is built in! This firmware works great! This is not my creation. I found this post in the WRT54G Yahoo group. Way to go guys/gals!
Hi all,
I just posted firmware version 1.42.3.2sv to »ftp://ftp.sveasoft.com/pub/Firmware1.42.3.2sv.bin.
Power adjust, xmit antenna, and recv antenna were added to the web interface under Wireless->Advanced Wireless Settings.
I have tested this firmware but as always USE AT YOUR OWN RISK!!!
From the Changelog -
Sveasoft Firmware Version 1.42.3.2sv
Changes
-------
Add power adj, ant rx, ant tx to WWW interface
-- under Wireless-> Advanced Wireless Settings
Added sshd (dropbear)
Added telnetd (busybox 0.60.x)
Added hexdump, cmp, wget to busybox
Added boot_wait, telnetd to web interface
-- Under Administration->Management
Client mode enabled
Updated source tree to 1.42.3 Linksys source
Re-enabled ping hack
Firmware version changed to 1.42.3.1sv
To Do
-----
Add frottle hidden-node management
Add wondershaper bandwidth management
Add wavelan or equiv. wl statistics
Add NoCatSplash compile time option
Add Client/AP Mode select in WWW interface
SSHD Key Generation Notes
-------------------------
1) Install openssh on your local machine
2) Run ssh-keygen -t rsa -f [filename] -N '' -C ''
3) Open a browser to the Linksys box (default 192.168.1.1)
3) Open [filename] and copy contents to Linksys web interface field
"RSA Host Key in ASCII Armored Format".
This is the linksys sshd daemon's private key.
4) Copy your public key from /[user name]/.ssh/id_rsa.pub to the
"Authorized Keys" field.
5) Enable SSHD in the web interface
6) Enter your Linksys password twice at the top of the screen
7) Click on "Save Settings"
8) Restart your Linksys box |
|
| very nice:) |
|
|
|
| reply to digiblur
Hi, does this version of firmware for the WRT54G belong compatible with the models of EU?? Or only do they belong compatible with the models US??
Thanks to all.. |
|
| reply to digiblur
I had a problem with this firmware. It did not contain a ping or tracerout option (ie, they would not open and locked my router up.) Anyone else have that problem? Version 1.1 router upgrading from 1.42.3 linksys firmware. |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to digiblur
Re: New WRT54G Firmware - Built in TX mW selection It does say use at your own risk though. I don't need the ping window anymore since you can now save you TX strength in the settings of the router. Only thing that threw me off at first was some how my router wanted an https connection to the settings page instead of a http. I had to go in and turn off the https since I didn't need that for my adminstration on my home network. I could see using it on a large network that might have someone sniffing. |
|
| reply to dlindman
Re: New WRT54G Firmware - Built in TX mW selection! Yeah i did went back to 1.42.3:) |
|
| Re: New WRT54G Firmware - Built in TX mW selection Hi guys,
Thanks for trying out our firmware. We're aware of the ping and traceroute bug and are working to fix it.
A new version with an experimental client mode feature will be available at »www.sveasoft.com (look under Q&A).
Any feedback to improve this firmware release is greatly appreciated. Please email support@sveasoft.com. |
|
3 edits | Im using newest revision 1.42.3.3sv so far so good.Ping and traceroute commands are fine. gj SV:)between seattle wireless and sv who needs linksys lol. Is client mode used for bridging? |
|
| "Is client mode used for bridging?"
Depends on what kind of bridging you mean.
The WRT54G has a full WDS implementation that can chain multiple APs together in up to a theoretical 6 hop chain. Essentially you can run mulitple AP's with tens of clients each and they will automatically forward all of the packets to the central AP.
There is another bridging mode called WET - wireless Ethernet T..something  - in the source that apparently requires client mode (the source forces client mode if you choose it - see src/router/wfconf for details). I assume it is some kind of hardware Ethernet bridging over wireless but haven't had a chance to play with it yet.
-- James |
|
1 edit | Thx james for explanation your firmware 1.42.3.3sv rocks:)Ps im allergic to linux lol:) |
|
| reply to digiblur
Re: New WRT54G Firmware - Built in TX mW selection! New firmware does not work with WPA and AES....the wireless client says the AP has TKIP and the key is missing. Also router time is messed up.
Went back to WiFi-box 1.42.3 hacked version and everything is fine! |
|
| didnt test wpa time was off |
|
| reply to phxuser
Can you send me some details about your problems? The intention is to rapidly fix any bugs found and release updates.
Where did you see that the router time was off? What client did you try with WPA? Any help is appreciated.
Please email me at support@sveasoft.com. |
|
| i mean the time was loosing sync becoming inaccurate on status page:) |
|
| There is an NTP (timeserver) client in the Linksys that can be activated. To use it the Linksys must be able to access the Internet (or a local timeserver).
I will take a look and see about activating it. |
|
 DrunkulaPremium
join:2000-06-12
Denton, TX
 ·Verizon FiOS
| reply to digiblur
WPA is, for the most part, unusable on my setup. I was able to get it to work for maybe 5 seconds, once. Not sure what the nature of the problem is. I had to fallback to wep (yuck!) for now. WPA was working fine with the previous firmware I was using.
--
Join BroadbandReports.com's SETI@Home Team
Put your unused clock cycles to work! |
|
| To all it may concern: I have a wrt54g with 1.42.2 (1.42.3 samething) firmware in it and it to has trouble keeping correct time.I have contacted Linksys many times about it, they told me I had a bad units. I am now on my 3rd unit same problem. When I talked to linksys they acted as if they never heard about this problem existing. The last time I talked to them they tried to say it was my ISP or my cable modem causing the problem. I believe 1.30.7 firmware had the NPT timeserver available on the setup page but on later releases taken off. Maybe Linksys needs to hear more about this problem. |
|
| Re: New WRT54G Firmware - Built in TX mW selection I also have noticed the time problem with 1.4.2x firmware. I am running 2.008 today and so far the router time has not
changed. The router gets the time from the dhcp server and if it was correct in previous versions it should work on 2.008. |
|
| reply to Sveasoft--
I believe Linksys WRT54G doesn't support WDS. I just bought a Buffalo WLA-G54C bridge/repeater to work with my Linksys WRT54G as a repeater. After try to config it for over 3 hours, I can't make it work. I call Linksys and Buffalo tech and they said Linksys didn't support WDS which Buffalo using.
I need to buy the Buffalo router to make it work with the repeater.  |
|
| WDS works from WRT54G to WRT54G at least. Try the tutorial here »www.seattlewireless.net/index.cg···ysWrt54g -- search on WDS. It's towards the bottom of the page. |
|
