You nailed it macedo!!!!! ... thanks alot!!!!!!! I cant tell you how appreciative I am of your efforts and all you guys who make this question/answer/discussion forum so valuable.
Pic 4 shows the panel antenna on the boat house to the right of the lightPS I fibbed a little about how far the boat dock was from the house. I said it was 200ft but actually its closer to 400ft. It's really impressive how powerful these ASUS routers are. On the exterior wall of my house there is is a 44" stem wall with a oncrete floor and and access to the entire 1st floor of the house. So it was easy to mount a AC68U on the interior wall behind the panel antenna which points toward the boat hose. Antennae is a 2.4/5Ghz on a single line. Line-of -sight from house to dock. See pics 1-3.
Pic 6 shows the boat slip with PTZ cameraPic 4 shows the panel antenna on the boat house to the right of the light
Pic 5 shows the AC1900P which runs the VOIP phone with 911 capability, Day/Night Camera monitored 24/7/365 all on UPS
Pic 5 Before you ask ... yes there is a beer cooler!
Tried that, too ... still didn't work.The pairing systems of Asus routers is the most horrible thing that any intern could design.
I ONLY ever got them to pair with them physically connected to each other.
DIRECTLY. You can not just have it on the same network for some stupid reason. They must be directly connected.
Probably not.
Just to be clear and find out exactly where you are having issues:
1) Disconnect all ETH cables from the node
2) Reset the node: a) turn the node off; b) press and hold WPS button; c) turn node on; d) wait until the power led starts flashing (around 25 seconds on my nodes); e) release the WPS button; f) wait for the node to boot up
3) Connect your desktop / laptop / tablet / etc to the router either wirelessly or wired
4) In your browser, navigate to either router.asus.com or your router's IP address. You should be accessing you router's GUI, not your node's then
5) Disable WAN/Internet
6) Connected an ETH cable to one of the LAN ports of the router and to the WAN port of the node
7) In the router's GUI, start the Add AiMesh Node and wait for it to complete. It may finish fine before reaching 100% and display a success message. It happened to me more than once to think it was an error as it finished earlier than I expected. So, be sure before you assume it failed.
8) Enable WAN/Internet
This... I've found stock on nodes and Merlin on main has always been successful for me.I suggest running Merlin on the main router and run the latest AsusWRT on all nodes.
You can try connecting your nodes by network initially, even of it means putting them next to your main unit.
After they are recognized and showing up on your main unit, you can power them off and place them back where you want them. They should reconnect wirelessly. Also, do not change any of the AiMesh backhaul settings, just leave them at the default settings.
You do not need or want Merlin on your AiMesh nodes… of course, this is JMHO
Huh? AiMesh has been officially supported since the Asuswrt-Merlin 384.13 (31-July-2019) firmware.I think @RMerlin should include a Warning on the Aimesh page that Aimesh it not officially supported, and therefore,
The issue more than a few face with AiMesh is just the wonky nature of Asus's implementation of the feature. People using stock Asus firmware face issues trying to get AiMesh to play nice. Some have found that it works to setup AiMesh Node first using an Ethernet connection, then move it to a WiFi connection.384.13 (31-July-2019)
- NEW: AiMesh Router and node support. Note that automatic live
update of Merlin-based nodes is not supported, you will have
to manually update any Merlin-based nodes when a new firmware
is available. Asus-based nodes (which is recommended) will be
able to make use of the automatic live update.
- NEW: ChaCha20-Poly1305 support in Strongswan (themiron)
- UPDATED: RT-AX88U to GPL 384_6210.
- UPDATED: Curl 7.65.3.
- CHANGED: dhcp_staticlist no longer contains hostnames, these
have been moved to dhcp_hostnames for better
compatibility with upstream and closed source
components, also allows more static leases to be
defined before reaching the size limit.
- CHANGED: Replace Nettle with OpenSSL for dnsmasq's DNSSEC
validation, which opens the door to supporting
more ciphers. (themiron)
- FIXED: Firmware Update check button would redirect to Asus
support site if scheduled checks are disabled.
- FIXED: Firefox was showing a no-op Uninstall button on the
AiCloud page
- FIXED: 5 GHz radio showing as disabled on the Sysinfo page for
the RT-AC87U
- FIXED: FTP would be accessible from the WAN even while disabled
if you had DualWAN load balancing enabled, or IPTV
configured.
- FIXED: IGMP Snooper daemon crashing when more than 32 hosts
are present (themiron)
- FIXED: External DDNS IP checker would fail for Chinese users,
as checkip.dyndns.org is blocked - switched to .com TLD.
- FIXED: Devices without a networkmap-defined alias wouldn't fallback
to their hostname on some webui pages like the IPTraffic
and QoS Classification pages.
- FIXED: Remote IP field filtering on Classification page wasn't
working.
- FIXED: Incorrect user permissions displayed on the FTP page.
- FIXED: Performance issues for some users, following the kernel
security fixes in 384.12. (gzenux)
Huh? AiMesh has been officially supported since the Asuswrt-Merlin 384.13 (31-July-2019) firmware.
if Aimesh pairing fails
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!