I see you are using the http://172.27.0.1:8080 URL to connect with your node.  This works as it should, but you should instead use http://localnode:8080.  If this doesn't work then you have a DNS problem.  It may still be possible to connect with http://localnode.austin.tx.us.mesh:8080 . If that doesn't work either then you have even more serious DNS problems.

Sometimes Windows does not do as it is told.  Sometimes it is configured in a way not entirely compatible with the proper use of DHCP supplied network parameters.  It may be just a simple issue of renewing your DHCP lease, which I have had to do myself on Windows (but never on Linux).  Otherwise you need to examine your TCP/IP configuration to see what may be preventing DNS from working properly.

I fully expect that if you go to http://10.1.2.3:1978 (substitute the actual address for W4BGH-002) it will work.

73

ad5oo

The 44.0.0.0/8 subnet, otherwise known as the AMPRNet, is a public address space and is in large part already allocated to other hams and regions.  As a public address space, these addresses are routable from the Internet, as are all other public addresses, and this is their purpose.

On the other hand, any mesh is a private network which is not dependent upon Internet routability.  The 10.0.0.0/8 address space is already set aside for this purpose, does not conflict with existing Internet addresses, and is the only IPv4 space large enough to adequately allow for automatic address assignment on a large scale.  The ability to connect to the Internet is generally considered a desirable thing, and to do so one must play by the rules of the Internet.

73

ad5oo

Thanks to the encouragement at SummerFest and the very nice documentation on the HSMM-MESH website, I have a tiny mesh network running here on the east side of Lake Buchanan.  It does not connect to much except itself, but I have enjoyed putting it together and configuring it. 

It did take me a while to get the routers - the Austin Goodwill Computer Store was a bust each time I tried, so mine came via eBay ($20 to $32 - but no gasoline expenses!). 

The next project is to get a little video going so we can keep tabs on the deer.

If I can help in testing or whatever, please let me know.

WB5BKL

Am I missing something? So far I have not seen anyone use the 44 block for their mesh network. Is there a reason for this?

I am just getting started and have configured two Mesh Nodes, called W4BGH-001 and W4BGH-002.  W4BGH-001 is a WRT54G V4 and W4BGH-002 is a WRT54GS V4.  The firmware installation seemed to go well.  I have W4BGH-001 configured as a Mesh Gateway connected via the WLAN port to a switch behind my Verizon Actiontec router.  W4BGH-002 is connected via a LAN port and CAT5 to my netbook showing an IP address of 172.27.0.5

I can connect to the Internet from my netbook just fine…so far, so good.  When I connect to http://172.27.0.1:8080 from the netbook I get a status page that shows the Default Gateway as W4BGH-001.  When I click on the Mesh Status button I see W4BGH-001 as a neighbor with an active link.

When I click on the W4BGH-001 link I get a “server not found” error failing to connect to http://W4BGH-001:8080/.  Also when I click on the OLSR Status button I get a “server not found” error failing to connect to http://W4BGH-002:1978/.  This doesn’t seem normal, but I can’t figure out any work-around.  I have tried two browsers: Firebox and Internet Explorer.  Any suggestions?

-73-

Bernie, W4BGH

Well, All I had to do was read ahead a bit. All three working now! Ready to explore.

I'll try to learn how to pass some kind of traffic now.

Thanks Again!

Trent/KJ4KAF

I have a couple Nodes working, but am just learning. A third one, I have lost contact with. In my learning process, I changed the node type from Mesh Node to Mesh Access Point. After I did this, I have not been able to get back in. My laptop sees the WIFI of the node, and I can connect to it via WIFI, but the URL I have been using does not work. 

A hard lesson..

73

Trent/KJ4KAF