An opensource OpenWrt variant for mainland China users.
Go to file
Soma Zambelly b9cb1ba2a5 realtek: add ZyXEL GS1900-24HPv2 support
The ZyXEL GS1900-24HPv2 is a 24 port PoE switch with two SFP ports, similar to the other GS1900 switches.

Specifications
--------------
* Device:    ZyXEL GS1900-24HPv2
* SoC:       Realtek RTL8382M 500 MHz MIPS 4KEc
* Flash:     16 MiB
* RAM:       W631GG8MB-12 128 MiB DDR3 SDRAM
             (stock firmware is configured to use only 64 MiB)
* Ethernet:  24x 10/100/1000 Mbps, 2x SFP 100/1000 Mbps
* LEDs:      1 PWR LED (green, not configurable)
             1 SYS LED (green, configurable)
             24 ethernet port link/activity LEDs (green, SoC controlled)
             24 ethernet port PoE status LEDs
             2 SFP status/activity LEDs (green, SoC controlled)
* Buttons:   1 "RESTORE" button on front panel
             1 "RESET" button on front panel
* Power      120-240V AC C13
* UART:      1 serial header (J41) with populated standard pin connector on
             the left edge of the PCB, angled towards the side.
             The casing has a rectangular cutout on the side that provides
             external access to these pins.
             Pinout (front to back):
             + GND
             + TX
             + RX
             + VCC

Serial connection parameters for both devices: 115200 8N1.

Installation
------------

OEM upgrade method:

