<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Sorry for the late reply, I just saw
your email.<br>
<br>
Yes, our edge router runs RouterOS and holds all the IPIP tunnels
open for AMPRnet routing. We (and by "we", I mean Tom/KD7LXL)
developed software for us to keep the edge routers refreshed with
tunnel updates. It's available here:<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/kd7lxl/hamwan_scripts/tree/master/amprupdate">https://github.com/kd7lxl/hamwan_scripts/tree/master/amprupdate</a><br>
<br>
Here's a snippet of what our config looks like on the router
itself:<br>
<br>
<tt>/interface ipip</tt><tt><br>
</tt><tt>add disabled=no dscp=0 local-address=198.178.136.80
mtu=1480 name=ampr-118.22.1.194 remote-address=118.22.1.194</tt><tt><br>
</tt><tt>add disabled=no dscp=0 local-address=198.178.136.80
mtu=1480 name=ampr-118.82.200.153 remote-address=118.82.200.153</tt><tt><br>
</tt><tt>add disabled=no dscp=0 local-address=198.178.136.80
mtu=1480 name=ampr-12.195.50.128 remote-address=12.195.50.128</tt><tt><br>
</tt><tt>add disabled=no dscp=0 local-address=198.178.136.80
mtu=1480 name=ampr-121.99.232.227 remote-address=121.99.232.227</tt><tt><br>
</tt><tt>...</tt><tt><br>
</tt><tt><br>
</tt><tt>/ip route</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.1.32/29
gateway=ampr-76.14.161.185 scope=30 target-scope=10</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.8.180/30
gateway=ampr-192.147.172.252 scope=30 target-scope=10</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.10.0/29
gateway=ampr-71.130.72.52 scope=30 target-scope=10</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.11.1/32
gateway=ampr-71.130.72.52 scope=30 target-scope=10</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.14.100/32
gateway=ampr-50.79.156.221 scope=30 target-scope=10</tt><tt><br>
</tt><tt>add disabled=no distance=1 dst-address=44.2.50.0/24
gateway=ampr-208.74.106.137 scope=30 target-scope=10</tt><tt><br>
</tt><tt>...</tt><tt><br>
</tt><br>
We haven't been able to test this since it's hard to know which
IPs on the target subnets are actually alive and have
corresponding tunnel entries for us. There's a few hundred of
these tunnels installed on our edge router which cover the whole
of AMPRnet. Anyone on HamWAN should have full routability to/from
these networks.<br>
<br>
--Bart<br>
<br>
<br>
On 8/20/2013 7:33 AM, Rod Ekholm wrote:<br>
</div>
<blockquote
cite="mid:CAB1OxHfcdTzpwF+2B9dGqS5_bY8v=U2rzN2wu8Xm-bDf_eHh7Q@mail.gmail.com"
type="cite">
<div dir="ltr">Can you tell me if the HamWAN is using a Mikrotik
router to interface to the AMPR network? Or is it using the
every required Linux box? I was looking to peer with AMPRNet,
however it looks like it is less than an optimal configuration
to try and do so with Mikrotik's.
<div>
<br>
</div>
<div>Thanks.<br clear="all">
<div><br>
</div>
-- <br>
Rod Ekholm Jr.<br>
Spokane, WA</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PSDR mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a>
<a class="moz-txt-link-freetext" href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
</body>
</html>