Bob,

    We had similar problems at the Plano(TX) Balloon Fest.   Last year, while we were testing 3.4-GHz, 2.4-Ghz worked almost as well with high gain directional antennas.  Yagis and a 24-dB dish worked great for us despite having 50-70,000 people around the area.  Also, while 3.4-Ghz is not an option at the moment 900-MHz as well as 5.8-GHz Ubiquiti gear is.  Just depends on your pocket books at to switch bands or antennas.

        -Rusty-

Using WRT54GL v1.1  Was using vers 3.0.0, upgraded to 3.1.

Problems with DNS.  Set DNS suffix to "local.mesh" and get "localnode:8080" to resolve once on Windows.  Works randomly  or not at all after.  

Can get to local server only with localhost:<port> but not localnode:<port> or localnode.local.mesh:<port>

Fails connection with DNS_PROBE_FINISHED_NO_INTERNET

Tried ipconfig /flushdns and /release and /renew but no joy.

Is it just me or am I missing something.

Thanks,

Martin

We are finding that an omni node on a very high building in the middle of the city is slammed by hundreds or thousands of wifi access points and cell phones. To the point that its receiver is almost useless.  On channel 1.  

We also find that in areas of dense cell users such as a public event, that same happens. We are concerned about what will happen to our demo planned for the Dayton Hamvention.

Do others see this problem, and if so what solutions do you have?

I am aware of these possibilities:

1. Moving to channel -2, which may be possible in the future with the Ubiquiti boxes, but that is still only 3 channels, and we need 5 to get away from the splatter.

2. Use horizontal polarization.  Not as easily done, and more expensive for omnidirectional antennas. Yes, they do exist from several vendors.  L-_com currently has a sell-out sale going on. Normally $175, now $46. The antennas are bigger and heavier.

3. Use lower bandwidth settings.

4. Depend on proximity when your node is much closer than the other QRM sources, so the signal is stronger.

Any suggestions would be helpful.

Bob W8ERD

Hi all

I've been playing around today with IRC, and installed the server on one of my Linksys units easily with the help of Rusty's very straightforward guide.

However, whilst installing the package I noticed that IRC server is only one of quite a long list of available packages and that got me thinking. Is there a definitive list of available packages in the repository, and details on what resources are needed to support them (i.e. memory overhead, etc.)?

Many thanks in advance

Phil (G8YQK)

I have a conundrum.. I'm trying to install tunneling via the instructions here: http://www.broadband-hamnet.org/documentation/204-the-tunnel.html

I SSH into the node no problem.. Login, and copy the client line from the above page and tell it to execute.. And get this

root@N9MXQ-GATE:~

# No connectivity! You must have internet access.

Testing internet connectivity...

Would you like to proceed? (Y/N) y

This script installs the vtun client on a FRESHLY installed BBHN Mesh node.BBHN vTUN Client Installer - Version 0.9.1

00:04:05 (80.63 KB/s) - `setup_client_vpn' saved [13750/13750]
100%[====================================>] 13,750        80.89K/s

Length: 13,750 (13K) [text/plain]

HTTP request sent, awaiting response... 200 OK

Connecting to www.broadband-hamnet.org|71.42.236.91|:80... connected.Resolving www.broadband-hamnet.org... 71.42.236.91           

=> `setup_client_vpn'--00:04:00--  http://www.broadband-hamnet.org/download/attitude_adjustment/12.09/ar71xx/generic/packages/setup_client_vpnroot@N9MXQ-GATE:~# wget http://www.broadband-

hamnet.org/download/attitude_adjustment/12.09/ar71xx/generic/packages/setup_client_vpn ; chmod +x setup_client_vpn; ./setup_client_vpn 

---------------------------------------------------Broadband-Hamnet(TM) build 2 version 3.1.0

(Don't know why that pasted upside down)

How is it a node can resolve http://www.broadband-hamnet.org, download the package, and then go on to say it DOESN'T have internet connectivity?

HamChat "should" now be available in the package lists on UBNT gear.

I had missed one little place to put stuff, but that should be fixed now.

If you try it and it still does not show, email me (jim@k5ktf.com) and Ill get on it.

I know it IS in the Linksys package downloader, as I ran it myself on one of my nodes and it installed with ease.

73

Jim

I have managed to fix it by slowly comparing olsrd configurations between BBHN and HSMM-Pi

 A line needed adding to the HSMM-PI olsrd.conf file in the name service module. PlParam "dtd interface IP" "Node name"

I now have a mesh on ch1 running WRT56GL and Ubiquiti hardware talking to a mesh on Ch 6 using HSSM-Pi via DTD.

Still having a few routing issues but they all show up in each others mesh status pages.

A bit of extra info:

The olsrd.conf file on the HSMM-PI ahs this added:

#DTD Link
Interface "eth0.2"
{
Mode "ether"
Ip4Broadcast 255.255.255.255
}

The IP of the DTD interface is the same as the WLAN interface but with the second octet +1

• I can connect to the DTD linked node by IP address via the other nodes
• If I look in the OLSR status page of an RF linked node I can see the IP of the remote DTD linked node listed under Topology Entries with a link cost of (1.000/1.000) 0.100

Hi Folks,

I am doing some experimenting getting DTD link working between a HSMM-Pi node and a BBHN node on an RF Mesh.

Here is what I have go so far:

• Both node connected to a cisco switch that is trunking vlan 2
• Both nodes can see each other and olsrd traffic is flowing according to a quick tcpdump
• the HSMM-PI node lists the BBHN node as dtdlink.nodename.local.mesh
• The BBHN node lists the HSMM-PI node by IP not name
• Non of the other nodes can see the respective dtd link node.

So, how do i:

1. Get the HSMM-PI node to show up by name?
2. Get the other BBHN nodes on the RF mesh to see the DTD linked node?

Any suggestions?

Thanks

Jon

Hi,

Here is what I know from my experimenting:

1. No.  A tunnel client just needs to be connected to an internet connection. The tunnel is an outbound connection so a router should allow outbound links to be created without any extra config.

2. Yes.  If you set a tunnel server up on an RF node it has connections to multiple nodes and can route traffic across the tunnel as well as the RF

3. I guess that's on way of looking at it.  A tunnel server is part of a mesh so the tunnel is just a link to another node. Maybe think of it as having multiple directional antenna on a node that connect to other nodes that cant see each other.

4. Yes. any clients that are on an RF mesh will also appear on another mesh if they are linked via tunnel.  A tunnel just extends a mesh in the same way 2 mesh networks that are just out of range having an RF node placed between them.  The mesh just gets bigger.

5. This website has a lot of info. Just search for tunnel.

Basically, a tunnel just extends an existing mesh with another mesh.  Here is a specific example:

I have 4 nodes in a mesh in my little corner of New Zealand.  Each of my nodes list the other nodes as current neighbors and the services that they advertise.  Standard RF mesh setup where all nodes are in range of each other.

I setup a node that is in gateway mode as a tunnel client to N5MBM in Texas.  When the tunnel was created the remote nodes list suddenly had a lot of nodes in it.  The remote nodes list included:

• All the nodes that were connected via the RF mesh in the area around N5MBM
• All the tunnel clients connected to N5MBM
• All the nodes that the tunnel clients connected to N5MBM could see either over RF or via tunnels of their own

Once the tunnel was up, I could connect to all the nodes in the list and see the various services they were publishing

Does that make sense?

Jon