The antenna use is software configured on one of the configuration pages.  Set for separate TX and RX or Diversity mode.  Diversity is the default.  It is common to have two different types of of antennas on a mesh node.

-Glenn

KD5MFW

Two different antennas, such as one directional, and one stock antenna are quite common, so I presume diversity mode is the normal setup.

So I have a dumb question.. the dual antennas... are they used as diversity antennas with mesh or is one trransmit and one receive? I could envision two directional antennas to extend the range but I have not seen anything on this website that might give a hint.

I would like to setup a large Mesh sometime in the spring. Is anyone interested in invading a local park and see what we can do?

Jim

KC4BQK

Physically changing the first 4 bytes through a hex editor. I used dhex and the WRT54G *.bin file.

Well, I managed to loose contact with one of my newer GL's that I just flashed with the latest firmware!

Was playing around in the settings and changed from mesh node to wireless client.

Hit save, it did its thing, and came back up saying something like the subnet has changed and I need to renew my DHCP lease!

Hmm, all fine and dandy, but I cannot log into it! 

Should not have been playing around with the drop down menu's!

Oh, was doing this messing up on a Windows XP machine running IE! In case that matters!

Any help will be greatly appreciated!

Louis - K5STX

Ok I have tested on an old Laptop with Ubuntu installed and had partial success. I was able to connect to the mesh and surf the net through a linksys router in gateway mode.

I was not able to check olsr status on the linksys, but the laptop did appear in the mesh.

OLSR web interface on the laptop showed the linksys in the routing table.

Things that need to be done:

Web interface scripts to modify the os to go into router mode (iptables ect)

maybe an HSSM-MESH.deb file for easy install.

Here are the steps if anyone would like to try it out.

Prerequisites: Working copy of Ubuntu Install OLSR and olsr-plugins, an a working wifi card.

Configure your wifi settings. I did this through CLI

1. Open a terminal

2. issue ifconfig and check the name of your wifi card,(wlan, eht1, ect.)

3. stop the network-manager $ sudo service network-manager stop

4. turn on wifi card $ sudo ifconfig eth1 up "Your device may be different"

5. Assign name and mode and ip to wifi card:

$ iwconfig eth1 essid HSMM-MESH mode ad-hoc channel 1 rts 250 frag 256 $ ifconfig eth1 10.62.34.145 255.0.0.0 ( choose your own private ip if you wish)

6. Temporarily change your name server (will revert after reboot)

vi /etc/resolve.conf and add "nameserver 8.8.8.8"

7. Change your computer host name to your call sign

vi /etc/hostname

8. Copy the olsrd.conf and olsrd.key file to /etc ( I copied it from my linksys HSMM-MESH router)

9. You should edit the olsrd.conf file.

remove any settings you may not need

change the interface name to reflect your wifi card mine was "eth1'

change the call sign

Have fun.

Anyone heard of any plans for HSMM-Mesh at Hamcation in Orlando this weekend?

I can bring my two units if so ...

Is there any reason we cant use any Linux based wifi enabled device to create a Mesh node?  It looks to me as long as you install dnsmask, OLSR and the required options it should work fine.  What is the reason it is married to the Linksys router?

Thanks.

I've had this problem before.

The solution I found that works is that in your Windows browser, if you want to type localnode:8080, you must type it as http://localnode:8080/. Without the http, it won't work. (At least with IE9)

If that doesn't work, usually an ipconfig /release & ipconfig /renew will fix the problem (you'd still have to type http://:8080/ if you didn't want to use the IP Address)

I think that might be caused by having used the same PC/browser on a non-mesh link first, and then hooking up to mesh without rebooting (or doing whatever it takes to get Win7 to forget the past.)

However, I never really investigated it any deeper, so I might be totally wrong.

I agree, having audio application sounds like the next natural step. I did some research on what could be used here and my first choice was looking at ECHOLINK. Imaging that we have a local ECHOLINK directory server on one of the routers. In this case every PC connected to the mesh network could run an ECHOLINK client the same way it is done on the actual global ECHOLINK network.

Unfortunately, their server software is not open-source as well as the protocol they use is not published. There was an old ECHOLINK linux-based client (which I tried on the actual ECHOLINK system with a great success): QTEL. You can google for SVXLINK for more information on it. I wrote a small function-limited directory server that supports a small subset of the ECHOLINK directory protocol, enough for QTEL to communicate with it. The server is written in LUA (I could not get it done in micro-pearl). LUA can be installed on the router without any problems, it has a fairly small footprint. When the server is running on the router QTEL clients could connect to it and see all who is currently connected. Then you can initiate a two-way audio connection with any of the connected clients.

Note that the server is not necessary as as far as I remember you could use an IP address of the target client directly. However, the server makes it much more convenient to use. Unfortunately, it does not support more sophisticated clients like ECHOLINK for windows, etc.

May be we can start a new thread on this if anyone has interest in it and some good ideas.

73, Nikolai

VE3NKL