Is the following a problem with release 1.1.1  ??

I have upgraded to the new release on two nodes..  I place both into the NAT mode.

When I have N1 connected to my laptop I see N3 in the Mesh Status. I cannot click on N3 in the mesh status from N1 to connect to N3 wirelessly.  The Laptop looks like it is still looking for N1 status..

I have tried various methods to connect wirelessly to N3 without success via the N1 Node.

This is a problem for us because we plan on putting a node on a tower and plan on possible changes to it wirelessly. We are only going to supply power to it.

Side note : Next to the N3 node I see   N3 (mid).      What is this telling me ???

Leon K8ZAG

I have two WRT54G nodes, one up above roof level and the second one in my ham shack (connected to the internet). The upgrade from v1.0.0 to v1.1.0 was easy, I connected my laptop to the shack node and logged into the rooftop node - refreshed the firmware list and downloaded the v1.1.0 software. I used the WiFi on my laptop to complete the configuration of the rooftop node. 

When I tried the same procedure to upgrade from v1.1.0 to v1.1.1, it was a no-go. I was able to remotely log into the rooftop node but when I clicked the Refresh button, I kept getting the response that there was no route to the internet. 

I have an ethernet cable plugged into the LAN port of the rooftop node (coiled up at the base of the tower), so I tried plugging it into the LAN port of my shack node. But it still reported that there was no route to the internet, although the "dtdlink" entry was listed on the mesh status screen. 

In my case the solution was simple, I just plugged the ethernet cable into my laptop and uploaded the v1.1.1 software directly. Hopefully not many people upgraded remote nodes with the v1.1.0 firmware or they may have to connect directly to them to upgrade to v1.1.1. 

  73, AL VE3RRD

I am unable to use the Secondary LAN port of the nanostation. It lights up and shows connection but unable to get an IP from it. My question is this used as a WAN Port? Anyway to config it to vlan2 = DTDLINKING (device-to-device linking)? 

Thanks guys for all your hard work!

Eli KD8RBH

Hello Everyone,

With yesterday's release of the v1.1.0 firmware OLSRd Secure Support is back in the mix.

This is one of the topics on my things to investigate list and I am looking for guidance on how to get started.  My kickoff questions include:

  How do I generate an OSLRd secure key?

  How do I configure my node once I have my OSLRd secure key?

      Where exactly (file path?) should the key be placed on the node?

      What other settings or configuration needs to be completed?

If this isn't the right place to post this topic, please let me know where it should be moved.

Bob, KO2F

If I wanted to post a message about selling some of my WR54GS units prebuilt nodes, would there be any problem of me posting it here or the Facebook page?

I am looking into switching to Ubiquiti devices instead for higher power.

Thank you Gentlemen.

After a big bowl of soup beans and cornbread I trird that and it worked.

Been a rough day at work and my patience was running a little thin.

Sorry...

I just flashed my node, Conrad. It's the default initial configuration. WF8S, you need to change the node name and password. And upon reboot, it will go into mesh mode

Are you sure it's mesh ap and not default configuration mode?

Upon upgrade the node defaults to  unconfigured

The BEFW11S4 is a closed, proprietary, architecture, while the WRT54G is an open source Linux based router.  BBHN can do nothing with the proprietary device.

Andre, K6AH

I just upgraded one of my perfectly running mesh nodes to the newest firmware and upon rebooting is too is now in MESH AP mode with a 172.27.0.1 IP address.

Any ideas?

Buddy of mine at work had this old router and knew of my HSMM project and just gave it to me.

I don't see it listed on the "Useable" device list.

Any useability at all for HSMM? 

If not just going to trash it as I am moving towards all Ubiquiti devices and probably going to sell off the other 3 WRT54GS's I have.

Thank god for Google!!!

http://wiki.openwrt.org/doc/howto/generic.failsafe

I have a WRT54GS version 1 router that had DD-WRT firmware on it. I followed the GUI install of BBHN firmware but now after the router reset it is in MESH AP mode ( ip of 172.27.0.1 ).

Can't find my saved link to how to do a master reset thru the telnet access way into the router.

Anyone have that link handy?