(Possible on master once https://patchwork.ozlabs.org/project/openwrt/patch/20210624210408.19248-1-bjorn@mork.no/ is merged)

* Log in to OEM management web interface
* Navigate to Maintenance > Firmware > Management
* If "Active Image" has the first option selected, OpenWrt will need to be
  flashed to the "Active" partition. If the second option is selected,
  OpenWrt will need to be flashed to the "Backup" partition.
* Navigate to Maintenance > Firmware > Upload
* Upload the openwrt-realtek-generic-zyxel_gs1900-24hp-v2-initramfs-kernel.bin
  file by your preferred method to the previously determined partition.
  When prompted, select to boot from the newly flashed image, and reboot the switch.
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
   > sysupgrade -n /tmp/openwrt-realtek-generic-zyxel_gs1900-24hp-v2-squashfs-sysupgrade.bin
   it may be necessary to restart the network (/etc/init.d/network restart) on
   the running initramfs image.

U-Boot TFTP method:

* Configure your client with a static 192.168.1.x IP (e.g. 192.168.1.10).
* Set up a TFTP server on your client and make it serve the initramfs image.
* Connect serial, power up the switch, interrupt U-boot by hitting the
  space bar, and enable the network:
   > rtk network on
* Since the GS1900-24HPv2 is a dual-partition device, you want to keep the OEM
  firmware on the backup partition for the time being. OpenWrt can only boot
  from the first partition anyway (hardcoded in the DTS). To make sure we are
  manipulating the first partition, issue the following commands:
  > setsys bootpartition 0
  > savesys
* Download the image onto the device and boot from it:
   > tftpboot 0x84f00000 192.168.1.10:openwrt-realtek-generic-zyxel_gs1900-24hp-v2-initramfs-kernel.bin
   > bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
   > sysupgrade -n /tmp/openwrt-realtek-generic-zyxel_gs1900-24hp-v2-squashfs-sysupgrade.bin
   it may be necessary to restart the network (/etc/init.d/network restart) on
   the running initramfs image.

Signed-off-by: Soma Zambelly <zambelly.soma@gmail.com>
2021-09-21 23:51:59 +08:00
config Merge Mainline 2021-08-29 00:53:33 +08:00
include kernel: bump 5.4 to 5.4.145 2021-09-15 10:29:40 +08:00
LICENSES LICENSE: sync with upstream 2021-02-16 14:19:09 +08:00
package realtek: add ZyXEL GS1900-24HPv2 support 2021-09-21 23:51:59 +08:00
scripts Merge Official Source 2021-09-03 03:26:54 +08:00
target realtek: add ZyXEL GS1900-24HPv2 support 2021-09-21 23:51:59 +08:00
toolchain glibc: update to latest 2.33 HEAD (bug 28213) 2021-09-21 23:50:33 +08:00
tools firmware-utils: tplink-safeloader: set EAP235-Wall v1 soft-version 2021-09-16 23:59:37 +08:00
.gitattributes fix permisson 2019-08-16 15:09:42 +08:00
.gitignore .gitignore: ignore any .vscode* file 2021-07-03 17:25:40 +08:00
BSDmakefile build: use SPDX license tags 2021-02-06 12:07:10 +08:00
Config.in build: use SPDX license tags 2021-02-06 12:07:10 +08:00
CONTRIBUTED.md Merge Mainline 2021-07-14 14:53:12 +08:00
COPYING LICENSE: sync with upstream 2021-02-16 14:19:09 +08:00
feeds.conf.default Merge Mainline 2021-06-15 23:45:52 +08:00
Makefile Revert "build: replace which with Bash command built-in" 2021-03-04 12:10:58 +08:00
README.md README: update domain for build-scripts 2021-09-11 04:12:11 +08:00
rules.mk build: add ninja build tool and make it available for cmake 2021-06-13 11:59:14 +08:00

logo

Project ImmortalWrt

ImmortalWrt is a fork of OpenWrt, with more packages ported, more devices supported, better performance, and special optimizations for mainland China users.
Compared the official one, we allow to use hacks or non-upstreamable patches / modifications to achieve our purpose. Source from anywhere.

Default login address: http://192.168.1.1 or http://immortalwrt.lan, username: root, password: password.

Development

To build your own firmware you need a GNU/Linux, BSD or MacOSX system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.

Requirements

To build with this project, Ubuntu 18.04 LTS is preferred. And you need use the CPU based on AMD64 architecture, with at least 4GB RAM and 25 GB available disk space. Make sure the Internet is accessible.

The following tools are needed to compile ImmortalWrt, the package names vary between distributions.

  • Here is an example for Ubuntu users:

    • Method 1:

      Setup dependencies via APT
      sudo apt update -y
      sudo apt full-upgrade -y
      sudo apt install -y ack antlr3 asciidoc autoconf automake autopoint binutils bison build-essential \
        bzip2 ccache cmake cpio curl device-tree-compiler ecj fastjar flex gawk gettext gcc-multilib g++-multilib \
        git git-core gperf haveged help2man intltool lib32gcc1 libc6-dev-i386 libelf-dev libglib2.0-dev libgmp3-dev \
        libltdl-dev libmpc-dev libmpfr-dev libncurses5-dev libncurses5-dev libreadline-dev libssl-dev libtool libz-dev \
        lrzsz mkisofs msmtp nano ninja-build p7zip p7zip-full patch pkgconf python2.7 python3 python3-pip python3-ply \
        python-docutils qemu-utils re2c rsync scons squashfs-tools subversion swig texinfo uglifyjs upx-ucl unzip vim \
        wget xmlto xxd zlib1g-dev
      
    • Method 2:

      curl -s https://build-scripts.immortalwrt.eu.org/init_build_environment.sh | sudo bash
      
  • You can also download and use prebuilt container directly:
    See #Quickstart - Build image via OPDE

Note:

  • For the for love of god please do not use ROOT user to build your image.
  • Using CPUs based on other architectures should be fine to compile ImmortalWrt, but more hacks are needed - No warranty at all.
  • You must not have spaces in PATH or in the work folders on the drive.
  • If you're using Windows Subsystem for Linux (or WSL), removing Windows folders from PATH is required, please see Build system setup WSL documentation.
  • Using macOS as the host build OS is not recommended. No warranty at all. You can get tips from Build system setup macOS documentation.
    • As you're building ImmortalWrt, patching or disabling UPX tools is also required.
  • For more details, please see Build system setup documentation.

Quickstart

  • Method 1:

    1. Run git clone -b <branch> --single-branch https://github.com/immortalwrt/immortalwrt to clone the source code.
    2. Run cd immortalwrt to enter source directory.
    3. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default
    4. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/
    5. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.
    6. Run make to build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
  • Method 2:

    Build image via OPDE
    • Pull the prebuilt container:

      docker pull immortalwrt/opde:base
      # docker run --rm -it immortalwrt/opde:base
      
    • For Linux User:

      git clone -b <branch> --single-branch https://github.com/immortalwrt/immortalwrt && cd immortalwrt
      docker run --rm -it \
          -v $PWD:/openwrt \
        immortalwrt/opde:base zsh
      ./scripts/feeds update -a && ./scripts/feeds install -a
      
    • For Windows User:

      1. Create a volume 'immortalwrt' and clone ImmortalWrt source into volume.
      docker run --rm -it -v immortalwrt:/openwrt immortalwrt/opde:base git clone -b <branch> --single-branch https://github.com/immortalwrt/immortalwrt .
      
      1. Enter docker container and update feeds.
      docker run --rm -it -v immortalwrt:/openwrt immortalwrt/opde:base
      ./scripts/feeds update -a && ./scripts/feeds install -a
      
      • Tips: ImmortalWrt source code can not be cloned into NTFS filesystem (symbol link problem during compilation), but docker volume is fine.
    • Proxy Support:

      docker run --rm -it \
        -e   all_proxy=http://example.com:1081 \
        -e  http_proxy=http://example.com:1081 \
        -e https_proxy=http://example.com:1081 \
        -e   ALL_PROXY=http://example.com:1081 \
        -e  HTTP_PROXY=http://example.com:1081 \
        -e HTTPS_PROXY=http://example.com:1081 \
        -v $PWD:/openwrt \
        immortalwrt/opde:base zsh
      

      Recommand http rather socks5 protocol

      IP can not be localhost or 127.0.0.1

    • For Windows User, binary is still in volume. It can be copied to outside via followed command:

      docker run --rm -v <D:\path\to\dir>:/dst -v openwrt:/openwrt -w /dst immortalwrt:base cp /openwrt/bin /dst
      

      Make sure D:\path\to\dir has been appended in File Sharing.

The main repository uses multiple sub-repositories to manage packages of different categories. All packages are installed via the ImmortalWrt package manager called opkg. If you're looking to develop the web interface or port packages to ImmortalWrt, please find the fitting repository below.

Support Information

For a list of supported devices see the OpenWrt Hardware Database

Documentation

Support Community

Sponsors

Dler Cloud

License

ImmortalWrt is licensed under GPL-3.0-only.