[HamGateNY] Current NY State DNS Entries

[Corey Reichle]

On Mon, Jan 30, 2017 at 3:14 PM, Brian <n1uro at n1uro.ampr.org> wrote:

> Hello Corey;
>
> On Mon, 2017-01-30 at 14:53 -0500, Corey Reichle wrote:
> > 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.
> >
> You're absolutely correct but there are guys using OpenVPN servers who
> are using push to force that issue. Not good.
>
>
While that may be true, that is neither hither, nor thither regarding the
NYS network.


> > We're discussing tunneling of IP traffic over an IP network that is
> > wired, that's all.
>
> One needs not to be licensed to be a glorified ISP.
>
>
I fail to see what that has to do with the price of tea in China.


> >
> > 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.
> >
> > 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.
>
> So since the hardware device would *still* require ipencap to speak to
> the rest of 44/8 and the global internet, why would you wish to
> introduce not one but 2 potential points of failure?
>
>
It doesn't need that.  It's desired, due to the "not invented here"
syndrome that plagues many ham activities.  If the manager of the 44/8
network is willing to do so, any number of points in the NYS network could
be bridged over a VPN tunnel into there, and appropriate routing decisions
made at that point (ie, based on link costing).  Or, two designated points
in NYS could be the uplink.  Or, none, and for example, myself, being close
to PA might have a route to the PA network via RF, which might have a route
to the wider network.

Of course, this is presuming a modern, link-state routing protocol is used,
such as OLSR, or OSPF.  Or, even doable with static routing.  All negating
the need for any of this.

So, it's not introducing 2 points of failure, it's a manner of providing
multiple, redundant paths.


> Case in point, ALL if Ireland now is forced to use an OpenVPN system.
> It is now quite isolated and unreachable. There was a perfectly working
> system with an HF gateway using ipencap to ARDC which is now DOA. Once
> that additional point of failure was brought in, the "wire" failed just
> as it would in an emergency.
>
>
Again, not pertinent to the discussion here, really.


> Also when you think about it, since vpns use a form of ipencap, and the
> method used by ARDC is designed **specifically for amateur usage** and
> it does indeed work, why reinvent the wheel?
>
>
>
They use a form of it, yet.  However, the method used by ARDC isn't
available in COTS hardware, therefore, makes the network more difficult to
deploy, and scale.  I fail to see how a custom RIP daemon and a niche
clear-channel tunneling protocol is specifically crafted for amateur
usage.  The AX25 stack, yes, but that's not what we're discussing here.
We're discussing IPv4 routing over RF links.  There is no "reinventing the
wheel" here:  What I'm suggesting is the exact opposite:  Stop reinventing
the wheel, and use the systems in place in the wider IPv4 networking world.

We could, and should, learn some lessons from the wider schools here.  What
we're discussing is a mesh network, on a wide scale.  Much like Freifunk
network (https://en.wikipedia.org/wiki/Freifunk).  They did not write their
own custom routing protocol.  They used an off-the-shelf, modern link state
routing protocol.  Nodes come and go at will, and the network autodiscovers
new routes.


> --
> I don't have to worry about body fitness in 2017. All I do is
> show my body to itself in the mirror and it throws plenty of
> fits.
> --------
> 73 de Brian - N1URO
> email: (see above)
> Web: http://www.n1uro.net/
> Ampr1: http://n1uro.ampr.org/
> Ampr2: http://nos.n1uro.ampr.org
> Linux Amateur Radio Services
> axMail-Fax & URONode
> http://uronode.sourceforge.net
> http://axmail.sourceforge.net
> AmprNet coordinator for:
> Connecticut, Delaware, Maine,
> Maryland, Massachusetts,
> New Hampshire, New Jersey, Pennsylvania,
> Rhode Island, and Vermont.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://n2nov.net/pipermail/hamgateny_n2nov.net/attachments/20170130/06b1b547/attachment.htm>