Does beg the question and raise the hopes!

Eager to hear if this thing will support hsmm or if it'll need it's own version. 

http://www.itbusiness.ca/news/linksys-launches-new-router-with-open-source-code/47992

Hello, 

Just want to let everyone know I finally got my node up in Randallstown (K3AKE-1)!

I'll be doing a presentation at the Hamilton Amateur Radio Club's monthly meeting on Wednesday, April 16, 7 pm, at Westdale High School in the Cafeteria. Anyone interested is invited to drop in and see what I've been up to all winter. I'll just be presenting the basic what and how, and demoing a few nodes. If you can make it, feel free to bring a node of your own. I don't have any Ubiquiti nodes yet, so it would be great to see one there.

Westdale High School is at the corner of Longwood drive and Main St. W. Parking is off of Longwood, enter the metal door located in the corner.

Feel free to email any questions - <mycall>@gmail.com

Ron Pereira, VE3RTJ

Hi,

I have switch my local nodes from IP 10/8 to 44.165.xx from AMPRNET and it is look better solution for us because our local nodes have direct access to wide Amprnet network and any host from AMPRNET have access to our Mesh BBHN nodes. I must change rules firewall on our one WRT54 which is gateway to Amprnet to pass 44/8 traffic to local nodes. We can use Amprent IP addresses on Mesh Nodes and setup local AmprNet gateway by register on http://portal.ampr.org.

73 Waldek sp2ong 

right

XM.v5.5.3# cat /etc/board.info
board.sysid=0xe2d5
board.cpurevision=0x00000101
board.name=Bullet M5 Titanium
board.shortname=B5T
board.subtype=
board.netmodes=7
board.hwaddr=DC9FDB328B0B
board.reboot=30
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=9192
board.phy.2.maxmtu=2024
radio.1.name=
radio.1.shortname=
radio.1.bus=pci
radio.1.subsystemid=0xe2d5
radio.1.subvendorid=0x0777
radio.1.txpower.max=25
radio.1.txpower.offset=6
radio.1.antennas=1
radio.1.def_antenna=4
radio.1.antenna.1.id=4
radio.1.antenna.1.name=Main
radio.1.antenna.1.gain=0

A bit more technical information:

Prior to and including version 0.4.3 we ran under hsmm-mesh for the SSID.

In version 1.0.0 we made a change at a low level (not usually visible to users) that was needed to enable device support across multiple vendors.  At that time we changed the SSID to BroadbandHamnet-V1 to show the networks are incompatible.

Going forward:

Anytime we make a change that will result in incompatibility the -V1 portion will change, next version is expected to be -V2 and so on and so forth.  This allows users an easy way to determine if their device can speak to the network they can see.

Anyone running under non-default SSID's is encouraged to use this format as well. An example would be if those of us in San Diego (we have a group called the San Diego Working Group or  SDWG)  created our mesh as SDWG  we should use SDWG-V1, when the next change that comes out occurs (which will happen from time to time)  it should be SDWG-V2 and so on.

A forward looking note:

An SSID jump -V2 is expected to come out in the near future. With the addition of Ubiquiti hardware having models with limited beamwidth patch antenna setups ticket BBHN->ticket:28  comes into play in creating a device to device linking, and BBHN->ticket:29 come in to play for new radios in 5ghz range which to allow RF changes. In addition re-adding the olsrd 'secure' (message authentication) module also requires a jump in SSID version number which is planned for the same time.

In regards to protecting the computer:

Some method certainly needs to be in place and don't think that the protection can be stressed enough (firewall,  running in NAT mode, etc),  While this is a Ham network, it is still a computer network, and all it takes is one infected laptop on the mesh to infect any unprotected system with a virus or other issues. One should really treat, in my opinion, the mesh as unsafe as the internet.  When you are in "Direct" mode you don't have the normal protection you have at home of having the router 'protect' your computer from direct attack .

BBHN 1.0 does not talk to HSMM-MESH and vice versa. 

Go ahead and upgrade everyone to BBHN.  The new version is pretty well debugged at this time.

