Check my "Patching Beta" post in the beta forum.

I have begun re-flashing nodes to 1.0.0.  So far so good using the download via the setup administration route.  The problem comes in port forwarding for devices and services.  My first example is in making an IP camera available.

In the last version all was well with the following in Port Forwarding:

Interface: WiFi  

Type: TCP

Lan IP: 172.27.0.5

LAN Port: 80

The link was then advertised and clickable across the MESH.

Now the same screen in 1.0.0 does not allow anything but WAN for an Interface.  I understand the LAN IP's have now changed to 10.67.184.xx. The camera is in the LAN IP with 10.67.184.93 and has been reserved.

Nothing seems to work.

Suggestions?

Thanks

Dave KM2O

Connecting to a mesh node is almost exactly the same as connecting to a stock WRT54G router or normal wired ethernet network. 

The magic of the mesh is mostly hidden behind the DHCP server, the DNS server, and the routing function programmed into the mesh node.   That's also true for a "normal" home router connection if you think about it.

The problem with Windows is that when you reconfigure the router, Windows tends to be slow about redoing the network configuration in terms of DNS, IP addresses, DHCP, ethernet up/down status, etc.  Even Linux PCs may end up confused.

This can happen even with a normal home router if you change something in the router configuration or swap routers.

Most of the time, the PC/Windows/Linux PC will eventually figure it out eventually.  If it doesn't, you have to tinker.  There are various shortcuts, but the safest bet is to reboot the PC after you change any configuration on the router is to reboot the PC.  If your PC won't connect to a mesh node after reconfiguring something, try a reboot of the PC before spending too much time on the shortcuts. 

Now that the endian problem has been dealt with by removing the secure plugin, many wireless platforms could be configured to run BBHN. I understand that it is "not an easy task" to configure a differnent device, and that the current priorities are to support the listed LinkSys routers.

If it is not too much trouble, could someone post a list of the steps people would need to take to configure a random Linux distro to make a BBHN node? Eventually maybe a cookbook recipe that anyone could use, but for now, just a list that a knowlegable, experienced computer/network person could use, including a specification of what the node should be able to do.

I appologize if this already exists and I missed it in my search.

73 de KG1L

 Sorry, I don't know how to dele this.  Moved my comment to more appropriate forum.

Thanks for the response, I believe this clarifies my concern.

If I may summarize what I think I hear:

1) while I am not directly configuring a DNS server, DNS services are being created by default in the mesh.  I need to make sure my clients attached to the mesh are properly configured to support the mesh's default DNS behavior

2) The address space is 10.0.0.0/8 providing room for the 5 local nodes to be directly attached to the mesh without address transaltion

3) HSSM mesh is using a hashing algorithm in the 10.0.0.0 space which minimizes the probability of collisions when two previously existing meshes are bridged.  

Also, I do need to be careful of the local names assigned to edge devices such as laptops.

That clarifies my concerns.

Thanks for the help.

I will reimage my systems tonight and see if anything smokes! :-)

73,

AB1PH

Don Rolph

Install Asterisk on a Raspberry Pi for use on a Broadband-Hamnet^TM network - Paul KF5JIM

I have ordered a Raspberry PI Mod B card with wall wart.  I have downloaded AsteriskNOW.  I read that Linux Debian is the preferred OS so thought I'd order an SD card preloaded.  I am assuming (ugh!) both the OS and AsteriskNOW should both be on that SD card.  What would be the recommended minimum size I should get (8 GB, 16 GB or 32 GB) assuming I might want to load additional experimental program(s) in the future?

I was super-impressed with the demos and information at this past weekend's Austin Summerfest 2013.  Thanks to all the presenters for your time and effort.  73 de Austin K5YKG near Houston.

First, in our initial configuration, we are not attaching to the internet.  Therefore there is no DNS structure in place.  So it is unclear how we must get "DNS working".  Thoughts?

5 host direct mode means that the LAN subnet on the node has enough space for 5 addresses and they are directly accessible from the rest of the mesh.

I'm not sure exactly what you are asking, and direct mode should actually remove complexity from the mesh.  Simply setting up two or three mesh nodes with other computers or devices connected to each node LAN should help you see how it works.

This proof-of-concept success with a USB wifi nic suggests that a BeagleBone-Black may be paired with a Broadband-Hamnet router:

BeagleBone Black: USB Wi-Fi... It Works!

Has anyone tried?

That is correct. "Upload" the bbhn-1.0.0-brcm.trx file from your PC to the router.

If the mesh node has an internet connection, you can also install the bbhn-1.0.0-brcm.trx file directly under the download firmware section.  Hit "refresh" and then the bbhn-1.0.0-brcm.trx file will be in the select firmware list.  "Download" will then install the .trx file.

I believe there is a theoretical risk of a name or IP address collision once you connect two previously independent mesh networks.  The wish list on the change log mentions "duplicate address/name detection." 

We use the 10.x.x.x address range, so there are 16 million IP addresses.  I believe the code allocates the IP addresses based on the MAC address of the router, so that makes collision less likely.

To avoid name collisions,  you should be sure that node names are unique.  For instance, name one node "AB1PH-1" and another one "AB1PH-2".   Bad things might happen if you have two with the same name.   

I suspect that you need to be careful about the name of your laptop as well.   For instance, if I give my laptop a hostname of "lap," and someone else names their laptop "lap" as well, there might be a name collision as well if we both connect.  They might both try to become "lap.local.mesh".  

If you have a laptop or other computer  you're going to connect to a mesh node from time to time, you should probably give the computer a host name of "AB1PH-lap1" or something similar.