Raisins4u wrote:Their website: w w w (dot)linksys (dot)com/us/support-article?articleNum=114663
Sorry by the way, the website won't let me link it directly, remove the spaces and replace the word dot with an actual dot
This is not a problem. I just wanted to know what source code you mean, so that I have reference point.
Raisins4u wrote:On the ea6100. Maybe I'm confused but is it not possible to copy the source code for the firmware and build an openwrt image with its front end?
I believe you have confused something now. OpenWRT is a complete system by itself, containing possible bootloaders, kernel, and lots of packages providing different functionality. There's even the LuCI package which provides the defaut web front end. If you build an "OpenWRT image", you usually get the whole lot. Of course you can customize the package to your heart's content.
I took a peek inside the Linksys source code package, and the source code is comprised of original source code of the packages, paired with a collection of patches to make it work on their target platform. The toolchain seems to be a Marvell ARMv7 cross-compilation toolchain.
From this point of view, OpenWRT and the Linksys source package follow similar philosophies.
You might want to look inside the router and identify the exact system-on-a-chip that is used. It might be a pretty simple process to get OpenWRT running on your router. See https://wiki.openwrt.org/doc/hardware/soc/soc.marvell for details on which Marvell SoCs are currently supported. From the target menu of OpenWRT's Chaos Calmer branch,, I found Marvell Armada 37x/38x/XP and Marvell Kirkwood targets. If your router has any of these SoCs, then your job just got a whole lot easier. All you need is build the default profile of the suitable target and attempt to run it on your router to see if it works.
As for the Linksys front-end, you can certainly extract the package that comprises the front-end from the Linksys sources, and create a new OpenWRT package with this source code, together with a set of patches to modify the sources so that they can properly use OpenWRT's UCI system to read and write settings. You would essentially build a replacement package for LuCI.
Raisins4u wrote:Also the ea6300 uses a Broadcom chip unfortunately so I don't think it would be possible with my router.
Then you cannot use those sources.
Raisins4u wrote:Where would I start porting? Is there an easier way without risking completely bricking my router?
Start by identifying the SoC on the router, then getting an OpenWRT build environment running in a virtual machine (https://wiki.openwrt.org/doc/howto/buildvm) and see if there's already a suitable target that you can exploit. Who knows, maybe you get lucky?