Hi,

I have wrote in http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-18-how-we-used-hsmm-mesh/topic-660-hsmm-mesh-and-amprnet.html

about me local Amprnet gateway connected with local Mesh Nodes network and this configuration allow connect via separate tunnel Local Mesh Nodes Network <-> Other Local Mesh Nodes Network

I have attached picture with example this configuration which we use

http://www.broadband-hamnet.org/components/com_ccboard/assets/uploads/17965_2e8f4252eb1e202acaa597b0b4561647.png

Yes, that's for fine tuning.  When shooting a few miles I'm hoping the laser will give me a pretty close alignment.  Then I can tweak from there.  I'll see in the next couple of weeks depending on the weather.

Kirk - N6SXR

On the Status page click on the [Auto] button that's next to the Signal/Noise readings.  Watch it go up and down as you move the yagi.  It's not real fast but it's useful.

        -Rusty-

Kevin

Any use of the 44.*.*.* would require registration for each node since you just can't willy nilly take any ol' address out of that IP space.  There's also a time consuming period to get an IP from that address space from the powers that be and (at this point) an uncertain possibility of receiving that address given that I'm not sure if anyone is actually maintaining the ampr.org domain or the 44. address space.  Maybe they are -- I just don't know nor have I seen any activity.

Secondly, as I recall, the 44.*.*.* is divided up by US states and other regions/countries.  We may have already blown the address space allocated to Texas with the number of nodes here.  It may have been used up just by KD5MFW alone. :)

Thirdly, (probably the most important) that address space is for full routing on the Internet, not all mesh nodes will be nor need to be connected thusly there's no need to use up such a limited resource.

Using the private 10.*.*.* space and NAT on the WAN interfaces, when used, we have few worries with regards to IP address collisions and no waiting period for registration of an address which allows people to come and go as they will.

There's probably other reasons but those are the ones that come to (what's leftof) my mind. :)

        -Rusty- 

Rusty,

Normally i would not have two interfaces running but this is the system I use for flashing routers and adding in s/w for the various options (like the USB add on), etc.  When in actual use I will disable the wireless interface.  I would just like to be able to have both running at certain times.  Just makes things easier.

I will try your suggestions.  And although I have used Windows forever I am not adept at manipulating routes.  It's always a learning process.

Thanks!

Kirk - N6SXR

Kirk,

    Currently, when you plug into a node's LAN port you are given an IP address for a small subnet that is your LAN. Apparently that is all that Windows™ networking allows you to see. What you need is a default route for 10.0.0.0 / 255.0.0.0 (netmask) with a gateway of 10.230.5.145 (if I did my math right :). This should get you to the rest of the mesh. Another issue befalling you is that you may not have access to the DNS for the mesh as well. This is why we suggest that you not use two network interfaces while connected to a mesh node unless you know how to manipulate the internal routing and DNS server tables within your PC's operating system. Windows especially has a hard time with multiple active interfaces.

    I am not a Windows person so I can't give you the commands to adjust your network settings. My suggestion would be to disable/turn off your PC's wireless interface when connected to a mesh node.

        -Rusty-

Look at Hamwan.org

https://www.hamwan.org/t/tiki-index.php

A Polycom 501 provisioning video would be greatly appreciated!

Thanks

Fred

This may be more related to XP itself but since I am having this problem when using BBHN...

I have two network interfaces on my laptop running XP..  A 'N' wireless for my local internet and my 10/100 for connection to my router(s).  When I have both interfaces enabled I can reach the internet and my network hard drive.  What I can't do is access my BBHN router(s).  It just sits and spins and eventually times out.  If I disable the wireless it will default to the 10/100 and work fine for accessing the BBHN.  I've looked but am still confused on the proper settings for proper operation with both interfaces enabled.

