Building all packages will likely be too burdensome. You might focus on the usual/common ones plus the packages that have kernel dependendies. Those can be difficult/impossible to install from the buildbot snapshot repo. Users could install normal packages from the snapshot repo.

Sorry if this has been answered somewhere else but I couldn't find any clear information.

I've been an OpenWRT user for a while now, running the latest 15.05.1 CC on my WRT1900AC v2 and I wanted to try one of your more up to date builds davidc502 but since last updating and returning to site this whole LEDE thing has popped up!

So now I'm really confused, which of your builds to stick to? More of the recent posts in this thread seem to allude to the LEDE builds having more teething problems, I guess since it's newer?

Anyway, my real question for your David or someone else who knows is, what's the difference? Why are you building for both? Will you continue to build for both?

Thank you!

@AuriconXS

The short answer is that many of the developers broke away from OpenWrt and formed LEDE. 

Currently I'm only building LEDE, so if you're wanting the latest wifi, patches etc from OpenWrt, I'd recommend another build.

Really, which is better is a bit subjective, so I do recommend you try lede, and see for yourself. However, don't keep any setting from OpenWrt if you decide to try lede, because it's very likely to break.

@davidc502

Thanks for getting back to me, apart from the latest wifi and patches, there are no functional differences right?

They both contain many of the same packages. LEDE was built from OpenWrt trunk, from a few months back, but has branched from there. So, there are differences, I just don't know about the exact functional differences because there are thousands of packages to choose from... << good thing

If you're a casual user, either lede or openwrt is going to be fine for you.

Update - New images available

All luci-apps have been included in the repo this time. I've tried to go back and make sure everyone's requested packages are included including all language support, but there's a chance someone was left out, sorry about that. I guess I didn't expect so many people being involved. It's okay, because this has helped to push me into learning more about what happens behind the curtain of OpenWrt/lede.

I did compile the new 3200acm, but didn't upload those images this time. Since it's such a new product it will take a few months for people to start requesting it.

Thanks David!

Any initial impressions so far on the latest WRT3200ACM catered driver on your ACSv1? I am tempted to flash this afternoon as my main driver is an ACSv1 as well.

If you need some testing, I also have a WRT3200ACM, but haven't popped it's cherry yet as I see over in the DD-WRT threads it seems there is still some growing pains to be sorted out.

Also, QQ, I notice you seem to also be providing a 9.22 build, Is this your deemed last "stable" build you are hosting to us as a fall back?

(Last edited by cybrnook2002 on 27 Oct 2016, 16:37)

If you want to give it a try 3200acm.zip --  http://davidc502sis.dynamic-dns.net/3200acm.zip

Correct on the fall back... There have been some who have asked me to archive older builds, so that's the reason why they are out there.

There are the DFS issues with Wifi (Driver claiming it detected radar), but haven't had any performance issues for quite some time. So, generally, I'm very pleased with the driver. There have been a few times where I've gone back and tested the Linksys firmware, but I still think, at this point, the opensource driver is a bit better.

Question, I see you are recompiling the packages as a moving target here with the builds :-) (must be stressful to begin with).

If a user was to stay on an older build, or potentially fall back to an older build (9.22 for example). Would they still be able to set the repo's to yours and download and install the packages, or would they now face a mismatch error because you would have already updated the packages in your repo to coincide with the latest kernel etc, and not the version that the older build was on...?

(Last edited by cybrnook2002 on 27 Oct 2016, 18:07)

Most certainly a mis-match error.

I need to just create a archive page to put both the older images and matching packages together. That way no worries about a mismatch.

Would it also be possible to just download all the corresponding packages you built/complied for a specific release and then maybe place them on a USB drive or something. Then, down the road if a user decides that they did want to install one of those packages (knowing surely it wouldn't be available anymore as you would have recompiled for a new build by then and that's what you would be hosting. Unless you do like you said in the prior and publish packages for older builds), could a user just change the path in the software path to reflect hard paths for the repository. Then install directly off a USB drive or something?

Like /mnt/package_repo/core etc..... (/sda.... not sure what LEDE uses as a mount point off the top of my head... likely /mnt though...)

If we are keeping known good older builds around, would be a shame to have your work go to waste as you did put time in compiling packages for that build at one point in time.

(Last edited by cybrnook2002 on 27 Oct 2016, 18:27)

The packages can be scp'd to the router.. Otherwise I think it is relegated to pulling packages via http.

There may be a way to just increment a directory on the webserver with every new build, and reflect that change in the build itself. This way the image loaded would always be pointing to the right packages. I do have plenty of space on the webserver, so no problem there. I guess it would be a matter of figuring out how much administration is involved on this end.

@davidc502 awesome build I really like it. I have one question
how can I install luci-mod-rpc in LEDE? It is required for the home automation program I run.
Thanks

TDW

WRT 1900ac LEDE (davidc502 Build)

@davidc502,

Thanks in advance, I notice you had the packages uploaded to your site for the 9.22 build :-)

