Ok,

I see from your other thread it was actually in Mesh AP mode now that you mention it was BBHN firmware.

Worst case you can always restore the BBHN image in the same manner as the Ubiquiti firmware (there is no option inside of BBHN to disable the reset button so that is fine and the reset is not expected to reset inside of BBHN)

If its mesh AP mode it should be by default be at 172.27.0.2 You would need to set your computer into a matching IP address such as 172.27.0.5/255.255.255.0 on the Ethernet in order to get to it from the wired port.

If you can't get to it that way firmware recovery would be your next easiest option as it blows the unit back to stock if you re-upload the image.

the bricked nano station was a functioning mesh node. as it is now, I cannot see an assigned ip address. the reset worked, before I flashed the Nanostation. I did not see an option to kill reset on the mesh setup.

the pico stations are airos.

73 mike

Doubtful,

I just posted to your other thread but I will put the relevant detail here for FIRMWARE RECOVERY MODE (see the other thread for soft reset details)

It is actually VERY hard to brick a Ubiquiti device (not impossible, but hard).... If you have disabled the reset button, or the reset button doesn't work you can download the Ubiquiti firmware from the Ubiquiti website www.ubnt.com/download and perform a TFTP re-flash of the unit by following the firmware recovery procedure.

http://wiki.ubnt.com/Firmware_Recovery

Currently all my nodes are running BBHN and not AirOS so I can't really test this use on this side for you.

It is actauly VERY hard to brick a Ubiquiti device (not impossible, but hard).... Unlike the Linksys units where you could very easily get to a point where you had to open up the case to get to the unit a Ubiquiti can be reflashed without unscrewing anything.

