What you say in the last paragraph is reasonable and was implemented
very early on; if one side changes its IP, it should be able to
reconnect provided that the other side isn't NATted (unfortunately it
always is!). If the reference is not propagating there is some sort of
bug...

On Sat, Apr 15, 2006 at 05:24:28PM -0400, Gregory Maxwell wrote:
> 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.
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
> 

-- 
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20060421/c7c8a782/attachment.pgp>

Reply via email to