Mon Feb 2 02:40:00 2026 UTC
Looks like I issued the wrong command to pack the archive, so it is
actually tar.gzip, not tar.bzip2. I've just renamed the file on the
server to .tgz which reflects the real format of the file.
Sorry for the inconvenience.
FEDAnet 0.0.40 has been published.
This version supports some interesting new features. First of all, the
fedaserv daemon is now capable of working as
FEDAproxy, serving as many users as you want (the technical limit
is more than 1000 of them, as the socket descriptors seem to be the only
limiting factor). See the file doc/fedaproxy.txt for details,
but to be short, new peer types named proxy,
proxyuser and direct are implemented—and,
well, seem to work.
Another implemented peer type is named nodenets. This mostly
makes sense for configuration of fedaserv instances running as
nodes (that is, with point number 254 a.k.a. 0xFE); in case
there's a peer of the nodenets type in the configuration file,
datagrams that have pseudopoints 0x00, 0xFF and possibly 0xFE (the latter
is for the case there's no virtual network interface locally) are forwarded
to that peer. This makes it easier to run various infrastructure (such as
web/mail/dns/whatever servers) in a location different from that where the
node is being run. To know what to do, the fedaserv instance
that receives this type of traffic (in case it is not the node, that is,
has the point other than 254) must have the line nodenets all
or nodenets some in its configuration file (some
means this instance shall accept traffic for pseudopoints 0x00 and 0xFF,
while all means all the three pseudopoints: 0x00, 0xFE and
0xFF),
There are also a lot of new means to explore what's going on within a
running fedaserv; launch the fedactl program and
try help and help show.
This news item is dated as 1770000000 seconds since Epoch,
but, believe it or not, I only noticed the upcoming interesting
date during the active preparations for this release; it gets published
today because I only managed to catch the last known bug just yesterday, so
it would be published today anyway.
Thanks for those who are still here :-)
From yeti (unverified) Mon Feb 2 13:06:54 2026 UTC
s/bz2/gz/
It looks like a gzipped tar on my end.
reply
From Andrey Stolyarov
Mon Feb 2 13:37:29 2026 UTC
in reply to
this comment
Re: s/bz2/gz/
You're right, thanks! I've just renamed the archive according to its real format. Sorry for the inconvenience.
reply