Hi,

I have run Mesh Node and I would like connect this node  to AmprNet. I have running AmprNet gate on Raspberry PI where I have local services like WWW , Forum, Mumble server, ICAST server for video stream, webmail running on Citadel package (very nice package to start SMTP/POP/IMAP/Webmail and BBS in one). This server is steup as AmprNet gate with IP address 44.165.32.xx. Server is connected to Internet via router OpenWRT and now I need get access to local Mesh hamradio users to my server http://sp2ong.ampr.org but how to do this ? To this server only can connect host with 44/8 class.

Maybe I need on HSMM-Mesh v1.0 run IPIP tunel to my RaspberyPI Amprnet gate and change IP address on LAN to 44.165.32.xx with one IP and tunel to AmprNet ?

Thank you for any help

Waldek sp2ong 

Hi,

I have try setup IPIP on WRT54 with HSMM v1.0 but it is look that busybox in our firmware is very old

BusyBox v1.4.2 (2008-08-04 21:28:11 CDT) multi-call binary

it is look that in this version "ip rouet" is not full support.

I have try follow:

ip addr add 44.165.3.254/32 dev tunl0
ip link set dev tunl0 up
ifconfig tunl0 mtu 1500

iptables -t nat -A POSTROUTING -s 10.0.0.0/8 -o tunl0 -j MASQUERADE
ip rule add to 44.0.0.0/8 table 44 priority 44
ip route add 44.0.0.0/8 dev tunl0 via 192.168.1.2 onlink table 44

but last command don't work

How to upgrade busybox on our firmware ???

Ok I have working setup with my WRT54 which is connected to my local AmprNet GW and now any

local Mesh Node can connect to AmprNet hosts

Script setup tunnel where 44.165.3.254 and IP WAN 192.168.1.5 is my WRT54 and 44.165.3.1 is IP interface tun0 on my AMprNet GW server

# AmprNet tunnel
ip tunnel add tun0 mode ipip remote 192.168.1.2 local 192.168.1.5 ttl 255
ifconfig tun0 44.165.3.254 pointopoint 44.165.3.1 mtu 1480 up
route add -net 44.0.0.0/8 gw 44.165.3.1
iptables -t nat -A POSTROUTING -s 10.0.0.0/8 -o tun0 -j MASQUERADE

I have add on my WRT54 which is AMprNet GW now for Mesh nodes information about default routing 44/8 network via this Mesh Node. In /etc/config.mesh/olsrd.conf I have add in:

Hna4
{
44.0.0.0 255.0.0.0
}

73 Waldek

Nice work Waldek,

Why do you do NAT towards the HSMM/BBHN 10.0.0.0/8 network ? This shoudl not be needed and is not allowed inside the network either.

Will you do some documentation of this AMPRnet gateway setup och how to tunnel HSMM/BBHN just like I did the GRE documentation for tunneling ?

I´d like to try to hook up our SM network to AMPRnet as soon as you have some functional documentation.

Hi,

If I want to connect from my laptop Ubuntu with WIFI Mesh to any Amprnet host for exmaple http://db0tv.ampr.org I must NAT 10/8 to my IP 44.165.3.254 because AmprNet olny generally allow connect with 44/8 and ip 10/8 is local IP not routed outside local network. Many Amprnet gateways setup firewall that allow only connect 44/8 <-> 44/8
With this my steup any local hamradio node which have IP address from 10/8 can connect with any 44/8 Amprnet hosts via local AmprNet gateway.
On WRT54 I have steup only IPIP link to my main AmprNet GW on raspberry PI which have full encap table for all world amprnet gateway. It is useful because routing table is take memory and it is not useful for WRT54. Better run local Amprnet/Mesh server on for example Raspberry PI which is connected to inetrnet and setup AmprNet GW and local services like we have:

Webserver HAMNET  (Nginx, PHP)
CMS-System web server WWW (GetSimple)
APRS-RX-iGate zDVB-T-Stick (PyMultimonAPRS)
VOIP-Server (Mumble)
Video-Server (Iceast)
SMTP/IMAP server + webmail server (Citadel)
Forum  (myBB)
DXCluster (DXSpider)
Jabber server (Prosody)

