You STILL need IPencap which is generally nonstandard and not well supported or easy to setup. One needs linux and the ability to configure it to make it work, and one can't host a netblock on their lan with it. After trying out and seeing how well it works with a simple supported vpn connection, I'd like to get others involved in setting up and supporting a shared resource that makes things easy and painless.
As for amprnet hosts routing point to point, many of us are still stuck on manually receiving what amounts to a hosts file and updating routes manually. those that do run a dynamic routing protocol (rip) are forced to run a bastardized and nonstandard version of said daemon such that it's compatible and works with amprnet.
What I'm proposing should be relatively plug and play with support for just about any device that speaks IP.
Eric AF6EP
On Tue, May 12, 2015 at 9:17 PM, Brian n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ Eric et al;
Recently I figured out a similar method of connecting an endpoint from a low grade router using NAT on the amprnet without the need for any other routing overhead except ipencap. See n1uro.ampr.org/linuxconf/ amprnat.txt and ampr-with-nat.html if you want to read more about it. It's already being used in the Boston area with success. A static host such as you mention is needed and we're using one.
As for traffic on ucsd, if that's a major problem I would think BK would mention something, but for ampr to ampr points that should be pretty much point to point bypassing ucsd. Pardon my brevity, as I'm on a smartphone. Sent through via axMail-fax by N1URO.
Sent with AquaMail for Android http://www.aqua-mail.com
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net