OpenWrt Forum Archive

Topic: Is my TP-LINK TL-WR703N bricked now?

The content of this topic has been archived on 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I flashed openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin to my TL-WR703N clone. I understand the GUI cannot work since I got only 4MB flash memory. I guess I should have flashed the command-line-only version.

On power-up the green LED starts a ~25 seconds blinking sequence and then remains green. Is my router bricked now? Or is there a way to establish a LAN connection again?

Best regards,

(Last edited by nirwana on 24 Apr 2018, 09:23)

You did flash a command line only version.  Builds that don't have a release number in the file name are daily snapshot builds.

The LED should blink for a while then come on steady when bootup is complete.

Connect the Ethernet port to your PC and ssh to the router at  It will not respond to http because it does not have that feature in the build.

(Last edited by mk24 on 24 Apr 2018, 02:01)

Thank you very much! I'm back in :-)

The hard reset I did yesterday must have cleared all my stupid settings so I'm fresh again. I had tried to install that LuCI thing to no avail. 4MB flash is just not enough. Now I'll stay with command line.

I want to make the TL-WR703N act as a WiFi-client bridge. Any recipe for that?

Thanks again.

(Last edited by nirwana on 24 Apr 2018, 09:25)

I followed the OpenWrt guide to

Configure A(ccess) P(oint or 'hotspot') + STA(tion or 'client')

However, there is

Step 3: Revert to AP Only mode on boot when Hotspot is not available

Do I really need that? I thought I can always access my router via the LAN port, can't I?

And if I don't want to run an access point at all, can I simply omit the second wifi interface?

config wifi-iface
    option    device    radio0
    option    network    lan
    option    mode    ap
    option    ssid    OpenWrt # ssid for wireless clients
    option    encryption none # not recommended for deployment
#    option    key    everybody_knows_this_key

Best regards,

I have

BusyBox v1.22.1 (2014-10-30 00:39:54 UTC) built-in shell (ash)
 CHAOS CALMER (Bleeding Edge, r43103)

Today I found I also got the UCI commandline interface built in

root@OpenWrt:~# uci help
Usage: uci [<options>] <command> [<arguments>]

    export     [<config>]
    import     [<config>]

Shouldn't I use the following method instead of vi - editing the config files?

1   type uci set network.lan.ipaddr='new-ip-address' and press Return
2   type uci set network.lan.gateway='your-gateway-address' and press Return
3   type uci set network.lan.dns='dns-address-here' and press Return
4   type uci commit && service network restart (this will save the changes and restart network interfaces)
5   the ssh session will not work anymore because the device has changed address, this is normal
6   now you can connect the network cable from the device's LAN port to your existing network (the other router's LAN ports usually)
7   connect again to the device at its new address as defined above

It is the same either way.  Running the uci commands changes the files one line at a time.

Yes, you're right. Thanks for answering.

Would you mind to have a look at my previous question regarding the second wifi client?

Thanks in advance,


The discussion might have continued from here.