I want to create a RF link between two AREDN local mesh networks on different channels.
I want to eliminate the Internet tunnel currently used.
I have two 31dBi dishes on opposite side of a tall tower with a clear path to each local mesh.
The transceiver on each dish is set to the channel of the connecting local mesh (see diagram).
Can I simply connect the Ethernet cable of each dish transceiver back-to-back through a switch,
or do I need an AREDN device between the dishes (hAP ac Lite or hAP ac3)?
Do I need a supernode to bridge these meshes?
I have read a lot of old forum articles and docs.
I would like your best recommendation using the latest firmware and moving forward with Babel routing.
I want to eliminate the Internet tunnel currently used.
I have two 31dBi dishes on opposite side of a tall tower with a clear path to each local mesh.
The transceiver on each dish is set to the channel of the connecting local mesh (see diagram).
Can I simply connect the Ethernet cable of each dish transceiver back-to-back through a switch,
or do I need an AREDN device between the dishes (hAP ac Lite or hAP ac3)?
Do I need a supernode to bridge these meshes?
I have read a lot of old forum articles and docs.
I would like your best recommendation using the latest firmware and moving forward with Babel routing.
File Attachment:
73
Orv W6BI
N0YWB:
Yes.
Simply connect the LAN ports of the two POEs with an ethernet patch cable.
No switch nor AREDN device is needed.
The two AREDN nodes will be DtD connected.
"Do I need a supernode to bridge these meshes?"
No.
You do not need any AREDN device to bridge the AREDN networks.
"I have read a lot of old forum articles and docs."
Please do not read or heed old articles no matter the source.
The current documentation
(and, maybe, recent posts on this forum)
is your best source.
https://docs.arednmesh.org/en/latest/
73, Chuck
There will be a weatherproof junction box on the tower roof, containing an SLA backup battery, PoE boost converter, and a hAP ac Lite hub.
I have this set-up per the attachment in my first message (the PoE injectors are not shown). The dish antennas currently have RM5-Ti transceivers, and AREDN v3.22.12.0 (14Dec2025) seems to be the last available firmware that runs on these. I have an RM5 (xw) and R5ac-Lite arriving next week to run current software. The dish Ethernet are plugged into LAN ports on a hAP ac Lite running current v3.25.5.1 firmware, with the 5GHz and 2GHz radios off, and a laptop PC also connected to the third LAN port.
With the laptop Ethernet connected to a LAN port on the hAP acLite between the dish antennas, The IP address of the ch 176 dish transceiver (probably the first device to connect) is DHCP assigned to the laptop. I can view the transceiver status (and mesh status shows the world AREDN network because a device with tunnel access is on the ch 176 mesh). I cannot see the ch 165 dish transceiver or its local mesh. A WiFi scan shows the ch165 Foreign A-hoc Network.
With the laptop Ethernet connected to a node on the ch 165 mesh, the local mesh or babel mesh view only shows other ch 165 mesh devices.
Similarly, with the laptop Ethernet connected to a node on the ch 176 mesh, the local mesh or babel mesh view only shows other ch 176 mesh devices.
Is there a way to configure the Hap AC Lite hub connecting the dishes to allow a view showing devices on both meshes - like the mesh view of the old GUI?
Or is up to the Supernode administrators at the Cedar Rapids ch165 mesh, KD0CGN; and Muscatine ch176 mesh, W0PCD ?
"and a hAP ac Lite hub. "
This was not in the original specification.
-----
"AREDN v3.22.12.0 (14Dec2025) seems to be the last available firmware that runs on these."
"14Dec2025" is in the future.
I think AREDN v3.25.5.1 is the last (stable) firmware that runs on the Rocket 5ac-lite.
See image.
-----
"With the laptop Ethernet connected to a node on the ch 165 mesh"
There was no mention of channel 165 in the original specification.
-----
Due to the changes of specification I wish to rescind my previous recommendations in this thread.
-----
I am concerned about using a sector antenna as a point in a PtP link.
The AM-5G19-120 has an electrical downtilt.
If mounted vertically (no physical up-tilt) and at 29 miles distance,
that antenna would best illuminate the ground under the other end from an elevation of 5347 feet.
Any height above ground at the other end would have less RF signal.
Any height of the AM-5G19-120 below 5347 feet
("atop of an old 221 foot AT&T Long Lines tower")
would best illuminate the ground at less than 29 miles.
73, Chuck
SLA? For real? Instead get a 100ah LifePO that is cold weather tolerant (has auto cold weather charging cutoff), they are selling now for $200 or less. In the box put the battery, the other misc stuff and a 5 or 10a battery charger. Using SLA is guaranteed failure as you will have to replace it every two to three years.
Ed
Edit ... several lingering questions.
Do you actually need LAN access on site? The only reason to use a hAP is to get a LAN port or LAN wifi. If you manage from a short distance using another AREDN device to connect then you don't need LAN.
It's way better to have your control box at ground level so you can test things, program things, and troubleshoot without having to climb. Unless the only power is at platform level ... just saying. The only drawback is the cost and labor to run cable 200' vertical. It's way different to have your hands directly on the cable to each device compared to having to go thru a network and a switch.
If you do need LAN instead of a hAP ac lite, get instead a hAP ac2 or ac3 as you can configure the ports so you can have two ports on VLAN1 and not need another switch.