Hello All,

I have a mesh node up now - but have some basic networking questions (it is a Ubiquiti Bullet M5-Ti) - 

*  WAN I/F - Is it best to leave that as DHCP (I do have a local network DHCP server running) or should I set that to be static and something that routes OK locally?

*  LAN I/F - Should I leave that as is - or do I need to make sure that can route on my local net?  I have made sure the LAN DHCP server works and have connected to the Bullet's Web GUI through the LAN using one of the DHCP'ed addresses - but what is a little unclear is how a client 'meshes in' and uses the LAN address.

*  Wireless I/F - That is pretty clear - and I have used what the bootcode suggests.

So, for the node - how does the routing work?  Does a client connect from the Wireless I/F - and then traffic for the Internet goes to/from the WAN I/F?  Then what is the purpose of the LAN I/F - is that just for local physical access (I assume) - I am just wondering how someone makes a client connection or maybe that is just the wrong way to look at this.

I am trying to figure out if I need to set up any routes or firewall rules on my main internet router to make all of this work.

I have looked at a lot of the things posted here - but I haven't seen anything that says if local firewall or routing tables need to be changed to make this useful.  I will set up a client station soon - maybe all of this gets obviated when you do that.

73's,
John
AJ6BC 

FYI, Channel 11 is part 15 only (not shared with part 97) and the use of amplifiers is illegal there.

(Ch1 thru 6 are shared, as well as channels less than 1/the negative channels)

This boils the rules down nicely:  http://www.afar.net/tutorials/fcc-rules

By chance, did you test it and backup your device before upgrading with my U-Boot Test tool?

http://bit.ly/u-boot-test

or

http://tinyurl.com/u-boot-test

Hello Again,

I have a Bullet M5-Ti online - at least it is broadcasting the SSID.

I want to do a better mounting job and I will get a better Omnidirectional antenna soon.

Bullet gets a little warm - I noticed Streakwave is out of them - at least the US version - does anyone

know if they are addressing the heat issue?  I have seen a lot of complaints about these overheating.
I may come up with a way for a short run to the antenna to keep the unit running cooler.

73's,
John
AJ6BC 

I'm the proud owner of two M2 Bullet bricks thanks to the XM.v.5.6.x firmware incompatibility. The OpenWRT site seems to indicate this can be prevented by "downgrading" a newer XM.v.5.6.x unit to an older Ubiquiti firmware such as XM.v.5.5.x before attempting to load the Hamnet firmware. Before investing further in this project, I'd like to hear from someone who has successfully done this.

Is there anyone out there who has successfully "unbricked" one of these newer units?

Is there anyone out there who has successfully flashed bbhn-3.1.x into a M2 Bullet of this latest generation?

73,

Chuck - AI4WU

Hello All,

I was thinking about getting a Ubiquiti Bullet-M - but don't know if that is still a good idea or not after seeing the announcement.

So, for my area - what is the best choice?  I liked the Bullet since I could try it with the omni-directional antenna - but I don't know if I will 'brick' the unit or not.

I will peruse the rest of the forum.

73's,
John
AJ6BC 

We're looking for a way to include IP address / Node Name information in a Hosts File style in order to show node names more quickly (i.e. before a successful connection has been made to the node).

There is a hosts file.  /etc/hosts  but it says not to edit it as it is dynamically created.

It says to use /etc/hosts.user, however, when we create that file it doesn't seem to be included.

We have 15 or so active nodes here, and growing, which include at least a couple of mobile nodes.  It would be nice to allow the nodes to recognize known nodes before connecting and passing all of the info needed to display the names.

Just wondering what it is that makes version 5 and up incompatible with bbhn? Is it a lack of memory and if so has anyone tried any sort of physical mods to try to remedy this? I'm curious because I have 3 of them and want to see what I can do with them.

Thanks!

Shawn

(KE6YCO)

I have a couple of mesh nodes that I keep running all the time at home.  I have a few more that I get out once a year to help with communications at an event in a remote location.  A couple of these others run in mesh AP mode to make it easier to connect to the network from tablets and phones.  

This week I connected and powered up all these nodes to prepare for the event next week.  The mesh nodes came up and connected just fine.  But neither of my mesh AP units appear to be working correctly.  If I do a wifi scan from a non-mesh device (like a Windows laptop) sometimes I don't even see the mesh AP.  When I do see it, I'm unable to connect to it.

I don't think it's a hardware fault, because it's unlikely that both of them would fail at the same time.  And aside from the AP connectivity issue, they appear to be running fine.  I can connect to them at 172.27.0.2 and everything looks normal.  

My next thought was that I'd never used them in mesh AP mode since upgrading to BBHN 3.1.0.  So I downgraded one of them to 3.0.0 and then to 1.0.0, but I still have the same problem.

Then I thought maybe it was an issue with Windows 10, since that what was running on the laptop I was trying to connect with and I'd never used Windows 10 before to connect to a mesh AP.  But I tried it with an Android phone and with a Linux PC and I get the same problem; either the mesh AP can't be seen or I can see it but can't connect to it.

This makes me think I've just forgotten something about how this mode works and I'm not connecting things properly.  I'm connecting an Ethernet cable between one of the LAN ports on the mesh AP and one of the LAN ports on a regular mesh node.  That's the correct connectivity, isn't it?  By the way, these are all WRT54G's.

Any suggestions for anything else I could check or try?

Thanks,

N7EGO