Posted: Wed Jul 06, 2011 7:37 Post subject: Belkin f5d7230-4 (v10001ak? v1444?) only LAN port a/flash?
I have an old Belkin f5d7230-4 (sticker said 1001ak). Following the instructions from the supported router database and one thread in the forum (which said it really was a v2000), I flashed it with Firmware: DD-WRT v24-sp2 (12/24/09) micro-plus-ssh
Now I have the strange result that the wireless side works, but on the wired side, apparently all ports are considered WAN, as it sends DHCO discovers there:
I originally thought I bricked this router.
I tested all 5 ports, all show the same behaviour.
In DD-WRT the LAN is set to 192.168.1.1, but I can only reach it in that address using wireless.
dd-wrt does identify it as a v1444, which according to the router database requires a different firmware (Micro Generic dd-wrt.v24_micro_olsrd_generic.bin 2009-10-10 1,66 MB)
Am I stuck? Is there any way to force it back to using that IP on the wired LAN ports, so that I can try flashing the other firmware?
Is there maybe a better firmware (I resd the Belkin thread, which in some places seems to indicate to NOT trust the router database, but whenever I try finding a better authoritative list of what firmware to use I am shunted back to the router database??)
The main reason I am trying to flash this is that I want to use it as wireless bridge, so that i can connect a wired LAN in another room to my main router (an original cisco E2000).
any help is appreciated.
I'll try and collect some more info from the router once I switch back to its 'dd-wrt' SSID and add that later, in case it helps
Here is some more info, collected from the router's web interface (via the wireless interface):
Router Information
System
Router Name DD-WRT
Router Model Belkin F5D7230-4 v1444
Firmware Version DD-WRT v24-sp2 (12/24/09) micro-plus-ssh - build 13491M NEWD Eko
MAC Address 00:11:50:4F:D0:07
Host Name
WAN Domain Name
LAN Domain Name
Current Time Not available
Uptime 35 min
CPU
CPU Model Broadcom BCM4712 chip rev 2
CPU Clock 200 MHz
Load Average 0% 0.00, 0.00, 0.00
Network
IP Filter Maximum Ports 1024
Active IP Connections 33 3%
WAN
Configuration Type
Connection Type Automatic Configuration - DHCP
Connection Uptime Not available
IP Address 0.0.0.0
Subnet Mask 0.0.0.0
Gateway 0.0.0.0
DNS 1
DNS 2
DNS 3
Remaining Lease Time 0 days 00:00:00
LAN Status
MAC Address 00:11:50:4F:D0:06
IP Address 192.168.1.1
Subnet Mask 255.255.255.0
Gateway 0.0.0.0
Local DNS 0.0.0.0
DHCP Status
DHCP Server Enabled
DHCP Daemon DNSMasq
Start IP Address 192.168.1.100
End IP Address 192.168.1.149
Client Lease Time 1440 minutes
There is so much talk od 'this is bad, that is bad' etc, that finding what is useful is hard. The post talks about 'in this thread'(but it's only one post).
b) I found that the link shown refers to Brainslayer build 14929, when there seem to be much later ones (by going ../..), namely r15962
Are those recommended? If not why not?
Overall I find the whole layout of this webpage extremely confusing and the bits and pieces of 'don't use that', 'don't use this' , with xxx you wil need XXX, spread all over in apparently hundred of disconnected threads, wiki-entries etc very user unfriendly.
That the database recommends builds that are not recommended does not help (yes, I understand that new builds are being updated into it, but can bad builds not be deleted or at least not recommended for the time being?
Also, from the main-page the 'download' link only points to the database. Finding the other builds is very hard, as everywhere one finds a link to a subset (but likely not the latest anymore, nor a recommended version) etc.
Belkin routers are a mess, especially the older ones where they stuffed whatever router board they had into whatever box they had while not changing the label..
Read the peacock announcement too, (on clarifying some of you build choice misunderstandings.) DD-wrt can be user intensive and a steep learning curve to get all the nuances sorted out. Read slowly. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Belkin routers are a mess, especially the older ones where they stuffed whatever router board they had into whatever box they had while not changing the label..
This version has a different flash chip than the other versions, and it will enter a reboot loop if a special serial flash build is not used. If you have already flashed the device and it is in a reboot loop, you can still flash the correct build using TFTP.
This appears to suggest that you need to use a serial flash, but it is unclear whether this is just for initial flashing or always. It does state that if a different build does not work, you can recover it by a simple reflash using tftp. If you choose to do that, report back. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Hmmm. I'd be prepared to try that, but there seems to be a Catch-22:
1. If I try upgrading/flashing over via the commandline, the upload of the image (1.7M) to the router fails, as in its current state it only shows 276 (kbyte) free, so copying the file to /tmp stops and hangs the router
2. When I reboot the router, it does not give me a 5-second ttl=100 ping reply (boot-loader). It goes straight to ttl=64 (I am also not using the standard 192.168.1.1 address, but that does not seem to be a problem). Yes, I have the 'boot-wait' setting enabled.
3. I cannot use the 30/30/30 reset, as that will leave it in the mode where the LAN ports have no Ip address (DHCP discovers being sent), and thus I cannot TFTP a new image in. Once I enable the LAN-ports using the nvram command, it is too late for the tftp it seems...
sigh, unless someone has a bright idea how to overcome this, I seem to be stuck with this version (which doesn't look too bad so far, but I'd rather have something newer that has the recent exploit fixed etc).
Is there maybe a smaller 'very bare' image that I could flash (which needs to fit into the 256 or so kb available), after which I might have sufficient space for the real 1.7MB image in ram?
Or is there a nvram setting I can use to make more RAM available for flashing (at the expense of other, unused functionality?)
You'll need the SF build every time you update and there is no more recent SF build than 13491. _________________ Kernel panic: Aiee, killing interrupt handler!
You'll need the SF build every time you update and there is no more recent SF build than 13491.
Thanks, I guess
Is there any hope of getting a newer SF build one day?
And I'd still need some way to apply it? Is there such a thing as a very basic intermediate firmware that can be flashed by commandline when only >300kb of space are free, and which then allows one to scp/ftp/whatever in a larger file?
