Awesome!  We now have a place to discuss local efforts to expand our mesh network.

Looking forward to meeting and conversing with fellow local Meshers!

Robert

W5HTF/WQRT338

There was a post on here about that.  It said to load original WRT54G v3 software and then upgrade.

I googled tomato on this site, and copied the URL and couldn't paste it into this message.  I think it was the first or second post listed in the google.

Hope it works for you.

John,  WoGN

(A mesh beginner)

I have attempted to load ngircd from the package index on several Bullets with no success.  I get the message "Cannot install package ngmircd".  Is this package only available for the Linksys router?

Fixed this node! 

typed in 10.51.85.153:8080 in browser, which is the gateway found with ipconfig.

It found the new node ID (W0GN-10) but didn't like my password.  Finally, I tried "hsmm" and it unlocked and I could set my own password.

In desperation, I had tried the 30-30-30 reset and it must have wiped out the one I set before.

Everything seems to be as it should, but no time to fully check it all out.  Preparing for ARRL FD at WoCWP.

Thanks for your help Jim.

73,  John  WoGN

Does anyone have any ideas of how to upgrade to HSMM-Mesh firmware on a WRT54G V3.0 router? I have downloaded the correct 3.10 bin file and tried to upgrade the firmware on the router. I keep getting a error "bad file".  Any help would be great as we are trying to use the Mesh network for Field Day Logging. 73s W1RGC

Does anyone have any ideas of how to upgrade to HSMM-Mesh firmware on a WRT54G V3.0 router? I have downloaded the correct 3.10 bin file and tried to upgrade the firmware on the router. I keep getting a error "bad file".  Any help would be great as we are trying to use the Mesh network for Field Day Logging. 73s W1RGC

Flashed a WRT54Gv3 with BBhamnet.  Entered node name and passwordOK.

I *think* I forgot to save them.  I rebooted, and since then have found no way I could connect.

What should I do next?

Thanks.

John WoGN

Hi All,

We have set up a 900Mhz link to our Field Day site, from a home station about 1.25 miles away.  We are excited to use this, so I thought I would put one of my wrt54g nodes in standard access point mode so people at the site can use their standard wifi devices (within Part 97 rules, or course).

So, I set my node to a standard access point, turned off DHCP, and set a nice name "Field Day".  I connected a network cable to a Ubiquiti mesh node, and after resetting that, I can now take a laptop and connect it to the "Field Day" wifi, and I get an IP and can see the Ubiquiti node.  So far so good.

I tried connecting the laptop via cable to the standard access point, and it doesn't get an IP this way, so looks like I can't do this.

The real question, though, is how do I talk to the standard access point again so that I can change it's settings?  To put it back in mesh node, for example?  I tried 172.27.0.2:8080 for talking to a mesh access point, but that didn't work.  Anything I can do with the reset button on the router?

Thanks!

Erik

Do we have, or are there plans for a 900 MHZ on Guinn? 

Does the Ubiquiti PowerStation5 fit any of the existing images?

Processor Specs = Atheros AR2313 SOC, MIPS 4KC, 180MHz
Memory Information = 16MB SDRAM, 4MB  Flash

Hello, I am successful in getting my linksys based hsmm mesh setup working properly with N1MM Logger plus between two nodes.
My last issue to deal with is the master computer using both the mesh network via the ethernet port and a wireless network via the wireless setup on the laptop. If the ethernet cable is plugged in, the computer can't locate any internet websites. If i unplug the ethernet cable, then the master computer can reach internet websites.

It appears that when the ethernet cable is connected, the dns process favors the mesh dns setting.

both network connections are setup with dhcp and dns being set to automatic.
I even tried setting dns manually with no luck.

my issue is having the master computer being able to access an internet time server and any other internet needs while we are running multiple nodes and computer.

Only one computer in the setup will have access to the internet via the wireless.

All computers have the same version n1mm logger plus and each node has the latest firmware.

suggestions?

I have posted this request in the n1mm logger yahoo group as well.

thanks

Stephen AC8QE

I hadn't thought much about the radio interface much past USB soundcard but something like the Signalink would make that a plug friendly process.  Provided of course one could set up the drivers for it in a basic router, which is the step I'm not yet familiar with.

Using some form of single board computer like a raspberry pi would fit my vision of a simple interface if direct connect to a router isn't possible.  They can start and run themselves and are small enough to be packaged along with the remote radio and mesh router.

I can't disagree with your vision of a radio with an antenna and an ethernet connection, but for now that option doesn't exist.  I'd be good with a simple interface for audio and PTT, and for extra credit maybe switching through a few channels.  The UHF remote base on my 2M repeater is a Motorola commercial HT that I switch frequencies using a touchtone decoder.  If I had that simple radio interfaced to a mesh network in a similar way, operable through a simple UI on a laptop or smartphone, that would be my goal.  Public use, access over the internet and other second order details are not my goal.  Just access the node via IP address and start the stream.  The IP phone interface does add greater control which could apply for a more involved system so that would be the next logical step, at least in terms of using off the shelf hardware.

Using a signalink is a good idea though, so will add that to the list of things to experiment with.

Mark K5LXP

Albuquerque, NM

For the sound-card-attached-to-radio approach, would the Signalink USB work for you? It says it supports VoIP mode. Presumably if there were firmware support for WiFi hubs having a USB port, one could plug the Signalink into the hub, the radio into the Signalink and the antenna into the radio. Otherwise, you'd still need at least a Raspberry Pi like computer.

I don't know how integrated you want to be. It seems to me that mesh/data hardware should remain separate from the narrowband FM voice hardware. I had in mind a black box with an antenna jack and an ethernet port (so you could plug it in to any mesh node without waiting for firmware support for something new). If you made the black box contain a raspberry Pi, a Signalink USB, and a commercially produced radio, I guess that would address your needs for fixed frequency simplex or repeater operation. You may still have to load up asterisk on the raspberry pi to implement the network server. I'm not sure what you could eliminate to make it simpler. My suggestion of an SDR just merges the functions of the Signalink and the radio into one item. The Raspberry Pi is just a really small server, but plays the same role as the PC one would normally throw at such a setup.

Got any links to reference?  A quick search turns up how to create a remote base interface for echolink, but not so much how to turn echolink into a client that doesn't rely on echolink servers.  The solution I'd want would run on a LAN or mesh netowork, with no internet.

Ideally the remote base wouldn't require a PC as an interface or host.  K5KTF's radio-IP phone interface is clever but I think it should be even simpler than that, using just a USB sound card and USB to serial/discrete I/O connected to a router.  The idea of loading up asterisk servers and controlling SDR's sounds like a lot of trouble and hardware for what should be a simple system to interface a radio to an IP network.  It's one thing I suppose if one really needs a frequency agile, all mode/all band remote but I'm thinking in the context of being able to pipe a 2M simplex or repeater frequency where a field mesh network has been set up.  Start simple and make it part of the cadre of basic services like IP cameras and phones that are readily supported by mesh.