Afternoon all,

I am recently into the mesh side of things and seem to have made a mistake at some point I think?  I have two nodes now, one a WRT54Gv3 and the other a WRT54GSv1.1, both running 0.4.3 FW.  Both can be connected to via lan cable, both can see the other if you connect to each one respectively and can be seen from the other node, to a point.. I will explain and please feel free to let me know if what I am seeing is "normal."

If I go under the Mesh Status button I can easily see the second node but if I click on it, the second node, I get the page stating that it cannot find the server on kd5wek-moble(GS). I did swap the nodes about and try using the GS to reach the G and its the same way, under mesh status, it lists the second node and has a link for the name but again when clicking on it the same page appears ?  I am hoping to eventually make this a mobile or portable node but am trying to ensure that they are operating as designed.  I am wondering if this has to do with advertised services ?  

I also appear to not be able to hit the node using the http://localnode:8080 link but have to use the ip address.  When attempting to access using the localnode it immediately shows a www.localnode.com:8080 so not sure why this is?  I did try using a different browser, IE8, and it also has issues accessing using the localnode link? Mind you I did some more checking and yes I did read the help file regarding having Javascript and page redirection enabled. This appears to be the default for Firefox as there is a checkbox to give the browser the ability to warn when a page is redirecting.  

I am able to see the other node using the WiFi scan and am also able to see the SNR info as well.

My other question is regarding the OLSR status button..

I have been browsing the forums about the OLSR button being greyed out and read that this is normal due to only using one node and that till more than one is connected OLSR has nothing to report, having only one till recently that was the case.  However I have two now and the button is active BUT when I click on it I do not get a page, I get that Firefox was unable to find the server at kd5wek-home or kd5wek-moble depending on which node I am logging into, having tried it both ways.  Previously when I took this same node, the G model, to last months digital wednesday I was able to select the OLSR button and see information there?

So I guess I am curious to know why the OLSR Status is not producing information when previously it was as there is more than one node here and also why I cannot see the page for the other node when I click on the link under mesh status?

Both nodes have been flashed using the appropriate packages, the G and GS, I even attempted an update the the GS using the trx file in case something was not quite right, this did complete and I have been able to get back in successfully.  Both nodes have been left with the default settings, aside from changing node names, no they are not the same and the passwords.  Both nodes have been as far as 15-20 feet to within 5 feet currently.

So any information would be greatly appreciated and if anyone has any tips, tricks, hints I would love to hear these as well. 

Take Care KD5WEK, Adam

I am just getting started with Mesh nodes myself, so take my suggestions with a grain of salt. I too had something similar happen. It all revolves around proper DNS resolution. 

If you try http://nodename.austin.tx.us.mesh:8080, I bet it will work. Just replace the "nodename" portion of that URL with the real node name you configured it with.  If your wired LAN connection is trying to use a different DNS server than the node or domain search suffix other than austin.tx.us.mesh, you will have issues. 

Hope you get it worked out. Please let me know if I was any help. 

Thanks

Jesse

OK, first, lets fix Firefox from adding the www and .com:

1. In the Location/URL bar (where you would type in www.somewebsite.com), type about:config and press "Enter"

   • The about:config "This might void your warranty!" warning page may appear. "Click I'll > be careful, I promise!", to continue to the about:config page.

2. In the Search field, type "browser.fixup.alternate.enabled"

3. Double-click the "browser.fixup.alternate.enabled" preference to set its value to false.

There may also be entries related to browser.fixup to add www and com. Watch and be careful, or you may have to reinstall Firefox

Next, the DNS issue.

Under the menu (to the left) User Documentation, Using the Mesh ( http://www.hsmm-mesh.org/documentation/96-using-the-mesh.html ) at the bottom you will find some useful things to do in Windoze to help work around the DNS problems. (scroll to the last black box/command prompt screenshot, and the paragraphs under that).

Another "trick" to see if its the DNS buggering you is see if you can find the IP address of the target node, and use it in the URL with :8080. If that works, then its the DNS on the machine you are on, and the webpage given above should fix it.

Hope this helps.

KTF