On Wed, Aug 16, 2000 at 06:10:31PM +0100, lists wrote:
> If you're running it on the router you're not really behind it so yes it
> would be a matter of just opening a port... I'm behind a grey box with
> flashing lights on it and my node believes that its IP address is
> 192.168.0.3 :-(
> 
> Port forwarding is only half the solution. I have a hole in my firewall at
> 19114 forwarded to 192.168.0.3:19114 but no node trying to reach me will
> ever get this far if my node doesn't put the router's (genuine, internet
> visible) IP address in outgoing messages instead of 192.168.0.3

Actually, in the current implementation the host part of the source
address is read of the socket at the receiving node. The host part of the
Source: field should actually be ignored in tcp Freenet applications (as
soon as I get down to speccing this it will say something like "the source
address should only be used for values that cannot be reliably read of the
transport" - ie everything but the port for tcp, but maybe nothing for for
phone lines without caller-id).

So as far as connecting out is concerned, I think the Source: as the
Internet node sees it will be that of your port forwarding router, since
that is what socket.getInetAddress() at the peer should return (AFAIK).

The other issue is the DataSource: address, which is used for data
requests to find you. That is not reset by the receiving node (since more
often then not it shouldn't be rest) so the sender will have to set it
correctly. It will probably be worth allowing for a "SetDataSource" config
value that overrides the automatic resolving since that also solves the
problem of people wanting to use a Domain name as the DataSource (so that
their node can still be found after an ip shift).

Having a "SetDataSource" might open up for some abuse with people pointing
them at the wrong places - but that is a fact of the system, trying to
hide it will not help us. 

-- 
\oskar

_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to