Re: [freenet-support] attention users of both freenet networks
On Fri, 25 Feb 2011 00:27:01 +0100 (CET), Nomen Nescio wrote: > > you have a right to know > > USK@1WZPo6qZmlCpi6rZWjtz~kig1gcpcnzh5drmqpW9L8Q,ksaFFDkSJfnOXB3ppYhQ2R14z3WQCYxGqXNERCYcHD0,AQACAAE/wordsoftoad/-1/ I can't access this freesite. Despite hours of trying. (Other freesites seem to work fine.) " Freenet was unable to retrieve this file. Data not found: No USK found " ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] msdnsdiscovery
On Friday 25 February 2011 21:45:26 folkert wrote: > I wonder why is msdnsdiscovery announcing itself on 192.168.64.1/24: My guess is that the plugin does not know too much about Freenet’s configuration and simply announces on the first interface it can find. For more details, read the source. :) > Folkert van Heusden David signature.asc Description: This is a digitally signed message part. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] msdnsdiscovery
I wonder why is msdnsdiscovery announcing itself on 192.168.64.1/24: Service NameMachine Address Parameters Freenet 0,7 Fproxy server -=next-20110211=- mauer.local. 192.168.64.1: path=/ Freenet 0,7 FCP server -=next-20110211=-mauer.local. 192.168.64.1:9482 Freenet 0,7 Node server -=next-20110211=- mauer.local. 192.168.64.1:52644 while it is doing all things on 172.29.0.0/24: mauer:/usr/local/FreeNet/freenet# grep 172.29.0 freenet.ini fproxy.bindTo=172.29.0.1 fcp.bindTo=172.29.0.1 ? Especially since there are loads of other interfaces on the system as well: mauer:/usr/local/FreeNet/freenet# ifconfig | grep 'inet addr' inet addr:192.168.64.1 Bcast:192.168.64.255 Mask:255.255.255.0 inet addr:192.168.178.2 Bcast:192.168.178.255 Mask:255.255.255.0 inet addr:172.29.0.1 Bcast:172.29.0.255 Mask:255.255.255.0 inet addr:192.168.59.1 P-t-P:192.168.59.121 Mask:255.255.255.255 inet addr:192.168.61.1 P-t-P:192.168.61.121 Mask:255.255.255.255 inet addr:192.168.18.2 Bcast:192.168.18.255 Mask:255.255.255.0 Folkert van Heusden -- -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] idea
> > > What about that the freenet daemon periodically > > > (configurable/disable-ble of course) announces itself on the lan(s) to > > > which it is connected? That way freenet-nodes can interconnect and > > > speed up distribution of data. > > There is a plugin: > MDNSDiscovery. > This uses it to announce FCP, but you still need to open FCP to the LAN... Or plugin to avahi. > > Data distribution on Freenet doesn't work like that. Data segments are > > actually spread all across Freenet, ideally with no particular peer > > having a large portion of a large splitfile. I don't think having fast > > random LAN connections would speed things up -- the bottleneck will > > still be the LAN's connection to the Internet. (Not to mention the fact > > that it would be at least somewhat less secure. (Better chance of > > traffic analysis and such tricks against you.)) > > We did think about an "is the lan trusted?" option some time ago. This would > both announce and open FCP and Fproxy. Unfortunately defining "the lan" is > hard, when big untrusted NATed networks (e.g. ISPs in russia etc) often use > private address space, and autodetecting it *reliably* is also hard. You could make it configurable. Default: do not trust. > You should however peer with the other computers on your LAN, if you know > their operators, of course. Which hopefully you do if the LAN is trusted! Troublesome if everybody's on dhcp. Folkert van Heusden -- MultiTail na wan makriki wrokosani fu tan luku den logfile nanga san den commando spiti puru. Piki puru spesrutu sani, wroko nanga difrenti kroru, tya kon makandra, nanga wan lo moro. http://www.vanheusden.com/multitail/ -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
