I see it more as there's not going to be any further development for that equipment.Basically the same thing as Icom won't support my old IC-2AT. Nothing stopping it from working, or me continuing to use it for events, but if I have a problem with it, I can't expect Icom to tell me what to do to fix it, or for them to fix it or continue providing parts for it. The way I understand the versioning, you can continue to use the Linksys stuff with versions of the protocol up to the last one compatible with the hardware (currently V3). I also understand the protocol version isn't changed unless there is a compelling technical reason to do so. It might not be as powerful or sensative as "replacement" models, such as my IC-91AD, but on FM, those two will talk as long as the batteries hold out.

I want to include a simple video camera in the mobile/portable node I am building.

Needs to be reasonably inexpensive and somewhat tolerant of outdoor use in a few special events, if possible.

What are you using and why did you choose it?  Thanks!

Bob W8ERD

I have a Linksys WRT54G router converted to a hsmm-mesh box, and I'd like to be able to connect it to my home network so I can look at the status and such thru my home network, (I can do that with the home network ethernet cable connected to a LAN port, but not the WAN port).  But I want to configure it so a mesh user cannot access the internet thru my home network.  I see a mesh gateway box under "WAN" on the setup page, but no such box under "LAN".   Is there a way to configure the WAN port so I can get to my mesh status web pages, but have the mesh gateway unchecked?  In my case I have my router as http://192.168.1.99:8080/cgi-bin/status (which I can get to when the home network is connected to a LAN port).  I configured the WAN port to be "static" and at 192.168.1.98 but I cant get to the mesh web pages over my network. 

One crude solution would be for me to physically unplug the ethernet cable from the mesh router when I'm not wanting to access it over my network, that would keep mesh users from seeing the internet.  But if there was a reasonably secure method of doing this via configuration I'd like to do that instead.

TIA, 73s

While I fully grasp and understand the need to come to a difficult decision of discontinuing support of the LinkSys WRT 54 hardware I hope that the software developers haven't gotten "tunnel vision" with regard to the people who volunteer their time, QTH's and resources for the MESH project.

Personally I have MANY WRT's in locations all over my region and am disgusted that newer hardware will NOT be able to be BACKWARDS compatible with the legacy equipment already in place!

I am not a person who has disposable income for my Ham Radio projects, buying the newest, latest, greatest piece of hardware out there..... I budget my money for projects as required. It makes no sense to me (or others I have spoken to) why a vertical marketing strategy for the MESH has taken place.

Who will promise that in another year that the Ubiquity hardware won't be tossed aside for the next greatest doo-dad?? Will that decision be as easily made as the one to discontinue LinkSys??

Is the "end-game" to create a saleable item to the general public in a for-profit mode that was built on the backs of hams?

The choice for no backwards compatibility is a puzzling one.... even if the newer hardware supported a vast amount of options that the older hardware couldn't fully support the older hardware should have been allowed to still participate in the MESH, supporting what it COULD do, rather than being cast aside for what it CANNOT do..

Any insight on reasons OTHER that the fact that the firmware has become BLOATED beyond the limits of the LinkSys hardware would be extremely well received..

I guess MY LinkSys hardware will be disposed of and MY nodes will go silent....

73 de

Rich Ser

N2PPN

There is a google map page on the website.

it is all about line of sight as far as distance goes.

Hmmm. Usually when I log out then back in it works for me.

Yeah, try and dump the cookies. I think the site drops a cookie to know that you are logged in (never actually looked at what it does...never had to).

Try a log out, close the tab/browser, and then log back in from the home page below the left menu.

What browser are you using? That might help me figure it out.

Do you have more than one window at the BBHN site open?

You have me curious now...

KTF

Just use our TRX file.

Hi

Couldn't find any topic that covered converting a WRT54G from OpenWRT to HSMM-MESH firmware. Anyone done this?

Am I able to install HSMM-MESH firmware on top of OpenWRT firmware or do I need to revert my router to a factory Linksys firmware first?

Thanks

Shawn  

For those using RadioMobile for modeling, here's a link to the Ubiquiti antenna pattern data files.  The ".ant" files can be uploaded directly to RadioMobile Online.

http://community.ubnt.com/t5/airMAX-Frequently-Asked/airMAX-Do-you-have-antenna-patterns-available/ta-p/902862

Remember, when you use a dual polarization antenna (such as UBNT NanoStation, one of their various sector antennas, RocketDiish, etc.) you're actually using two antennas... each having their own V and H patterns. They'll need to be modeled separately.  Their file naming convention describes the model and polarization the data file represents.

Andre, K6AH

Naw, just a bug....

I would suggest logging out and back in and trying again.

I have seen this a couple times myself, but cant quite catch what is doing it. I think its something with page session timeouts or something.

Happy Meshing!

Jim

hello guys. two questions.

I have a node on the air near the Amateur Electronic Supply here in Las Vegas. I would like to program the cordinates into that node so that it is displayed in the status page. CLI is not my forte' at all, so may someone walk me through it?

I also have a mobile node that will get a GPS hooked to port 2 very soon. I am very comfortable with hardware, but not so much with software. I read jims article, and I still cant make heads or tails of the coding part. Eventually I would like to connect my Byonics TT4 to the node. Hardware wise, its very simple, just cut the traces on the TT4 and it spits out TTL level serial. The same thing can be done with the MTTT4, and you'll have a complete 2m<>2.4G<>Internet box.

The sticking part with me is the software. Running the soldering iron is a blast, but coding looks like a nightmare. I'm a GUI man. HIHI

any thoughts.