I can't seem to find what the differences are in the Bullet M2 vs the Bullet 2 other than the Bullet M2 is Airmax Compatible and supports 802.11 b g and n mode.

The bullet M2 has the Atheros Mips 24kc @400mhz with 32Mb of Sdram and 8Mb of flash memory.

The bullet 2 has Atheros MIPS 4KC, @180MHz with only 16MB SDRAM, 4MB Flash.

So the question is will the firmware for the M2 run on the 2 as well? Or is it to large of a program

and won't fit into the 4mb of flash?

73 de KF7PSM (mesh in Las Vegas, NV)

Thanks, Conrad.  That cleared up a bunch of questions for me.  I like my Pi as well, it has brought my interest level in both radio and computers.  Fortunately I have a fellow ham living 5 doors away and both or out mesh-nets are test beds for each other.  We are hoping to set up a county wide mesh-net but it'll be a difficult task since the county is in a mountainous region of Western North Carolina.

73

Dick

1)You are likely getting a response from the first dns server saying "NXDOMAIN" (no such domain)  Windows does NOT ask the 2nd dns server for an address after this (At least on my test XP box)

Try switching the order of the DNS servers.

2nd) You also have to deal with what is known as the "search root" (local.mesh)  this may need to be added to  the Advanced>DNS list (depending how your computer is setup) try using <node>.local.mesh in your connections instead of just <node> to see if t his solves your issue.  example: http://localnode.local.mesh:8080

Thanks for the info.

Regarding the DNS, i have already done as you thought, routes have been added to the 10.xxx network with the route command on the win7 pc and the alternate DNS has already been set to the local node IP address on the LAN so i'm not sure where to go next with that one.

Ok on HSMM-PI, probably incompatability then, i will try find out some info and report back on that.

Rob

Hello Dick,

You don't usually need a special application written to use an IP cam over the Mesh.

Most IP cameras I have run across have a WEB interface on them that you can just let users access to view the photos.

An example would be an IP camera, obtaining a DHCP lease from your mesh node in direct mode (easiest setup)  would be directly accessible at its address over the mesh. You could choose to advertise the web interface on the services page of the mesh node so everyone knows the camera exists but not strictly required.

Pi's are great devices when used inside of the capabilities.  Rendering video is a weak spot for them as is viewing dynamic content. I enjoy mine they make great terminals for my needs but they certainly have limits.

I have a webcam connected to a Raspberry Pi which is connected to one of my mesh nodes.  It currently is streaming at 2 frames per second.  I'd like to explore the use of an IP Camera rather than a usb cam.  Has an application been written for Mesh-Net to do so,?

If you have any suggestions  to point me in the right direction, I'd appreciate it.

Thanks

Dick. W4RSS

Item 1)

If you are setup how I think you are the Mesh node likely has an IP address, DHCP is being provided by your main router and is telling all your local systems that it is the DNS server and Default Router

The client PC on your LAN network would need to have static routes put in to go to the mesh node for the 10.x network AND would need to have the LAN Mesh node set as its DNS server manually. Otherwise the computer on your LAN doesn't know that the Ubiquiti node is is providing you access to the mesh network.

Item 2)

HSMM-PI project to my knowledge is NOT connected to the BBHN project. I would suggest contacting the makers of that software for their input on the configurations as it is really out of scope for this group.

The Ubiquiti build of BBHN is compatible protocol wise with the Linksys 1.0.0 build. I can't  guarantee the same about the HSMM-PI project.

Hi,

I'm pretty new to this mesh stuff and finally got to a sticking point hence some questions to the experts...

Here we go:

#1

I'm testing with 2 nodes(Ubuquiti M2 HP) which are talking to each other fine.

One is stand alone into an xp laptop for testing the links.

The other is connected with NAT to my home LAN on 192.168.1.x.

The stand alone unit can resolve the hostname of the other node but not vice versa, the DNS gets lost across the NAT somehow... so how do i fix this?

On the LAN with a win7 pc i have setup the route and DNS as the LAN IP of the node but it does not resolve any host names. I can get to both nodes with the IP addresses but not as nice!!

#2

I've installed HSMM-PI on an MK808 mini pc with picuntu OS, the system boots up fine and i have configured it for the correct SSID BroadbandHamnet-v1, give it IP and Name etc.

On the MK808 pc i can 'see' the other two nodes and access them but  the mk808 node is not seen by the ubuquiti nodes.

I looked in OLSR and is it reporting that the mk808 node is not 'SYM' to the others.

I looked in the source code to see what SYM means:

* If the sender interface (NB: not originator) of this message
* is not in the symmetric 1-hop neighborhood of this node, the
* message MUST be discarded.

Is there something i have missed or is the current Ubuquiti HSMM setup not compatable with HSMM-PI?

Would not having a LAN interface on the HSMM-PI node stop the it from working? (currently is is set to a false interface name as it only has WiFi network port)

Apologies for any obvious mistakes!

Any ideas on either problem is appreciated.

Thanks

Rob

M0DTS

I am attempting to setup a VoIP over mesh system.

2 Polycom 501 phones

2 WRT54G V2 & V3

Latest mesh firware - bbhn-1.0.0-brcm.trx

Latest Asterisk downloaded and installed on RasPi.

Followed Jim's video for Asterisk/Pi/Phone setup.

Mesh router displays host name but no blue Service Link on the Mesh status page.

Phone displays " url call is disabled " and no dial tone.

I can ping phone from RasPi using IP address but not by name. DNS???

Any suggestions are most appreciated.

Thank You,

Fred