The netstat -r command shows what appears to be the proper routing.

Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0b db 98 ba 03 ...... Broadcom 440x 10/100 Integrated Controller - Pac
ket Scheduler Miniport
0x10004 ...84 1b 5e 9a ae 35 ...... NETGEAR WNA1000M N150 Wireless USB Micro Ada
pter - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
0.0.0.0          0.0.0.0     10.230.5.145    10.230.5.149       20
0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.6       20
10.230.5.144  255.255.255.248     10.230.5.149    10.230.5.149       20
10.230.5.149  255.255.255.255        127.0.0.1       127.0.0.1       20
10.255.255.255  255.255.255.255     10.230.5.149    10.230.5.149       20
127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
192.168.1.0    255.255.255.0      192.168.1.6     192.168.1.6       20
192.168.1.6  255.255.255.255        127.0.0.1       127.0.0.1       20
192.168.1.255  255.255.255.255      192.168.1.6     192.168.1.6       20
224.0.0.0        240.0.0.0     10.230.5.149    10.230.5.149       20
224.0.0.0        240.0.0.0      192.168.1.6     192.168.1.6       20
255.255.255.255  255.255.255.255     10.230.5.149    10.230.5.149       1
255.255.255.255  255.255.255.255      192.168.1.6     192.168.1.6       1
Default Gateway:       192.168.1.1
===========================================================================

(sorry for the format)

I see that there is a default gateway and read that that is a problem when running two interfaces.

Any help here?

Kirk - N6SXR

HamCation 2014 is coming up just short of two weeks from now.  Any plans on any Mesh activities this year ?  If all goes well I should be there Friday and Saturday.

So far it is working, the only thing that I had to do to get it to broadcast is add a line in the "olsrd.conf" in both folder locations, on both routers is Ip4Broadcast 255.255.255.255 and they started talking to each other. When I looked at what each router had for BCAST setting they were based on their IP settings on the LAN side.

The setup is in my house. I have cabled between two routers and whether I put antenna on the one I am connected to a PC on or not changes the route tables accordingly or shows both wl0 and/or eth0.0 as the route(s). I'm going to let it run for a while to see if I have any crashes. I am not putting any data through yet.

Based on another person doing a similar scheme, he added some longer times which would help loading at least on the processor. I don't know if those times are the best that he selected, see below. Someone else could chime in on what the timing should be for the Ethernet interface.

Interface "eth0.0"
{
Ip4Broadcast 255.255.255.255
HelloInterval 6.0
HelloValidityTime 108.0
TcInterval 4.0
TcValidityTime 324.0
MidInterval 18.0
MidValidityTime 324.0
HnaInterval 18.0
HnaValidityTime 108.0
}

We had our winter tailgate in Albuq, and a few folks brought their mesh hardware, we had Raspberry Pi, Ubiquity and Linksys hardware all working together.  One node was serving up a camera feed, I provided internet access through my node on the HMMWV.

I was able to use my SIP phone client thru the mesh, thru a VPN connection to my Asterisk server at home to make calls.

I did notice a problem, not sure what causes it though.

When plugged into the first mesh node, I could initiate a VPN connection, but when plugged into any subsequent nodes, I could not connect with VPN  It would fail every time after successful authentication.

Plug back into the original node, and VPN works.   all 3 tested were linksys with stock BBHN firmware.

Here's a screenshot from the day.

Attachments
 mesh at tailgate.jpg [69 KB] ::

Hi all 

Question 

Why are the 44.***.***.*** series of IP addresses not use in the Broardband-Hamnet system and available routers 

seems a waste of addresses to me but I guess that an IP boffin can give me an answer

73  Kevin  G7UXW  IO91QE 

NNNN

The process is going to be quite similar to the Cisco 79xx phones. I can create a provisioning video on how to set it up, if you would like (which I think I will do as that would give BBHN videos on Asterisk, Grandstream, Cisco, and Polycom). There is also information in the HSMM Files --> IP Phone Files link on the side (http://www.broadband-hamnet.org/hsmm-files/ip-phone-files.html). Though it claims SPIP601, the config should work for the SPIP501. Only the firmware file will be different.