Entware Entware armv7sf-k2.6 EOS

[thelonelycoder]

I'm still compiling it for FT see https://www.linksysinfo.org/index.php?threads/entware-for-arm-updates.78507/

If you don't mind, amtm will automatically add your repo for compatible routers, just as it does for the old mipsel routers.

 

[maurer]

If you don't mind, amtm will automatically add your repo for compatible routers, just as it does for the old mipsel routers.

no problem - just remember I don't follow these forums anymore - as I don't own Asus routers so please post questions via linksysinfo.org forum

 

[garycnew]

@thelonelycoder FYI... @maurer discontinued updating the Backports Repo in Jan 2025. However, there are individuals, like myself, that still use it and roll our own upgraded packages when unavailable there.

Update: I took the liberty of backing up @maurer's Backports Repo... https://web.archive.org/web/20250307025413/https://maurerr.github.io/entware-armv7-k26/

 

[garycnew]

@thelonelycoder Picked up with the Entware armv7sf-k2.6 updates:

entware for arm updates

 

[thelonelycoder]

@thelonelycoder Picked up with the Entware armv7sf-k2.6 updates:

entware for arm updates

That's very kind of you to update and make available all these Entware packages.
Your repo will replace the no longer maintained repo by @maurer for armv7sf-k2.6 routers in amtm.

There were a bunch of updates for my test router, up from maurers repo. I can confirm that jq, coreutils-date and wget-ssl work without a hitch after the update.

 - zoneinfo-europe - 2024a-1 - 2025b-1
 - jq - 1.7.1-1 - 1.7.1-2
 - coreutils-date - 9.3-1 - 9.6-5
 - coreutils-base64 - 9.3-1 - 9.6-5
 - grep - 3.11-1 - 3.11-2
 - zoneinfo-asia - 2024a-1 - 2025b-1
 - coreutils - 9.3-1 - 9.6-5
 - zoneinfo-core - 2024a-1 - 2025b-1
 - entware-release - 2024.07-1 - 2025.05-1
 - wget-ssl - 1.24.5-1 - 1.25.0-1

I will release an amtm update this WE that replaces @maurer's repo with yours if that option is enabled in amtm.
Thanks again for putting in the work - much appreciated.

 

[ColinTaylor]

