htw
join:2004-04-18
Rio Rancho, NM
1 edit | reply to techie06
I had a USR8054 sitting around, since I normally use a Linksys WRT54G, so I thought why not try this... since the USR Firmware sucks.
I have now had the 1.19 DI-624+ firmware running for 4 days, with no problems.
Here is my setup:
Actiontec GT701 in transparent bridge mode ->
USR 8054 WAN port.
Connected to the LAN ports of the 8054 are a MS Switch, Linksys print server, and 1 PC with built in Realtek ethernet.
Connected to the Switch are 3 other PC's, with 3Com ethernet cards. These are connected a bit of distance by cat5 cable through the location.
1 PC situated about 100 feet away using a Linksys wireless PCI card.
2 Notebook PC's, one with an Intel wireless PC card, the other with a Linksys wireless card.
Oh, and all the wireless clients except the PCI card are 802.11g, the card is 802.11b.
The wireless is set up with private SSID, 6 chars long, WPA-PSK encryption (TKIP). Best I can tell, this firmware does not support AES, it just does WPA-802.1x (Radius) and WPA-PSK(TKIP). There are no problems so far, the clients stay connected steadily, and get good signal and throughput. Wireless power is set to highest, with speed enhanced mode enabled.
Of course, on the hardwired side, no issues at all.
The built in DHCP server, while not needed, I enabled and disabled DHCP on the Win2k3 server (for testing). Using some static leases, some dynamic. All working great.
Have tried various things for incoming connections (Virtual Servers... heh), firewall'ing certain PC's for a time, or even throwing an old copy of Diablo 1 on a PC and trying it out.
The PC's, if using SSDP, do see the router via the upnp feature.
VPN passthrough, multicast streaming, dynamic DNS updates, all testing and working fine.
I have not tried DMZ function yet.
All log features were enabled, and for 4 days, no router resets and the DSL connection has not been dropped.
All-in-all, everything seems quite steady, and honestly I like this way better than the WRT54G (even with custom firmware), and definitely no contest as far as the USR Firmware goes.
I have not tried to see if you can recover the USR firmware, if you are having problems, but here are a couple suggestions:
1) When you do firmware flashes, please remember, it's best to reset to factory defaults, then reboot router, then flash, then reset factory defaults, reboot. THEN set your router up.
2) Try this recovery procedure for dlinks, I do not know if it'll work, but worth a try.
On a hardwired PC, config your TCP/IP properties manually with: IP 192.168.1.2 (or other unused IP from 2 to 254), subnet mask 255.255.255.0, gateway 192.168.0.1. DNS can remain blank.
Unplug power cable from the router, hold in the reset button, plug it in. Keep holding the button for 15 seconds, then let it go.
This puts the router in crash recovery mode. There are two ways to try this recovery, via web interface, and via tftp.
For web, now open IE on the statically assigned IP PC, and go to »192.168.0.1. User admin, password blank. Select your USR firware file, and try to upgrade it.
For tftp, look on google or soemthing, and grab a tftp client. When you get the router in crash recovery mode as above, use the tftp program to send the USR firmware to the router.
Directly after the upgrade is finished (web or tftp), go to the router (leave it powered on), and reset it. Hold in the rest button for 15 seconds, the router will reset.
Now restore your PC to use DHCP (automatic), renew the lease, and see what IP information you have. If you have an IP in the 192.168.0.0 network, you're still dlink, if it's in the 192.168.1.0 network, you have USR. Either way, browse to either 192.168.0.1 or 192.168.1.254 username admin password blank, to verify dlink is still there, or usr flash worked.
Honestly, if this doesn't work, I have no help for you.
Personally, I'm sticking with the dlink firmware. 
Edit: Dyxlexic! |
