How do I connect a 2.4 ghz node to a 5ghz airmax node?

73 de mike

Hi Derek, The Ole Virginia Hams in Manassas is discussing setting up a BBHN node at their repeater location at NOVEC, 10323 Lomond Drive. Ole Virginia Hams: w4ovh.net My node is up in Centreville, its posted on remoteamateur and here on this sites googlemap mesh map. 73, David, kk4zuu

I'm running two nodes near the South Campus Gateway area of OSU campus. I'm using the stock antennas at the moment on two WRT54GS's. I'm looking to build some cantennas shortly for some direction coverage. A few students I know who live around the campus are interested in the project as well and I've been in the process of getting them set up with routers.

Hi Andre. I didn't get the email (k0fei@arrl.net - k0fei@me.com) but went ahead and loaded the current ubnt Bullet M on the Picostation M2. Other than the yellow banner on the status page warning it is untested - everything seems to be working fine. It is talking with a LinkSys WRT54GS, 2 Beagle Bone Blacks, a Raspberry Pi and a NanoStation Loco M.

Last weekend I was able to re-flash a WRT54G3G-AT and two -STs.  (Thanks very much to whomever posted the info on modifying the binary file's 'magic number' (the initial bytes of the file) to fix the 'signature' the re-flash utility was looking for.

When I have the mesh node connected directly to my laptop computer via lan cable, I can visit the node's status and setup pages, and from there visit other nodes in the mesh.

I then plugged one of the nodes directly into an open lan-port on my service providers WiFi router (a Westell unit provided with Frontier/Verizon FiOS) but find no matter what I try, can't now get to the mesh node, even coming into the Westell on a wired lan line from my desktop computer.

I've logged into the Westell's admin server and run all the 'discovery' scans that looked reasonable.

Do I need to have the mesh nodes use the Westell for their DHCP server?

Should the mesh nodes themselves show up in the Westell's tables or only additional IP gizmos (IP Cameras, etc) plugged into the mesh nodes?

Any help appreciated --

Benton 17jun14

KF7QLP

Hi, Sean;

I've tried Byzantium, which uses a usb bootable Linux called Porteus. It uses OLSR, so it might be easy to configure for compatibility with BBHN. I'd be interested in any success you have with this idea.

http://project-byzantium.org/

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