ZyXEL NWA55AXE

Under Construction!
This page is currently under construction. You can edit the article to help completing it.

Write a short, relevant description of the device. Include a technical overview, but avoid marketing buzzwords/useless stuff. Two to four sentences is about right. A picture is good, too. Edit the page to see how to add pictures.

FIXME Any text with a light background (like this one) provides instructions for creating the Details Page. When you have filled in correct/useful information (instead of any template that's there) remove the instructions, as well as the <WRAP> that encloses it.

Generic Router

FIXME

  1. This is an empty template that suggests the information that should be present on a well-constructed Device Page. This means, that you have to fill it with life and information.
  2. There are several “fixme” tags with text on a light background (like this text) throughout this template. As you fill in the page, remove those tags so that people can judge its completeness.
  3. When there are no more “fixme” tags left, delete this one too, along with the <WRAP> that encloses it.
  • Please include only model specific information, omit bla,bla and put everything generic into separate articles
  • If you have no time to write certain stuff, link to docs
  • base-system should lead the way, do not explain this again
  • DO NOT provide a complete howto here! Instead groom the general documentation.

FIXME

  1. The tables below are automatically generated, once the correct filters for Brand and Model are set.
  2. If the tables below show information for ZyXEL NWA55AXE , everything is OK and you can delete this text and the <WRAP> that encloses it.
  3. If the tables below contain “Nothing found”, it means that either
    1. the dataentry page for ZyXEL NWA55AXE is missing. Please create a new dataentry page first, then reload this page. The tables should then contain $something. If they do, delete this text and the <WRAP> that encloses it.
    2. filters are not set correctly. Most common reason for “Nothing found”: The dataentry does not contain a Version, but we are filtering here for version → Please edit this section and adjust the filters with the proper Brand, Model and Version. In case the dataentry does not contain a version, delete the line filter : Versions~. Just try, it's easy. The tables should then contain $something. If they do, delete this text and the <WRAP> that encloses it.
  4. If the tables still contain “Nothing found”: Don't panic, calm down, take a deep breath and contact a wiki admin (tmomas) for help.

None at this time.

Web UI

  1. Connect to the device via lan
  2. Set your IP to `192.168.1.20`
  3. Open Web UI at `192.168.1.2`
  4. Login with username “admin” and password “1234” in standalone mode
  5. At maintenance/firmware-package upload the factory image (see Techdata: ZyXEL NWA55AXE)
  6. The device should reboot into openwrt an be accessible via `192.168.1.1`

As the device uses a dual-image partition layout, OpenWrt can only installed on Slot A. This requires the current active image prior flashing the device to be on Slot B.

If the currently installed image is started from Slot A, the device will flash OpenWrt to Slot B. OpenWrt will panic upon first boot in this case and the device will return to the ZyXEL firmware upon next boot.

If this happens, first install a ZyXEL firmware upgrade of any version and install OpenWrt after that.

TFTP

This installation routine is especially useful in case

  • unknown device password (NWA55AXE lacks reset button)
  • bricked device

Attach to the UART console header of the device. Interrupt the boot procedure by pressing Enter.

The bootloader has a reduced command-set available from CLI, but more commands can be executed by abusing the atns command.

Boot a OpenWrt initramfs image available on a TFTP server at 192.168.1.66. Rename the image to owrt.bin

 $ atnf owrt.bin
 $ atna 192.168.1.88
 $ atns "192.168.1.66; tftpboot; bootm"

Upon booting, set the booted image to the correct slot:

 $ zyxel-bootconfig /dev/mtd10 get-status
 $ zyxel-bootconfig /dev/mtd10 set-image-status 0 valid
 $ zyxel-bootconfig /dev/mtd10 set-active-image 0

Copy the OpenWrt ramboot-factory image to the device using scp. Write the factory image to NAND and reboot the device.

 $ mtd write ramboot-factory.bin firmware
 $ reboot

FIXME Find out flash layout, then add the flash layout table here (copy, paste, modify the example).

Please check out the article Flash layout. It contains examples and explanations that describe how to document the flash layout.

Upload the Factory image using the devices web interface.

As the device uses a dual-image partition layout, OpenWrt can only installed on slot A. This requires the current active image prior flashing the device to be on slot B.

If the currently installed image is started from slot A, the device will flash OpenWrt to slot B. OpenWrt will panic upon first boot in this case and the device will return to the ZyXEL firmware upon next boot.

If this happens, first install a ZyXEL firmware upgrade of any version and install OpenWrt after that.

This installation routine is especially useful in case * unknown device password (NWA55AXE lacks reset button) * bricked device

Attach to the UART console header of the device. Interrupt the boot procedure by pressing Enter.

The bootloader has a reduced command-set available from CLI, but more commands can be executed by abusing the atns command.

Boot a OpenWrt initramfs image available on a TFTP server at 192.168.1.66. Rename the image to owrt.bin

  $ atnf owrt.bin
  $ atna 192.168.1.88
  $ atns "192.168.1.66; tftpboot; bootm"

Upon booting, set the booted image to the correct slot:

  $ zyxel-bootconfig /dev/mtd10 get-status
  $ zyxel-bootconfig /dev/mtd10 set-image-status 0 valid
  $ zyxel-bootconfig /dev/mtd10 set-active-image 0

Copy the OpenWrt ramboot-factory image to the device using scp. Write the factory image to NAND and reboot the device.

  $ mtd write ramboot-factory.bin firmware
  $ reboot

generic.sysupgrade

FIXME These are generic instructions. Update with your router's specifics.

  • Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
  • Upload image file for sysupgrade to LuCI
  • Wait for reboot

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:

  • sysupgrade
  • mtd

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

sysupgrade

  • Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
sysupgrade /tmp/xxx.abc

mtd

If sysupgrade does not support this router, use mtd.

  • Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
mtd write /tmp/xxx.abc linux && reboot

Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

FIXME Please fill in real values for this device, then remove the EXAMPLEs

The default network configuration is:

Interface Name Description Default configuration
br-lan EXAMPLE LAN & WiFi EXAMPLE 192.168.1.1/24
vlan0 (eth0.0) EXAMPLE LAN ports (1 to 4) EXAMPLE None
vlan1 (eth0.1) EXAMPLE WAN port EXAMPLE DHCP
wl0 EXAMPLE WiFi EXAMPLE Disabled

FIXME Please fill in real values for this device, then remove the EXAMPLEs

Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.

Port Switch port
Internet (WAN) EXAMPLE 4
LAN 1 EXAMPLE 3
LAN 2 EXAMPLE 2
LAN 3 EXAMPLE 1
LAN 4 EXAMPLE 0

hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

FIXME Please fill in real values for this device, then remove the EXAMPLEs

The ZyXEL NWA55AXE has the following buttons:

BUTTON Event
EXAMPLE Reset reset
EXAMPLE Secure Easy Setup ses
EXAMPLE No buttons at all. -

FIXME

  1. This table is automatically generated, once the correct filters for Brand and Model are set.
  2. If you see “Nothing.” instead of a table, please edit this section and adjust the filters with the proper Brand and Model. Just try, it's easy.
  3. If you still don't see a table here, or a table filled with '¿': Is there already a Techdata page available for ZyXEL NWA55AXE ? If not: Create one.
  4. If you see a table with the desired device data, everything is OK and you can delete this text and the <WRAP> that encloses it.
  5. If it still doesn't work: Don't panic, calm down, take a deep breath and contact a wiki admin (tmomas) for help.

Front:
Insert photo of front of the casing

Back:
Insert photo of back of the casing

Backside label:
Insert photo of backside label

Note: This will void your warranty!

FIXME Describe what needs to be done to open the device, e.g. remove rubber feet, adhesive labels, screws, ...

  • To remove the cover and open the device, do a/b/c

Main PCB:
Insert photo of PCB

port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port

FIXME Replace EXAMPLE by real values.

Serial connection parameters
for ZyXEL NWA55AXE @@Version@@
EXAMPLE 115200, 8N1, 3.3V

port.jtag general information about the JTAG port, JTAG cable, etc.

How to connect to the JTAG Port of this specific device:
Insert photo of PCB with markings for JTAG port

None so far.

COPY HERE THE BOOTLOG WITH THE ORIGINAL FIRMWARE


COPY HERE THE BOOTLOG ONCE OPENWRT IS INSTALLED AND RUNNING


Space for additional notes, links to forum threads or other resources.

  • ...
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/02/12 11:13
  • by 127.0.0.1