This build offers these extras on top of a official OpenWRT 12.09 release:
- Recent code from the Attitude Adjustment branch
- Wireless Country code configurable by user (enables use of channel 12 & 13 in my country)
- IPv6 support
- Extra WAN connectivity (PPPoA, PPPoE, ATM Bridge (AAL5), 3G USB dongle)
- Quality-of-Service settings
- USB storage support (filesystems FAT32, ext2/3/4, more can be installed)
- File sharing over Windows networking (Samba)
- UPnP support
- Wake-on-LAN support
- Dynamic DNS settings (new!)
This build is based on r37838 of the Attitude Adjustment branch, compiled for the TP-Link TL-WR1043ND. The official version number is still 12.09, but the IPv6 configuration framework from trunk has been backported to the Attitude Adjustment branch. Because of this you should use the instructions for OpenWRT 12.09.1 and current trunk builds when configuring IPv6 networking.
Compared to my previous build (r36655), as said above, there is a new IPv6 framework in which
radvd has been replaced by
6relayd. The firewall has also been upgrade to the
firewall3 version, which enhances flexibility and configuration options, so there is less need to touch
iptables directly. LuCI’s version has also been bumped and the wireless drivers are also a bit more recent. On the subject of wireless stability there aren’t that many advances in this build. But in the current trunk code there are experiments with software queues for all packets going over wireless. So far this seems to help with stability and fairness, but it has not been backported yet. When this has happened I plan to quickly release a new version of my builds.
New IPv6 framework backported from trunk. If you use IPv6 you will have to redo that configuration, because
radvdis no longer used nor included and has been replaced by
6relayd. Do have a look at the OpenWRT Wiki - OpenWrt native IPv6-stack for more information, and tips to migrate from the old to the new framework. Because of the new framework, look at instructions intended for OpenWRT 12.09.1 (and current trunk) when configuring IPv6.
Driver code for the WiFi chip has been updated to code with datecode 2013-06-27, and some extra patches from the OpenWRT team. Previous version used by my builds was dated 2013-02-22.
Firewall has been upgraded to
firewall3. This version adds some more options and flexibility, have a look at OpenWRT Wiki - Firewall configuration for it’s configuration.
Dynamic DNS updater wasn’t working correctly in the previous build. This should be fixed now, feedback is welcome!
Wake-on-LAN functionality wasn’t working fully. This should also be fixed now, feedback is welcome!
Notes for upgraders
When you use IPv6 manual intervention is required to get this up and running after an upgrade, due to the new IPv6 framework. Have a look at the first bullet under the previous heading for more information.
You will want to update the software repository configuration (
opkg.conf). Because I have added my own repository to the configuration file, it gets left alone by the
sysupgrade script (since the file is modified compared to the OpenWRT release). It will still work, but will point to the repository for the older version, which might cause dependency issues. Updating it can be done via the LuCI GUI and is therefor quite easy:
In LuCI, go to System > Software and select the Configuration tab.
Change the lines starting with
src/gzto these two new ones. Only the release-number needs to be incremented.
src/gz attitude_adjustment http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/packages src/gz ultrawrt-chunky http://openwrt.sjoosten.nl/files/attitude_adjustment/12.09/r37838/ultrawrt-chunky/ar71xx/packages
Submit to save the changes.
Always confirm the MD5 hash is correct before flashing! LuCI shows you the hash after you have uploaded the file.
For those installing OpenWRT for the first time, the factory image:
For those upgrading from another version of OpenWRT, the sysupgrade image:
The configuration file used for this build is also available:
These builds are provided as-is, and the licenses for it’s components apply to each respective component.
I am furthermore not responsible for broken routers, angry users or etherkillers going haywire and killing your pets.
I welcome feedback. Preferably using the forum, but here on the website is will also be possible once I have implemented the functionality.