villagetelco / vt-firmware Goto Github PK

Asterisk is pre-installed in SECN 2.0 RC4a on the MP02 and TP Link devices which have sufficient flash memory eg WR842 and WDR3600/43x0

The Ubiquity M devices such as Nano 2M have 8MB of flash and so can also have Asterisk installed as part of the base firmware.

It appears that 802.11 N-G mode is not supported by Ubiquity devices.
If this mode is selected the wifi stops working completely.

Resolved by removing the selection from the web interface Advanced page.
Default is 802.11G mode.

I had a Bullet M2 with SECN 2.0RC1, and I used the sysupgrade image to upgrade to RC3. I chose to "keep current settings". batman-adv did not start after upgrade. The "Enable Mesh" checkbox on the web gui could be set and saved, but after a reboot, the checkbox was still unset and batman-adv was not operational. I edited the config file to try to enable it there, but this was also unsuccessful. - I re-upgraded with the same sysupgrade image, but chose not to keep settings. This was successful , and batman-adv was enabled.

In WiFi WAN mode, the SSID field for the upstream Access Point does not allow the use of space characters.

This means that you can not connect to an AP which has been configured to have space characters in the SSID.

In SECN RC1, Asterisk is started prior to the mesh being fully operational due to the order of scripts in /etc/rc.d for Asterisk and mesh-gateway.

This can result in Asterisk not registering a SIP service correctly due to the startup requirement of Asterisk that it be able to access the internet.

Restarting Asterisk manually fixes the proble till the next reboot.

Fix is to move the Asterisk startup script after the mesh startup script.

In SECN 2.0 RC3, the AP is disabled when the WAN mode is selected.
However it is possible to run both AP and Station mode, so the AP can be left running in WiFi WAN mode.

Note that the AdHoc mesh interface can not be run in conjunction with Station mode.

In SECN 2.0 the "opkg update" command fails because the opkg config points to the AA "12.09.1" repo which does not exist.

This is automatically generated when the firmware is compiled.

A workaround is to edit the /etc/opkg.conf file to point to the "12.09" repo which does exist.

When submitting a password change via the web ui, any special characters, such as exclamation marks etc are url-encoded prior to being saved.

In current SECN firmware, TxPower setting is limited to a range of 1-20dBm which corresponds to a maximum power output of ~100mW

Many devices, in particular Ubiquity devices, are capable of higher power (eg 500mW) and are often provisioned for just this reason in order to allow long links or wide coverage.

The range needs to be increased to allow proper use of these devices.

SECN 2.0 RC1 UBNT firmware images (for Nanostation, Rocket, Bullet) are not processing fields for Chanbw and Mesh GW bandwidth correctly.
In addition, DNS fields are not displayed in the DHCP section, and DHCP subnet is not being set correctly.

The above are due to updates not being applied to the device specific config.html, conf-get.sh and conf-sub-adv.sh files in the UBNT overlay directory.

The RC1 firmware will be updated for these devices and will show as RC1b

On devices with a designated WAN port e.g. MP02, the port is only used if the WAN mode is selected as Ethernet.

Provide a facility to allow the WAN port to be included in the LAN bridge.

This will provide a extra LAN port e.g on a MP02 there will be two LAN ports available.

In RC2f, WiFi WAN setting does not work due to incorrect setting of Mesh Enable control in script /etc/config-secn

Add snmpd package to package repo so that it can be installed if required.

/etc/opkg.conf currently points to trunk package repo.

This can cause incompatible packages to be attempted to be loaded due to changes in kernel etc.

Two changes required:

• Set up a package repo from the build server Packages directory in VT Downloads
• change /etc/opkg.conf to point to it

Bug in SECN 2.0 RC1
Setting timezone where a '+' is required for the time offset produces a html encoding error. Negative time offsets are OK.

I had a Bullet M2 with SECN 2.0RC1, and I used the sysupgrade image to upgrade to RC3. I chose to "keep current settings". This caused two problems:

1. After the wait for reboot, the web page tried to revert to 10.130.1.20 (even though it successfully left the ip address unchanged at 10.130.1.21)
2. batman-adv did not start after upgrade. The "Enable Mesh" checkbox on the web gui could be set and saved, but after a reboot, the checkbox was still unset and batman-adv was not operational. I edited the config file to try to enable it there, but this was also unsuccessful. - I re-upgraded with the same sysupgrade image, but chose not to keep settings. This was successful , and batman-adv was enabled.

SECN 2.0 RC1 is based on OpenWrt Attitude Adjustment 12.09 RC1.

The build needs to be upgraded to AA 12.09 Stable Release.

The main item of work is to deal with the change to the way batman-adv is included in the build which was changed in OpenWrt AA 12.09 Stable Release.

Reported by Tim Moody (OLPC).
Unable to activate 5GHz band mesh.

Investigation:
The logic for enabling and disabling wifi interfaces in relation to WAN settings was changed in this release, and the changes were not correctly implemented for the interfaces on the second band.
Two files require changes:
/etc/init.d/config_secn
/www/cgi-bin/config/conf_sub_adv.sh

Two additional packages are required for full support of USB 3G modems:

• kmod-usb-serial-option
• kmod-usb-serial-wwan

Packages need to be added to the Setup script, and included in updated .config file for all USB equipped devices.

Reported by Edwin Chan against SECN 2.0 RC2 firmware.

If WiFi WAN is selected, then subsequently Eth WAN is selected, the wifi sta interface is not disabled when Eth is selected.

Correction applied to /etc/init.d/config_secn for RC3b firmware.

Workaround is to select WAN Disabled and save, prior to selecting WAN Ethernet.

Asterisk 1.8.10.1 hangs when resolving dns in register only. not for the peers.
If you change the register from :
register => user:[email protected]/number
to
register => user:pass@IP-Address/number
The problem is gone.
You can see the same issue in the openwrt issue tracker.
https://dev.openwrt.org/ticket/11929

It s seems to be an issue in uClibc 0.9.33.2 resolv.c
the is a patch here
https://dev.openwrt.org/attachment/ticket/11929/560-res_init_asterisk.patch

But it need to recompile Asterisk in openwrt and i dont know how to perform this.

Regards

Daniel

The TP-LINK 741ND ver 4.24 defaults to radio - wifi mode - 802.11G. If I switch the wifi mode to 802.11G-N and reboot I receive the message

BATMAN mesh bat0 disabled - please specify interfaces to enable it.

NOTE: I ordered 2 X 741NDs is a single order from Amazon. It is 100% reproducible on one unit and 0% reproducible on the other.