Seems that when a node changes it's physical identity its peers do not learn of this new identity.
For example, I have a running freenet node that everyone knows based on my IP. I realize this IP might change at some point in the future, and I don't want to need to expend the effort to go contact all my neighbors again ... So I got get a dyndns name. I set my ipoverride to this name, and I see in my new reference that my client now considers its physical address to be the dyndns address. I would now expect that all the peers I connect to would learn of this address and would adjust their records accordingly. But they don't. Is this just unimplimented or is there a security implication I'm missing? My thought is that when I recieve a packet, I can tell if it's from a friend because it will be cryptographically authenticated. I shouldn't care what IP/port it comes from. Once they connect if they claim to now be operating with a different physical address than they used to, I should update my records so that I know where to connect in the future.. This way, as long as both parties in a peering don't change IPs at the same time the peering can remain good forever without user intervention.
