> Kjell Rune Skaaraas ([EMAIL PROTECTED]) wrote: > > However, rather than defining it myself > > whenever my IP changes, or running some kind of > > dynamic DNS, applications like mIRC do a > server-side > > lookup. How difficult would it be to do the same > for > > Freenet?
> --- Greg Wooledge <[EMAIL PROTECTED]> skrev: > > One of the simpler forms of the proposal is this: > > (long & complex proposal removed) Granted, to include it in the *default* IP detection mechanism would be a complex change. What I was hoping for would be to set it manually to a setting of "remote lookup" instead of setting it to a specific IP address. The responding node would then simply have to respond to the IP it was sent from (permanently). Of course a node too old to recognize it wouldn't return the packet, but if I have no valid IP to send to begin with, we're no worse off than before. Oh and I really don't see why it is important for *my* node to know its public IP address. If I manage get a packet back at all, I have already achieved what I wanted to do! As long as my node figures out the correct private IP to send from (LAN IP), everybody else can figure out the public address themselves. To the best of my knowledge, noone is using masquerading (only forwarding) on incoming transmissions, so that should not be a problem. In fact, a simple "return to sender" return address would require people to spoof their source IP in order to redirect traffic... If you still need to implement it over an IPv4 address to not change the structure, simply pick an illegal IP and define it as "ignore IP in Freenet packet, return to source IP of the TCP/IP connection instead". Kjella ______________________________________________________ F� den nye Yahoo! Messenger p� http://no.messenger.yahoo.com/ Nye ikoner og bakgrunner, webkamera med superkvalitet og dobbelt s� morsom _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
