User:Skyhook
From Ubiquiti Wiki
How to add a firewall rule
Author: Skyhook 19 March 2009
Contents: Add firewall rules in AirOS
SR71-A miniPCI MIMO
Author: Skyhook 06 June 2009
Contents: Firt test of UBNT SR71-A MIMO radio module on RouterOS/Mikrotik board
Introduction
Starting from v4.0beta3, RouterOS support 802.11n draft wireless card.
To enable 802.11n support you need:
- upgrade RouterOS to v4.0beta3 or above
- upgrade RouterOS Licence Key to new format
- upgrade Routerboard BIOS to the latest version (recommended 2.20 or newer)
Refer to RouterOS ducumentation for more detailed info.
RouterOS info about UBNT SR71-A:
[admin@MikroTik] /interface wireless> pr
Flags: X - disabled, R - running
0 R name="wlan1" mtu=1500 mac-address=00:15:6D:84:06:66 arp=enabled interface-type=Atheros 11N
mode=ap-bridge ssid="test!" frequency=5180 band=5ghz-onlyn scan-list=default
antenna-mode=ant-a wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default compression=no
note: interface-type=Atheros 11N ;-)
[admin@MikroTik] /interface wireless info> pr
0 interface-type=Atheros AR5416 chip-info="mac:0x40/0x0, phy:0xb0, a5:0xc0, a2:0x0, eeprom:0x0"
pci-info="00:14.0" capabilities=tx-power-control,ack-timeout-control,virtual-ap,alignment-mode,
scanning,nstreme,sniffing,ht40-a,ht40-g,wmm
default-periodic-calibration=enabled supported-bands=2ghz-b,5ghz,2ghz-g,5ghz-11n,2ghz-11n
2ghz-b-channels=2412:0,2417:0,2422:0,2427:0,2432:0,2437:0,2442:0,2447:0,2452:0,2457:0,2462:0
5ghz-channels=5180:0,5185:0,5190:0,5195:0,5200:0,5205:0,5210:0,5215:0,5220:0,5225:0,5230:0,
5235:0,5240:0,5260:0,5265:0,5270:0,5275:0,5280:0,5285:0,5290:0,5295:0,5300:0,
5305:0,5310:0,5315:0,5320:0,5745:0,5750:0,5755:0,5760:0,5765:0,5770:0,5775:0,
5780:0,5785:0,5790:0,5795:0,5800:0,5805:0,5810:0,5815:0,5820:0,5825:0
2ghz-g-channels=2412:0,2417:0,2422:0,2427:0,2432:0,2437:0,2442:0,2447:0,2452:0,2457:0,2462:0
5ghz-11n-channels=5180:0,5185:0,5190:0,5195:0,5200:0,5205:0,5210:0,5215:0,5220:0,5225:0,5230:0,
5235:0,5240:0,5260:0,5265:0,5270:0,5275:0,5280:0,5285:0,5290:0,5295:0,5300:0,
5305:0,5310:0,5315:0,5320:0,5745:0,5750:0,5755:0,5760:0,5765:0,5770:0,5775:0,
5780:0,5785:0,5790:0,5795:0,5800:0,5805:0,5810:0,5815:0,5820:0,5825:0
2ghz-11n-channels=2412:0,2417:0,2422:0,2427:0,2432:0,2437:0,2442:0,2447:0,2452:0,2457:0,2462:0
Hardware setup
This test are performed between two indoor (about 5 m distance) devices with:
- 1 x RB433AH
- 1 x SR71-A miniPCI MIMO Radio Module
- 3 x antenna omni 5dBi on MMCX pigtail
Basics 802.11n configuration options
I have tested SR71-A on 5 GHz band, 5180 MHz, starting from default configuration value and settign as below:
- band: 5ghz-onlyN
- frequency: 5180 MHz
- ht-ampdu-priorities: 0
- ht-guard-interval: any
- ht-extension-channel: above-control
- ht-txchains: 0-1-2 (all chains)
- ht-rxchains: 0-1-2 (all chains)
- tx-power: 5 dB, Card Rate (due to short distance, setup a low power to prevent radio saturation...)
More detail on some 802.11n configuration options
- ht-ampdu-priorities (0,1,2,3,4,5,6,7 - any combination of these)
A-MPDU (Aggregated Mac Protocol Data Unit) Frame Aggregation allows the transmissions of multiple ethernet frames to a single location as burst. Iin other word, this protocol allows several MAC-level service data units (MSDUs) to be aggregated into a single MPDU. Some study dimonstrate that A-MPDU aggregation allows to achieve a high channel utilization of 95% in the ideal case while without aggregation the channel utilization is limited by just 33%. - ht-extension-channel (above-control | below-control | disabled)
The current 802.11n draft allow wireless channel bonding. There is one 20Mhz channel defined as the "control channel" while the "secondary channel" (or exended channel) can then be set to sit above or below the control channel. I recommends channel bonding be used in the 5GHz band due to the limited number of non-overlapping channels available in the 2.4GHz band (remeber: exended channel = base channel + 20 MHz).
For more info visit 802.11n Channel Bonding - ht-rxchains/ht-txchains (0,1,2 - any combination of these)
Which antenna connector to use for TX or RX. We can use one of these or combination of these . UBNT SR71-A support up to 3 MMCX antenna connectors and to use all antenna ht-tx/rx-chains need to be check 0,1 and 2 for max perfomances.
Test results
From a first test, the results are interesting, but can be emproved: over 82 MBits TCP throughput, over 211 MBits UDP throughput.
TCP throughput
UDP throughput
How to add a static route
Author: Skyhook 16 May 2009
Contents: Add static route in AirOS
AirOS Manual Scripting
AirOS allow users to add scripts in the /etc/persistent directory of Ubiquiti device.
These scripts can modify configuration by starting additional services and more.
The standard scripts are:
/etc/persistent/rc.prestart /etc/persistent/rc.poststart /etc/persistent/rc.prestop /etc/persistent/rc.poststop
They are called before and after the standard boot and shutdown scripts start or stop services...
Add static route via script
- Reboot devices to clean all static routes and access via SSH/Telnet to AirOS device
- Create a script /etc/persistent/rc.poststart and write here commands to add static route
- Make sure that /etc/persistent/rc.poststart are executable
- Check if your script work fine running the command line: ./etc/persistent/rc.poststart
note: the command now start with a "dot" = run the script!
- Run the command: cfgmtd -w -p /etc/ to make persistent
- Reboot and verify that all it's working...
FAQ
Q: What's a linux script?
A: A text file where each line it's a linux command like you enter in CLI like:
#! /bin/sh route add -net 10.10.10.0 netmask 255.255.255.0 gw 192.168.2.101 dev eth0
Q: How to make the scritp file /etc/persistent/rc.poststart?
A1: Use the embedded text editor in AirOS device, the vi editor: vi /etc/persistent/rc.poststart. To save this file press [ESC] [:] [x]
or
A2: Make file rc.poststar on you PC and upload in AirOS device, in the /etc/persistent/ directory...
Q: How to check if a file have executable permission (under Linux)?
A: Run command ls -l and check if the file have x option enabled:
XS2.ar2316.v3.4-rc.4351.090504.2146# ls -l /etc/persistent/rc.poststart -rwxr-xr-x 1 admin admin 6 May 16 16:32 /etc/persistent/rc.poststart
Q: How to simply enable executable permission of a file (under Linux)?
A: Run command like: chmod +x /etc/persistent/rc.poststart
XS2.ar2316.v3.4-rc.4351.090504.2146# chmod +x /etc/persistent/rc.poststart
Firmware Recovery Step by Step
Author: Skyhook 11 May 2009
Contents: How to recovery a broken AirOS device
Requirements:
- UBNT devices to upgrade ;-)
- A narrow tool like the pin of a headset or paper clip to press down reset button
- A Ethernet Cable
- A PC or Laptop always configured to access the units (es. [1])
- Network settings of PC: 192.168.1.254/255.255.255.0
- TFTP client running on PC
- AirOS firmware file (e.g. XS2.ar2316.v3.4-rc.4351.090504.2146.bin... you can find it in AirOS Support Page, check for yor device!)
Note: this guide refer to PC running Windows OS, but is easly applicable to other OS.
IMPORTANT!
- Do not switch off, do not reboot and do not disconnect the device from the power supply during the firmware upgrade process as these actions will damage the device!
Recovery procedure (apply to AirOS devices running firmware v1.5 or higher)
- First of all, power off the device
- Setup your PC: Windows PC's Ethernet must be configured manually with the following settings (under Network Connections):
IP Address: 192.168.1.254, Subnet Mask : 255.255.255.0 - Connect AirOS device to PC
- Power on AirOS device and keep on holding reset button for ~10 seconds (do not hold it longer!)
- Signal LEDs will be lit indicat that device is ready for recovery
- Make sure that AirOS device responds to pinging (perform a ping 192.168.1.20 from a DOS window), if it does not, go to first step
- Upload firmware image file .bin to 192.168.1.20, using TFTP client software (binary mode). From Windows PC, you can use TFTP command line from a DOS window (START>>>CMD):
Go into the same directory structure as the firmware (e.g., assuming that you have stored the image files in c:\firmware directory, type the command :cd c:\firmware) and enter the following (for help type TFTP -h) , e.g.:
tftp -i 192.168.1.20 put XS2.ar2316.v3.4-rc.4351.090504.2146.bin
- Signal LEDs will keep blinking one by one in 4 different colors during firmware upgrade
- Wait for about 7-10 minutes (devices and firmware depending) - do not power off the device during procedure!
Note: from a PC running a Linux like OS, you can upload via TFTP typing in Terminal Console following commands (for example):
root@ubuntu:tftp 192.168.1.20
tftp> bin
tftp> put XS2.ar2316.v3.4-rc.4351.090504.2146.bin
Sent 1965199 bytes in 35.2 seconds
tftp> exit
AirOS Wireless Repeater/Network Extender Configuration
Author: Skyhook 01 March 2009
Contents: How to make a Wireless Repeater AirOS
Introduction
Wireless Repeater or Network Extender
From UBNT Forum
Typical scenario is to install a Network Extender device to provide wireless signal to Clients that cannot be reached from AP #1 (poor signal level). We consider this simply network topology:
- 1 Router connected to Internet and/or private LAN (IP Address: 192.168.1.254/24)
- 1 AirOS device AP #1 directly connected to Router (IP Address: 192.168.1.21/24)
- 1 AirOS device AP #2 connected via wireless to AP #1 (IP Address: 192.168.1.20/24)
- 1 or more Wireless Clients (Notebook, WiFi-Phone, other Wireless devices...)
- The Router assign IP Address to network devices by DHCP Server. Alternatively, if you prefer, you can set static IP Address to Clients.
In this schema, AP #2 is a Wireless Repeater device.
Configuring
Minimal configuration:
- all AirOS devices in AP-WDS mode
- same SSID
- same Channel
- enter mutual WDS Peers (or enable Auto WDS)
AP #1 Setup
Login into AirOS WEB User Interface of AP #1 and set as below:
- NETWORK Tab
- Network Mode: Bridge
- Bridge IP Address: Static
- IP Address: 192.168.1.21
- Netmask: 255.255.255.0
- Gateway IP: 192.168.1.254
- Click Change button to confirm
- Click Apply button to apply changes
- Wait until process is complete
- LINK SETUP Tab
- Wireless Mode: Access Point WDS
- WDS Peers: 00:15:6D:B6:6D:4E (WLAN MAC of AP #2, you can see on MAIN Tab of AP #2)
- SSID: mywlan (or any stringh to identify your WLAN, but the same for all WDS Peers)
- Country Code: set according your location
- IEEE 802.11 Mode: B/G mixed (assuming devices running in 2.4 GHz band)
- Channell Spectrum Width: 20MHz
- Channel: 1 - 2412 MHz (or any other free channel, but the same for all WDS Peers)
- Output Power: 10 dBm (or check Obey Regulatory Power according your country law)
- Data Rate, Mbps: 54, Auto
- Click Change button to confirm
- Click Apply button to apply changes
- Wait until process is complete
AP #2 Setup
Login into AirOS WEB User Interface of AP #2 and set as below:
- NETWORK Tab
- Network Mode: Bridge
- Bridge IP Address: Static
- IP Address: 192.168.1.20
- Netmask: 255.255.255.0
- Gateway IP: 192.168.1.254
- Click Change button to confirm
- Click Apply button to apply changes
- Wait until process is complete
- LINK SETUP Tab
- Wireless Mode: Access Point WDS
- Auto: enable check box
- WDS Peers: 00:15:6D:B6:6C:E2' (WLAN MAC of AP #1, you can see on MAIN Tab of AP #1)
- SSID: mywlan (or any stringh to identify your WLAN, but the same for all WDS Peers)
- Country Code: set according your location
- IEEE 802.11 Mode: B/G mixed (assuming devices running in 2.4 GHz band)
- Channell Spectrum Width: 20MHz
- Channel: 1 - 2412 MHz (or any other free channel, but the same for all WDS Peers)
- Output Power: 10 dBm (or check Obey Regulatory Power according your country law)
- Data Rate, Mbps: 54, Auto
- Click Change button to confirm
- Click Apply button to apply changes
- Wait until process is complete
How to configure port forwarding in AirOS
Author: Skyhook 28 February 2009
Contents: How to configure port forwarding in AirOS
Remark: Tested on AirOS version 3.3.1 (applicable for Router mode)
Introduction
Port Forwarding allows specific ports of the hosts residing in the internal network to be forwarded to the external network. This is useful for number of applications such as FTP servers, gaming, etc. Latest AirOS Versions support PortFW, for detailed info see AirOS Router Mode
Consider simple scenario as you can see below. We want connect to Windows PC (10.10.10.30/24) via Remote Desktop (Terminal Server) from Wireless LAN. To achieve this, we need to port forwarding TCP/3389 port (standard Remote Desktop port) from AirOS WLAN to Windows PC.
AirOS Devices is configured in Router Mode, with WLAN IP Address 192.168.1.20/24 and LAN IP Address 10.10.10.254/24.
Configuring
Login into AirOS WEB User Interface, go to NETWORK Tab and set as below:
- Network Mode: Router
- Enable NAT: check box on
- Port Forwarding: check box on (to activate Configure... button)
Note: Port Forwarding are located in WLAN Network Settings if the device is running in AP/AP-WDS mode or in LAN Network Settings if the device is running in Station/Station-WDS - Press Configure... button to open Port Forwarding window
- Add a new rule setting:
- Private IP: 10.10.10.30 (Windows PC address)
- Private Port: 3389 (port on Windows PC)
- Type: TCP
- Public Port: 3389 (port on AirOS Device)
- Comment: RemoteDesk (or any your comment...)
- Enabled: check box on
- Click Save button to confirm
- Click Apply button to apply changes
- Wait until process is complete
Now you should be able to connect to Windows PC via Remote Desktop typing 192.168.1.20 on Remote Desktop Client.
Note: you can reach internal WEB Server, FTP Server, SSH login to servers, etc simply replicating a Port Forwarding rule for each services.
MAC Access Control List (ACL) Management
Author: Skyhook 28 February 2009
Contents: How to configure MAC ACL in AirOS
Remark: Tested on AirOS version 3.3.1 (applicable for AP and AP WDS modes only)
Introduction
MAC Access Control List (ACL) provides ability to allow or deny certain clients to connect to the AP (applicable for AP and AP WDS modes only).
This is useful to manage wireless network topology, load balancing associated stations to APs with same SSID, but is the weakest security approach. WEP (not recommended, very poor), WPA™ or WPA2™ security methods shoud be used when possible.
Note: MAC Access Control List is avaible only if AirOS device is running in AP/AP-WDS mode.
As detailed in AirOS Wireless Security, there are two ways to set the Access Control List:
- MAC ACL Policy Allow: only wireless devices in the list will have granted access to the Access Point while the access will be denied for all the remaining
- MAC ACL Policy Deny: all wireless devices in the list will have denied access to the Access Point while the access will be granted for all the remaining clients.
Configuring via WEB GUI
Login into AirOS WEB User Interface, go to LINK SETUP Tab:
- In MAC ACL Section, check Enabled
- Select Allow or Deny policy
- Add/Remove MACs to/from list (be careful!!!)
- Click Change button to confirm new configuration
- Click Apply button to apply changes
- Wait until process is complete
Add more then 16 MACs in ACL (Manual editing)
AirOS WEB User Interface manage up to 16 MAC Address.
If you need more then 16 MACs, a workaround is to add MACs manual editing configuration file.
- Download configuration file
- Open configuration file whit text editor supporting Linux/Unix format and manually add additional lines of MAC filtering:
... wireless.1.mac_acl.17.mac=XX:XX:XX:XX:XX:XX wireless.1.mac_acl.17.status=enabled wireless.1.mac_acl.18.mac=XX:XX:XX:XX:XX:XX wireless.1.mac_acl.18.status=enabled wireless.1.mac_acl.19.mac=XX:XX:XX:XX:XX:XX wireless.1.mac_acl.19.status=enabled wireless.1.mac_acl.20.mac=XX:XX:XX:XX:XX:XX wireless.1.mac_acl.20.status=enabled ...
- Upload edited configuration file
- Apply new configuration
Note: set status as:
- enabled = allow
- disabled = deny
The AirOS WEB GUI always show only first 16 MACs, but if the configuration file are correctly edited, it work fine.
Simply AP Setup
Author: Skyhook 28 February 2009
Contents: How to setup AP to share a Internet connection or to access your private LAN
Remark: Tested on AirOS version 3.3.1
Network Topology
We consider this simply network topology:
- 1 Router/Gateway connected to Internet and/or private LAN (IP Address: 10.10.10.254/24)
- 1 Switch for private LAN (optional)
- 1 AP AirOS device directly connected to Router (IP Address: 10.10.10.253/24)
- 1 or more Wireless Clients (Notebook, WiFi-Phone, other Wireless devices...)
- The Router assign IP Address to network devices by DHCP Server. Alternatively, if you prefer, you can set static IP Address on Client.
Devices configuration
Router Setup
Router can be your ISP ADSL Router, a Ubiquiti Routerstation or a Mikrotik RouterBoard plus Ethernet Modem... please refer to device manual.
- Set your Internet connection according to ISP paramenters (WAN IP Address, DNS IP Address, ...)
- Set LAN IP Address/SubnetMask: 10.10.10.254/255.255.255.0 (10.10.10.254/24)
- Enable DHCP Server to assign IP Address to Network Devices (e.g. range Client IP Pool from 10.10.10.1 to 10.10.10.100)
AirOS AP Setup
Connect your PC directly via Ethernet cable to AirOS Device to confiigure as AP and login into WEB-GUI.
Note: need to configure your PC with an IP Address of same Subnet of AirOS device.
By default, AirOS device have 192.168.1.20/255.255.255.0, you can assign your PC IP Address like: 192.168.1.1/255.255.255.0 (see this guide)
- In LINK SETUP Tab, set:
- Wireless Mode: Access Point
- SSID: yourSSID (or any other string to dentify your WLAN)
- Country Code: set according your country
- IEEE 802.11 Mode: B/G mixed (assuming devices running in 2.4 GHz)
- Channell Spectrum Width: 20MHz
- Channel: 1 - 2412 MHz (or any other free channel)
- Output Power: 10 dBm (or check Obey Regulatory Power according your country law)
- Data Rate, Mbps: 54, Auto
- Security: WPA (or any other, supported by Wireless Client)
- WPA Preshared Key: yourpassphrase (this is a secret key for your WLAN, minimum 8 printable ASCII chars, maximum 63)
- Click "Change"
- Wait until process is complete and click "Apply" to confirm new configuration (or click "Discard" to refuse).
Note: we suggest to set Wireless Security only after you are sure that Wireless Client are able to connect your AP.
Note: not all Wireless devices support all Wireless Security (WEP, WPA, WPA2, ...)
- In NETWORK TAB, set:
- Network Mode: Bridge
- IP Address: 10.10.10.253
- Netmask: 255.255.255.0
- Gateway IP: 10.10.10.254
- Primary DNS IP: 10.10.10.254 (or DNS IP provided from your ISP)
- Secondary DNS IP: as Primary DNS IP
- Click "Change"
- Wait until process is complete and click "Apply" to confirm new configuration (or click "Discard" to refuse).
- Now the devices should be reachable on new IP Address 10.10.10.254.
- Remember to assign to your PC a IP of Subnet 10.10.10.x (e.g.10.10.10.200/255.255.255.0)
Client Setup
Wireless Client devices can be: Laptop (whit Windows, MAC, Linux...), PDA, WiFi-Phine, WiFi IP Cam... refer to manual.
In TCP/IP Network Section:
- If supported, set device to obtain Address IP automatically
- Otherwise set statically:
- IP Address: any free IP 10.10.10.x/255.255.255.0
- Gateway: 10.10.10.254
- DNS: 10.10.10.254 (or DNS provided by your ISP).
In Wireless Section, set the same parameters used in AP Setup:
- WiFi Channel
- Wireless Security (WEP, WPA, WPA2,...)
Monitoring Associated Clients/Stations
- In MAIN TAB, select Show Station from Extra info menu.
.
A popup window will list Associated Stations
For detailed info, click on the MAC address.
Configuration File Management
Author: Skyhook 27 February 2009
Contents: How to manage configuration file: download, upload and edit.
IMPORTANT!
Use only configuration backups of the same type device and same AirOS version.
Example: configuration backed up from NanoStation5 suits only NanoStation5, but not NanoStation2 or LiteStation5!
Behavior may be unpredictable when mixing configurations from different type devices and/or AirOS version.
DOWNLOAD/BACKUP Configuration File
- Connect you to AirOS Device via WEB browser.
- In SYSTEM Tab, click "Download..." button to save cfg file on your PC (e.g. XS2-00156DA67108.cfg).
UPLOAD/RESTORE/UPDATE Configuration File
- Connect you to AirOS Device via WEB browser.
- From SYSTEM Tab, clicking "Browse..." button, will open a window popup (make sure your browser have popup enabled) to navigate and select the configuration file. From "Firmware File" select configuration to restore (e.g. XS2-00156DA67108.cfg).
- Click "Upload" to start the transfer.
- Wait until process is complete and click "Apply" to confirm new configuration (or click "Discard" to refuse).
- Now the devices apply new configuration file.
EDIT Configuration File
You can simply edit configuration file with a text editor capable to manage Linux/Unix text format.
Note: Manual editing of configuration file is recommended only for advanced and skilled users!!! Behavior may be unpredictable if you set wrong or improper parameters.
A tipical CPE WISP mode configuration
Author: Skyhook 27 February 2009
Contents: A tipical CPE configuration for WISP.
We suppose that the WISP want to use PPPoE authentication.
From AirOS device with default configuration, set parameters as see below:
- LINK SETUP Tab
- Wireless Mode: Station
- ESSID: set according with your APs
- NETWORK Tab
- Network Mode: Router
- WLAN IP Address: PPPoE
- PPPoE Username: Customer_PPPoE_username
- PPPoE Password: Customer_PPPoE_password
- Enable NAT: on
- Enable DHCP Server: on (and configure desired Range Start, Range End,Netmask)
- Enable DNS Proxy: on
- ADVANCED Tab
- Incoming Traffic Limit: 2048 kbit/s (es: customer profile download up to 2 Mbits)
- Outgoing Traffic Limit: 256 kbit/s (es: customer profile upload up to 256 kbits)
- SYSTEM Tab
- Host Name: set a customer IDentifier
- Administrator Username: remember to change default administrative username and password
You can also customize other parameters: Wireless Security, Data rate, Logo Customization...
After customization, you can download configuration file and reuse it for different customer, simply editing customer values (PPPoE account, LAN...).
Firmware Upgrade process
Author: Skyhook 27 February 2009
Contents: This guide describe the Firmware Upgrade process of AirOS.
Requirements:
- UBNT devices to upgrade.
- Ethernet Cable.
- A PC or Laptop always configured to access the units (es. [2]).
IMPORTANT!
- Do not switch off, do not reboot and do not disconnect the device from the power supply during the firmware upgrade process as these actions will damage the device!
- It is highly recommended to backup the system configuration and the Support Info file before uploading the new configuration.
- If Upgrade procedure fail, don't worry, you can try Factory Firmware Recovery Procedure
Step 1: Download Firmware file from UBNT Support page
- From UBNT Support Page select specified Firmware for device (Nanostaion2, Bullet5, Powerstation5,... ) to upgrade.
- Download Firmware file and save on your PC.
Note: before to dowload, take a look to AirOS Firmware Revision History
Step 2: Upload Firmware package
- Login your AirOS device via WEB browser, go to "SYSTEM" Tab.
- In "FIRMWARE" Section, click "Upgrade...", will open a window popup (make sure your browser have popup enabled).
- In "FIRMWARE UPLOAD" Window, click "Browse..." to navigate and select the new firmware file. From "Firmware File" select file just downloaded (e.g. XS2.ar2316.v3.3.1.4227.090128.1828.bin)
- Click "Upload" and wait to complete transfer process.
Note: If you wants to cancel upload proces, click "Close this window" button.
- Check if new Firmware are correctly transfered, press "Upgrade" and wait to complete upgrade process. The firmware upgrade routine can take 3-7 minutes.
Note: AirOS based device will be unaccessible until the firmware upgrade routine is completed.
Note: After upgrade process is activated, "Close this window" button closes the firmware upgrade window but will not cancel the firmware upgrade process!
Factory Firmware Recovery Procedure
If Upgrade procedure fail, don't worry, you can try Factory Firmware Recovery Procedure
(coming soon...)
Make persistent changes on AirOS (extra standard file configuration)
Author: Skyhook 28 February 2009
Contents: How to make persistent changes on AirOS configuration (extra standard file configuration)
Introduction
AirOS is Linux based. If you are a Linux guru, you can customize many typicals of Linux that are not in standard configuration file of AirOS, adding your customizations in this files:
/etc/persistent/rc.presysinit
/etc/persistent/rc.postsysinit
/etc/persistent/rc.prestart
/etc/persistent/rc.poststart
/etc/persistent/rc.prestop
/etc/persistent/rc.poststop
Example procedure
- Make sure that AirOS device have a active console CLI (in SERVICES Tab, enable Telnet or SSH as you prefer)
- Login to CLI
- Make yours customizaions using vi text editor (e.g.
vi /etc/persistent/rc.poststart...) - Check your changes...
- When you are sure, run command
cfgmtd -w -p /etc/to write permanently into flash - Now, you can reboot device, run
reboot - After reboot, your changes should be already active
Note: We recommended this type of deep changes only for advanced and skilled users!!! Behavior may be unpredictable if you set wrong or improper parameters.