Experimental build of Gargoyle 1.11.0 for ipq806x architecture routers
Posted: Sun Apr 28, 2019 12:08 am
29October2019: This build withdrawn - superceded by a 1.11.x build.
Download archive: gargoyle-1.11.0-ipq806x-experimental.7z - NO LONG AVAILABLE
The above archive contains the images and packages generated from an experimental ipq806x target configuration for Gargoyle 1.11.0. The source was from Gargoyle's git repository at the 1.11.0 tag.
PLEASE NOTE: the above archive may be withdrawn or replaced by a later build at a future time due to limited website space...
Please see https://downloads.openwrt.org/releases/ ... x/generic/ for a reference list of OpenWrt ipq806x target device images which this experimental package has attempted to match (except for the gargoyle-*-compex-wqp864-*.bin files which weren't built due to a typo - since fixed - in the target's profile_images file).
The only image I have tested is the TP-Link C2600 factory image, which installed via the factory firmware (v150924) upgrade function on a v1.0 C2600 without incident.
The router has run for more than 4 days now as my primary internet gateway behind a bridged VDSL2 modem with a PPPoE WAN interface. Both upstream and downstream QoS have been enabled as the upstream internet stream is subject
to severe bufferbloat - which Gargoyle's QoS appears to be controlling satisfactorily.
My testing has not been particularly comprehensive as my requirements are modest. In particular I haven't exercised the WiFi interfaces as I have no use for them most of the time.
With this configuration I have endeavoured to match the functionality configured for the Gargoyle mvebu target, which is the target with the most similarity to the ipq806x target in terms of hardware capability (e.g. CPU speed, available RAM and flash etc).
The archive includes the following subdirectories:
- built/ [contains all the packages built by the configuration]
- images/ [all firmware images generated]
- targets/ [configuration files for the ipq806x target]
The contents of the above subdirectories reflect the structure as built by Gargoyle's build script for the ipq806x default target.
All packages identified in the mvebu configuration with the configuration option "m" (i.e. "module", aka optional rather than included in the firmware image) have been included. As there is no current package repository available for the ipq806x target, my understanding is that desired optional packages will have to be installed by copying to the target router (e.g. by scp or WinSCP) and manually installing with the opkg command from an SSH session.
Support...
There are always risks associated with flashing firmware, especially third party firmware, so please carefully consider your circumstances before attempting to install one of these images and be prepared for the possibility of failure and the potential for your router to become unusable (aka "bricked"). Neither I or the Gargoyle team can accept any responsibility for such outcomes.
Unfortunately I cannot practically support this experimental release - despite having been able to assemble a configuration and build at least 1 apparently usable firmware image, I lack a lot of knowledge about router hardware and have extremely limited experience with Gargoyle itself.
If you have a question about installing these images, please refer in the first instance to the relevant OpenWrt hardware page for your router as what is written there for OpenWrt applies to installing Gargoyle. You should consider installing OpenWrt before installing any of these experimental Gargoyle images; you should then be able to install the respective Gargoyle "sysupgrade" image via OpenWrt's firmware upgrade
function - all being well. If in doubt, don't attempt to install one of these images.
For questions specific to this experirmental build, please post a followup to this thread. You may get lucky with someone able to provide assistance.
If you have questions about Gargoyle's interface or general functionality, queries should be addressed to an appropriate section of Gargoyle's user forum.
Successful installations of these images should also be reported by posting a followup to this thread, so that Gargoyle's maintainers can evaluate whether there's enough interest in the ipq806x target to use this experimental build as a basis for adding full support for at least some ipq806x devices to future Gargoyle releases.
Good luck!
pythonic
screenshot - TP-Link C2600 v1.0
Change log
28April2019: Initial build released
12June2019: Updated build to include patch for IMQ related NAT issue as discussed here - no other changes were made to the build configuration. This build has been briefly tested (several days uptime as of this writing) on a Netgear D7800 configured identically to the TP-Link Archer C2600 v1.0 tested with the original build. The updated patch file used in the build has been included in the download archive.
29October2019: Build withdrawn - superceded by 1.11.x build.
Download archive: gargoyle-1.11.0-ipq806x-experimental.7z - NO LONG AVAILABLE
The above archive contains the images and packages generated from an experimental ipq806x target configuration for Gargoyle 1.11.0. The source was from Gargoyle's git repository at the 1.11.0 tag.
PLEASE NOTE: the above archive may be withdrawn or replaced by a later build at a future time due to limited website space...
Please see https://downloads.openwrt.org/releases/ ... x/generic/ for a reference list of OpenWrt ipq806x target device images which this experimental package has attempted to match (except for the gargoyle-*-compex-wqp864-*.bin files which weren't built due to a typo - since fixed - in the target's profile_images file).
The only image I have tested is the TP-Link C2600 factory image, which installed via the factory firmware (v150924) upgrade function on a v1.0 C2600 without incident.
The router has run for more than 4 days now as my primary internet gateway behind a bridged VDSL2 modem with a PPPoE WAN interface. Both upstream and downstream QoS have been enabled as the upstream internet stream is subject
to severe bufferbloat - which Gargoyle's QoS appears to be controlling satisfactorily.
My testing has not been particularly comprehensive as my requirements are modest. In particular I haven't exercised the WiFi interfaces as I have no use for them most of the time.
With this configuration I have endeavoured to match the functionality configured for the Gargoyle mvebu target, which is the target with the most similarity to the ipq806x target in terms of hardware capability (e.g. CPU speed, available RAM and flash etc).
The archive includes the following subdirectories:
- built/ [contains all the packages built by the configuration]
- images/ [all firmware images generated]
- targets/ [configuration files for the ipq806x target]
The contents of the above subdirectories reflect the structure as built by Gargoyle's build script for the ipq806x default target.
All packages identified in the mvebu configuration with the configuration option "m" (i.e. "module", aka optional rather than included in the firmware image) have been included. As there is no current package repository available for the ipq806x target, my understanding is that desired optional packages will have to be installed by copying to the target router (e.g. by scp or WinSCP) and manually installing with the opkg command from an SSH session.
Support...
There are always risks associated with flashing firmware, especially third party firmware, so please carefully consider your circumstances before attempting to install one of these images and be prepared for the possibility of failure and the potential for your router to become unusable (aka "bricked"). Neither I or the Gargoyle team can accept any responsibility for such outcomes.
Unfortunately I cannot practically support this experimental release - despite having been able to assemble a configuration and build at least 1 apparently usable firmware image, I lack a lot of knowledge about router hardware and have extremely limited experience with Gargoyle itself.
If you have a question about installing these images, please refer in the first instance to the relevant OpenWrt hardware page for your router as what is written there for OpenWrt applies to installing Gargoyle. You should consider installing OpenWrt before installing any of these experimental Gargoyle images; you should then be able to install the respective Gargoyle "sysupgrade" image via OpenWrt's firmware upgrade
function - all being well. If in doubt, don't attempt to install one of these images.
For questions specific to this experirmental build, please post a followup to this thread. You may get lucky with someone able to provide assistance.
If you have questions about Gargoyle's interface or general functionality, queries should be addressed to an appropriate section of Gargoyle's user forum.
Successful installations of these images should also be reported by posting a followup to this thread, so that Gargoyle's maintainers can evaluate whether there's enough interest in the ipq806x target to use this experimental build as a basis for adding full support for at least some ipq806x devices to future Gargoyle releases.
Good luck!
pythonic
screenshot - TP-Link C2600 v1.0
Change log
28April2019: Initial build released
12June2019: Updated build to include patch for IMQ related NAT issue as discussed here - no other changes were made to the build configuration. This build has been briefly tested (several days uptime as of this writing) on a Netgear D7800 configured identically to the TP-Link Archer C2600 v1.0 tested with the original build. The updated patch file used in the build has been included in the download archive.
29October2019: Build withdrawn - superceded by 1.11.x build.