[pkobel]

With our latest upgrade, we unified firmware of APPro2405, APPro54G, and APPro 54G Client versions intended for devices with 2MB Flash / 16MB RAM. We encourage all users of APPro 54G and APPro 54G Client to try the latest generation of APPro firmware.

Note: This operation is performed only once and cannot be reverted. Due to massive amount of introduced changes, we cannot guarantee accuracy of configuration conversion process.

You can perform a conversion regardless of used license format (hardware module / license file) or type (client / full license).

Conversion procedure depends on device type, and consists of two stages:

Stage One:

in case of devices:

* AirLive 5470AP;
* D-Link DAP-1160;
* Minitar MNWAPG-2;
* Techniclan WAR-54GS

it is required to re-install software as described on this page. All licensing data will be retained.

in case of devices:

* AirLive 5460AP;
* Edimax EW-7209APg;
* Planet WAP-4035, WRT-414;
* Planex GW-AP54SP;

it is possible to install new firmware via Web interface - exactly the same way as in case of a standard upgrade.
Upgrade procedure:

* download intermediate firmware
* decompress file and upload it to the AP
* after restart AP should be available with new firmware and correct licensing data

Stage Two:

After installing new firmware you should review AP's configuration, correct settings when needed, and at least once save settings by clicking on OK button. After confirming the configuration, you need to download latest version of APPro2405 from download page.

With the conversion completed, further upgrades will use firmware files in a new format - the same for all APPro2405 / APPro54G or APPro54G Client devices. Our firmware is available in two variants: one is based on the latest WLAN driver (standard version), and one based on WLAN driver 1.08 (requested by small group of customers). For optimum operation we recommend version with the latest WLAN driver.

Files with APPro firmware are named in following fashion:

appro-2405-dd-mm-yyyy-zzz-revxxx.bin

where:

* dd-mm-yyyy - release date
* xxx - number of compilation
* zzz - WLAN driver version

We did our best to preserve configuration compatibility with older versions of APPro54/APPro54G Client, but the massive amount of changes made it impossible to guarantee complete compatibility. For that reason, we recommend installation method that will ensure complete control over the device, and the ability to reset the device or reinstall the firmware using TFTP protocol. Due to possible incompatibilities and a risk of damaging the device with an incorrectly performed conversion, we protected intermediate firmware with a password "approsoftware". If you are commited to install this firmware, by typing the password you confirm that you accept the risk and relieve us from any liability for resulting problems.

In case of trouble:

* reset the device by depressing Reset button for 3 seconds; release Reset button when Status/Power/CPU LED blinks
* upload firmware via TFTP protocol, as described here.

[DaNY]

Several questions about new APPro54G fw 23-12-2008-1.14d-rev1088.bin for devices with HW module:

1/ AP Status - Sensors Info
This status info is empty, no more info about temperature and voltage? :-(

2/ AP Status - System
There is no possible to identify version of WLAN driver currently installed? Is it somewhere else?

3/ AP Status - Interface Settings
Ports eth0 and eth1 have problematic description (LAN1-4 / WAN). It is probably according to APPro2405...but there are normally LAN1 / LAN2 ports on WL-5460 and others. This description is more problematic in TCP/IP - Advanced Settings - Bandwidth Management.

4/ According to scripts/qos.sh the Traffic Managers is now HTB type without any burst again? So, is it possible to add by user some burst option to the script and save it? The same question like in my other topic about APPro5000 - how to save my changes ("flash save-all" does not work and there is no option "flash save-file")?

5/ There is still small mistake in Active Wireless Client Table description for a long time... There is double "for for" in the description. :-)

Thanks for reply.

[Scorpio_cz]

Hello,

I upgraded my Edimax EW-7209APg to APPro2405.

Positives :
=======
- it worked OK, updated through WEB via the intermediate FW
(why the ZIP is password protected ?)

- now LED indicators WLAN and POWER on the Edimax EW-7209APg are lighting
(the WLAN LED was not lit with APPRO 54g)

Negatives :
========
- AP Status - Sensors Info - info is empty :
( License Name: APPro54G HW licence)
APPro Module: ---
Temperature: ---
Voltage: ---

- AP Status - System - not easy to identify WLAN driver version from build string :
2.4.18-sdk5 #1088 Tue Dec 23 20:08:17 CET 2008

- AP WEB - when login is made to the WEB, it displays config wizard ... why ?
Status page is much better start point than the config wizard

- AP Wireless Clients - no IP address of client is displayed in AP & Bridge mode
(APPRO 54g displayed IP addresses of the wireless clients even in AP bridge mode)

- Even with use of intermediate FW the config was lost and whole AP must have been reconfigured - it even lost the IP address at one moment and reverted to default

[DaNY]

Another note:

6/ LAN2 led does not light on Ovislink WL5460, but works

