If you flash unofficial firmware, you cannot manually install kmod-* packages later. Other packages can manual install.

Just add option 'SHORT-GI-40' or option 'ieee80211n=1' in /etc/config/wireless you will see N mode in luci.

(Last edited by congquynh284 on 15 May 2014, 23:14)

I can add in ext4 support, however I will need to juggle around some packages, as otherwise the build scripts fail at the end complaining that the images are too large.  And indeed, for some router models the image actually is too large; so in the spirit of offering these builds to as many people on the ar71xx platform as possible I do what I can to keep things within the size limits as set out in the OpenWRT build scripts without modifying them just to squeeze a bit more in.

Now, as for the wifi in luci not showing the N support on the 3600, I am unsure on why that is so as I don't have a 3600 to test on.  I have a 4300 and that functions at full 300Mbits for 2.4GHz and 450Mbits on 5GHz.  However it too also does not show the support for N, but it does function at full N speeds.

I won't release a new build for now though; it seems a recent update in trunk has broken native dual stack ipv4/ipv6 again so I will need to sit down and track back and find the culprit revision then report this to the OpenWRT devs.  I've also got another current issue where my WDR4300 is bricked so I need to go buy a replacement, a bad flash really broke it, the sys light won't even flash.  Will need to get my hands on a JTAG USB adapter/cable...

Hi all,
I've uploaded a fresh build of images.  Note that I have not tested these as of today's date however I will be able to test in around 24 hours time.  For those of you bold enough to try this build now go right ahead, and do let me know how it went.

EDIT:  These images WILL BRICK YOUR ROUTER!  After finally getting my hands on a test unit, the end result is a bricked device which requires a serial cable to recover from.  Some models will allow you to via hardware put the router into emergency tftp mode, allowing you to tftp another image up, for those routers (TP Link noteably) that don't, you'll need a serial cable/JTAG to recover.

They were based on revision 40820.  I will be removing them from the server shortly based on my findings.  I must be missing something in my build environment after upgrading to Ubuntu 14.04LTS but it is odd since the compile works fine, no errors that I could see!

The latest WORKING image version I have is based on revision 40727.  I will try and find out why I can generate images but those images brick the devices; this may take a bit of time however.

Cheers everyone

(Last edited by AdamK on 23 May 2014, 08:54)

Looks like I have resolved my build environment issues.  Whew.  Turns out that some of the upgraded Ubuntu bits in 14.04LTS don't like it when you try to compile a more recent version of binutils other than the default when building OpenWRT from source code.

For now, I have built some Backfire images which are tested as working on a Linksys WRT54GL v1.1

http://www.mcservices.com.au/downloads/ … re-r40842/

These builds include:

*  DDNS
*  UPnP
*  QoS & Wondershaper
*  NTP client
*  radvd & IPv6 tunnel scripts
*  LuCI full (non SSL only) -- I tested a build using the luci-mini option but it was buggy esp with flashing another firmware not to mention lacking several features.
*  iftop on the CLI only for bandwidth monitoring

That's about all there's room for on the device, that left around 300KB free which obviously is needed for configuration changes and such to work and be saved.  Tight!!

I'll work on Barrier Breaker builds during the week and will also test these on two devices:
TP-LINK TL-WDR4300
Netgear WNDR4300

Until then the latest stable Barrier Breaker build is 40727, my own router has been up and running on that for 10 days without fault which is nice

(Last edited by AdamK on 25 May 2014, 05:40)

I need 40727's kmod-macvlan, other's kmod-macvlan is MD5 error. My devices is Netgear WNDR4300.
Future versions will provide kmod-macvlan， OK? Thanks.My English is very bad.
My email:yangzhiwei@gmail.com

I need 40727's kmod-macvlan, other's kmod-macvlan is MD5 error. My devices is Netgear WNDR4300.
Future versions will provide kmod-macvlan， OK? Thanks.My English is very bad.
My email:yangzhiwei@gmail.com

That is the 802.11Q VLAN module I believe.

I have built a fresh set of images for all based on trunk revision 40859 which I am in the process of testing.  And yes, it does have the 802.11Q VLAN kernel support in it.

I've added some bits too.  For generic routers I have added tcpdump and support for ext4 filesystems.
For the WNDR4300/WNDR3700v4 I have also added all the UBI features in, including ubi-flash, Strongswan (for ipsec support, since having 128MB of NAND flash means we have loads of space), arpwatch, full version of hostapd, iptaccount, whereis, and ds-lite support.  For those of you with generic routers that have enough space, I'll be providing the packages for the extra's I've listed -- to install these you can either attempt to get the normal OpenWRT bot built modules or you can install them manually via the CLI and wget them from my server.

