23 Aug
2013
23 Aug
'13
8:15 p.m.
In another thread, it was said:
> everyone in the mesh ought to be running a dynamic
routing protocol thus
> increasing redundancy and reliability.
This is a good idea. I'm not up on the latest RFCs
concerning routing in
tunneled (VPN, GRE, etc) networks. Do you have a recommendation?
I am not an expert to answer this question, but I have stumbled on an
emerging method for routing that has remarkable similarities to
threads here. Along with the connections/associations I list below, it
is experimental communications, and I believe we (Hams) have something
to contribute.
RFC 6830, LISP (Locator/ID Separation Protocol - see
[http://www.lisp4.net/] ) decouples Location from unique IDentifier in
IP addressing. I first saw the need for this concept with APRS
messaging, but that is for another group.
"LISP follows a network-based map-and-encapsulate scheme ... both
identifiers and locators can be IP addresses or arbitrary elements
like a set of GPS coordinates or a Mac address." {or call sign?}
The LISP Papers at [http://blog.pattincon.com/lisp-papers/] seems to
be a good place for me to start to understand the application of this
protocol.
It is implemented in recent versions of Cisco IOS/NX-OS (out of my
reach at this time) and LISPmob (Mobile Node) at [http://lispmob.org/]
runs on OpenWRT/Linux.
I am working on experimenting with something from here.
Peace, Jim A. KB3TBX