You can use the reset button at boot to reset to factory default (as long as you didn't select 'disable reset'

https://www.youtube.com/watch?v=0-h48wELJtw

IF that fails or you have disabled reset you can download the Ubiquiti firmware from the Ubiquiti website and perform a TFTP re-flash of the unit by following the firmware recovery procedure.

http://wiki.ubnt.com/Firmware_Recovery

Both methods can get your unit back to stock condition.

I managed to screw up a working nanostation and need a backdoor to reset it to a node. I fat figured it into MAP, hit reboot and now it makes a pretty good paper weight.

NS powered up, poe connected, lan connected tp lan port of another (functioning) node ... nothing happens. I do not see a wifi ap ssid.

Reset button does not function, no IP show on connected node.

have I just wasted 90 bucks??

73 de mike

The picostation connectrd to a lan port would not play nice.

I tried configuring the ps as:

wifi = ap

network = bridge

access to other portions of the mesh only by IP

wifi = ap

network = router

access to other portions of the mesh only my IP

it has to be DNS issues, but I am not savvy enough to figure it out.

I did brick one on the brand new nanostations by make it a mesh ap. it is now a hidden element. I can set the mac but cannot figure away to get  back into it to correct my fat  figure mistake.

I guess it becomes another paper weight. I seem to collect those easily.

73 de mike

If you use the QUICK REPLY, then it munges it all together without formatting.

If you want it nice and neat the first time, click the POST REPLY.

I know... PIA, and it bites me every so often too....

Hopefully on the next revision of the site, with Kunena forums, it will be better...

KTF

I am using a Ubiquity AM-2G16-90 sector antenna.  It is a 90 degree sector with 15 db gain.  The 90 degrees is subjective (The UBNT datasheet lists this as a -6db value).

I have links established with this node at 13 and 8 miles.  The 13 mile link has a similar setup on the other end and works quite well.  (20 db s/n ratio of 13 miles)

I have not go a any experience with any other antennas and the rocket but I can tell you that this setup works. 

Clint, AE5CA

Hello

I am realy new at this. I have a wrt54g 2.2. I uploaded the software and walked through it with the old buzzards guide. No problems. Until I hit the part about saveing the initial setup with the callsign. It would not take my callsign with out putting in a password. I used the hsmm like the other password. well now I can access the status page but not the setup page. I have tried every combination of everything with no luck. Is there something I am missing? Thanks for any help Kg4vhv john

Even for WRT54GL I can't get a serial number prefix from any online retailer.

Linksys only made two versions of the WRT54GL's: v1 and v1.1. Both currently work with the firmware. You only need to inquire about serial numbers with the WRT54G and WRT54GS routers. Both of the latter two can be found on Ebay, and a quick contact to the seller might be in order to compare the first 4 characters with this document (quick google search for "WRT54G Serial Number List"): http://www.dd-wrt.com/wiki/index.php/Linksys_Serial_numbers

If all known and purchased brand new WRT54GL devices have worked fine up to a given date of today, maybe it would be worthwhile to add that to the hardware selection document.

It's already there on page 1: http://www.broadband-hamnet.org/images/hsmm_docs/WRT54Shop.pdf

"Enough with the bogus statements of "I cant get them anymore".

Point taken.

Here is the problem:

The hardware document says version 5.0 and above of the WRT54GS devices do not work... yet if I'm trying to order anything online, I can't tell what version it is.  It is *very* true that Version 3 of this router is no longer made, though some can be found online.  Newest versions are version 8 I believe, which clearly is not going to work, but can't be determined online.

Even for WRT54GL I can't get a serial number prefix from any online retailer.

Bottom line:  to the new folks out here.. it is not clear, other than going to a store and yanking the device out of the packaging what is ok to buy, and what is not.

If all known and purchased brand new WRT54GL devices have worked fine up to a given date of today, maybe it would be worthwhile to add that to the hardware selection document.  Those of us who have never purchased one would not know what version we would be getting if we purchased one today.

Ken

i have six nodes up and running several applications including RPi asterisk, d-rats, and cams. what I want to do is put picostations on mesh node as a wifi ap for users to get to services.

this message is being sent using wifi connected laptop on picostatio connected to mesh-node, through the mesh gateway.

I can access the picostation via ip but not mesh serverrs

pico is configured as AP and network router. can anyone help figure what I am doing wrong???

73 de mike

Hi, my name is Ed, and I'm a newbie to mesh networks.  I have a WRT54GL, and am in the process of putting up an antenna.  Almost there, but not quite.  I'm located near Norristown in East Norriton (fn20hd).  Interested in seeing who else in the area is active here.

Hi all

Anyone interested in some long path testing to the Wickenburg area?  I have node set up but need to get a directional antenna for range.

Ron

I've seen everything from Omin's to high gain directionals used.

I'm looking at SECTOR's for a tower site (The NanoStations are basically all in one sector setups as well)

The AirGrid has a high gain unit built in, as to the NanoBeam/NanoBridge (dish based)

For demonstrations ive been using just small panel antennas (similar to NanoStation) and  small low gain omni's (on a bullet)  and for long range I did some testing with a grid (single polarity) that was originally hooked up to a Linksys before being swapped out.

A note about the 2 antenna ports, when running in a diversity mode they are intended to receive different paths between two similar type antennas (aka 2 omni, or 2 different polarities on a dish, etc) from the same sending station.

This 'multi antenna' ability has been (ab)used on the Linksys to use an omni and a directional dish, it works, but it wasn't how the devices were meant to operate.(Someone posted a much better explanation some time back in the forum)

So while it works keep in mind the unit will take the strongest signal it gets on either antenna.  This means one port could 100% mask another port (this could be what you want in some cases) while a remote party is transmitting.

Ive already seen setups of Ubiquiti do the same, and again it works, just be aware of the limitation that if two people are shouting at you  than you can only hear the loudest person.

If you try and ramp up to the much higher speeds (150mps) than you actually need both ports pointed to the same direction as it relies on the multi-path multi-polarity to ramp up to higher speeds (802.11n)

NAT mode is going to be your best bet unless you can re-number.

The mesh network needs to be thought of as a mini-internet.

Unless your devices can be on the assigned range generated by the device you need to do some form of NAT just like you would need to do to hook the com-van up to the internet.

The NAT can be either done on the BBHN node, or on a downstream router from the BBHN node (treating the node just like you would an internet provider)

Switching to NAT shouldn't change anything other than the fact that  some services will not work unless you put passthrough entries on the PORTS page for any services you want to run locally and they will be referenced to your node name to access.  This is how the mesh was ran by default up till version 1.0.0.

Using anything outside of the ranges assigned could cause unforseen routing issues across the board.