@garycnew At first glance your repo appears to be missing tailscale and tailscale_nohf (perhaps because they're go packages which are compiled differently - just guessing). I didn't check for any other packages as I don't have a k2.6 router.

 

[jksmurf]

@garycnew At first glance your repo appears to be missing tailscale and tailscale_nohf (perhaps because they're go packages which are compiled differently - just guessing). I didn't check for any other packages as I don't have a k2.6 router.

Thank you Colin.

@garycnew see here (and prior posts) for history and reason for this for the Tailscale addon, for those (admittedly few) users wanting to install tailscale on older Asus Router hardware.

 

[garycnew]

Thank you Colin.

@garycnew see here (and prior posts) for history and reason for this for the Tailscale addon, for those (admittedly few) users wanting to install tailscale on older Asus Router hardware.

@jksmurf and @ColinTaylor

While most of the core packages are available within my armv7fs-k2.6 repo, there are undoubtedly some packages that failed to build for one reason or another.

As I stated in the linksysinfo forum, there are some issues with the newer packages being built against the armv7sf-k2.6 platform related to missing kernel and glibc components that they rely upon.

Due to the kernel and glibc related issues, I was only able to get the older go_1.22.5 to compile. However, I was able to confirm that older versions of go packages (i.e., adguardhome-go) should compile, if you downgrade the related go feeds/packages (i.e., tailscale) that work with go_1.22.5.

I would recommend git cloning my armv7fs-k2.6 source and try downgrading the feeds/packages (i.e., Makefile, patches, and/or files) for the tailscale package and compile it, individually.

If you're able to successfully package an older version of tailscale, with my repo, tar the related feeds/packages subdirectory for tailscale and send it my way to update the armv7fs-k2.6 github source.

In short, there are just too many packages for one person to maintain and I am open to your assistance.

Respectfully,


Gary

 

[jksmurf]

If you're able to successfully package an older version of tailscale, with my repo, tar the related feeds/packages subdirectory for tailscale and send it my way to update the armv7fs-k2.6 github source.

First off, really appreciate what you’ve done here to keep the maurer repo or parts of it alive, for the reasons posted above

Unfortunately I have absolutely no idea about packaging any of these elements of the repo, completely out of my sphere of expertise, I’m not in IT or computing in any way, shape or form. I’m going to have to defer to others far more qualified to do this.

 

[garycnew]

@thelonelycoder Attached are the related amtm patches (change from .txt to .gz) to replace maurer's with my repo. All packages that I've installed appear to be working as expected.

 

[thelonelycoder]

Attached are the related amtm patches (change from .txt to .gz) to replace maurer's with my repo. All packages that I've installed appear to be working as expected.

Thanks. But it needed a lot more changes, hence my delay.
See release thread amtm 6.0.2

 

[garycnew]

I needed to update a package and took a cursory check of the tailscale package. It appears that tailscale is not a package maintained by Entware. maurer must have pulled it from OpenWRT and included it in their personal Entware repository. I wish maurer would have made the feeds/packages Makefile(s) available, so I didn't have to reverse engineer everything. As it stands, tailscale has dependencies of go, ca-certificates, and kmod-tun. The kmod-tun dependency has me down a rabbit hole. Any assistance is appreciated.

 

[dave14305]

It appears that tailscale is not a package maintained by Entware.

Are you looking for this?

entware-go/tailscale at master · Entware/entware-go

Unique Entware packages written in GO. Contribute to Entware/entware-go development by creating an account on GitHub.

github.com

 

[garycnew]

@dave14305 Thank you for the reminder that Entware places go feeds under feeds/golang and not in feeds/packages (like OpenWRT).

@jksmurf Attached are the tailscale and tailscale_nohf 1.84.2 packages (change from .txt to .ipk) compiled against my repo. Please test and confirm that they work as expect.

P.S. In the future, remind me that often all that is needed to compile go packages is a go_1.22.5 compatible Makefile (changing the version and hash to the latest release).

 

[jksmurf]

@jksmurf Attached are the tailscale and tailscale_nohf 1.84.2 packages (change from .txt to .ipk) compiled against my repo. Please test and confirm that they work as expect.

Thank you. Just to clarify, is the “tailscale” version here the normal one for more recent routers and the “tailscale_nohf” version for armv7sf-k2.6 based devices such as the RT-AC68U?

I ask as for the former, is that not serviced by the standard (non-maurer) entware install, i.e. does the standard tailscale needed to be wrapped up in this new repo?

For the latter, unfortunately I’ve got no way to test this as you’d need an RT-AC68U. @ColinTaylor might have one, I know @Nesalex did, being the original poster that drove the need to retain the maurer repo, @Brenneke did too, perhaps one of them or someone else with the older model could try it out. Not sure if @Viktor Jaep has an older model in his armoury.

 

[Viktor Jaep]

Not sure if @Viktor Jaep has an older model in his armory.

Haha. no. I'm living on the bleeding edge with my GT-AX6000 and RT-AX88U thank you very much!

 

[garycnew]

Thank you. Just to clarify, is the “tailscale” version here the normal one for more recent routers and the “tailscale_nohf” version for armv7sf-k2.6 based devices such as the RT-AC68U?

Something like that. I believe @ColinTaylor knows the specifics of hf vs nohf.

I ask as for the former, is that not serviced by the standard (non-maurer) entware install, i.e. does the standard tailscale needed to be wrapped up in this new repo?

This is the latest version of tailscale (1.84.2). tailscale_hf and tailscale_nohf are built at the same time in the same process. It's of no consequence, if the tailscale_hf version isn't used under the armv7sf-k2.6 architecture.

I must say... I'm a bit confused why you pleaded for tailscale to be built for the armv7sf-k2.6 architecture; when, you don't have any compatible devices.

The garycnew.github.io/Entware/armv7sf-k2.6/ repo is only for the armv7sf-k2.6 architecture.

 

[jksmurf]

I must say... I'm a bit confused why you pleaded for tailscale to be built for the armv7sf-k2.6 architecture; when, you don't have any compatible devices.

Simply because (per the intro to the tailscale thread) I was the one pushing for tailscale to be added to amtm as an add-on, helped test it (offline) together with others with significantly more knowledge, then felt duty-bound to try to help interested users install and configure it, despite my limited knowledge and experience.

This included, when the occasion arose at the request of those with the older hardware, finding out how to install the correct entware version, which (if you read that linked thread) you will see I eventually found (following some dogged searching) that it required the maurer repo to be selected at the entware install stage. So to answer your question, it was the right thing to do, regardless of my own hardware.

 

[garycnew]

@jksmurf Thank you for the explanation. As I don't use tailscale, I would appreciate it if someone whom does use tailscale on an armv7sf-k2.6 device would test and confirm the 1.84.2 package is successfully working, prior to being added to the repository. Thank you.

 

[Viktor Jaep]

@jksmurf Thank you for the explanation. As I don't use tailscale,

You should definitely use Tailscale... I've become a HUGE believer thanks to @jksmurf. So at this point, I've pretty much got all devices hooked up, and using Rustdesk as a free remote access solution to my local PCs and servers from remote. Of course, with Tailscale, you can use a browser or SSH to get to other devices if needed. It's truly been a fun project.