To get these images (yes, I've confirmed they shouldn't brick your router unless you do something silly) go to:

http://www.mcservices.com.au/downloads/ … er-r40859/

The images are up and live on the server now.  I am testing the images with a TP-Link TL-WDR4300 and a Netgear WNDR4300.  This build version works fine on both so far.

(Last edited by AdamK on 26 May 2014, 12:18)

A quick update, another linux & openwrt buff who tests images for me has found that in some cases, the build based on trunk 40859 fails due to a change in the ath9k driver.  I've had a look and added the option to support some OEM cards.  Taken from SVN revision logs:

ath9k: make support for PC-OEM cards optional, reduces module size

This means that while the image does boot up as expected, for some router models the build will crash and reboot when attempting to bring up the wifi interfaces on the device.

In the build I am working on now based on trunk 40863, I have enabled this option, and also will only have the ath10k driver available for the TP-Link Archer C7 routers...I think they're the only one in the ar71xx supported router list that have the AC WiFi card in them?  Someone like to confirm this for me please?

Other than the above, build 40863 will be identical to build 40859.

Hi Adamk!  Thanks for all your great work here..  Without it most of us would be stuck. I'm trying to enable NFS client abilities for the device..  Kernel dump happens I believe related to kernel version mismatch to the one available to install.

