Home Forums Getting Started OpenWRT?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #406

    Are there any docs for OpenWRT? I’ve used it before, but after installing to my Espresso board none of the network interfaces are up. I’ve only got access from the serial port and wasn’t able to get the interfaces up.

    I’ll need to do some more testing but I don’t think it reboots cleanly either. I had to re-run the steps (including the save) when booting from mmc.


    I couldn’t get the network working correctly either, but then I stumbled on to this Arch Linux wiki page about the ESPRESSOBin. The “Default system configuration” section has a useful hint on how networking on the ESPRESSOBin works.

    The ethernet port nearest the USB 3.0 port is the primary ethernet port, and is instantiated as the wan interface for connecting to the internet.
    This is set up via wan.network. The eth0.network file is required to bring up the link on the eth0 interface to bring up all three ports.

    That gave me enough to whip up a /etc/config/network file with a working wan interface.

    config 'interface' 'eth0'
            option 'ifname' 'eth0'
    config 'interface' 'wan'
            option 'proto' 'dhcp'
            option 'ifname' 'wan'

    I was able to get mine to boot correctly after using the provided documentation and OpenWRT-DD image from this official site. Using a WIN10 PC, I was able to access command line prompt through use of a microUSB cable and the supplied USB COM tty driver and using putty.

    Following the documentation; I was able to configure uboot to auto-boot to OpenWRT on the MMC on each powerup.

    I was able to define the eth0 and wan interfaces, and then set up corresponding networks using the following UCI commands on putty;

    # I brought up the physical interfaces, and gave eth0 an IP address.
    ifconfig eth0 netmask up
    ifconfig wan up
    # I set up the lan network to be a static IP (but have yet to define it as a DHCP server, as I plan to later);
    uci set network.lan=interface
    uci set network.lan.ifname=eth0
    uci set network.lan.proto=static
    uci set network.lan.ipaddr=
    uci set network.lan.netmask=
    uci commit network
    # I set the WAN network to be a DHCP client of another router device, so I could (hopefully) pull updates from the repository later;
    uci set network.wan=interface
    uci set network.wan.ifname=wan
    uci set network.wan.proto=dhcp
    uci commit network

    I then connected a run of CAT5E ethernet cable from a LAN port on my existing (and online) home router, to the WAN port of the espressobin. I kept the espressobin connected to my Win10 desktop via microUSB/Putty connection, since I needed to enter a few more commands yet…

    # I restarted the lan and wan networks
    ifup wan
    ifup lan
    # Then, I confirmed that I have an WAN IP address for the espressobin's WAN network which resides on my existing home network subnet.
    # I ran a handful of pings to Google to confirm i was online.
    ping -c 10

    HOWEVER, when I attempted to use opkg update, the command failed. I jumped online to find that the address listed in the OpenWRT image as the repository feed for packages (luci, dropbear, etc.) doesn’t actually exist online.

    Is there an third-party repository for this OpenWRT image?


    I think you may need to use the “snapshot” since DD is not released yet


    Unfortunately; there is no device tree for “mvebu64” architecture, only “mvebu”, which I would assume is most likely non-compatible with the espressobin. I could be wrong though…

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.
Signup to our newsletter

Technical specification tables can not be displayed on mobile. Please view on desktop