Re: Important Announcement: Freenet naming change

[s7r]

Dr. Arne Babenhauserheide wrote:


Ian Clarke  writes:

You're speaking as if you speak on behalf of the Freenet community. Who 
specifically are you speaking for and what gives you the ability to speak for
them?


I share the sentiment. Steve spoke to me before sending this message,
and he also speaks for me, the release manager of Freenet. Also David,
Florent, and xor disagree strongly with the renaming plan. These are
most of the non-anonymous core developers of Freenet.

And the actual Freenet community that communicates on Freenet via FMS
and Sone is absolutely enraged over this.

Best wishes,
Arne


Steve speaks in my name too, and I strongly share Steve and Arne's 
sentiments.




OpenPGP_signature
Description: OpenPGP digital signature

Re: Remaining reviews needed to release Freenet 1495

[s7r]

Dr. Arne Babenhauserheide wrote:

Hi,


We’re getting ever closer to release. I merged the already reviewed
pull-requests, but some important PRs remain so we can release. Please
help getting these reviewed!



Thanks for the work!

I would like to propose we change something that has been bothering me 
for years, and I have extensively tested it under Debian, FreeBSD and 
Windows during the last 4 Freenet releases and it does not cause any 
problems at all if we change it the way I suggest.


In the default wrapper.conf file we ship with Freenet, there is this 
over a decade config line:


# Needed for some linux distros? Shouldn't prevent using IPv6, just make 
it prefer IPv4?

wrapper.java.additional.3=-Djava.net.preferIPv4Stack=true

The thing is, it actually really prevents you from using IPv6! At least 
on Debian, Windows and FreeBSD (I am confident on every OS this is the 
case, because it's a Java thing more than an OS thing).


With these lines in wrapper.conf we have the following problems:

- node does not bind to IPv6 interfaces, only bind to IPv4 available 
addresses for both opennet and darknet;


- It also does not connect to any IPv6 peers. If you remove it, even if 
node bind to and node opennet bind to is set to the `default` 0.0.0.0, 
it properly binds to *all* interfaces (IPv6 and IPv4).


- it doesn't open the localhost FProxy except on 127.0.0.1, regardless 
the freenet.ini setting is to also bind to 0:0:0:0:0:0:0:1 -- with that 
line removed, FProxy successfully finds to 127.0.0.1 and [::1].


*So there are no additional settings to do to make sure all goes well 
except as remove these two lines from wrapper.conf.*


We should remove it entirely or comment it out, and also make sure it 
overwrites the `wrapper.conf` on disk for users that already have 
freenet installed and are upgrading automatically.


This will add better IPv6 support, more reachable nodes in the Freenet 
network (IPv6 and NAT is much rarely used together) and it makes sense 
to do it finally, after 25 years since the IPv6 RFC :)


I'll do a PR to update the seednodes for better bootstrap support to new 
connecting users, hopefully the windows installer will take them on in 
time. Monitoring service is running here:


https://freenet.dotbit.zone/



OpenPGP_signature
Description: OpenPGP digital signature