DD-WRT /
Belkin F5D7230-4 v2000
- Factory firmware 4.05.03; has run DD-WRT v24-sp2 micro-plus (r13491M 2009-12-24)
- 2MB ROM / 8MB RAM
- 2014-02-20: DD-WRT firmware was installed using the tftp-on-reboot method as described in the Belkin F5D7230-4 pages on the DD-WRT wiki using my I-Opener running NetBSD 3.0 as the sender:
- This unit is not fully functional with DD-WRT firmware. The WAN port is not usable ordinarily, but the LAN ports are. (Or, one can assign the LAN ports to the WAN side and all five ports work, but then you have no wired WAN-to-LAN routing.) My main purpose with this unit is to use it as a client-bridge, allowing one or more wired devices to be routed through the router wirelessly to the main LAN, so this limitation works fine for me. Also, be aware that immediately after initial flashing DD-WRT the LAN ports are not active at first. But after making one manual configuration change via wireless TELNET to the unit the ports can be activated and then function fine.
- Using DD-WRT wiki instructions, after the reflash I telneted in and entered these commands to enable the wired LAN ports:
nvram set Belkin_ver=2000 nvram commit reboot
then, to prepare for configuring the client-bridge:nvram set wan_to_lan=yes nvram set lan_ifnames="eth0 vlan0" nvram set port0vlans=0 nvram set lan_ifname=eth0 nvram set wan_ifname=vlan1 nvram set wan_ifnames=vlan1 nvram commit reboot
- One thing never to try through the web-based GUI: Never enable the WAN-port-to-LAN checkbox. It will hang the router and only a power-on-hold-the-reset-button action will recover, but then LAN ports are disabled again, so back to square one. Take care. Otherwise, I used the GUI to enable the client-bridge function, set the wireless config and I was in business.
- 2014-05-06: This unit will hang on occasion, roughly once ever week or so, maybe every 10 days. It might be running out of free memory or something as the routing tables grow from various usage. In any case, two weeks ago I set up a cron job via the Administrator tab to reboot the system every Sunday at 2AM. {-Seemed to be working, but this morning (Tuesday) I find that the system is again locked up.} (False alarm) However, I did discover that the router has NOT been rebooting via cron. Today, the system indicates that it has been up for 17+ days! So the cron jobs configured in the Administration tab are not effective! I might want to reflash this unit to it's original factory firmware and use a Linksys WRT box as my client bridge, as was successful for the past couple of years.
- 2015-04-11: The factory firmware can be restored using the DD-WRT GUI firmware update page, as long as the factory firmware .BIN file is stripped of the first 28-byte header.
- 2015-04-12: Reverted to factory firmware 4.05.03 using the DD-WRT GUI firmware update page. Went without a hitch.