HW support for GL.iNet AR-750

[Commifreak]

-> https://www.gl-inet.com/ar750/

OpenWRT supports it: https://openwrt.org/toh/hwdata/gl.inet/gl.inet_gl-ar750 since commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=2e5252d346e2ec832a203af778b5c1d949f0ae5f

Is there a chance that gluon/FF support it?

[mweinelt]

OpenWrt support was added after LEDE 17.01 and has not been backported. Therefore support is only possible until after Gluons master branch was updated to the next OpenWrt release or if the device support was backported to 17.01, but it is quite late for that imo.

[achterin]

@Commifreak i tried to backport it from openwrt. you can find the patched gluon here: https://github.com/achterin/gluon/tree/gl-ar750-backport

Please verify that the image is working as i dont have a device on hand to test it myself. If everything works i can create a pull request based on that feedback.

[mweinelt]

If the device was in OpenWrt master you will need to do a backport to lede-17.01 first. Sorry, getting the device into OpenWrt master is enough, my mistake.

[achterin]

Why would I have to do that? Right now the backport for "TP-Link Archer C7 v4" is almost accepted and the code for this device comes straight from OpenWrt master as well. Sorry if this is a dumb question as I am fairly new to the gluon development.

[rotanid]

@mweinelt as upstream does reject almost any hardware related backport, we don't apply this restriction as far as i know.

[Commifreak]

@achterin I've tried to build gluon with the ffharz site:

make GLUON_TARGET=ar71xx-generic GLUON_REGION=eu

which exited normally. I've got several images now, but none that has AR750 in it. Where do I find an image for the AR750 to flash it with gluon? Am I missing something?

...time passes...

Got it! ->

./output/images/sysupgrade/gluon-ffharz-0.9.1~20180504-gl-ar750-sysupgrade.bin

But thats for sysupgrade only, where's the factory image?

[pbriesch]

So far as I know there is OpenWrt/LEDE preinstalled. Therefore no factory image is needed, only sysupgrade.

[Commifreak]

Yep, just read that on the openwrt device description. I'll give it a try. Stay tuned ;)

[Commifreak]

So, I've tried it. Upgrade went successfully, the AR750 is now in config-mode (led flashing accordingly), BUT: I get no Web-UI. DHCP is not working on any interface. static IP (my PC: 192.168.1.10) access using 192.168.1.1 is NOT working.

Any ideas how to access the Web-UI?

[achterin]

I think I've messed up the port config. There was an openwrt change on master, that was not applied onto lede-2017.1, that changed the port naming. I've updated my branch and it would be nice if you could rebuild and test again. Sorry for the trouble.

[Commifreak]

No problem, I build it again asap and let you know if it works!

[Commifreak]

Tested it. Updated local repo by using git pull. The new built image also does not work :(

Still no connection to the device (neither dhcp nor static address)

What else could now be wrong?

EDIT: Just noticed that I have to make update again, which fails. I cleared out everything and start from scratch, now the make update added the new patch and build is running now, testing it again asap.

[Commifreak]

It is working fine!

I'll test some functions, but it seems to work well. Thanks for your help!

Maybe this patch is included in gluon soon ;)

[achterin]

Awesome. Before the backport to v2017.1.x will be merged, I'll have to do another backport to master first. I will submit a PR tomorrow and it would be nice if you could build and test that as well.

[achterin]

@Commifreak As promised, here you can find the master-backport. Please build and test again. Keep in mind, that you might have to update your site config. If the build works on your device, I'll open the PRs for master & 2017.1.x.

[Commifreak]

Why do I have to update site conf? I would copy the ffharz as usual or do I need to adapt something?

[achterin]

Because master uses some renamed and new config values. I had to update our site.conf and site.mk as well. Otherwise you will get compile errors. If you need help, hop onto irc and I'll help you.

[Commifreak]

Thanks.

Where are those change documented? The test-build from your repo was GLUON 2017.1.7, master is currently 14 days beyond 2017.1.7 - what do I need to adapt here to get this site working on a test build based on your master backport?

[achterin]

I did the following changes to ffharz site config to run compile without errors:

site.conf

• rename 'site_seed' => 'domain_seed'
• add 'vxlan' option to 'mesh'
• remove 'gluon_ssid_changer' package because it needs changes

site.mk

• rename 'GLUON_ATH10K_MESH' => 'GLUON_WLAN_MESH'

i uploaded a gist containing the diff: https://gist.github.com/achterin/5589e72a7ea9561599b29e662a710e8a

[Commifreak]

Thanks, awesome! I'll test it asap.

But where are the config changes documented?

[achterin]

I checked this forum thread. I dont know if there is a documentation available right now as the current master has no official release yet. Maybe @NeoRaider or @rotanid can help.

[Commifreak]

Oh, thanks. Informative thread.

[rotanid]

let's stick with the forum thread until there's a major release ( v2018.1 ) with release notes

[Commifreak]

@achterin This is the master image:

Seem to work as well