You are here

Local mesh

6 posts / 0 new
Last post
km4eug
Local mesh

setting up 2 m5 bullets to Link my control console to my transmitters and their respective computers wirelessly 

i have the AREDN software installed, 
SSID set the same on both. 
Node names are different 
mesh mode
channel 179
Milage  set  
lan 5 host direct 

what are are the other settings I need to set for the two to communicate with each other and pallor 
devices in the 192.168.1.200-255 range to communicate 

this is not on any other network nor is internet connected. 
Down the road will add one more M5 as a hop for extended links 


Looking for help with AREDN mesh set up.  Stand alone for linking remote rig control to the transmitter across the property.  
I have two M5 bullets talking to each other with AREDN firmware 
I am able to get into set up of the 2nd with the first one plugged into computer.  

Set up consist of 

Control point. Two remote rigs 192.168.1.225 192.168.1.227
And two lap tops 192.168.1.203 192.168.1.204

The transmitter location 
Two remote rigs 192.168.1.226 192.168.1.228
And two thinkcenter computers  192.168.1.201 192.168.1.202

System works flawlessly with cat 6 between the transmitters and the controls.   

Terry Baker 
Km4Eug 
731-394-2028

AE6XE
AE6XE's picture
Terry,  end to end across
Terry,  end to end across these 2 bullets running AREDN firmware, it does not act as if a straight cat5 cable, rather think of the mesh nodes as a router.   The rig and other devices on both ends will have to have coordinated IP addresses with the mesh nodes, so they know how to route across the network (which could be 100 mesh nodes and many hops away in the extreme).  

How does your rig, laptop, etc. get an IP address today?  If this is a static address that you manually typed in, then it would be straight forward to change each device to DHCP mode instead.  Then the IP address is provided by the Bullets on each end (and the addresses 'reserved' on the Bullet if needed).  

Joe AE6XE
km4eug
Joe 

Joe 

All devices are fixed ip to properly interact with each other 
so is there a bridge mode with in the AREDN firmware ? 

I have tried changing the ip config of the M5 to the ip scheme of the other hardware.   
This did not work nor could I access the m5 

can i I load the ubiquiti software back onto the m5 ?   

The m5 do not respond to localnode:8080 or any of the other variations I've read to use. 

I use the gateway ip on the computer to find the scheme and use angry ip scanner to find the ip of the m5. 
And only one at a time. 

I have seen seen this done with linksys blue routers to connect logging computers for field day, sand I have heard of them back hauling, Wanted to stay in ham band to minimize interference issues 


Thank you for your response 

Terry KM4EUG 

Image Attachments: 
AE6XE
AE6XE's picture
AirOS in bridge mode
AirOS in bridge mode

Terry,  It is an option to directly tftp upload AirOS back to these devices.  Configure one as an AP, the other as a Client, in bridge mode to have the desired outcome. 

AREDN firmware doesn't have a bridge like this.  The intent was to be able to bring up a node anywhere and magically become part of a greater mesh network.  Thus, the mesh nodes expect to give out the IP addresses to laptops and other devices automatically to coordinate everything.

Joe AE6XE   
km4eug
Tftp
Having trouble with tftp. Needing insight.  Can any one help
K5DLQ
K5DLQ's picture
Quick TFTP instructions

disconnect power
hold RESET button
connect power (while holding)
KEEP holding for approx 30 secs until the "signal" leds begin flashing in an alternating pattern like 1 & 3, 2 & 4, 1 & 3, 2 & 4, 1 & 3, 2 & 4, etc
set your computer network interface to static IP:  192.168.1.2  (mask 255.255.255.0)
disable any wifi adapters on your computer
start your tftp client (or commandline on OSX or Linux) (ex.    tftp 192.168.1.20 on OSX)
put your tftp client into BINARY upload mode   (ex.  type:  'bin' on OSX)
copy the name of the (un-renamed) firmware file to your clipboard.
in tftp, send/PUT the file
after it's loaded, the LEDS on the node will begin to cycle in a "cylon" pattern (ie.  1,2,3,4,3,2,1,2,3,4,3, etc)
after the firmware is processed, the node will reboot
set your computer network back to DHCP
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer