Problem reverting to Linksys firmware

Hello all,

I have a Linksys WRT54GL V1.1 with the HSMM firmware 0.4.3 installed that I need to restore to Linksys

firmware to permit an alternate use.  I have the current Linksys version 4.3.0 bin file dated 20130308

downloaded and saved. LAN mode is NAT.

A proble arises When going to the Administration page and then the Firmware Update portion, browsing to

the saved Linksys file, and clicking Upload. The file transfers for a couple of minutes and completes by

giving the message:

Firmware CANNOT be updated
the uploaded file is not recognized

No internet connection is available to the router to use the Download feature but there is internet

available on the client Windows XP PC via wireless to another router.

What I have already tried without success:
1. The Linksys TFTP MFC application - no joy - responds "Unable to get responses from the server"
2. The Windows TFTP application - no joy - responds "timeout occured"
3. The 30/30/30 reset
4. The NIC in 10MHz mode

Your suggestions would be much appreciated.
73,

Richard

I'm just getting started and need help. I have loaded the mesh firmware on my wrt54gs v1.1. It shows  up as broadbandhamnet-v1 on my wifi list under devices (mac os x mavericks). If I select it and try http://localnode:8080/ I get 'no network'. Help?

Thanks,

Tom

W6TPA

Depending on what you're trying to do, you may also be able to use a WRT-54G based BBHN mesh node to provide internet into a Ubiquiti based mesh network. 

It's easy to see how you'd do this if the mesh node is linked in to the mesh through RF.  Could you use the 54G to do this if it was connected to a Ubiquiti via a wired connection?

KA0PIZ, no problem. I just wanted to make sure everything was clarified. Welcome to the forum, and if you have any questions, feel free to ask. Happy meshing! :)

A correction to my previous statement:

The internet is on tagged vlan 1 (I'll go back and edit the original post).  Sorry about that I've been doing way to much work on a different part of the device build and mixed the two in my mind.

All un tagged packets are treated as LAN packets.

The setup you can run will depend a lot on what your router supports and how you wire it up.  Once you get away from using a smart switch to break out the networks your getting into advanced networking which you will need to do some design on your side to integrate.

if you use a vlan interface on your router it will need to listen on VLAN 1 and allow access from vlan 1 to the internet.  Exact setup will be better rendered to you by your router forum on this step.

For local pc's to the internet if you plug them all in and put dhcp on the  Ubiqutiit you would end up with a setup where packets go from local PC to router to Ubiquiti back to router to internet.

Another option is you can set the mesh node in NAT mode and use static routes on a few if your local PC's and have them route to the mesh that way rather than directly exposing the local pc's to the mesh.

A key note you only need is WAN port for a node that's going to provide internet access or allow access from LAN to internet.  If you don't need those you can get away from it to reduce cost.   You can also have multiple Ubiquiti devices (if they are at the same location) on the same smart switch.

On my system at home, I am using a GS108E.  This is the eight port version.  There is also a GS105E.  I have used both and they do work.

The setup is not exactly obvious. When I set up my GS105E i used the following:

Port        Connected to:

Attachments
 clip0008.jpg [80 KB] ::
 clip0007.jpg [80 KB] ::
 clip0006.jpg [80 KB] ::
 clip0005.jpg [79 KB] ::
 clip0004.jpg [79 KB] ::
 clip0003.jpg [87 KB] ::

I am very impressed with the performance of the Rocket/Sector Antenna combination.  If you need the wider coverage angle then I recommend this combination.

I will tell you that my favorite UBNT device is the NanoStationM2.  I have lso used a pair of these on my 13 mile link.  With excellent results.  

I have been very unimpressed by the AirGridM2.  The BulletM2 is a decent device if you have an existing antenna that you want to use.  I replaced a Linksys box with a Bullet while using the same antenna.  The performance was significantly better with the Bullet both on receive and on transmit But its performance is not as good as the Rocket or NanoStation even with a grid antenna.  

With a NanoStation on one side of my 13 mile link and an AirGrid on the other, the Nano was seeing the AirGrid with a high LQ.  The AirGrid did not even detect the Nano.  After switching the AirGrid for another Nano, I had a working link.  The Rocket/Sector antenna combo has given me a few extra db of signal.

My thought is the NanoBeam is going to be a hot performer for long distance links.  I am looking forward to it being supported in the next release.

Having used the Ubiquiti gear, I would be hard pressed to use the Linksys Hardware in an outdoor setting.  I believe that by the time I get a Linksys box, a waterproof enclosure, coax cables, and antennas, the Ubiquity is cheaper to install as well.  

Clint, AE5CA

UNBRICKED!

I connected the NS to POE on secondary port a laptop set for dhcp on main port.

the laptop was assigned 172.27.2.19 with a gateway of 172.27.2.1. I set browser to 172.27.2.1:8080.. node came up.

it was set to wireless client and nat. reset to mesh node and direct 5.. back in business.

now back to trying to set airos picostation up as a wifi ap for Linksys node.

thanks for the help.

73 de mike

In order to pull the WAN port out like you would on Linksys you need what is called a "smart switch"  or "vlan capable switch"  or a "VLAN capable router"

The WAN port is assigned to an 802.1q VLAN of 1.

If your router can add a virtual network for the VLAN of 1  you can use that direct, otherwise a smart switch (such as the Netgear GS105e GS108e)  which allows you to assign a port as a 'trunk port' with VLAN 1  and than assign another port as a "WAN" port (assigned as a PVID id of 1 -- untagged

I think we have a setup guide for the GS10xe sitting around somewhere if you end up needing it. DD-WRT may support the VLAN tagging on its own, but that is better referred to the DD-WRT support team on that question.

Using the recovery mode the node comes up on 192.168.1.20 for TFTP re-flash.

http://wiki.ubnt.com/Firmware_Recovery

What happens is once you hold the reset button long enough that it goes into RECOVERY mode it brings up a recovery mode at IP address 192.168.1.20 that supports TFTP upload of the firmware (BBHN or AirOS)  --- this mode ONLY supports TFTP upload, no web access, nothing else, but ping, and TFTP (as shown in the link above)

the problem is that I cannot get any IP connection to the NS. So there is no way to reflash that I can find.

73 mike

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