{"id":1536,"date":"2011-11-23T22:28:59","date_gmt":"2011-11-24T02:28:59","guid":{"rendered":"http:\/\/www.braindeadprojects.com\/blog\/?p=1536"},"modified":"2011-11-23T22:28:59","modified_gmt":"2011-11-24T02:28:59","slug":"openwrt-on-the-mikrotik-routerboard-493ah","status":"publish","type":"post","link":"http:\/\/www.braindeadprojects.com\/blog\/what\/openwrt-on-the-mikrotik-routerboard-493ah\/","title":{"rendered":"OpenWRT on the MikroTik RouterBoard 493AH"},"content":{"rendered":"

I recently came across a MikroTik RouterBoard 493AH<\/a> at work. We’d acquired the device among numerous other pieces of equipment from a now defunct wireless ISP.<\/p>\n

\"\"<\/a>
It smells of Goo-Gone and looks to have dandruff.<\/figcaption><\/figure>\n

The 493AH features 9 ethernet ports, can accept POE on its WAN interface, has 64M NAND,\u00a0 128M RAM, and can support 3 mini-PCI cards. Configuration can be performed via a serial interface and there is an external power connector available if POE isn’t used.<\/p>\n

The device itself wouldn’t boot, only hang at the RouterBoot bootloader. Attempts to boot the NAND image failed, but the bootloader gives an easy option for downloading an image to it via TFTP<\/a>.<\/p>\n

\"MikroTik<\/a>
A brand that's loved by WISPs<\/figcaption><\/figure>\n

Looking around, it appears the 493AH is an Atheros AR7161<\/a> .. an architecture readily supported under OpenWRT<\/a>. Sure, I could just re-install RouterOS<\/a>… but let’s do that later.<\/p>\n

To install OpenWRT to the 493AH, first format the NAND. This can easily be done via the bootloader (option e):<\/p>\n

\"FormatNAND\"<\/a>
Waxing the memory<\/figcaption><\/figure>\n

Next, use subversion to check out the Backfire version of OpenWRT:<\/p>\n

mkdir ~\/svn\/<\/p>\n

cd ~\/svn\/<\/p>\n

svn co svn:\/\/svn.openwrt.org\/openwrt\/branches\/backfire backfire<\/p><\/blockquote>\n

Building the image is fairly easy, all configuration is done via a “make menuconfig<\/em>“. First, we’ll build a small initramfs<\/a>. This will give us a tiny environment to boot into the device and later install our kernel with.<\/p>\n

Ensure that you’ve selected the AR71xx target architecture…<\/p>\n

\"\"<\/a>
Building an AR71XX System<\/figcaption><\/figure>\n

Next, I opt for the default profile (to give me all the modules I should need)<\/p>\n

\"TargetProfileSelection\"<\/a>
I demand everything!<\/figcaption><\/figure>\n

And finally, select the build of a ramdisk image:<\/p>\n

\"BuildRamDisk\"<\/a>
Fun with arrow keys and a spacebar.<\/figcaption><\/figure>\n

After you’ve made your selections, exit saving your changes, and run make<\/em>. The build itself will take some time, but when you’re finished you’ll have the first key ingredient – a basic root filesystem embedded into the kernel. This image is essentially a “Live CD” that we’ll use to install our real kernel.<\/p>\n

As with all of the images you create, you’ll find them under ~\/svn\/backfire\/bin\/ar71xx\/ Our newly created image is openwrt-ar71xx-vmlinux-initramfs.elf<\/strong><\/p>\n

Next, we’ll want to build our actual system. To do this, re-run make menuconfig<\/em> and select the packages that you wish to compile and include in your firmware image. After you’ve made all of your selections, change your Target Image to squashfs and exit saving your changes.<\/p>\n

\"SquashFSBuild\"<\/a>
Planting a SquashFS Garden<\/figcaption><\/figure>\n

A quick make<\/em> later, and we now have a working rootfs and kernel – in addition to our initramfs to install the system with:<\/p>\n

openwrt-ar71xx-vmlinux-initramfs.elf <\/strong><\/strong>(Our temporary kernel)
\nopenwrt-ar71xx-vmlinux.elf<\/strong> (The kernel)
\n<\/strong>openwrt-ar71xx-root.squashfs<\/strong> (Our Root Filesystem)<\/p>\n

We now have almost<\/em> everything we need.<\/p>\n

\"\"<\/a>
Oh, the sticker says "Warranty Void if Removed"...<\/figcaption><\/figure>\n

To install our kernel, we need a few additional tools. First off, we need to configure a DHCP<\/a> server (I’m using ISC’s). Here’s an example from my dhcpd.conf file:<\/p>\n

authoritative;
\nddns-update-style interim;
\nsubnet 192.168.1.0 netmask 255.255.255.0 {
\nrange 192.168.1.20 192.168.1.40;
\noption subnet-mask 255.255.255.0;
\noption routers 192.168.1.1;
\n}<\/p>\n

host routerboard
\n{
\nhardware ethernet 00:0c:xx:xx:xx:xx;
\nfixed-address 192.168.1.17;
\n}<\/p>\n

 <\/p><\/blockquote>\n

Next, we’ll need a TFTP server. I prefer atftpd<\/a>. No configuration is necessary, simply create a directory to serve files from and start the server:<\/p>\n

mkdir \/tftpboot\/<\/p>\n

chmod 777 \/tftpboot\/<\/p>\n

atftpd \u2013\u2013daemon \/tftpboot\/<\/p><\/blockquote>\n

The only file that has to be loaded via TFTP is the initramfs kernel. Copy it to \/tftpboot with the filename vmlinux and we’re ready to start.<\/p>\n

cp ~\/svn\/backfire\/bin\/ar71xx\/openwrt-ar71xx-vmlinux-initramfs.elf\u00a0 \/tftpboot\/vmlinux<\/p><\/blockquote>\n

Power up the RouterBoard and quickly press the space bar. Select “boot over Ethernet<\/em>” and it will download and boot the linux kernel.<\/p>\n

\"BootEthernet\"<\/a>
Opting to boot via TFTP<\/figcaption><\/figure>\n

Next ,we need to install the kernel and root filesystem. Here’s where I ran into my first problem – the kernel has no init variable specified so it panics. Thankfully it clearly states this: “Kernel panic – not syncing: No init found.\u00a0 Try passing init= option to kernel.<\/strong>”<\/p>\n

\"KernelPanic\"<\/a>
Gratitous Image of a Kernel Panic<\/figcaption><\/figure>\n

Unfortunately the boot loader doesn’t appear to allow one to specify command line options for the kernel and I was unable to find a way to set this when configuring the kernel. (I vaguely recall seeing it when compiling for x86, but may be mistaken). Either way, the solution is simple:<\/p>\n

Add your kernel parameters to a file (kernel-params in my instance) and use objcopy to insert it into the ELF file:<\/p>\n

The options I used are:<\/p>\n

root=\/dev\/mtdblock2 rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 init=\/etc\/preinit<\/p><\/blockquote>\n

The toolchain supplied with OpenWRT contains a MIPs compatible version of objcopy that will allow you to add a kernel parameters section to the ELF file:<\/p>\n

cd ~\/svn\/bin\/ar71xx\/<\/p>\n

~\/svn\/backfire\/build_dir\/toolchain-mips_r2_gcc-4.3.3+cs_uClibc-0.9.30.1\/binutils-2.19.1\/binutils\/objcopy \u2013\u2013add-section kernparm=kernel-params\u00a0openwrt-ar71xx-vmlinux.elf<\/p><\/blockquote>\n

To install the kernel, configure an IP on your ethernet\u00a0 (or bridge) interface, mount \/dev\/mtdblock1 and use scp to copy your kernel to the device (as “kernel”).<\/p>\n

ifconfig br-lan 192.168.1.10<\/p>\n

mkdir \/mnt\/boot<\/p>\n

mount \/dev\/mtdblock1 \/mnt\/boot<\/p>\n

cd \/mnt\/boot\/<\/p>\n

scp 192.168.1.1:~\/svn\/backfire\/bin\/ar71xx\/openwrt-ar71xx-vmlinux.elf kernel<\/p><\/blockquote>\n

 <\/p>\n

Next, install your squashfs root filesystem to \/dev\/mtdblock2. Unlike the kernel, This shouldn’t be mounted when installed.<\/p>\n

cd \/tmp\/<\/p>\n

scp 192.168.1.1:~\/svn\/backfire\/bin\/ar71xx\/openwrt-ar71xx-root.squashfs .<\/p>\n

cat openwrt-ar71xx-root.squashfs > \/dev\/mtdblock2<\/p><\/blockquote>\n

After the root filesystem is installed, reboot the device and welcome to OpenWRT on the RouterBoard 493AH<\/p>\n

\"ItBoots\"<\/a>
It's Alive!<\/figcaption><\/figure>\n

I’m not quite sure what I’ll end up doing with the 493AH just yet. The neighborhood wireless system now consists of 2 Engenius EOC2610 units running firmware images based off OpenWRT… so there may be the potential to add it to the fray.\u00a0 The 9 ethernet ports would make it ideal for a Quagga router (although I already have one). Installing the MikroTik RouterOS and working with MPLS is another options. Right now it sits on my desk at work as a “pretty cool paperweight with a lot of potential”.<\/p>\n

If you have any suggestions – please let me know.<\/p>\n","protected":false},"excerpt":{"rendered":"

I recently came across a MikroTik RouterBoard 493AH at work. We’d acquired the device among numerous other pieces of equipment from a now defunct wireless ISP. The 493AH features 9 ethernet ports, can accept POE on its WAN interface, has 64M NAND,\u00a0 128M RAM, and can support 3 mini-PCI cards. Configuration can be performed via … Continue reading OpenWRT on the MikroTik RouterBoard 493AH<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[37,38,1,18],"tags":[],"class_list":["post-1536","post","type-post","status-publish","format-standard","hentry","category-mikrotik","category-openwrt","category-what","category-wireless"],"_links":{"self":[{"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/posts\/1536"}],"collection":[{"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/comments?post=1536"}],"version-history":[{"count":89,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/posts\/1536\/revisions"}],"predecessor-version":[{"id":2099,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/posts\/1536\/revisions\/2099"}],"wp:attachment":[{"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/media?parent=1536"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/categories?post=1536"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.braindeadprojects.com\/blog\/wp-json\/wp\/v2\/tags?post=1536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}