Self-hosted service
wukongdaily/ImmortalWrt-ImageBuilder avatar
wukongdaily/ImmortalWrt-ImageBuilder

Inside ImmortalWrt-ImageBuilder: one default IP, two device classes

A workflow for quickly building ImmortalWrt firmware, with optional Docker support and selectable 1-4GB firmware sizes. It acts as a cloud-based ImageBuilder (image assembly, not compilation) and also supports on-demand integration of third-party plugins.

2,732 stars9,517 forksShellGPL-3.0

At a glance

What is it?
A CI workflow that packages ImmortalWrt firmware after you fork it, where the headline management address exists only on boards with two or more ports and the WAN port ships with its inbound firewall rule enabled.
Who is it for?
Read it as a convenience workflow for people who already understand how OpenWrt images are assembled, not as a beginner installer. Forking and running a workflow really is two steps, but the port split, the bypass router address and the WAN inbound rule are three separate things to understand before the image is useful.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 60 days ago.
What is it written in?
Mainly Shell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • wukongdaily/ImmortalWrt-ImageBuilder2,732 ★ · +51
Star history
Repository2026-10-042026-11-15
wukongdaily/ImmortalWrt-ImageBuilder2.7k2.7k

51 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A CI workflow, not a compiler, and a license line pointing elsewhere

The project places itself in the build category rather than compilation: it calls the official ImmortalWrt ImageBuilder to package firmware, and it calls the whole arrangement a cloud side ImageBuilder, with Shell as the primary language, GPL-3.0 as the license, and master as the default branch. The disclaimer at the top says this is a personally maintained third-party script with no affiliation with ImmortalWrt official, that it only borrows the official packaging tool, and that any bug produced by a user's own customization does not represent a bug in official ImmortalWrt firmware. It asks that questions go to this project's Discussions rather than to ImmortalWrt groups. Directly under that disclaimer sits the only license line, and it points at `https://github.com/wukongdaily/AutoBuildImmortalWrt/blob/master/LICENSE`, a file in a different repository, while this repository carries its own top level `LICENSE` entry. Producing an image takes two steps: fork this project, then inside the fork click action, pick the workflow you want and run-workflow.

192.168.100.1 reaches only boards with two or more ports

Setting the management address is one of the headline options, and the example given is `192.168.100.1`. The same line carries the qualifier that decides everything: the option applies only to multi-port models, because single-port hardware still falls back to the automatic mode, dhcp, with no fixed address at all. The default attributes section spells the split out in full. A single-port board comes up in dhcp mode and takes whatever the upstream router hands it, the same arrangement a NAS uses. On a board with two or more ports the WAN side takes dhcp while LAN sits at `192.168.100.1`, and eth0 is WAN with every remaining port treated as LAN. If the dial-up fields in the workflow are filled in, the WAN port switches to pppoe instead, and users on pppoe are told to restart the ONT once before first use. Moving the LAN address to something like `192.168.80.1` is presented as ordinary, with one stated reason: avoiding a subnet clash with the ONT or with another router already in the house. Most users, the text notes, need no change at all.

The bypass router warning points away from the workflow input

A section addressed to bypass router users opens by reporting that a lot of them recently edited the default IP address in the configuration file, assumed the workflow could set the bypass IP directly, and ended up with a scrambled setup. That mistake is then corrected with a sequence rather than with a setting. The bypass arrangement has to run in single-port mode, where the one port defaults to dhcp, so the first step is reading the assigned address off the upstream router, the second is opening the immortal backend page at that address, and the third is configuring the bypass address there to match the main router's subnet. The correction never goes back to the workflow input. The address value exposed in the workflow form is not the address the running system answers on, which is why editing the default and expecting a side router IP lands in a broken configuration.

Port defaults and the WAN inbound rule both land in 99-custom.sh

Two separate defaults point at one file. The default attributes list closes by saying every one of those characteristics can be configured and adjusted through `99-custom.sh`. The special note then says the firmware built here leaves the WAN port firewall inbound rule enabled, for ease of use, and it puts the responsible code at the head of `files/etc/uci-defaults/99-custom.sh`. Turning it off is described through the interface instead: Network, then Firewall, then the wan inbound entry, choose Reject, then save and apply, and do it once the first round of debugging is finished. The stated reason for shipping it open is convenience rather than a decision the user made, and the file path plus a discussion link are offered right beside that instruction, so the default can be read before anyone goes looking for it in the interface.

A 7 to 8 minute ISO build ends at one prompt on the disk

For virtual machines the ISO path is laid out as two stages: stage one builds the imm firmware, stage two wraps that into an ISO format installer, taking about seven to eight minutes end to end. Once the ISO has booted in the VM and the boot output has finished, you type `ddd` at the command line and follow the prompts to write the virtual disk. The stated advantages over working with converted formats are no format conversion, no decompression, a choice of which disk to install onto, and usable leftover space on it afterwards. Physical hardware arrives at the same `ddd` step. Windows users copy the ISO onto a prepared Ventoy drive, macOS users burn it to a USB stick with balenaEtcher, the stick goes into the soft router before power-on, and the boot menu key is Del or F12, F11 or F7 depending on the board. Two project specific details sit alongside this: the ISO installer is called unique to this project, and the detailed write-up is pushed to a separate img-installer repository, although one of the two links given for it points at `armbian-installer` while carrying the img-installer label.

