<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>The Use case I was thinking is if my 44.68.86.X/29 is total RF
with one device as a gateway that tunnels across wired internet
back to the UCSD gateway to the rest off 44 that have a GW there<br>
</p>
<br>
<div class="moz-cite-prefix">On 01/30/2017 02:53 PM, Corey Reichle
wrote:<br>
</div>
<blockquote
cite="mid:CALvFBuzHDJtqwLVR0mFQXYYLZPdjKK4ESrOgAeNk=ZYW_VxOTQ@mail.gmail.com"
type="cite">
<div dir="ltr">Why would you use OpenVPN (Or, any other tunneling)
over RF links? That would be silly. Routing of IP packets is
handled by the AX25 stack (Or other link layer protocol in use,
which could be 802.11). No IPEncap required for that. Just
routes.<br>
<br>
We're discussing tunneling of IP traffic over an IP network that
is wired, that's all.<br>
<br>
OLSR is also a dynamic, self-healing routing protocol, that is
heads and shoulders above RIP protocols, as it is also a
self-discovering of neighbors and routes. See Broadband
Hamnet's work with that. It is also usable over wired networks.<br>
<br>
OpenVPN tunnels are used to bridge two networks together.
Hardware behind that provides the routing to other networks, and
with OSLR, having mutliple possible routes is possible, with
routing loops prevented due to it's design.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 30, 2017 at 1:21 PM, Brian
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:n1uro@n1uro.ampr.org" target="_blank">n1uro@n1uro.ampr.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Mon, 2017-01-30 at 10:37 -0500, Joe Cupano
wrote:<br>
> I agree on all points but also respect when it comes
to Ham Radio how<br>
> long change can take : )<br>
><br>
</span>One way to look at it is, why are wired technologies
used for RADIO?<br>
OpenVPN is like putting a bandaid on a wound that requires
stitches.<br>
It will work temporarily but it's not a permanent fix.
IPEncap is the<br>
method provided by ARDC (who owns 44/8) and it's somewhat
dynamic in<br>
nature as to how it provides routing especially to those
dynamic<br>
clients. If you wish to use OpenVPN, it can be done, but you
won't have<br>
any routing except to your OpenVPN server host and hope that
host can<br>
provide the IPEncap you need for the rest of 44/8.<br>
<br>
If you're routing via RF, OpenVPN will cause you to violate
Part97 in<br>
regards to encryption on the air.<br>
<div class="HOEnZb">
<div class="h5"><br>
--<br>
I don't have to worry about body fitness in 2017. All I
do is<br>
show my body to itself in the mirror and it throws
plenty of<br>
fits.<br>
--------<br>
73 de Brian - N1URO<br>
email: (see above)<br>
Web: <a moz-do-not-send="true"
href="http://www.n1uro.net/" rel="noreferrer"
target="_blank">http://www.n1uro.net/</a><br>
Ampr1: <a moz-do-not-send="true"
href="http://n1uro.ampr.org/" rel="noreferrer"
target="_blank">http://n1uro.ampr.org/</a><br>
Ampr2: <a moz-do-not-send="true"
href="http://nos.n1uro.ampr.org" rel="noreferrer"
target="_blank">http://nos.n1uro.ampr.org</a><br>
Linux Amateur Radio Services<br>
axMail-Fax & URONode<br>
<a moz-do-not-send="true"
href="http://uronode.sourceforge.net" rel="noreferrer"
target="_blank">http://uronode.sourceforge.net</a><br>
<a moz-do-not-send="true"
href="http://axmail.sourceforge.net" rel="noreferrer"
target="_blank">http://axmail.sourceforge.net</a><br>
AmprNet coordinator for:<br>
Connecticut, Delaware, Maine,<br>
Maryland, Massachusetts,<br>
New Hampshire, New Jersey, Pennsylvania,<br>
Rhode Island, and Vermont.<br>
</div>
</div>
<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>