Freenet is not a point-to-point network. I.e. you cannot address a specific computer on Freenet by something like an IP.
(Well you can, but you shouldn't want to, will explain below.)
Freenet is a datastore: It addresses content, not computers.
So a Freenet address points to a file or a directory of files (a zip). The addresses can be versioned so files/dirs can be updated.
A file/dir may be stored anywhere in Freenet. Where it is stored is not known - the machines which store it are anonymous so censorship is prevented. If many people request a file, it will get stored on more machines automatically.
Now of course you can make a specific computer constantly publish new versions of a file to "send" data like on IP and poll for a remote file to receive data. This can emulate direct connections and does work.
But it invalidates the whole point of Freenet:
Freenet wants to be censorship-resistant, so content should not rely on a single computer to keep existing because that is a single point of failure.
(Well you can, but you shouldn't want to, will explain below.)
Freenet is a datastore: It addresses content, not computers.
So a Freenet address points to a file or a directory of files (a zip). The addresses can be versioned so files/dirs can be updated.
A file/dir may be stored anywhere in Freenet. Where it is stored is not known - the machines which store it are anonymous so censorship is prevented. If many people request a file, it will get stored on more machines automatically.
Now of course you can make a specific computer constantly publish new versions of a file to "send" data like on IP and poll for a remote file to receive data. This can emulate direct connections and does work.
But it invalidates the whole point of Freenet:
Freenet wants to be censorship-resistant, so content should not rely on a single computer to keep existing because that is a single point of failure.