If the wifi connection is not encrypted, you could use another WRT-54G with BBHN and put it into the "wireless client" mode.  It will then take a wifi signal and then put out a wired ethernet connection.  Plug the mesh node into the wireless client router.

I'm not sure whether a BBHN router will connect to an encrypted wifi network if it's running in wireless client mode.  Does anyone know?

If a BBHN router won't hook to an encrypted wifi, you could put DD-WRT on the second WRT-54G, and I'm pretty sure DD-WRT will do wireless client function on an encrypted wifi network.

Then that would be the issue. Port 1978 is not open to the WAN on the node; ergo, no connection.

You could very well be trying to access OLSR over the WAN. Plugging your computer into the LAN on the node and go to http://localnode:1978/. This has happened to me when you have the node plugged into your home network and you are trying to access it over your home router.  If going through the WAN, you might also have to type in the router-assigned ip address (eg. http://192.168.1.74:1978/).

When I click the OLSR status page from my node, I get redirected to port :1978 and the page is not found. I just get the browser page showing not found.

Any thoughts?

I'm on v1.0.0 of the firmware

I have look in source of firmware and I have see that we use apache package. It maybe better replace apache by NGINX

"Nginx is a high-performance http-server with other functions as well. It is a perfect candidate to run on OpenWRT due to the performance and memory handling."

http://wiki.openwrt.org/doc/howto/http.nginx

or other small http server which is used in openwrt gargoyle distribution:

"httpd_gargoyle -    A small HTTP server for use in Gargoyle,  An open-source web interface for OpenWrt
  Created By Eric Bishop http://www.gargoyle-router.com
             This program is a modified version of mini_httpd
               The original mini_httpd was created by Jef Poscanzer
               http://www.acme.com/software/mini_httpd/"

http://www.gargoylerouter.com/gargoyle/projects/gargoyle/repository/revisions/0ed4be5168d96443662ef6aa98af6cf247ad4ccc/show/package/httpd-gargoyle

These types of questions can get many different responses and opinions from many different users. I am no lawyer, but here is my take on it:

FCC 97.113.5 states that "No amateur station shall transmit...Music using a phone emission except as specifically provided elsewhere in this section; communications intended to facilitate a criminal act; messages encoded for the purpose of obscuring their meaning, except as otherwise provided herein; obscene or indecent words or language; or false or deceptive messages, signals or identification."

With that, what is the FCC's definition of a "phone emission?" In FCC Part 97.3(c)(5) it states "The following terms are used in this part to indicate emission types: Phone. Speech and other sound emissions having designators with A, C, D, F, G, H, J or R as the first symbol; 1, 2 or 3 as the second symbol; E as the third symbol. Also speech emissions having B as the first symbol; 7, 8 or 9 as the second symbol; E as the third symbol. MCW for the purpose of performing the station identification procedure, or for providing telegraphy practice interspersed with speech, incidental tones for the purpose of selective calling or alerting or to control the level of a demodulated signal may also be considered phone.

So with that, what type of emission is 802.11g? According to Cisco's documentation, 802.11g uses OFDM (Orthogonal Frequency Division Multiplexing), Documentation.

So what is OFDM? What's its emission type? Wikipedia (as much as I try to stay away from them) has a good article. Acording to Digi, OFDM, DSSS has an emission designation of 16M8GXW.

What does 16M8GXW mean? Take a look at this article for the FCC's emission designation definitions. And remember what was mentioned earlier? A phone emission is that which has "designators with A, C, D, F, G, H, J or R as the first symbol; 1, 2 or 3 as the second symbol; E as the third symbol. Also speech emissions having B as the first symbol; 7, 8 or 9 as the second symbol; E as the third symbol."

Since 16M8GXW doesn't have an A, C, D, F, G, H, J or R, a 1, 2, or 3 nor an E as the thrid simbol (and likewise with the "Also speech emission..." part), OFDM is not a phone emission. This means that 97.113, "No amateur station shall transmit...Music using a phone emission except as specifically provided elsewhere in this section." does not apply to OFDM and therefore we can send databit across the mesh that are interpreted by the VoIP phones as electrical waveform that command the phone speaker to make the sound, or "music" we hear.

Hi Harry,

Glad you got it working!! Its a blast when it all works and you can do some really cool things over it.

Sending email with more details about my current (and future)  whereabouts... Dont want to bore the masses :-)

KTF

This is hilarious...I had just discovered what you posted on my own and was about to post it myself!  So yes, this does work.  Attached is my new setup screen.  Thank you!

I gather you live in the Pittsburgh area?  How about sending me an email?  My email address is hbloomb@gmail.com.  Or you can call me on 443.45 PL 100 Hz.

One of my goals it to write some HSMM training materials for Western PA ARES as I've done for NBEMS.  This will certainly go into the training docs.

73,

Harry Bloomberg W3YJ

hbloomb@gmai.com

Attachments
 mesh-config_2.png [84 KB] ::

I have a mesh network that works! Thanks to the instructions I found here, I have a WRT54g and a WRT54gs, both flashed with BBHN ver 1. They play well with each other. So I connected my IP camera on aux2 and configured the software for it to look for it while I was connected to aux1. A few keystrokes (and NO bad language!) and I was streaming video over the mesh. Now I have 4 Cisco 7960 phones which I will have to flash with SIP firmware. Once my Rasberry Pi comes, I intend to make it an Asterisk server, and see if I can get some phones to work on the mesh. I may need help. Am I trying to swim too far, too soon?

I can think of two possibilities...

1) The SSH port is non-standard - use 2222.

2) I have never gotten the key load feature to work myself. I use the standard login.

73;

Bob KV4PC

As the subject states.  I thought I had things setup with the wrt54g and Putty but get a rejected connection.  Need someone that can walk me through it step by step.  Not sure of a lot of things in the Putty setup.  And should the key file for the wrt54g be a simple text file?  It DID say that a key was loaded.  Good sign.  Anyway...any takers on the help.

Kirk - N6SXR

Hi,

I have WRT54GS v1.0 with fiirmware TOMATO. Which version broadband hamnet firmware I must use to upgrade my WRT54GS with TOMATO? version bbhn-1.0.0-wrt54gs.bin   bbhn-1.0.0-brcm.trx ???

73 Waldek

What might help is to use Pelee Island as a hop point maybe cut it in half.

https://maps.google.ca/maps?q=pelee+island&ie=UTF-8&ei=NUqjUuOdBs-yqQG6m4DoDg&ved=0CAgQ_AUoAg