Thanks, That was the information I needed

KK6IVW

Peter T

Unless you turned off the dhcp server as you did the set up you node should give you an IP address when you connect a computer to the LAN ports that is set up to use dhcp. 

If that doesn't work connect your WAN port to your home router. Go into the home router and determine the IP address it assigned and from another computer connected to your home router connect using the assigned IP address. For example if my router assigned 192.168.1.103, I should be able to get in using http://192.168.1.103:8080.

As a last resort reflash the node using the tftp instructions on the install page. 

Clint, AE5CA

My recommendation would be to try a tftp install.  The bottom of the firmware installation instructions explains how to do it. 

Basically as you first apply power to the node you have a around a one second window to execute a tftp command to install new firmware.  I have used this method many times to recover from a bad install or a lost password. I do not recommend a 30-30-30 reset. It is almost guaranteed to brick your system.

Clint, AE5CA

For a linksys wrt54G v3.0 is there a way to look at the source code? I would like to know how the range of addresses is calculated for the 10.x.x.x network used in the final installation step

Comments please

KK6IVW

Peter T

I was able to do the following:

1. Access the Linksys box

2. Load the firmware

3. Access the linksysbox with an address of 172.27.0.1

Problem - when I rebooted the box I am not able to access the 10.x.x.x address

I am using static addressing so localnode does not work. How do I locate the 10.x.x.x address?

What is the valid range for the 10.x.x.x address in your software? What is the subnet mask? 255.255.255.248?

Thanks

KK6IVW

This should get you there

http://ubnt.hsmm-mesh.org/products/BBHN/ticket/55

I know this is an old thread but the discussion is one I am dealing with right now and trying to understand the mechanics of how it works.  What exactly happens "behind the scenes" when the "Gateway" box is checked, this is to say, how does the routing change across the mesh to route other remote mesh notes to the Internet connection on the router that has "Gateway" checked?  I've looked at the route tables in all of my mesh nodes and I see no changes in the routing that would tell those remote mesh nodes to route a call to www.google.com, for instance, across the mesh to the one node that has an Internet connection on its WAN and has the Gateway checked?  What exactly is the man behind the curtain doing on the Internet-connected mesh router to propagate it's Internet connection to the rest of the mesh?  I'm trying to fully understand how the routing changes when that is checked as I am trying to build a non-Internet Internet...I want to place a "fake" Internet on the WAN port of the one router with Gateway checked to do some testing.  So far it isn't working for me so I am clearly missing something in how the routing changes across the mesh when that magic "Gateway" box is checked.  Thanks.

73, Bill, N4SV

Conrad, can you provide a link to "Ticket 55:", as I'd like to read this issue over a bit more.  I put ticket 55 in the site search but came up empty.  You indicate a workaround is to add an external Ethernet switch, but until I try it I am skeptical this will work.  As I have proven in my testing not all NICs are susceptible, some work on the LAN and some don't.  The type of switch might work and might not and so doesn't seem a reliable workaround, and certainly can't be considered a "fix".  Guess I am looking for a more technical description of the issue to fully understand.  You say it is a hardware issue, that in releases beyond 1.0.0 you are utilizing the Linksys hardware differently and because of an issue in Linksys the LAN stops working properly.  Again as I said before, if you change your code and something breaks (and you can't fix the hardware) then it seems you want to revert that part of the code causing the issue back to the way it was done in 1.0.0, even if you loose some other added new functionality.  Something as basic is if the LAN works or not seems a pretty important feature to have to "work around" to make functional, don't you think.

Bill, N4SV

Reflashing one of my Linksys nodes with 1.1.2. the load failed all I get now is:

(1) rapid flashing power led

(2) slow blinking DMZ led

(3) no connection can be made to the router

Is there a recover method I can use to reflash and put it back in the network?

73 de mike

Hi Erich,

If you plan to play around with mesh, then just pick up a WRT54G and build a Pringles can antenna.  You can find the plans by Google'ing it.  These configurations are great for learning about mesh and constructing neighborhood networks.  

If, on the other hand, you plan to tower-mount an antenna and participate in a broader mesh, then I'd recommend you find others in the area who have done, or plan to do the same.  Likely they will be using Ubiquiti devices, many of which have attached, high-gain antenna and all run significantly higher power.  You will also benefit from learning which band the local mesh group is operating.  We currently support 2.4 GHz and 5.8 GHz.  Any given device will operate on only one band: Linksys is 2.4 GHz only.  Ubiquiti is 2.4 GHz (M2 series) or 5.8 Ghz (M5 series).  We continue to work on supporting other bands.  Eventually we intend to add the Ubiquiti M9 and M3 devices.

I hope this helps.  Have fun with it!

Andre, K6AH

If I am going to be looking for a device anyway, I may as well get something with 5GHz support too. My first step into SHF.

What makes a good quality antenna at 2.4 and 5 GHz? Any recommended sources? I don't have the tools or skills to fabricate my own.

Sorry but the WAP54G will not be able to load the BBHN firmware as it doesn't have the CPU nor sufficient memory as it's a simple access point, not a wireless AP/router like the WRT54G.

Insofar as using amplifiers -- unless you ABSOLUTELY POSITIVELY **NEED** it for a distant node, you are doing more harm than good, especially at 8-watts. This is not HF and more power does not always equate to a better signal. Use of quality antennas and better placement thereof will get you a far better link as history and experience has shown.