Hi all:

 I am trying to get Team Talk 4 up and running.  I have installed the server and client software and have configured the server.  

Question 1. Do I need to bind to a specific IP address?

               2. What do I need to do to log in to the server over the mesh?

               3. How do I advertise this as a service?

               4. Team Talk uses TCP and UDP ports 10333. How do I set that up?

I can login to the server on my laptop where it is installed by using localhost or my IP address or the name of my router  (N7FV-1)

What I cannot do is login from another laptop connected to the mesh.

All routers were re-flashed tonight with the latest firmware. 

I realize that I am asking to be spoon fed. I don't have an IT background and I am hoping that there is a more general tutorial out there that explains how all this works as the help document included in the firmware is still the same from HSMM-MESH, and now the options have changed but the help menus have not.

Thanks in advance

Cory

N7FV

I use an app on my iPhone called "Inet" it shows me what is connected to my network. I have an access point on my node so I scanned my network and it show port :8080 I opened the port and it allowed me to view  Mesh status and wifi status.  It gets unstable trying to run setup and  when connected to another node. 

So I was working on my node, and just got a raspberry pi. Trying to get them to connect to each other. However, I think I've messed my  linksys up. I think I put it in mesh gateway mode and for some reason I see two SSIDs now one with the IP of what the node used to be, and the name of the node. I can connect to either of them but get no IP address, and I'm trying from memory to figure out what it is.

Anyway I can reset this thing so I can upload the firmware and start fresh?

I wish I had seen this post before I flashed my PicoM2HP with the Bullet factory .bin.  The PICO M2HP is running well except for - as you have requested - the antenna and power setting.  If I leave the antenna at "right" and the power at default of "16" dBm all appears OK.   When I tried to change from default - Pico appears to have shut down the RF interface.   Thanks for all your effort into getting the Ubiquiti FW up!

Robert, WB6WGM

1) It must be running the AirOS.

2) Telnet or Putty into the node (default user is ubnt; password ubnt; default ip 192.168.1.20)

3) Run "cat /etc/board.info"

4) Save the resultant file and post it in response to this post.

Damn quick reply... fixing the formatting...

OK, I just cracked it open to see what I did.
I remember it was EXTREMELY easy to wire up.

=====================================================
There are 4 conductors in the cable coming from the display:

Red: -> 12VDC (back of the main power barrel)
Yellow: -> Pin3 of WRT serial port (1/3/5/7/9=bottom row)
Black : -> Pin10 of WRT serial (2/4/6/8/10 top row)
Green: N/C
=====================================================

For code just echo/cat stuff to /dev/tts/1 .

I had a script where it would awk (print $3 /etc/node.history) into a variable then for loop through with a 1 second delay between entry.
If you dont delay it, it just blasts the whole list, and with only 2 rows of display, you watch it scroll REALLY FAST and end up with the last 2 showing.

Then I cron job'd it to run every minute.
The issue with 1 minute cron is that if I get into a LARGE mesh, it starts again while the first list is still running, and they start interlace the previoous with the current, so maybe then up it to every 2 minutes, adjust as needed.

Unfortunately, I forgot and blew it all away when I upgraded to 1.0.0.
Paul and I worked on it again, but Ill be darned if I can find it now.
But there are the basics...

Jim
K5KTF

Sorry for the confusion.  Please any information or scripts you have would be appreciated!

You are wanting the other Jim, K5KTF. However, I did assist on re-writing the code that outputs to the display. I'll yeild the remainder of my time to K5KTF. ;)

Thanks!

That explains things.  I had no trouble sharing a drive but never needed to utilize the run command and associated entry to get access to a network drive.  Just something I never came across before.  On my home network the shared drive showed up automagically although I did have to map a network drive.

Onward and upward.

Kirk - N6SXR

We did meet and got three nodes talking to each other.

Now to figure out how to do something useful.

Thanks to all who made the new firmware possible. Here in El Paso, 3 of us purchased several Bullet M2HP devices. We will be using 5 of them to support the Susan Komen Race for the Cure to be held In El Paso on March 2. We will be using several of the Linksys devices as well. This years event will be held in an area with lots of buildings so the extra power will certainly help.

I will keep you posted.

Doug Garcia, AE5HE

Grazie Leo!

E 'sempre meglio avere un membro del team tradurre questo che fare affidamento su Google :-)