[Scorpio_cz]

For DaNY: on Edimax EW-7209APg all 5 LAN LED's are working OK.

[DaNY]

small update to my question 4/

I did study the latest version od flash command and help says:

flash {save-config, restore-config, save, restore, save-all }

save-config - save current settings to flash
restore-config - restore settings from flash
reset - reset configuration flash
save - save user configuration (/usr/local, /etc, /scripts) (16MB)
restore - restore user configuration (/usr/local, /etc) (16MB)

So the flash save command should save changes in the /usr/local, /etc, /scripts directories. When the command is processed, you can see mesages like:

Compressing user files
tar: Removing leading '/' from member names
usr/local
scripts
etc
Reading: /tmp/user.tgz to buffer
File size: 154
Writing file to flash
Done !

But the problem is, that the file user.tgz contains empty structure of files and one directory, so nothing is saved. My changes in scripts/qos.sh are lost after reboot :-( The problem of APPro5000 is simillar... Please help. Thank you

[pkobel]

Just FYI - we did not ignored posts above. We are busy with final batch of fixes, so we could finally get them out and take care of 5 GHz firmware.

[Scorpio_cz]

Thank you for an update Mr. Kobel.

We're looking forward for the new FW build with the bugs fixed.

Edit :
BTW: I just realized I have HW-ID string just all zeros :

HW ID:
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

Is this a mistake reading the HW module (which I have installed), or is this because I do have a HW module installed ?

[Scorpio_cz]

Hello,

a first real problem ... today, after 4 days of uptime, the WiFi on the Edimax EW-7209APg get hanged - I have FW with driver 1.14 installed ...

The WiFi SSID had been broadcasted (devices saw it) but it didn't allow association of the devices. I tested 2 different devices and none of the associated.

The devices WEB itself responded on the ethernet, so I tried to reload the settings to make WiFi alive - and device reboot instead the reload only. After reboot the WiFi works OK.

I don't remember such behaviour with APPRO 54g Turbo, WiFi driver 1.11
There usual uptime of the device was around 40-50 days between reboots.

[pkobel]

Thanks for the info. While we try to track this (if you have any more details, it would help), I'd suggest using either watchdog or an auto-reboot every 24h.

[Scorpio_cz]

Mr. Kobel I am sorry, I don' have any more details.

I was under presure to make WiFi alive, and I planned to read syslog after I make WiFi working ... and the self-reboot of the device wasn't realy "cooperating" so I think I have lost all evidence ... you can e-mail me on my forum mail with the list of details you need - I am willing to provide as much as I can.

[Scorpio_cz]

Hello,

I upgraded my Edimax EW-7209APg to APPro2405 test build #1219.

Issues :
========
- AP Status - Sensors Info - info is empty :
( License Name: APPro54G HW licence)
APPro Module: ---
Temperature: ---
Voltage: ---
=> This issue still exists

- AP Status - System - not easy to identify WLAN driver version from build string :
2.4.18-sdk5 #1219 Sat Jan 10 03:17:44 CET 2009
=> This issue still exists - the only way to get WiFi driver version is via build ID

- AP WEB - when login is made to the WEB, it displays config wizard ... why ?
Status page is much better start point than the config wizard
=> Still exists - I believe it's nonsense on already configured device
=> Device shall first display Status page (like APPRO 54g did) and
=> You shall better make "Wizard" one of the options on left hand menu

- AP Wireless Clients - no IP address of client is displayed in AP & Bridge mode
(APPRO 54g displayed IP addresses of the wireless clients even in AP bridge mode)
=> SOLVED - IP addresses of wireless clients are now displayed OK

- HW ID is all zeroes :
HW ID: 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
Is this a mistake reading the HW module (which I have installed), or is this because I do have a HW module installed ?
=> This issue still exists

[Scorpio_cz]

Hello,

similar problem like yesterday, just much much faster - uptime is 1h 28m.

The AP status shows wlan started :

Kod:

Channel Number: 3 Tx Rate: 54 State: Started Associated Clients: 0

But the 3 different wireless clients (WiFi WM60 smartphone, WiFi WM60 PDA, Notebook with Intel 3945ABG) doesn't see SSID being broadcast and cannot connect to the WiFi.
Somewhere around 15:30 it was OK, around 16:00 when I returned the WiFi is hang.

00:1B:77:xx:xx:xx - Notebook with Intel 3945ABG, Windows XP PRO, radio module on the card had been switched off around 15:00 - but still appears on the client list - maybe it's the problem

00:1A:6B:xx:xx:xx - WM6.0 WiFi PDA iPAQ 214

00:1B:FB:xx:xx:xx - WM6.0 WiFi SmartPhone iPAQ 514

Message log last message seen is :

Kod:

Jan 10 15:39:31 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 15:41:59 Scorp-Scorp user.warn kernel: wlan0: A expired STA is resumed - 00:1B:77:xx:xx:xx Jan 10 15:44:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 15:49:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 15:52:00 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 15:54:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 15:59:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 16:00:44 Scorp-Scorp user.warn kernel: wlan0: A expired STA is resumed - 00:1B:77:xx:xx:xx Jan 10 16:04:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 16:09:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 16:10:44 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 16:12:10 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1A:6B:xx:xx:xx Jan 10 16:12:11 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:FB:xx:xx:xx

I will now try to reload only a config ... and see what will happen.

RELOAD DIDN'T HELP

State of the wlan0 interface after reload :

Kod:

wlan0     Link encap:Ethernet  HWaddr 00:0E:2E:xx:xx:xx           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:116684 errors:0 dropped:0 overruns:0 frame:0           TX packets:193156 errors:160 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:20           RX bytes:10517441 (10.0 MiB)  TX bytes:190899259 (182.0 MiB)           Interrupt:2

I have tried following sequence ... and WiFi come up again :

Kod:

Scorp-Scorp$ ifconfig wlan0 down Scorp-Scorp$ ifconfig wlan0 up Scorp-Scorp$ /scripts/wpa.sh

Yes, I forgot to mention, I use WPA2/AES authentification on the WiFi.

[Scorpio_cz]

Hello again,

more details ... I think I have found the pattern to hang the WiFi on APPro 2405 :

1) I start WiFi on PDA, and start the internet radio ...
2) I start WiFi on SmartPhone, I also start internet radio ...
3) I start WiFi radio on Intel 3945ABG card in my notebook ... via Intel tray utility ... WiFi ON
4) The notebook associates with WiFi
5) I wait for a while, in APPro 2405 notebook is listed in active clients
6) I stop WiFi radio on Intel 3945ABG card in my notebook ... via intel tray utility ... WiFi OFF
7) within less than 1 hour the APPro 2405 WiFi stops responding - both PDA and Smartphone looses WiFi connection.

