New subject: RIPv2

28 Jul 2015

...
  Subject:
 Re: [44net] RIPv2
 From:
 Brian Kantor &lt;Brian(a)UCSD.Edu&gt;
 Date:
 07/27/2015 05:44 PM

 To:
 AMPRNet working group &lt;44net(a)hamradio.ucsd.edu&gt;

 On Mon, Jul 27, 2015 at 08:26:08AM -0700, Assi Friedman wrote:
  >Addressing residential internet service with
DHCP is a problem with the
 >encap method.  Does RIPv2 address this problem?
 >Thanks,
 >Assi  Short answer: Not really.

 If you're referring to the dynamic nature of some home connections where
 the address may vary from hour to hour or day to day, there is no good
 solution to the problem. 
It is interesting to see that the implementation of home connections varies so much over
the world.  Over here there is a legal obligation to always be able to produce the name
and address of the subscriber that owned an IP address at a certain point in time, and it
appears that most providers have taken the easy way of assigning a fixed IP to each
subscriber.

DSL connections all have a fixed IP.   Cable connections usually have an IP that is fixed
as long as you do not turn off the cable modem for a few days or so.   There is no hourly
or daily cycling of addresses anywhere.

Truly dynamic IP is only in use here on mobile connections, and often they are behind NAT
so not possible to use an ipip tunnel on them anyway.  I have implemented OpenVPN and
IPsec
on our gateway so those users still can get connected to AMPRnet.

I would think that when your address really changes hourly, and you want to be on an
AMPRnet
tunnel, it would be best to arrange something similar, a VPN to a system on a fixed
address.
It should be easy to arrange for such a thing, e.g. with a group that share a cheap VPS
for it
that can also be used for mail, a webpage etc.

Rob