Let me know when you get it working.  It sounds like you are further along than my source.

Bill Wallace  KCOTGY (AT) ARRL.NET

For Sale

3 working Linksys WRT-54GL routers.  2 5db omni antennas, 6 RP-TNC to Female N pigtails, 3 sets of Power over IP adaptor cables.  3 Wall warts.  All boxed and shipped CONUS only.

$115 shipped UPS.

It's all good I just can't get anyone to work on this out here.

Contact k4rjj at comcast dot net direct for info.  Will also trade for UHF radio gear. 

For those not on the development mailing list:

Fellow Meshers (messy or neat),

FYI, FWIW, IYGARA.... I have come to state that the issue with the
secure plugin not working across different CPU byte-orderings has finally
been fixed. This code has been running on my home mesh for over a month
now and I have just committed my changes into the official OLSR source
code respository on the olsr.org website.

Alas, this really doesn't help those of us working on the Ubiquiti and
other hardware because my changes compile to null functions on that
equipment. The real 'relief' will come when my fixes are incorporated
into the HSMM-MESH firmware for the WRT54G{,S,L} hardware as *THEY*
were the real "problem children" on this issue (x86 PCs and ARM-based
hardware was too).

But be forewarned!! When this patch/upgrade happens, it will be like
what happened when we went from version 0.3.x to version 0.4.x in that
different firmware versions will not mesh with each other.

At this point what has to happen is to get my changes incorporated into
the HSMM-MESH code base. Also, those in control of the source code will
need to decide when and how to bring out this fix.

Have a happy and safe 4th of July, y'all!!!

 -Rusty-

Steve,

This is a topic of extreme interest to the developers and progress is being made. CPU byte ordering problems appear to have been a major issue. Check out this under development post for more.

73,

Keith Stevenson - AJ4KI

I'm curious if anyone else has already done this or been Interested in doing this?

To me it seems a lot more attractive to do this on Atheros equipment such as Engenius' EOC-2611

or the ubquiti stuff.. the radios are much better performers.. with far more functionality..

200-600mW output power and (significantly)  better rx sensitivity 5MHz narrow band channel modes and they are software controllable to go in the ham band... no hardware mods or crystal change needed.

5MHz channel mode let's you use it exclusively in the ham band below channel 1 and further improve s/n.

What gives here?! :-)

Is there enough interest around here to help me roll out an Atheros hardware based flashable firmware version on HSMM-MESH?

What about interoping DD-WRT's OLSR to play with existing HSMM-MESH stations?

DD-WRT seems to come eith OLSR but it's half hearted untested and does not even include a config file to get started with.

Oh and greetings! I'm Steve (N8LBV) in the Ann Arbor/Detroit Michigan area.

I just flashed 4 WRT-54gx's they work great and 2 Windows XP OLSR switch installations..

Am taking all to a 4 day ham radio family camping & activity trip in Lupton/MI this week.

We will cover the entire camp property and guest center with these 6 stations as we did successfully at last year's event.

See http://sectionouting.info

Also I'm sharing a live view into what we are playin with at: http://iridium2.michiganbroadband.com:1978 (good year BTW) and http://iridium2.michiganbroadband.com:8080 <-- that will be back later today.

Thanks for your reading & possibly your help on this!!

Steve Gladden N8LBV

at 7pm, come early if you need help loading firmware.

Talk-in is the PARK repeater, 147.180+ with a PL of 107.2.

For those elsewhere, Kip's tunnel node is now our gateway node so those of you connected via tunnel should see our smiling faces because I plan to bring a node with a video camera.   Sorry, no audio from my camera but maybe another attendee will have a better camera.

-Rusty-