Around 19:40:50 I have issued "ifconfig wlan0 down" - extract from the log is :

Kod:

Jan 10 19:14:01 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 19:14:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:14:25 Scorp-Scorp user.warn kernel: wlan0: A expired STA is resumed - 00:1B:77:xx:xx:xx Jan 10 19:19:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:24:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:24:26 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 19:24:50 Scorp-Scorp user.warn kernel: wlan0: A expired STA is resumed - 00:1B:77:xx:xx:xx Jan 10 19:29:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:34:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:34:51 Scorp-Scorp user.warn kernel: wlan0: A STA is expired - 00:1B:77:xx:xx:xx Jan 10 19:39:12 Scorp-Scorp daemon.info init: ^Mcalling mini cron actions Jan 10 19:39:25 Scorp-Scorp user.warn kernel: wlan0: A expired STA is resumed - 00:1B:77:xx:xx:xx Jan 10 19:40:53 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:53 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:53 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:54 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:54 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:57 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:57 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:57 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:57 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:40:57 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:00 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:00 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:00 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:01 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:01 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:20 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:20 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:21 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:21 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:41:21 Scorp-Scorp user.warn kernel: wlan0: A wireless client is deauthenticated - 00:1B:77:xx:xx:xx Jan 10 19:42:13 Scorp-Scorp user.info kernel: br0: port 1(wlan0) entering disabled state Jan 10 19:42:25 Scorp-Scorp user.info kernel: br0: port 1(wlan0) entering listening state Jan 10 19:42:27 Scorp-Scorp user.info kernel: br0: port 1(wlan0) entering learning state Jan 10 19:42:29 Scorp-Scorp user.warn kernel: wlan0: A wireless client is associated - 00:1B:FB:xx:xx:xx Jan 10 19:42:29 Scorp-Scorp user.info kernel: br0: port 1(wlan0) entering forwarding state Jan 10 19:42:29 Scorp-Scorp user.info kernel: br0: topology change detected, propagating

As you can see, at the "ifconfig wlan0 down" the MAC address 00:1B:77:xx:xx:xx is being deleted from driver's table 21 times, while I only have ONE such MAC.

From my point of view that looks very unusual - namely when the card radio is down.

[Scorpio_cz]

So finaly, the issue realy appears to be related to the WiFi driver version.

Both FW builds with WiFi driver 1.14d hanged in the same scenario.
(appro-2405-23-12-2008-1.14d-rev1088.bin, appro-2405-10-01-2009-1.14d-rev1219.bin)

Now I have deployed the FW with 1.08 WiFi driver version and I try to reproduce.
(appro-2405-23-12-2008-1.08-rev1087.bin)

Uptime is now around 3 hours and until now I haven't reproduced the WiFi hang.
With 1.14d driver it required less than 1 hour regulary.