* Add experimental support for the GL.iNet GL-AR150 - https://openwrt.org/toh/gl.inet/gl-ar150
Mesh networking and tunneling have been confirmed working.
This device has been confirmed capable of operating on channel -1, but /etc/config/wireless has to be manually edited to select this channel.
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150 - seems like only 18 dBm TX power is possible
* Remove Experimental comments and designate as stable
* Configure Ethernet ports & VLANs for GL-AR150, and update README.md
* Fix misunderstanding re README.md
* Patch Upstream OpenWRT GL-AR150 LAN & WAN LED mapping, configure WLAN LED as mesh linked indicator.
This reverts commit d5be7814b3.
Auto Distance is not ready for a release and will be
reintroduced afterwards. Added logic to reset '0' distance
to 60km so tower nodes will continue to respond after
upgrade if running the experimental auto distance
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
* aredn: hAP ac lite enable 5GHz LAN Access Point
enable ability to bridge LAN physical ports with wireless
LAN Access Point capability. On dual band hAP ac lite,
used in parallel with mesh RF on 2GHz. Enables future
features on single band devices to turn off mesh RF and
repurposed for mesh LAN Access Point.
closes: #215
The aredn project benefits from precompressed files given
mesh nodes are typically long distant RF links and UI
is accessed remotely. uhttpd will look for the filename
requested first, then if not found, look for filename.gz
and update content header passed back as appropriate.
https://patchwork.ozlabs.org/patch/514918/
Config the NanoStation M2/M5 XW devices to be fully
functional with a standard aredn port definition.
The vlans are not configured in the switch, rather
acting like a dumb swtich, enabling tagged and untagged
packets to exist on the same switch port at the same time.
This commit enables the ports on the switch to directly
send all traffic to all other ports when not configured
directly in vlan mode.
The NanoStation M2 and M5 XW switch configuraiton had LAN
on primary port (untagged) and DtDLink and WAN (vlan 1 and 2)
on secondary port. This change enables untagged, vlan 1,
and vlan 2 on primary port to function. This configuration
also functions on the secondary port. However, devices on
the same network can not communicate with one another across
the two ports. Although, access works from the greater mesh
and the node to devices on both ports on the same network.
When using one port the behavior is now consitent with all
other AREDN devices. The use of both ports offers some
benefit, but with the above limitations.
Add support for the hAP lite model rb952UI-5ac2nD equivilent to
the UBNT AirRouter. The 5Ghz interface will be configured in a
2nd phase. This hAP lite model has double the RAM and Flash
of the AR. the 2Ghz is MIMO (5Ghz is single antenna).
The patch was wrongly removed by a kernel version bump to 4.9.106 in
the believe that it was merged upstream thow it wasn't. This lead to
unrecoverable link losses on devices which use those PHYs such as
many ubnt single-port CPEs.
Fixes: 6f8eb1b50f ("kernel: bump 4.9 to 4.9.106 for 18.06")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
(cherry picked from commit a497e47762)
Closes#81
* Trim Packages
Kernel support for USB has been moved to modules
libpcap and tcpdump have been moved to modules
libnetsnmp and snmpd have been moved to modules
IPv6 has been removed from the kernel
IPv6 support has been removed from busybox network utils as well.
(no more funny DNS responses in nslookup!)
* Remove ping6 and traceroute6
They are no longer needed
* Changed patch name and number and updated series file
This Device is almost the same as the CPE210 V2.0
Once Support for the TP-LINK CPE210 V3.0 gets added to the OpenWrt code we
will need to drop the patch 001-add_support_for_TP-Link_CPE210_v3.patch
Once the PR for this is accepted by Openwrt we will need to remove the file
001-add_support_for_TP-Link_CPE510_v2.patch
Removed 001-add_support_for_TP-Link_CPE210_v2.patch as PR #937 has been committed
Updated 99_setup_aredn_include to remove unused Rssi Led configuration
newer versions of Ubiquiti uboot constrain
the firmware header version sting. Current
openwrt formated versioning results in a
uboot firmware check error
Joe Ayers