root@OpenWrt:/proc# opkg install kmod-fs-nfs kmod-fs-nfs-common kmod-fs-nfsd
Installing kmod-fs-nfs (3.10.36-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Installing kmod-fs-nfs-common (3.10.36-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Installing kmod-fs-nfsd (3.10.36-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Configuring kmod-fs-nfs-common.
[ 5668.250000] CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 866800a0, ra == 80208140
[ 5668.260000] Oops[#1]:
[ 5668.260000] CPU: 0 PID: 8584 Comm: insmod Not tainted 3.10.36 #2
[ 5668.260000] task: 87bcf670 ti: 858d2000 task.ti: 858d2000
[ 5668.260000] $ 0   : 00000000 00000000 0000000e 00000000
[ 5668.260000] $ 4   : 00000001 00000004 8032da28 000793ed
[ 5668.260000] $ 8   : 8655d080 858dcd40 86905180 00000000
[ 5668.260000] $12   : 87b7e000 8656e764 00000000 86dc6a00
[ 5668.260000] $16   : 80337b28 858dce80 8585cbf0 858dcd00
[ 5668.260000] $20   : 0000003c 80337b28 00000000 00000023
[ 5668.260000] $24   : 00000000 8009d49c                 
[ 5668.260000] $28   : 858d2000 858d3d30 00000124 80208140
[ 5668.260000] Hi    : 0000000e
[ 5668.260000] Lo    : 00000000
[ 5668.260000] epc   : 866800a0 rpc_init_generic_auth+0x3c/0xe0 [sunrpc]
[ 5668.260000]     Not tainted
[ 5668.260000] ra    : 80208140 ops_init.constprop.11+0xfc/0x140
[ 5668.260000] Status: 1100dc03 KERNEL EXL IE
[ 5668.260000] Cause : 00800008
[ 5668.260000] BadVA : 00000000
[ 5668.260000] PrId  : 0001974c (MIPS 74Kc)
[ 5668.260000] Modules linked in: sunrpc(+) qcserial pppoe ppp_async option l2tp_ppp iptable_nat ath9k usb_wwan sierra_net sierra pptp pppox ppp_mpph
[ 5668.260000] Process insmod (pid: 8584, threadinfo=858d2000, task=87bcf670, tls=77788440)
[ 5668.260000] Stack : 80330000 858dce80 8585cbf0 80207f88 8039912c 858dcd3c 858dce80 8585cbf0
          858dcd00 80208140 80330000 85860000 800c0000 8585cbf0 8039912c 8585cbf0
          8039912c fffffff5 00000000 80330000 80330000 80208204 00000000 00000000
          80370000 00000000 80340000 8585cbf0 85860000 80208280 00000124 86680034
          8110217c 86680144 858d3ee0 00000000 00000000 86680184 00000000 00000000
          ...
[ 5668.260000] Call Trace:
[ 5668.260000] [<866800a0>] rpc_init_generic_auth+0x3c/0xe0 [sunrpc]
[ 5668.260000] [<80208140>] ops_init.constprop.11+0xfc/0x140
[ 5668.260000]
[ 5668.260000]
Code: 8c8305c4  10400003  24040001 <8c640000> 0082202b  00040336  24420001  00021080  00621821
[ 5668.630000] ---[ end trace 7b95b4da666e7ee2 ]---

find_hif: bootstrap = 0xaf055a
WASP BootROM Ver. 1.1
Nand Flash init
ONFI: Control setting = 0xb44
hdr: [0xbd004000 : 0xbd004000 : 0x3000 : 0xc200e86

again thanks for making bits available..

(Last edited by gary.collins on 28 May 2014, 23:06)

Gary,
For Kernel modules like the one you're looking to install, you cannot install the ones from the OpenWRT snapshot builds.  That said, if I haven't provided a kernel module package for something then it is likely not going to work for you.

I'll be doing a fresh set of builds next week, looks like your device is a WNDR4300 so I will see what I can do up.  Note that I am having problems with WiFi interfaces not coming up in recent trunk revisions for some of the generic devices (one being the TP-Link WDR4300) and I do have a separate thread open on the forums here, plus a ticket open for the devs too.  No solution is forthcoming so far...

Thanks Adam!  Looking forward to trying you WNDR4300 setup.  Can you provide a .config I could use to get me to the same point you are at?
I've not been successful to get latest trunk to build. make menuconfig is really hard to get it right.. Looks like you have the magic set to work.

NFS is one of the last parts to fix for me.  ?? why does overlay filesystem only 12mb instead of 128mb NAND.  I tried installing allot of
packages on device. Ran out of mem pretty quickly..  I tried to use an alternate overlay via the gui. Plugged in a USB stick with 5GB. I checked
use this as the root overlay.. Yet its not taking..   Any ideas?

I tried following this guide to enable USB device as an overlay.. It failed to work at boot..  I think because USB devices are not init early enough to
be seen.  Any ideas?

(Last edited by gary.collins on 30 May 2014, 20:01)

TO AdamK, Can you help me?
http://www.right.com.cn/forum/thread-142613-1-1.html

Hi all,
Due to ill health I've had to take a breather from a few things so as soon as I am back on deck I will update you all on what I have updated things with.
I also had a difficult task of migrating servers into VM's as well and I think most of this is now completed; the savings of this work out to at least $1 per day on electricity alone.  I had to do it since I've been unable to work full time now for over 6 months...and with that in mind $30 a month is a lot of money to save.

@AdamK, health matter the most so do take care of yourself. Appreciate what you have done to this community and looking forward to your future contribution.

Cheer.

Well it looks like finally sysupgrade may be available for NAND devices.

@41131      8 hours    blogic   
ar71xx: add sysupgrade support for wndr4300

I may be unwell but I think this alone warrants me doing a new build

There's also the latest openssl bug to get patched too.

Okay so I have uploaded images for all ar71xx generic and NAND generic routers onto the server.

Fixes:

*  Upgrade OpenSSL to 1.0.1h to patch latest security hole
*  Re-wrote config for NAND generic devices i.e. WNDR4300 & WNDR3700v4 to allow for major changes made to trunk by OpenWRT devs
*  Sysupgrade features now enabled for WNDR4300 & WNDR3700v4 (tested as working on WNDR4300)
*  pppd version bumped to 2.4.6 from 2.4.5
*  All trunk updates as per https://dev.openwrt.org/log up to r41336

Find your image here http://www.mcservices.com.au/downloads/ … er-r41336/

Enjoy.

hi,AdamK,thanks for your  working on building OpenWRT.I have looking for your update for a few days .Today I have install your latest firmware on my wndr3700V4 and it works well.But when I mount my USB harddisk (the file system is ntfs)with mount /dev/sda1 /mnt/sda1 and the file system is readonly even I use mount -o rw .Then I want to install ntfs-3g with opkg install ntfs-3g and I got
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for ntfs-3g:
*     kernel (= 3.10.36-1-427233cd53f4a891ecf66f4299844a5a) *
* opkg_install_cmd: Cannot install package ntfs-3g.

another is how to mount cifs  , there are too many errors===>  http://wiki.openwrt.org/doc/howto/cifs.client   
So,what I should do.And would you mind build a ntfs-3g.ipk in your packages.

(Last edited by zhouruixi on 25 Jun 2014, 15:46)

I'm surprised that I had not built that package already.  For some reason I thought I had.  You are quite correct however, that package is not being built and according to the wiki it needs to be.  I will do a fresh build today including that package and also will include fdisk which according to the wiki will allow for manual scripting of hotplug features.

As for CIFS, I will try adding that in for all ar71xx devices, however if it makes the image too large I may have to omit it for generic devices and only offer it for devices with 16MB of flash & NAND generic devices (which would cover off on your WNDR3700v4).

Thank you very much for highlighting that mistake!

(Last edited by AdamK on 25 Jun 2014, 23:06)

Okay yes having CIFS and the extra modules with that for it to function properly does blow out the size of the images.

So this is what I will do.  I will have it compiled in for the NAND generic devices and for the TP-LINK TL-WDR3500-3600-4300-4310 and MW4530r-v1

However for all other devices, Samba, and file system support will not be in the base image.  What I will do though is offer the ipk files on the server for you to download and install should you desire Samba functionality and have the flash space to support this.  Otherwise the image with everything included is too large for several devices.

Changes so far with this build:
*  Removed the ath10k driver for all devices except the Archer C7 v2 which needs this for 802.11ac
*  Removed Samba and the following filesystem support for all devices except all NAND generic and TP-Link devices listed above.  Filesystems are ext4, ntfs, fat32/ms-dos and associated supporting kernel language modules.  Should users of affected devices need this support they can download the ipk files from my server
*  Except as mentioned above, added CIFS, UTF-8, NTFS-3G packages/support
*  TP-LINK Archer C7 v2 now is built separately and is the only device built with ath10k support (for 802.11ac)
*  Corrected a configuration regression which meant the block-mount package was no longer compiled, this is required for various filesystems to mount in openwrt.

Sorry if that all seems confusing, but with all the features, many devices now do not have enough flash space

(Last edited by AdamK on 26 Jun 2014, 01:47)

Adam,
Thank you for all the hard work building and providing all these images.
I'd really appreciate it if you could also post your config file to your site, so I could try my hand at building images.
Is it possible for you to create an ar71xx/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-x86_64.tar.bz2
so that we could use that to create custom images with different packages?
Thanks.

Bob

I'm testing a build based on r41337 presently, when I upload that to the server I can see about putting up the configs as well.  They have changed since the recently posted r41336 build so I'll check that out.

Will see how large the imagebuilder tarball turns out to be -- I have limited upload bandwidth and don't want to bog down the bandwidth too much.  I may see if I can increase my upload bandwidth but if it becomes a cost thing I can't afford to do a lot about it.
EDIT: 67MB for the NAND generic tarball so I can live with that.  Will do another for the normal generic.

(Last edited by AdamK on 26 Jun 2014, 04:06)

Okay so the latest build is on the server after testing for several hours.  I know that at the very least these images work on a TL-WDR4300 and WNDR4300, and are stable.

http://www.mcservices.com.au/downloads/ … er-r41337/

These images are as per post # 69 above.

I have also put in the directory the imagebuilder tarballs for NAND and generic devices.  This will aide you in customizing your images further, ultimately mostly based on the code I have compiled.

For those of you who just want to install a couple of extra packages in addition to the base images I have built, you'll find a repository of ipk files that I have built in the packages subdirectory.

Finally, for those who just want to compile from scratch without the headache of working out what packages to add, what to configure etc, I've also put several .config files in the base directory.  generic.config is for most routers in the list, archerc7.config is for the archer c7 v2 with the 16MB flash and properly support 802.11ac/ath10k, wdr4300.config is for the TL-WDR4300 (TP-LINK) which has most features pre-built into the image, and lastly wndr4300.config which is for the Netgear WNDR4300 & Netgear WNDR3700v4.

As always, appreciate feedback, bug reports etc that you guys find.

It might be more informative if you would (also) run "./scripts/diffconfig.sh" for each router and provide its output instead of the full .config file. That diffconfig lists only the differences compared to global default and excludes the thousands of lines of non-selected non-related packages. That output can be used as a seed .config for "make defconfig" or "make menuconfig", which will explode it to a full .config.

Thanks hnyman I'll work on that -- I only run 4 different config files for everything in the ar71xx list as you can see but I guess some ppl would like to know the selections.  Should I post that output on here?

OK,I'am not good at English。And I want to say:我必须要好好学习英语了！
I will try to building by my self based on your wndr4300.config
Any how,thanks for your hard working.
Cheers!

(Last edited by zhouruixi on 26 Jun 2014, 13:26)