On Saturday 26 Feb 2011 23:19:31 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,
> > 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. :)
Which can be found where? It is not
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.
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.