1GB is the default size and the store checkbox stops at 24.10.6

The repository description advertises optional docker and firmware sizes from 1G to 4G. The numbered feature list is narrower: default size 1GB, not recommended to set larger, 1G to 2G recommended, and anything beyond that left to the expansion plugin among the custom plugins. Docker is an optional pre-install, and the checkbox in the form that decides whether the store gets integrated carries a note that it applies to 24.10.6 and below. A later addition put a luci version selector in the same form, defaulting to the newest 25.12.x. Put the two together and a build on the current default is already past the range where that store checkbox applies, so the size advice and the version advice were written against different release lines. Supported lines are given as 24.10.x and 25.12.x, covering x86-64-ISO, x86-64, rockchip, allwinner sunxi and wireless routers.

Package lookups split in two and one path is pinned to 24.10.4

Two different questions get two different answers. For packages already inside the ImmortalWrt repository, a mirror directory is given, and it is pinned to one version rather than to a moving path: `https://mirrors.sjtug.sjtu.edu.cn/immortalwrt/releases/24.10.4/packages/x86_64/luci/`. For anything outside that repository the pointer is a separate store repository. How to wire third-party packages in is not written out at all; both the feature list and the lookup section send you to discussion 209 in the companion AutoBuildImmortalWrt repository. The top level tree also holds a `PACKAGES.md` file that no line of the text points at. For users chasing plugin updates the advice is to visit a separate run building project, download the run file there, and overwrite the existing install with `sh xx.run`.

sh
ddd
sh xx.run

The tree carries five targets the support sentence never names

The support line names five families: x86-64-ISO, x86-64, rockchip, allwinner sunxi and wireless routers, then pushes the full machine list into a separate `SUPPORT.md` file that gets linked rather than reproduced. The top level entries are wider than that sentence. Next to `arch/`, `x86-64/`, `rockchip/` and `sunxi-cortexa53/` sit `mediatek-filogic/`, `raspberrypi/`, `glinet/`, `armsr-armv8/` and `n1/`, alongside the workflow inputs `model/`, `shell/` and `files/`, plus `info.md` and `PACKAGES.md`. A person hunting for a board has to open SUPPORT.md rather than trust the feature list. Both published release assets are labelled as test material not to be downloaded: an armsr-armv8 rootfs base dated 2025-07-27, and an asset belonging to the separate img-installer project dated 2025-05-31, so neither one is an output of this workflow. The default branch's last recorded push is 2026-09-16.

Editorial conclusion

Read it as a convenience workflow for people who already understand how OpenWrt images are assembled, not as a beginner installer. Forking and running a workflow really is two steps, but the port split, the bypass router address and the WAN inbound rule are three separate things to understand before the image is useful. On a multi-port board, move 192.168.100.1 off whatever subnet the ONT already uses. Before the device joins any network you do not own, set the wan inbound rule to Reject. And check your board against SUPPORT.md rather than the feature list, because the tree carries targets the feature list never names.

Frequently asked questions

What is the default IP address on an ImmortalWrt-ImageBuilder build?

It depends on the port count. On a board with two or more ports, eth0 is WAN and takes DHCP while the LAN side is 192.168.100.1, changeable to something like 192.168.80.1 to avoid a clash with the ONT. A single-port board comes up in dhcp mode with no fixed address and has to be looked up on the upstream router.

What is ImmortalWrt, and what does wukongdaily add to it?

The instructions here never define ImmortalWrt itself. What this repository adds is a CI workflow that drives the official ImmortalWrt ImageBuilder to package firmware, and the project states plainly that it is a personally maintained third-party script with no affiliation with the ImmortalWrt side, so bugs from custom builds are not treated as upstream firmware bugs.

Does ImmortalWrt-ImageBuilder compile firmware from source?

No. The project places itself in the build category rather than compilation and describes itself as a cloud side ImageBuilder workflow. Its primary language is Shell, and the whole run is triggered from GitHub Actions inside a fork.

Which ImmortalWrt versions and boards does the workflow cover?

The lines named are 24.10.x and 25.12.x, covering x86-64-ISO, x86-64, rockchip, allwinner sunxi and wireless routers, with the luci selector defaulting to the newest 25.12.x. The tree also carries mediatek-filogic, raspberrypi, glinet, armsr-armv8 and n1 directories the support sentence does not name, so the per-board list lives in a separate SUPPORT.md.

Can I download a finished image from the ImmortalWrt-ImageBuilder releases page?

Not a firmware build. The two published assets are both marked as test material not to be downloaded: an armsr-armv8 rootfs base dated 2025-07-27, and an asset belonging to the separate img-installer project dated 2025-05-31. Images come out of running the workflow in your own fork.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. wukongdaily/ImmortalWrt-ImageBuilder on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/wukongdaily-immortalwrt-imagebuilder.svg)](https://hysenlabs.com/projects/wukongdaily-immortalwrt-imagebuilder)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/wukongdaily-immortalwrt-imagebuilder.svg)](https://hysenlabs.com/projects/wukongdaily-immortalwrt-imagebuilder)

Was this useful?