Actually the key exchange wasn't broken because there was no key exchange. :-)
     [Technically, you never exchange keys, you issue "challenges" that are encrypted
      by both ends of a connection. If you have the proper key you can decrypt each
      other's challenges. Doing that successfully will let you into the PARTY! :-]

The problem was more like the timestamps were not net-byte-ordered before being sent out and verifying the responses from crypto-challenges were not getting done correctly either. I have the secure plugin fixed now. The question is "When do we want to release this and break everything again?" This will probably go into the next major release, say 0.5.0, whenever that occurs. David, AD5OO, and I talked about this during HamCom and this was pretty much the consensus.

Since the byte-ordering on the Atheros and other Big Endian processors actually works (only by virtue that Big Endian has the same byte ordering as the 'net') it are the WRT54G{,L,S}'s that need fixing. Still, having the proper code on both ends is a more proper solution.

I also have a PC version of the secure plugin running on my x86 laptop and meshes just fine with my test mesh.

You're right, I'm a bit worried that this wasn't found/fixed by now. Then again, the secure plugin isn't about security so much as it is about who do we let into the mesh. It's more like a secret handshake because other nodes without the right key, on the same channel, with the HSMM-MESH SSID, can still browse the mesh nodes webpages and 'ssh' into a node if they know the right IP addresses.
So, maybe it's not such a big deal because no one uses the secure plugin??? I dunno.

-Rusty-

A node set to work in Mesh Access Point mode is not meant to be used by itself, but instead to have one of its lan ports connected to the lan port of another node operating as a Mesh Node. As such, it does not run a DHCP server and you will not be able to have your computer's network set up automatically.

Connect both your computer and the mesh access point to the lan of a mesh node and you will be able to connect with either http://localap:8080/ or http://172.27.0.2:8080/

73

ad5oo

Node Type sets the operational mode of the node. For our purposes it will be set to Mesh Node, but if needed it can also be set to one of the other modes, to be described at a later time.

The one mode I will mention is called Mesh Access Point. It is a configuration meant to be used to give standard wireless access to the LAN port of a mesh node. This is to be used on a second router whose LAN port is connected with the LAN port of a mesh node. When running a router in this mode it does not use OLSR and as a result its hostname is not available to the mesh. It can be accessed from the LAN by its IP address which by default is 172.27.0.2. Like the name "localnode", an automatically generated name exists called "localap" which is set to the localnode address plus one, but only when the node is operating in the default NAT mode.

Try address 172.27.0.2

-Glenn

KD5MFW

Alright.

My club had 4 nodes sitting around that for whatever reason before I joined the club were not in 'ready to go' condition.

I have taken it upon myself to try and atleast get them serviceable so that should a need arise, they will be pretty close to ready to go outta the box- atleast as far as firmware setup goes.

WRT54G V2.2

I managed to flash to the latest firmware for this version (as of the date of this post).  Successfully plugged into my home internet via home router.  I believe this required me to change away from the default setting of 'mesh node' if memory serves me to something with 'access point' in the name.   I was connecting successfully and able to 'surf' the web so to speak thru wireless to the node while connected wirelessly and via lan.  So, I got adventurous I guess and I think I changed the setting to "mesh access point" and after saving and rebooting I believe that is where my problem developed in not being able to get back into "setup" to change it back again. I can't get in wirelessly nor via lan.

I have RTFM since lastnight (initially when learning to set things up and then especially tonight to get successfully setup.  But, now unless my eyes are just crossing and not seeing the correct procedure- I am unable to get to the login page which would then allow me to login and get to where I can change the setting back where it should be.

Whatever it takes, I wouldn't mind even having to re-setup the name of the node and all if I had to reset to defaults of the hsmm mesh firmware... I'm just not sure how to get there if it takes that... or if there is an easier fix.

BTW I haven't forgotten the password I setup. :)

Is there some hope for me?  Can someone toss me a rope?

James

KB5FVS

I have two Cushcraft S2406BP36RTN 8dBi (6 dBd) Omnidirectional Mast Mount Antennas w/RP-TNC (S2406BP36RTN)  These antennas for the 2400 - 2500MHz frequency band and exhibit a 13 degree E-Plane beamwidth.  These were rescued from old Mesh project at the office so I will start with these and a cheap NEMA box...

I was looking at dmswireless.com, they seem to make some nice WLAN Yagis...

Happy Meshing!

Billy, N5EVD

Small note: The serial ports are NOT present in the WRT54G version 1.0 and 1.1. In the v1.1 there are pads for the UART chips and associated components but they are unpopulated.

FWIW, FYI, IYGARA... :-)

-Rusty-

Just ran into this myself. So it looks like the OLSR key exchange code is broken.Should we remove it till it gets fixed and use our own variant? Also odd to me with as many systems as I see out there that we are the first to encounter this.