I hope you don't mind, I wrote a couple small curl scripts to basically download the contents locally here at home for your 9.22 repo and the 10.27 repo (base, luci, packages, routing, telephony).

QQ, if I have the packages here locally on my end, and want to use a local copy that I have downloaded from you, what's the best way for me to deploy one (or many) to the router?

I assume I could follow this guide:
https://wiki.openwrt.org/doc/techref/opkg

example:

opkg install /tmp/david_is_the_man_v1.0.ipk

EDIT: and I notice there are a few locations here , like luci and packages. So for example I wanted to install "ad-block", I notice there is an ab-block ipk in luci and in packages. Which would be the correct one?

(Last edited by cybrnook2002 on 28 Oct 2016, 16:25)

Hi @davidc502. I've been testing your latest build today for the first time. Great work thank you. I have a couple of suggestions.

• If the Ash shell could have a history file ~/.ash_history to remember the last shell commands typed even after logout. In the busybox compiled .config:
  CONFIG_FEATURE_EDITING_HISTORY=255
  CONFIG_FEATURE_EDITING_SAVEHISTORY=y
  CONFIG_FEATURE_REVERSE_SEARCH=y

• I use OpenVPN with OpenWrt to send all my LAN device traffic through a VPN. The latest SQM 'cake' qdist from the bufferbloat repo makes a significant difference to the responsiveness of my router traffic with the VPN. With kmod-sched-cake and tc-adv I can configure SQM to achieve an A+ connection quality and bufferbloat rating on dslreports.com/speedtest. There are some instructions here https://www.bufferbloat.net/projects/co … structions but these require kernel recompilation. If you can manage to add cake to a future build please let me know and I can post instructions for others using your build to optimise responsiveness. With your current build I can see the PIE qdist in the SQM lua interface but not cake.

• Add tcpdump package for packet capture and troubleshooting.
  

Great work and thanks again David.

(Last edited by iancd on 30 Oct 2016, 21:37)

Hi David,

Can you build igmpproxy too please, as it is needed for UDP multicast traffic such as BTTV. Would be handy for my current project.
If it is easier for me to build it myself, let me know.

I need more crypto modules enabled in the 4.4.27 kernel build for IpSec VPN to work. Sooo close!
/proc/crypto mentions sha1 but ipsec throws netlink "file not found" errors when trying to use that algo.

package kmod-crypto-sha1 (w/dep kmod-crypto-hash) is in the snapshots repo but do not contain any module files.

/proc/config.gz isn't available (CONFIG_IKCONFIG, CONFIG_IKCONFIG_PROC) so I cannot confirm the kernel's build settings.

@davidc502: could you please confirm the menuconfig (.config) on the latest build for these? 

github.com/lede-project/source/blob/master/package/kernel/linux/modules/crypto.mk#L38
CONFIG_CRYPTO_HASH=m

github.com/lede-project/source/blob/master/package/kernel/linux/modules/crypto.mk#L535
CONFIG_CRYPTO_SHA1=m

I promise a full write up for anyone else having to use awful Palo Alto "GlobalProtect" VPN from wrt.

Neither of those are showing in the .config

I can manually add them?

Apologies, looks like they are built-in:

root@lr1:~# grep sha1- /proc/crypto
driver       : sha1-generic
driver       : sha1-neon
driver       : sha1-asm

Thanks for checking.

I think I am connecting successfully now and the VPN server promptly hoses the default route, making my router unreachable!

Does the latest contain the tor and tor-geoip? I am a release behind and my opkg update fails signature check but I was going to upgrade tonight and I am trying to get a tor adapter running using these instructions medium.com/openwrt-iot/lede-openwrt-setting-up-tor-bebc2828d71a#.ck7e1muez is it worth the trouble?

Very nice work by the way, loving the stability and speed of your releases!

I don't believe it is, but can probably be added.

Is there a way people can help add packages to your builds? I am looking to help build for the WRT1900ac but am not really a programmer I know enough to keep my Home automation up to date.
I scanned the LEDE website but could not find instructions on how to build packages for LEDE from OpenWRT versions

Again great builds and awesome work.

TDW

Actually, no. They need to come from one source. When I started, I thought builds would be shared a perhaps a few people would try it out, and that would be the end of it. However, that's not what happened as there have been thousands of downloads. Out of those downloads, it's unknown how many people actually installed or continue to run the builds.

Over the past year I've attempted to build all packages, but have never managed to make it happen, but it's still on the horizon. It could be that I need a new machine with a lot more power and storage space. As AMD is coming out with a new processor at the end or perhaps the beginning of next year, I'm hoping to jump on board and see what I can do building the entire enchilada.

If you are interested in building your own, I can relay the basic instructions to get you going. It's really not hard to do.

I wish I could PM you, if you're in the market I could help you get on some X99 gear....... However don't want to take the thread into the weeds.

(Last edited by cybrnook2002 on 3 Nov 2016, 16:00)

That would be awesome, thank you!