Was trying to connect to KF5MFL's node.

The LED's etc all work, I can login to the web interface just fine and all seems ok on the firmware front. Not sure where to set which antenna to use, is there a spot in the firmware for that or are you just referring to plug/unplugging them? 

My current limitation is testing the equipment to make sure it can link up, I plan to install on my roof ~28'AGL once everything is tested working.

The cable is <3' of LMR-400, per antenna. The connectors are 2 chassis mount BNC female on the wrt54g and appropriate connectors leading to the antennas. I was worried somehow the BNC connectors are bad, I have no way to plug the stock rubber ducks into the router now that it has BNC connectors so I don't think I can test that. 

I am running a custom build of the latest svn repo so maybe I will just flash over vanilla just to rule that out.

Running latest firmware, using a 24dbi dish from here and 12dbi omni from amazon. Used my cell phone to test the range, pointed the dish down the street out my window and I don't even get one block away before it doesn't show up on scan. Meanwhile I can scan and even connect to my homes wireless router from the end of the street(3 blocks), it's a linksys wrt310n with stock everything. The wrt54g is slightly modified on the inside(power over ethernet, new connectors) and I'm wondering if the connectors could be bad and wondering how I can test it.

I am bringing up a node in Hudson, MA area.  Would like to find other nodes in area so that I may locate my node appropriately.  I want to maximize the mesh connections.

Well, it was worse than I thought.  I expected the wireless interface to have a different name, instead it doesn't even show up.  That means that the kernel does not recognize the wireless chipset used in that model.  It may be possible to get it working if the appropriate kernel module can be added to the firmware, assuming it exists in this version of OpenWrt.  If you are really motivated you can download the firmware build environment from the svn repository and try making your own custom firmware to try to get it to work.

The other alternative is to be patient and wait for, or even contribute to, the next version of HSMM-MESH which will be based on the 10.03.1 version of OpenWrt.  It has support for a much broader selection of hardware platforms.  This firmware is still in the very early phases of development and not yet available in the svn repository.  No date can be given yet for when it will be, but keep an eye on this website over the coming weeks (or months) for an announcement.

73
ad5oo

Here is the sysinfo file:

node:
model: unknown

br-lan 00:1A:70:58:00:D5
eth0   00:1A:70:58:00:D5
eth1   00:1A:70:58:00:D6
tunl0  00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

/proc/cpuinfo
system type        : Broadcom BCM4704 chip rev 9
processor        : 0
cpu model        : BCM3302 V0.6
BogoMIPS        : 262.96
wait instruction    : no
microsecond timers    : yes
tlb_entries        : 32
extra interrupt vector    : no
hardware watchpoint    : no
VCED exceptions        : not available
VCEI exceptions        : not available

nvram
blink_diag_led=1
boardflags2=0
boardflags=0x0010
boardnum=42
boardrev=0x10
boardtype=0x0472
boot_hw_model=WRT150N
boot_hw_ver=1
boot_ver=v4.2
boot_wait=on
bootnv_ver=2
cardbus=1
clkfreq=264
diag_gpio=1
dl_ram_addr=a0001000
et0macaddr=00:1a:70:58:00:d5
et0mdcport=0
et0phyaddr=30
et1macaddr=00:88:88:88:00:2a
et1mdcport=0
et1phyaddr=4
lan_ipaddr=192.168.1.1
lan_netmask=255.255.255.0
mfg_wait=on
opo=0x0
os_flash_addr=bfc40000
os_ram_addr=80001000
parkid=0
pci/1/1/aa2g=3
pci/1/1/ag0=2
pci/1/1/ag1=2
pci/1/1/ag2=2
pci/1/1/boardflags2=1
pci/1/1/boardflags=0x200
pci/1/1/boardrev=0x4b
pci/1/1/boardtype=0x46d
pci/1/1/boardvendor=0x14e4
pci/1/1/bw40po=0
pci/1/1/bwduppo=0
pci/1/1/ccdpo=0
pci/1/1/cck2gpo=0
pci/1/1/ccode=
pci/1/1/devid=0x4329
pci/1/1/itt2ga0=0
pci/1/1/itt2ga1=0
pci/1/1/ledbh0=8
pci/1/1/ledbh1=-1
pci/1/1/ledbh2=-1
pci/1/1/ledbh3=-1
pci/1/1/macaddr=00:88:88:88:00:2a
pci/1/1/maxp2ga0=0
pci/1/1/maxp2ga1=0
pci/1/1/mcs2gpo0=0
pci/1/1/mcs2gpo1=0
pci/1/1/mcs2gpo2=0
pci/1/1/mcs2gpo3=0
pci/1/1/mcs2gpo4=0
pci/1/1/mcs2gpo5=0
pci/1/1/mcs2gpo6=0
pci/1/1/mcs2gpo7=0
pci/1/1/ofdm2gpo=0
pci/1/1/pa2gw0a0=0
pci/1/1/pa2gw0a1=0
pci/1/1/pa2gw1a0=0
pci/1/1/pa2gw1a1=0
pci/1/1/pa2gw2a0=0
pci/1/1/pa2gw2a1=0
pci/1/1/pa2gw3a0=0
pci/1/1/pa2gw3a1=0
pci/1/1/regrev=0
pci/1/1/sromrev=4
pci/1/1/stbcpo=0
pci/1/1/txpid2ga0=91
pci/1/1/txpid2ga1=91
pci/1/1/txpt2g=0x36
pci/1/1/venid=0x14e4
pmon_ver=CFE 4.81.56.0
scratch=a0180000
sdram_config=0x0062
sdram_init=0x054B
sdram_ncdl=0x208
sdram_refresh=0x0
size: 2930 bytes (29838 left)
sromrev=4
tftpd_ipaddr=192.168.1.254
wait_time=3
watchdog=5000
wl0gpio0=8