If I understand your concern about making services and files, just change the "LAN" setting on the basic setup page to "NAT" mode. 

You really shouldn't have your individual computer "wide open" to whatever LAN you're hooked to these days anyway, even if you're on a "trusted" network.  There are just too many poorly designed internet devices, Internet TV's, insecure home routers, friends with bot infected laptops, insecure smart phones, tablets, thermostats, etc.  Plus too many professional criminals wanting to take control of your PC for nefarious purposes.  You need a good firewall running on your PC, plus configuration to not share files willy-nilly. Plus, if you ever use a wifi hotspot, or a friend's wifi, something there may be infected.

However, even if your PC is "secure," if you're not going to offer any services or files to the mesh, setting your mesh node to NAT mode may not be a bad idea.  Just be SURE you remember your node is "crippled" and you know how to re-enable direct mode before you loan it out, or decide to do something on it, like use VOIP. 

(I'm not sure VOIP needs an "open" connection, but lots of apps do need to be routable.)

A few in my area are attempting to establish a MESH.  Some have experimented for a while, others like me have just gotten some equipment and are looking to start. 

I understand that there are significant changes to the new firmware.  Do the others who have nodes ready to deploy have to upgrade their firmware to be compatible?  Is the new SSID Broadband-Hamnet or does the older HSMM-MESH still work?  The new firmware allows, by default, access to services and files on computers and servers on the net.  Will changing the setting to the older setting affect others on the net or the node's compatibility with the net?  I am very risk averse when dealing with network security and want to connect my laptop without having extra concerns.

Thanks to any and all who can provide help.

That's an easy fix.

Your 169.x.x.x address simply means that your computer cannot properly get an IP address from the routers DHCP server. This holds true for Access Point mode because in AP mode, DHCP is disabled. In AP mode, you have to plug that Mesh AP router into a router in Mesh mode.

With the "non-fuctional" AP node plugged into your computer, set the Ethernet static IP address on your mac to 172.27.0.5 with a netmask of 255.255.255.0. Once you that, simply point your browser to 172.27.0.2:8080 (note the 2 instead of 1).

From the Help file located on a mesh node and a quick search for "Access Point" yeilds:
http://www.broadband-hamnet.org/section-blog/36-network-faqs/94-i-changed-my-unit-to-mesh-ap-and-i-cant-get-back-in.html

Mesh Access Point considerations

When a device is configured in Mesh Access Point mode it is essentially 'transparent'. You are going through the device to reach a mesh node, and there is no need to get to the device unless you wish to change its configuration. When the time comes to reconfigure a device in this mode be aware that it is not running its own DHCP server because that is the job of the mesh node it is connected to. You will need some other way to configure your computer's network interface. There are two ways to do this:

• Manual configuration
  Connect only your computer to the LAN port. Set your IP address to 172.27.0.100 and your netmask to 255.255.255.0. No other settings are needed.
• Automatic configuration
  You will need another mesh node that is using NAT mode on its LAN, and using the default LAN IP address of 172.27.0.1. Both of these are required, otherwise this method will not work. Connect both your computer and the LAN of the Mesh Access Point to the LAN of the mesh node.

In this mode the default IP address on the LAN port is 172.27.0.2. After one of the above steps you should be able to send your browser to http://172.27.0.2:8080/. If you used automatic configuration you should also be able to go to http://localap:8080/. Like the name "localnode", an automatically generated name exists called "localap" which is set to the localnode address plus one, but only when the node LAN mode is set to NAT. If you changed the default IP address of a Mesh Access Point you will have to modify these instructions accordingly.

Glad to hear that you got your node on the air. I will aim my node north and with any luck one of the 4 nodes in the Sunnyvale/Cupertino area will try aiming south and we can link nodes.

Now if only we could get some more nodes on the air between here and there.

I have a HSMM-PI VPN set up and I am connected to Austrailia ZL1FLY and I am looking for anybody with a spare PI that is interested in setting up a gateway client to join in. I can send instructions on how to set up the client. I can only take 7 more on my gateway server.  This is a good way to connect mesh networks together that are not able to be connected.   

I can also help anybody set up a server. 

W1BAW