[freenet-support] Unbundling Frost

Matthew Toseland wrote: > Ian has stated that Frost is a separate project, and we should not wait > for a usable FMS. (Background: Frost has been severely DoS'ed recently due > to being based on KSK queues, and FMS is the answer). Right now we are not > actually being DoS'ed, but yesterday we

[freenet-support] Can't bind fproxy to LAN IP

I am trying to set up my node so a client on a separate machine on my LAN can browse Freenet through FProxy. I was able to do this with FCP by changing the 'IP address to bind to' from: 127.0.0.1,0:0:0:0:0:0:0:1 to 192.168.1.103,127.0.0.1,0:0:0:0:0:0:0:1 However, when I make the same change

Re: [freenet-support] Unbundling Frost

Matthew Toseland wrote: Ian has stated that Frost is a separate project, and we should not wait for a usable FMS. (Background: Frost has been severely DoS'ed recently due to being based on KSK queues, and FMS is the answer). Right now we are not actually being DoS'ed, but yesterday we were;

[freenet-support] Can't bind fproxy to LAN IP

I am trying to set up my node so a client on a separate machine on my LAN can browse Freenet through FProxy. I was able to do this with FCP by changing the 'IP address to bind to' from: 127.0.0.1,0:0:0:0:0:0:0:1 to 192.168.1.103,127.0.0.1,0:0:0:0:0:0:0:1 However, when I make the same change