Thanks again,

K4NED

Sorry to hear your trouble.  You may be the first one to use that specific model.  My guess would be that it is not 100% firmware compatible with the wrt54g since it uses an N radio and the wifi address came up blank.

You should be able to put the factory firmware back on with the tftp process, then install our firmware again.  If you can get it back to the state it was in where you could access the mesh web interface, send your browser to http://172.27.0.1:8080/cgi-bin/sysinfo and post that information here.  I suspect that the interface name for the radio is different on this model of router and the sysinfo page will confirm that.

73
ad5oo

Yes, the source code is open but no official declaration has been made yet as to which specific open source license applies.  But do feel free to extract any pieces of it you need for your project.  Give us credit where applicable and don't call it HSMM-MESH.

Now bear in mind that our firmware works under the presumption of a large amount of available bandwidth and this is something that any legal HF mode cannot even begin to supply.  I'd be interested to see more details about just what it is you intend to do.

73
ad5oo

I flashed the WRT150 firmware file into the router. It rebooted and came up. I was able to log into the setup page. I entered the node name and a password. The wireless lan address had just "10." in it. So I put in a valid address, "10.238.150.233". Everything else looked ok. So I pushed the "Save" button. The router rebooted. It now longer functions. No DHCP. No web access. No SSH access. No ping response.

I was able to get to a management interface by holding down the reset button while powering up. I could telnet to it on 192.168.1.1. I was able to copy the .trx file into /tmp using scp. Then I used the mtd -r write file.trx linux command to re-flash. It completed and rebooted. But it is in exactly the same state described above.

This is a Version 1.0 router. I did update the OEM firmware successfully before loading hsmm-mesh. I have two of these in the same condition. Does anyone know if it is possible to make these work with hsmm-mesh? I used the firmware file from the web site that had this router model in the name.

Thanks for any help you can give.

The idea is one of openness -- allowing other hams to connect as they drive by.
If you want to encrypt your mesh then no one can connect to the mesh. HSMM-MESH is
primarily intended for event or emergency communications and not replace your home
wifi network. With encryption the added steps to obtain the key used by the event's
mesh gets cumbersome at best.

I'm not sure why you consider it strange that the access point mode doesn't have a
password since using WiFi in McDonald's, StarBucks, or any of the Texas Rest Stops
(amongst others) doesn't require it.

Mesh's can be encrypted -- one of mine is that way -- but the specification of the
method and key requires being able to use the Linux shell and and manually edit one
of the config files.

-Rusty-

Hello Everyone--

I'm new... Robert K6KGS in Dana Point (Southern) CA.

This looks like very nice work.

I'd like to know if this software is Open Source, and if so, under which License.

I'm asking because I'm working on a gateway module for an HF engine that links meshes across gaps in the direct connections. Very useful for times of emergency when the usual cast of characters' backbones are down... Like real emergencies.

Thanks in advance.

Happy Thanksgiving everyone!

very best 73's/robert

I have changed the title to get this going as a separate discussion. What you are asking is a topic that has been discussed for quite a while. The concept is "service processor". We envision roles of the service processor could include reporting battery voltage, control or restart 12v or 120v devices, GPS location using APRS over the network, weather, and similar. WB5AOH has a proto of a board he has demonstrated. There are several approaches to this. The Austin QRP group (on Yahoo) is actively developing the Arduino kits. This motor control daughter board http://www.makershed.com/product_p/mkad7.htm along with the Arduino host board would be the basis for turning things on and off. The basic Arduino kits can directly sense voltages. All that is needed is a bit of programming to pull the outputs and submit them as data traffic. "developers welcome".

All up and running now with 5 nodes. Question for all the openwrt experts, is there a way of remotely checking supply voltage. The nodes are all running off of 9ah gel cells (approx 12hr service) but it would be great to be able to work out remotely when a node needs swapping out.

Yes, that was a stale address.  My firewall died and I have a temporary replacement running in its place and not everything is working as it should.  I updated the address and you should be able to get to the svn repository now.  Thanks for pointing that out.

73
ad5oo