Hey there Everyone,

First off I hope the Dad's here are having a great father's day.

Secondly, I recently acquired two EnGenius EOC-1650's and I was wondering if anyone had taken a crack or would care to help me to set these things up as mesh nodes.  I figured because they're outdoor 200mW bridges (that are supported by dd-wrt so I would think we could get them to take openWRT as well) that they would make a good outdoor node (not to mention I have them and they were cheap).

Anyways, enjoy the rest of your weekend, just thought I would put it out there that I have these and see if anyone would care to help me out (I'm willing to build the firmware myself if need be but I'll need guidance from those who are in the know.)

73 de Travis W9HDG

Hi Andre, I have two AirGrid M2 HP that I have flashed the firmware to Broadband-Hamnet already and get the error message, but still seems to work fine. Are you still conducting the test? I'm not sure where to check the info concerning the "board.sysid=0x242". I'd be willing to reflash one of these if you still need the info and they are the right ones. 73 Mike, n7kmj

Never mind, I see these are already covered. Strange way message is presented on login. Oh well, this happens to newbies. ( smile )

73

    After flashing the NAT device with the appropriate custom OpenWRT firmware and configuring the firmware for first use I cannot obtain a gateway IP address or connect to the node via LAN using localnode:8080, localnode.local.mesh:8080, or KG5CNK.local.mesh:8080. I have tried numerous times resetting the WRT54G in hopes that I would be able to access it prior configuration of the newly flashed firmware. With no luck, I am unable to access the WRT54G now. It is powered on, and shows an ADHOC logo for the wireless networking capabilities. I've reset the laptop's NIC along with resetting the WRT54G. Nothing I do is allowing me a gateway IP address into it. I've been using CMD > ipconfig. No matter what I do, I am basically locked out of the device.


Any suggestions would be greatly appreciated.


73s, KG5CNK, John J Favaloro Jr

Hello All,

I saw a demonstration by KD8RBH at Thunderbase that got me very interested in HSMM-MESH.  I just ordered a Nanostation and hope to get a node up soon.

I tried to make one of my mesh nodes into a mrs ap this evening and now I can't back into it to return it to mesh node operation.

I can see the wireless (WF8S-101) and connect to it but nothing else works.

I tried both static & DHCP on the wireless as well as the wired ports to no avail.

Any suggestions?

I'd say it's a bad idea to buy gear until we announce what we'll support.  Take it from me... I made the mistake myself... and I'm the project manager!

Andre, K6AH

Hi there, I've just started learning about / playing with this system. 

Thought occurred to me, would it be possible to build a USB Live Linux Key that would contain the OSLR / HSMM-MESH software so any newer computer that will boot from USB could potentially become a node?

I've found a few mentions of people getting Ubuntu laptops to act as nodes. The information I've found so far is a little lacking in content on how they accomplished it.

I'm going to continue my research and try to get an old laptop to act as a node first then maybe try building a live USB key.

Sean VE6SAR

Forgot to add this to the instructions.  AGWPE has a SETUP INTERFACE menu wherein you will enable the WINSOCK, set the level of security (password and login), and a HTTP port to enable the "I-server"

Miss this step and you will pull your hair out for a while trying to figure out "why you cannot log on to the AGWPE engine on the server.

Hope this helps.

Kenny

KC4OJS

Understood.

My 'locally' reference was to the LAN side of the node used to physically connect to the network.  My WAN reference was to the RF side of the node used to connect to other nodes on the mesh network.

I can connect to the LAN side of my node without difficulty.  This thread was related to using the RF side of this node to connect to the web interface of an adjacent mesh node. 

Now that I know how this is supposed to work, it appears that I have an issue on the LAN side of my local node.  Most likely something I overlooked in the configuration of NAT on my local node.  I agree that this is a separate topic.

Bob, KO2F

Is there any VOIP guru's out there that can help me out?

That would be me.

Send me an e-mail and I'll get you fixed up. The 79x1 series is different.

Never mind as I finally found the answer on the site. . .

It has been a long day . . 

41.444142° N 74.568651° W 1135 ft

101° 22.8 miles 23 total

41.378944° N 74.136688° W 1483 ft

I just got 2 ip cameras identical to the ones K5KTF has in his Tower Cam article.

However these are wireless ip cameras and the wired port is only for configuration.

Which node mode would I use to let the cameras connect to the wireless side of the mesh node?

Also, which mode should I use if I have a node with internet access and by which port? WAN? LAN? with or without a crossover cable?

I am trying to build a VOIP setup with a raspberry pi for a Field Day demo of hamlet but have ran into a small problem.

The Cisco IP phones I got donated to me are the 7961 & 7962 models and all of the videos I have found are for the 7941 phones.

Is there any VOIP guru's out there that can help me out?

I have all of the flew needed but cannot seem to figure out how where in the config to tell the phone to look at the RPI as the TFTP server in the phones config file. I have the phone set to look for the TFTP servers ip address but can't get the phones to register with the server.