Just wondering if there is a group of SLCO hams on this board who would be willing to be part of the beta testing of the Ubiquiti Firmware release. (See...http://www.broadband-hamnet.org/documentation/179-ubiquiti-support-now-in-beta-test.html)

I'd be up for being part of the group (=footing the bill for my hardware), but don't have probably all the *NIX skills to go this alone.  

Lance / K7LQH

Per K5KTF:

"If you tie two (or more) rnodes together via the LAN port(s), and you want to be able to mesh all of them as if it was over RF, you need to edit:
/etc/config/olsrd.conf
/etc/config.mesh /olsrd.conf

And down where the Interface section is, by default it just has wl0 and its section.

What I do is right above the wl0, and after #### Interface ### I add:

Interface "eth0.0"
{
}

(those are curly braces)

save both files and reboot.

That tells OLSR to also mesh over the LAN ports.
In 0.4.3 and before, OLSR had a problem handling more than one interface, and would crash horribly and frequently."

Per WX5U:

"I haven't tried it myself, so try this out and see what happens.  Please back here with success/failure."

none of that worked

I think I got a bad router, if so not that big of an issue I have two others that are working, just wish I can get this one working

The answer to your question is really quite complex. There are books written about router configuration. An approach to the question should start by realizing that the wrt54g platform includes routing capability on the LAN. When you use a bullet, which has only one LAN port, the routing needs to be handled with an external router. So think about how you would duplicate the LAN routing of the WRT54G in a router that does not have a radio included.

I can ping the ip address

but i can not reach the router via web 

using http://localnode:8080

or by ip adress

how do I get in to the hsmm node?

How do i reset the node back to default?

WRT54GS v4

Please take a look at the video section under "HSMM-MESH Info."
http://www.broadband-hamnet.org/documentation/182-cisco-7940-with-asterisk-raspberry-pi
Same rules apply to the 7960 as they do to the 7940's

I have a mesh of 3 nodes running at my QTH. I have had no problem seeing my IP camera across the mesh (although there is more to come on that). I am trying to get a phone system to span the mesh. I have 4 Cisco 7960 IP phones which I have switched to SIP (that's a whole 'nother story!!), a RASPBX plugged into Node1 and 1 of the phones plugged into Node 1. I intend to plug another phone into Node3. The problem is in provisioning the phones. They know TFTP, not HTTP. How do I get these phones provisioned and known to RASPBX? Thanks for any help.

Update: IT WORKS and MORE!  

I finally got Teamviewer to work through the Mesh nodes!

No special configuration in BBHN (default 5-node Direct). Teamviewer justs need to have "Incoming Lan Connections" on the General Tab, set to "ALLOW". When your network is  LAN only (with no Internet), Teamviewer will show the IP address of your PC. No portforwarding to configure, no rules, no tunneling. Just some clean up on the leftover PC network configuration (DNS & DHCP) after changing from wifi to LAN.

I disabled my wifi adapters on my test PCs and did an "ipconfig /flushdns", "ipconfig /release" and "ipconfig/renew" to clean up the net configuration on the WIN7 PCs. After that, it worked flawlessly! I think the problem was that Windows (7 & Vista) gets confused when you start changing network configurations. Now I can remote control any PC (whether it's XP, Vista, Win7 or Linux) on the Mesh.

If you add Internet to your Mesh, it will display a 9 digit number or if you are using the online web management, you can assign a name to each PC. You can connect to remote PCs using the 9 digit number, IP address or Name.

The main objective was to be able to control an HF rig at my home from the EOC. I can connect to the PC at home (the radio and PC have to be on) with a connection to a Mesh node (Internet for normal use). Once connected to the remote PC I can bring up HRD (v.5.X, the last free version), activate the VOIP on both PCs (I keep the mic muted in VOIP on the PC I'm working from. If you don't, it will key the transmitter VOX). With a headset/boom mic, I transmit & receive, change bands, frequencies and do anything I would do with HRD, sitting in my shack.

Added benefits of Teamviewer 9 besides being free: It has built in Chat, VOIP, Video, file sharing and of course remote control! One free application that does a whole lot.

Don't you have to enable the OLSRd code to use the eth0 as another path to route the nodes if they cannot be seen by the wireless default method? How is that done?

That is MY intent for these, to use them ONLY for this project where the router is up a pole and there is one of these at each end.  Hopefully i didn't mislead anyone as I am new to POE.

And we are experimenters so it is assumed that we look at these things before we jump in.

Kirk - N6SXR

Be aware this is NOT "Power over Ethernet" or PoE.   There is a standard for Power over Ethernet that involves voltage choices, switching, safety features, etc. when a device connects and tries to turn on. 

Plugging anything but the pigtail adapter on the "unpowered" end of a cable with the pigtail adapter might cause damage to the device.  It also won't power a standard Power over Ethernet device.

I believe these adapters are simply connectors and wires used to run a DC current down the unused wires on a 100 Base TX Cat5 cable.   When you use this on one end of an ethernet cable, the cable is no longer standard Ethernet nor PoE ethernet.  

Gigabit ethernet  uses all the wires in a Cat5 Ethernet cable.   If someone plugs a device with Gigabit Ethernet, such as a laptop, into your "pseudo PoE" Ethernet cable without the pigtail adapter on the other end, it might damage the laptop. Or switch, router, etc."

Standard PoE is also 48 V.  

You're probably OK as long as you have the pigtail adapter on both ends of the Ethernet and nobody ever accidentally or deliberately removes the pigtail on the "downstream" end and plugs directly into the Ethernet cable.  Just be aware that if you use these adapters, you have what looks like a standard Ethernet plug on the other end of the cable, but it isn't. 

It looks like the WAP54G V3.1 only has 8/2 MB memory, which isn't enough. BBHN needs 16/4.

I don't have an authoritative source for this info, just a little Googling. 

Even if it DOES have 16/4, it may not run BBHN. 

The OpenWRT and DDWRT web sites are good sources for info on hardware and how to reflash firmware on other routers.  Sometimes you can load BBHN once you've put a different type of open source firmware on the router.  However, BBHN will NOT load on a router that doesn't have 16/4 memory.

Sometimes Windows will just never get the configuration right, no matter what commands you type.

Try unplugging and replugging the ethernet connector.  Then shutdown (not just reboot) and power the PC back on.

Google is working on a project (Project LOON) that uses balloons to provide wi-Fi access to remote communities.  It would appear that this would be useful in the period after a natural disaster when normal telecommunications are down.

Suggest that communications be opened with Google to convince them of the need to make their system a part of disaster responses.  In addition consideration should be given to how we can make use of this resource

Folks:

There will be a meeting of the Huntsville Broadband Hamnet Special Interest Group on the evening of Thursday, January 30, 2014 in the Huntsville Madison County Library on Saint Clair Ave,. Huntsville AL.

Check here or hsv_bbhn on googlegroups.com closer to the meeting date for more details.

If you would like to join hsv_bbhn (at) googlegroups (dot) com please contact me kv4pc (at) qsl (dot) net and I will send you an invite.

73;

Bob KV4PC