Is this normal behavior ?

I have 3 sites deployed across 5 counties now. Three of the sites have multiple radios and I have deployed switches to connect the radios at each site.

On one site the radios are not running the same version of code. i.e. 1.1.2 on one radio 3.0.0b2 on the other. The 1.1.2 is connecting to another site running 1.1.1 and the 3.0.0b2 is linked to another site running 3.0.0b2. from the 1.1.x side I can't see past the first 3.0.0 node and the same coming back in the other direction.  The sites are all running 3.0 code with the exception of the one site.

Site 0 AE4ML500 Linked 0.5miles to AE4ML501 ( Both 3.0.0b2)

Site 1 AE4ML501 (3.0.0b2)

Site 1  AE4ML510 linked 36 miles to AE4ML509

site 2 first link AE4ML509 linked to AE4ML510( Both 3.0.0b2)

site 2 second link AE4ML502 1.1.2 linked 18 miles to KO2F505 1.1.1

site 2 third link  AE4ML509 linked 8 miles to W4LAN500 (Both 3.0.0b2)

Site 3 KO2F505 linked to KO2F502 1.1.1

Local Switch site 2

fa0/14 AE4ML509 (3.0.0b2)

fa0/15 AE4ML502 (1.1.2)

fa0/16 AE4ML202 (3.0.0b2)

As seen from AE4ML509

AE4ML502 shows up as an IP address only and not a name. I'm unable to hop over to that IP address of AE4ML502. 

The question becomes is this normal behavior for the two versions of code ? If so I only need verification to go to that operator to get him to upgrade.  

site 3 W4LAN500 linked 7 miles away to AE4ML509

Would it be worthwhile to connect two yagis, one Horizontally polarized and and one Vertically polarized to create a circular pattern?

That's not how diversity works (please see the top of page 8 of WNDW - Chapter 10). If you wanted to create a simple circularly polarized pattern (many different types), you could use one antenna port, then split the signal to go to the two antennas. One of the feedlines in the splitoff would have to be a half-wavelength longer or shorter than the length of the other feedline.

Would be the minimum/optimum/maximum separation distance between the two beams and/or the cable length(s) feeding them??

Per mention above, both the Yagi antennas would be on the same beam with one vertical and the other Horizontal.

What net increase in gain and link reliability would I likely expect?

I do not know as there is no single right answer. One of the above links should have your answer (antenna dependent).

Given that the WRT devices have two removable antennae, would it be worthwhile to connect two yagis, one Horizontally polarized and and one Vertically polarized to create a circular pattern? What would be the minimum/optimum/maximum separation distance between the two beams and/or the cable length(s) feeding them? What net increase in gain and link reliability would I likely expect?

We are not "DUMPING IT".

Whatever version WRT firmware has been updated/released as of the end of April will be the last version from us, and will be available on the web site forever till the end of time (or when the project is trumped by something better 20 years down the road).

WRTs will still be quite usable on that last version. I know Ill still take them to Field Day for the logging network. I will still use them around my QTH for stuff. I have so many, I cannot justify returning them all to Goodwill and buying all new UBNT gear. Just Aint gonna happen.

So chill, relax, and flash up another. They are still very workable and will be until YOU decide to upgrade your own.

Jim
K5KTF
Webmaster (so Ill make sure the FW stays up there!)

Also along those lines, its http://localnode:8080   not localnet that is the other reason you could not connect.

Glad to see you got it by IP address.

Hello, I just received my Bullet today.  I went straight ahead to flash the firmware. I used "bbhn-1.1.2-ar71xx-generic-ubnt-bullet-m-squashfs-factory".  But, now after it finished flashing.  I get an ip address from it using dhcp but I can not reach the web interface.  I've used "localnet:8080" and I've used the ip address 192.168.1.1 - I'm assuming that's its IP since it gave my laptop 192.168.1.9

Any ideas?  Thanks!

*EDIt - Nevermind. I was using the IP without specifying port 8080. Once I caught that it loaded.

I know...
It's a horrible thing that OpenWRT has dropped support for the legacy Broadcom chip in one of their later releases. Furthermore, it's a shame that a know issue with OpenWRT's Attitude Adjustment is that lower end devices with only 16 MiB RAM will easily run out of memory...
If only OpenWRT continued support longer...

That is so idiotic!

You have robust, inexpensive plentiful hardware, that has been thoroughly documented by many sources, lots of hardware/firmware hacks, serial ports/usb, etc.   The WRT54G series is essentially a very versatile platform.

And.. they dump it.

Dear Members,

Where is the IRC software to download from the BBHN... I couldn't find it in the

software download area like the article said it would be.

I am looking for the program file that Rusty Haddock AE5AE posted in the applications section.

Any help appreciated

73 Dave WA5DJJ

Correct.

There will be am informal meeting of meshies from Franklin, Delaware and Marion counties on Saturday Nov 22 at 4 PM, at Panera Bread in Lewis Center.  You are welcome.

Bob W8ERD

Greetings. I have a node up and running in Pataskala. Would love to get the net extended to our area and perhaps all the way to Newark. Email here is k8rya@hotmail.com

sysupgrade file will work through the GUI, factory for TFTP. 

FYI: the current build is 3.0.0rc1 which is a move from our previous beta status to release candidate status on the 3.0.0 release.

Assuming no reports of major issues are submitted on rc1 it will transition to be the final 3.0.0 build.

Looks like I'm the first actual central Ohio poster in this forum so far. QTH is Pataskala, Licking County, Ohio east of Columbus and west of Newark, Ohio. From what I read in the latest news posting, looks like I'll have to replace my Linksys node before too much longer. Wonder if there are any meshers in Columbus? My node's getting lonely.

I'm currently running 1.0.1 code on my ubiquiti Airgrid.  I'd like to upgrade to the 3 beta code to see what it's like.  Is it possible to then downgrade back to 1.0.1?  Which files would I use to downgrade?

Looking for other meshers in the area.  Just picked up a WRT54G, will be playing with it in the next few days.

73 Bud KD6NOF