You are here

Looking for equipment suggestions for Repeater linking project.

11 posts / 0 new
Last post
k9wra
Looking for equipment suggestions for Repeater linking project.


Hello all .   I am working on a repeater linking project that requires both repeaters to be on the "same" network.   My thought was to do the following since I wanted to start learning about the AREDN networking.      Both sites have internet  so I thought about using a tunnel between the 2.    Then from that I would work my way into the rf.  What pieces of equipment would be good to start me out.. I know I would need a tunnel server on a node at one site and the other would be a client..  Would a AIR ROUTER work for this at each location?   That way i could use  wan port from network  1 lan port to my repeater 1 lan port to another node to use for RF later?   IF so  who has experience flashing a air router  as I tried to flash one and i bricked it.  Or if there is a better choice what is it?

Bradley 
kc9gqr for k9wra repeater group. 
K5DLQ
K5DLQ's picture
If you mesh them normally
If you mesh them normally with AREDN, then both repeaters would be on the same "10.x.x.x" network.
Can you provide more details on what you are trying to do?
 
k9wra
 Want to link  2 dr2x Yaesu
 Want to link  2 dr2x Yaesu repeaters that have the LAN board in them..  In order for them to work properly through the internet each repeater needs to have their own static IP address.   We have 2 at 1 site and 1 at another.  So my thought would be since the site that has 2 of them doesn't have 2 static ip addresses I would take a AIr router at that site and make it the TUNNEL server connect both repeaters up to the LAN 1 and Lan 2    then at the remote site use another AIr router and set it up as the tunnel client and point it to the server so all 3 repeaters would be on the same "network" as far as they are concerned.   Then I could use the LAN 4 to add a outside node for future use.          will the Air router work like that?  If so I already bricked one of them trying to get the firmware in it. Is their any tricks ?
 
K5DLQ
K5DLQ's picture
i would suspect that the YSF

i would suspect that the YSF repeater IP would need to be static AND PUBLIC, which, this would not solve your issue.
That being said, it's totally not what AREDN was designed for.

If you wanted the repeaters on the mesh for local comms across the mesh, then, that would be closer to the intent of AREDN.  (in my personal opinion)


EDIT:  Perhaps I'm not fully understanding the use case here.  Apologies.


 

k1ky
k1ky's picture
Looking for equipment suggestions for Repeater linking project.

The AirRouter (either AR or HP) are perfect for this application.  We have linked YSF DR-2X repeaters with the Yaesu native network linking mode over our MESH system, both via RF and Tunnel.  All you need is one single AirRouter on each end, plug it up to your MESH network (or Internet tunnel) and your repeater's ethernet connector. Use ports 1-3 on the AirRouter to connect to your repeater.  you will also want a computer plugged up to the AirRouter with remote access capability to be able to change some configurations of the repeater via the USB programming cable. Works great!  We have also set them up to support WIRES-X nodes, but that is a bit trickier requiring some dedicated ports to be opened and passed to the HRI-200 Controller computer.

k9wra
Ok excellent   I figured I
Ok excellent   I figured I would start with using a tunnel to link them and then hopefully ad  RF node up on the tower to deploy soem RF stuff.    I think i bricked the one I have  is their any special  way to get the firmware in them. I think now they come with 5.6  but when i ran the tool it said  BAD/GOOD    Good idea on the computer also..   I will buy another Air-router but don't want to brick the next one..  The one I have now no matter what firm ware i put in it it keeps rebooting every few sec's     
Kc9gqr
k1ky
k1ky's picture
Ok excellent I figured I
Some of the new UBNT Equipment has firmware that can't be easily downgraded and the AREDN development firmware will need to be loaded directly via TFTP.  5.6 UBNT should be able to be downgraded (if not Signed) to 5.5.11 (XM) of 5.5.10 (XW) be sure to match up the proper board revision. If the unit is constantly rebooting, that may be a bigger problem.  I have put 2 of our units in our "MESH HOSPITAL" for evaluation and resolution to this problem. (I can load firmware via TFTP, but the units still reboot even with fresh loads of UBNT firmware).  We are going to try a serial firmware load, otherwise they are probably going to have to go back to Ubiquiti for replacement as it could be an unresolvable hardware issue.
k9wra
Where would I find the board
Where would I find the board revsion to see if it is xm or xw?       So do not do  web down grade  start off downgrade right from tftp?     
WU2S
WU2S's picture
Board ID

What we need is a board.info file to process this. 

1) The device must be running the AirOS. 
2) Telnet or Putty into the node (default user is ubnt; password ubnt; default ip 192.168.1.20)
3) Run "cat /etc/board.info"
4) Save the resultant file and post it in response to this post.
k9wra
Will do tonight.. Thank you. 
Will do tonight..

Thank you. 
k9wra
got the node up and running
got the node up and running anyone running a tunnel they will let me connect to to see how to work with tunnels before buying another  node?

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer