This last Field Day we ran VOIP between 7 phones using Direct IP Calling.  The devices used were Grandstream Ht-701's, HT-286 and a Grandstream IP Phone.  These  worked fine except for the long memory number needed (longer than some phones were capable of).  Next year we will have a switch on one of the routers.

We had three WRT54GL routers running v1.0.  In two cases, the router owner connected the router to the Internet and used the built-in Download Firmware option.  In the third case, I chose not to connect the router to the internet, and instead downloaded the file to a laptop, and then manually uploaded that file to the router.  In all three cases, all appeared to go well and the routers indicated they had successfully been updated to v3.1.0. 

But... none of the routers could see each other afterwards.  Closer examination indicated that in the case of the first two routers, even though the router indicated the current version was 3.1.0, if you scrolled to the end of the SSID field, you found that "-v1" was appended to the SSID.  Even after correcting that, the routers still couldn't see each other.  There were no other obvious problems.  None-the-less, that SSID issue made us suspect the v3.1.0 software update hadn't replaced all the v1.0 code properly.

So... we manually uploaded the file to the first two routers to over write the firmware that had been installed using the integral download feature.  After that... all three routers saw each other fine.

If this had happened just once, I'd be inclined to write it off as a fluke.  But in this case it involved two routers experiencing the same problem.  And involving the same model router. This version has been out a little while now, so I'd have thought if there is a bug, it would have been caught by now.  But I don't know how frequently people use the download feature or how often they do that in combination with an update from v1.0 rather than an intermediary version.  In any event, thought I'd report our experience so you can consider whether this is an issue that needs to get chased down.

Dave

You can find information on www page

http://wiki.openwrt.org/toh/ubiquiti/nanostation

where is information that you can upload firmware on LiteStation2:

"LiteStation 2 - uses openwrt-atheros-ubnt2-squashfs.bin . Steps for flashing are the same as NanoStation2"

for example:

https://downloads.openwrt.org/attitude_adjustment/12.09/atheros/generic/

https://downloads.openwrt.org/attitude_adjustment/12.09/atheros/generic/openwrt-atheros-ubnt2-squashfs.bin

73 Waldek SP2ONG

Good morning!

I'm a newbie, just having flashed two Linksys routers for version 3.1.0.  One router is a WRT54G, version 2; the other is a WRT54GS, version 4. 

I originally flashed these on a Windows 7 computer, and the install went well.  However, when I tried to log onto http://localnode:8080, I kept on getting an UNABLE TO CONNECT display on the browser (Firefox) to complete the setup. This happened for both units.  So I went into troubleshooting mode.

I first connected the routers to a Linux computer (Ubuntu 14.04), and was able to connect to http://localnode:8080 to complete setup, as per the install instructions. 

However, I can no longer connect to http://localnode:8080 on EITHER computer.  Both work fine as network routers, so I can connect to the INTERNET.  But the MESH connection simply doesn't work. 

On the Windows computer, I tried "ipconfig /release" and then "ipconfig /renew" when disconnected from my home network (hardwire connection).  According to ipconfig and McAfee, the WRT54GS router has an IP of 10.161.13.233, and I still can't lon onto localnode:8080.  And the router will not re-connect to my home network unless I run "ipconfig /release" and then "ipconfig /renew" again. 

On the Linux computer, it simply won't connect anymore.  I have not tried the Ubuntu equivalent of "/release" and "/renew".  The WRT54G router works fine for hardwire connection to the INTERNET, and I can detect the Broadband-v3-20 Hamnet by wireless.  But I can't connect to http://al1q-1.local.mesh:8080/, even though it shows up in Firefox as "Mesh Node Administrative Console" (see the screen shot below).

I also tried a hard reset on both routers.  No luck.  And I have rebooted both computers as well -- again, no luck.

I clearly made a mistake somewhere on the Linux box, but I'm not sure about the Windows box.  I thought that maybe the McAfee firewall was the issue on Windows, but turning that off makes no difference. 

Any suggestions would be welcome. Thanks in advance!

73, Jeff AL1Q

I'm trying to get a couple cams to work for a demo in a couple weeks.. Both have HTTP interfaces that can be accessed by typing their respective ip address in the location bar of the browser when the computer and cams are on the same MESH node LAN. 

I've put links up, and forwarded the ports the way it should be done, but when I go to another computer connected to a different MESH node and click the links, I get nowhere. The links are also a no-go on the computer connected to the same node as the cams...

Any ideas? I've beat my head against it long enough.. And have read, and re-re-read everything I can find on the site..

The 79x1 series are xml based.  The 79x0 series phones are text based.  I've got the configs for the 79x1 phones on my server. Let me see what can be done.

I do not have anything for 7912's at this time.  Sorry for any inconvenience caused.  I got my configs from the cisco support website.  You will have to create an account there to get them straight from the source.

Sorry.  I cannot delete the extra lines anymore since there are other posts (I have to split them and then delete the split thread...which would result in other peoples replies being deleted).  My recommendation:  Do not double, triple, or quadruple click the post/submit reply button.  Just press it once and let it do it's thing no matter how long it may take.

And I see we revived a dead thread too.  Let's try to refrain from doing that too.  ;)

I recently upgraded to a Ubiquiti EdgeRouter POE. One of the reasons for the upgrade was because it can be configured for different subnets and/or WAN connections. I'm somewhat familiar with the mesh firmware, running on Ubiquiti hardware, but because there's not a whole lot of interest in my area I haven't done very much with it.

With that in mind, here's what I would like to do: 1) Get a bullet configured as a gateway and tunnel server. 2) be able to access mesh network from my home (NAT) subnet. 3) Keep mesh traffic off my home subnet.

High level overview of the router:

Eth0 = WAN address. Firewalled and configured for native IPv6 (Comcast ISP). DynDNS configured and verified working.

Eth1 = Desired port for mesh node. VLAN capable, although I'll need to read up on exactly how to go about that. Would prefer not having to get another managed switch for breaking out the gateway VLAN.

Eth2 - Eth4 = home network, Eth2 and Eth3 go to 8 port managed switches. Eth4 runs an access point.

If the mesh node can't be a gateway and tunnel at the same time, that's fine. The goal is to see if anyone else in the area would be interested in connecting up to the mesh, then they can use my tunnel. I'd also likely be running an IRC server and possibly Asterisk server. I understand that on my LAN I'd likely have to either use the IP address of the local node, or build a Hosts file, since DNS will be a problem, but that's fairly straightforward.

Thoughts?

It is a percentage of packets that DO NOT need to be resent. i.e. LQ=25% means 75% of packets need to be resent. This means slower speeds and longer transfer times.

The 7940 and 7941 are the same phone just the 7941 has more lines. Changing the firmware is required for both the 7940 and the 7941. They use the same files and the same process. The files you need can be found here on the site. http://broadband-hamnet.org/download/7940/NG5V-Cisco-11-12-2014.zip 

Hope this helps.
KE8AVJ

My apologies I was confusing the 7941 and 7960. The 7940 and 7960 are the same with the 7960 having more lines. The files you need ARE different. The 7941 and the 7961 use the same files. This site has some good instructions on changing the phone and getting the right files.

http://www.adrianandgenese.com/blogger/2011/02/16/how-to-upgrade-or-convert-a-cisco-ip-79xx-7940-7960-794x-796x-797x-phone-to-sip-or-sccp/

Easiest way to power through the Ethernet cable. I used blue and blue/white as positive. Brown and brown/white as negative. Cut at both ends of the cable so no power running back into my computer. Twisted the the blue two together, and the brown two together. Soldered the power supply at one end and the plug on the other.