Thanks for the "Thats what I thought" reply.

Being very new to this, I just wasn't sure if it was advisable or not to do it this way.

I know there are problems doing this with other applications.

But your cleared up my questions.

Now I just have to get the antennas up and connected.

Not sure how much good it will do, since there are no other nodes near me.

But will get them up and see what happens.

Bob

W8RID

KB9ZMR,
Please take time to read the forum and posts and/or do research before making a claim like that. There are five versions of that router (WRT54G3G/WRT54G3GV2 Mobile Broadband router). Earlier posts in the same category on this forum (Page 4 & 5), show how to get the WRT54G3G-ST and WRT54G3G-AT to work. The firmware located on the homepage is only valid for the WRT54G3G (non-ST, AT, EU, or V2-VF). With that said, do not expect it to work with any other derivative of the WRT54G3G series.

Picked up a cheap Linksys WRT543G3-ST on ebay. I could not get the WRT543G3 firmware to load on it. Just got the generic "Failed" pop up screen.

Need help getting started with HSMM-Mesh? Just can't get the firmware to "take"? Wanna find out if that old WRT54G router can be reborn as a High Speed MultiMedia (hsmm-mesh) network node?  Only have one node and no one to mesh with? :(  Have an extra node you want to sell/trade?
Join Jesse Alexander WB2IFS/3 and a gang of other Mesh "Elmers" (Mesh-mers?) at Unallocated Space (http://www.unallocatedspace.org/uas/) 14 June 2014, 1000-1500L for a Meshfest! We'll be hacking routers, and helping people get up on Broadband-Hamnet!
Where: Unallocated Space, 512 Shaw Ct #105, Severn, MD  21144
When: 14 June 2014, 1000-1500L

Hello Steve,

Have you put a "smart switch" (vlan capable) switch connected to the node so you can pull out the WAN port to a physical port to plug into your connection to the internet?

Any cable that is plugged into the Ethernet port is treated as part of the "LAN" unless it speaks in 802.1q tagged VLANS to tag traffic as "WAN" port by putting a "VLAN ID" of 1 on the packet.

A couple forum posts previously talked on this subject a bit more in depth.

We just put the UBNT M5 release into beta test. I can't commit to a date on the general release yet, but it should be soon.

Hey, we need assistance from owners of the following Ubiquiti M5 (5.7 GHz) devices:

• Nano Beam
• Bullet HP Titanium
• Rocket HP Titanium
• PowerBridge

We currently don't have any of these, nor do our regular beta testers.  If you do, then you could be a huge help to run a few tests for us to confirm we've accounted for the unique peculiarities of these devices.

Please respond to this post if you can help.  The testing is straight forward and shouldn't take a lot of time.

Thanks and 73,

Andre, K6AH

UPDATED: 5/9/2014 with current needs

Much of what accounts for the differences between Ubiquiti devices is the way their antenna gain and power level is handled.  There is a data sheet in the filesystem of UBNT devices when they are running their factory operating system, AirOS, which identifies key parameters we need to add support for these devices.

The following table describes those that we still need.

M3 Rocket HP Titanium 

PowerBridge

M5 Rocket HP Titanium

PowerBridge

M9 Nano Station

Nano Bridge

Rocket HP

Rocket HP Titanium

So, if you have any of these devices, we are asking for your help in running the following procedure:

1) It must be running the AirOS.

2) Telnet or Putty into the node (default user is ubnt; password ubnt; default ip 192.168.1.20)

3) Run "cat /etc/board.info"

4) Save the resultant file and post it in response to this forum thread.

As you can see, we are nearing the end of this exercise, so thanks for the tremendous support you have already been.  As the final responses come in I'll continue to post periodic updates to this chart.

Thanks and 73,

Andre, K6AH

Hello

I just got one brand new airgrid and a brand new NanostationM2.

I flashed them with the appropriate firmware but they both have a similar problem

The Internet gateway doesn't work. But when I setup a wrt54gl as an internet gateway,  the airgrid node and the NanostationM2 node can connect to the Internet via the wrt54gl gateway. .

Can you help me with getting the airgrid or the NanostationM2 to work properly as an internet gateway  ?

Regards

Steve

You could try using Wireshark to capture the ip when the node boots up.  I have used this on many routers that I do not know the IP, or failed to write down when I configured for some test.  Just direct connect to it and fire up the software on the correct interface and the unit should announce it's IP shortly after you apply power.

Try this...(I just thought of this)
Go into failsafe mode (we divert after we type "mount_root") on the "not-quite-bricked" router, and in the /etc/nvram file, change/add a line that reads "config=MESH". Next, copy and paste the contents of the /etc/config.mesh/ folder over to the /etc/config/ folder (overwriting everything). Then, reboot.

If that fails to work, the only other option I can think of is to tftp the firmware back to the router.

Try setting the ip of the computer manually.

the old 2 node trick is no longer valid because the AP now gives 10.x address unless you put in NAT mode.

Have you tried plugging the two nodes together via an Ethernet cable, and either connecting via wireless or a hard Ethernet cable connection to the AP, and navigating to http://172.27.0.2:8080/ ?

Thanks for that information. I had searched for the word "brick" without finding what I needed.

However, I still did not find the solution to my problems. I still am unable to access the WRT54GS that is now an access point -- not by connecting to it directly at 172.27.0.100 and not by connecting it by ethernet cable to the router that is operating as a mesh node then pointing the browser to 172.27.0.2:8080. In fact even the one that is a mesh node is accessible not at 172.27.0.1:8080 but at 10.110.144.121:8080 (and I am sure that I did not change it to that); the one that is now an access point is not accessible at 10.110.144.122:8080 when connected by ethernet cable to the other one either: in fact

arp -a

shows 10.110.144.122 as the address of the laptop's Ethernet interface and shows nothing with a MAC address corresponding to that of the access point.

A further problem is that the WiFi scanner sees the access point on Channel 6 rather than on Channel 1. I did not change it from whatever the bhnn firmware set it to: the only things I changed were the SSID and then, when it was working OK as a mesh node, I changed it to an access point without changing anything else -- not even the IP address.

Question has already been asked many times on the forum before. You can also find your answer on the website. Please check FAQ --> Network FAQs --> I changed my unit to mesh AP and I can't get back in

or

User Documentation --> How to use the web interface --> Mesh Access Point considerations