With this many servrices running Raspberry PI computer working very well.

I have attached image with idea which I have local Network setup. Instead router mikrotik we can use other router with WFI etc.

You have access to Amprnet you can see http://sp2ong.ampr.org

Attachments
 HamNET-Mesh-Server.png [152 KB]

I have must understand how to announce via my main WRT54 DNS servers to others Mesh Nodes.

I have found that in olsr plugin we can put information about main dns server follow:

LoadPlugin "olsrd_nameservice.so.0.3"
{
PlParam "dns-server" "44.0.0.1"

....

but I can not see that working

From help of this plugin:

PlParam "dns-server" "IP.ADDR"
        anounce that this IP has a full (upstream) DNS server. if 
        IP.ADDR is not specified (""), the main address is used.
        nodes which don't know a nameserver will automatically use
        this nameserver.

I have see that when I have put in olsrd.conf

dns-server ""

in my Mesh node in /etc/reslove.conf found

### this file is overwritten regularly by olsrd
### do not edit

nameserver 10.199.171.232

### written by olsrd at Sat Dec 21 19:44:01 2013

but others DNS server like 44.0.0.1 not included in this file. It is look like in dns-server we can put only one IP address Mesh Node which will be main DNS server

Ok DNS working very well in my local BBHN. Now all local Mesh Nodes have information about local dns server which we use to connect amprnet hosts. Now we have full integrated Local BBHN network with AMprnet hamradio network and local users can connect and use servrices not only local but Amprnet 44.x network. We can connect via WIFI with any hosts amprnet like http://db0tv.amr.org etc.

73 Waldek sp2ong

Hi Waldek

I'm Kevin G7UXW. i've been testing my pi,beagleboard and routers to great effect and all is looking good. I copied your HamNET-mesh-server.png file and added some questions in red with regard to IP addressing for attached devices.. I've posted the page at www.qsl.net/g7uxw/44network.png .. This mite seem a strange way of doing things but it will put a picture in my head of what things should look like 

 This is the fastest learning curve i've been on 

73  Kevin  G7UXW 

Hi,

I have attached picture with my IP addresses. NanoStation and AirGrid link it is outside Mesh Node and you must use different class IP for example 192.168.2.x for Access Point local users via NanoStation and for link PointToPoint via AirGrid 192.168.3.x . nanoStation and AirGrid in this example I have use when You want mix hamnet solutions. One is Mesh Nodes working on 10/8 Ip addresses use WRT54 and now NanoStation but with special firmware BBHN. and other solution Hamnet like exit in Europe were base on firmware Ubiquiti and hardware but working on ham radio bandplan. You can skip NnaoStation and AirGrid configuration.

Raspberry Pi have internal network IP like 192.168.1.2 and run AmprNet GW with IPIP tunnel where my amprnet ip is 44.165.32.1.

WRT54 with BBHN firmware which I have connected via WAN to my local router use ip address 192.168.1.3 and I have run pointtopoint tunnel to my raspberry P for 44/8 network and WRT54 have 44.165.32.254 ip. I have setup masquerade  ip adress10/8 via tun0 interface to 44/8 network. and add to OLSRD config that my WRT54 is router for 44/8 network. For this all users from Mesh Nodes can connect to Amprent and my Raspberry PI server which have many services for local users.

I have show part my config amprnet GW on post: http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-4-applications/topic-775-nntp-network-news-transport-protocol.html#ccbp3486

73 Waldek sp2ong

Attachments
 amprnet-hamnet.png [164 KB]

Hi,

I have switch my local nodes from IP 10/8 to 44.165.xx from AMPRNET and it is look better solution for us because our local nodes have direct access to wide Amprnet network and any host from AMPRNET have access to our Mesh BBHN nodes. I must change rules firewall on our one WRT54 which is gateway to Amprnet to pass 44/8 traffic to local nodes. We can use Amprent IP addresses on Mesh Nodes and setup local AmprNet gateway by register on http://portal.ampr.org.

73 Waldek sp2ong