24 Aug
2013
24 Aug
'13
7:15 a.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
24 Aug
24 Aug
8:45 a.m.
This looks very interesting indeed. I've just started reading, but it
looks like there's an implementation for OpenWRT enabled routers. It would
be very cool if LISP could be used in some way with Broadband Hamnet to
provide mobile clients with a static net44 address as they roam across
nodes.
Thank you for the links!
Blaine, K1QV
On Fri, Aug 23, 2013 at 5:15 PM, Jim Alles <kb3tbx(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
In another thread, it was said:
--
Blaine Forbort
Special Event & Operation Center Staff
Google Security
1600 Amphitheatre Pkwy
Mountain View, CA 94043
> 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
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
4141
days inactive
4141
days old
1 comments
2 participants
participants (2)
-
Blaine Forbort -
Jim Alles