Main
News
Proposal
Readings
Download
Backbone
License
Donate
Feedback
Guestbook
Wed Jun 24 01:29:34 2026 UTC
Someone recalled there was a test web
site inside FEDAnet. The site was running on a machine inside my home
network, but for some reasons I had to stop keeping that machine running
24x7. As of now, the site on the same IPv6 address
feda:c508:097b:d6c3:47a4:a317:3700:feda
runs on one of my VPS machines (I won't tell you on which, heh; anyway, you
can't access it from outsite, only from within FEDAnet).
Besides, I got tired copy-pasting that IPv6 address which is, just like all IPv6 addresses, impossible to remember. Hence, now the domain name fedatest.feda.croco.net now resolves to that address. This is not very consistent, as the address is not accessible from the Internet, while the domain name is; however, I still couldnt't find a solution for DNS service inside FEDAnet.
Well, enjoy :-)
From feriman
Sun Jun 28 06:14:18 2026 UTC
Unable to open site
I can not open the site in browser or ping the address.
reply
From Andrey Stolyarov
Sun Jun 28 07:59:17 2026 UTC
in reply to
this comment
Re: Unable to open site
I'm not at home now, so I can only check if the site is reachable from the node machine. It is.
Well, fedaserv is not a mature program, so a lot of other problems can occur so that you can't reach the site.
reply
From fedamember (unverified) Wed Jun 24 22:08:52 2026 UTC
connection refused
nc -v 45.13.38.102 5080
reply
From Andrey Stolyarov
Thu Jun 25 16:21:00 2026 UTC
in reply to
this comment
Re: connection refused
Funny, heh. What the hell did you expect? An open text-based TCP port there? FEDAprotocol is UDP-based, so it is a UDP port, connectionless, and the protocol is cryptographic. so hardly you can make any use out of nc here.
reply
From fedamember (unverified) Thu Jun 25 21:19:24 2026 UTC in reply to this comment
Re: Re: connection refused
All right. I wanted to inform you that my node stopped connecting to the node that provided access to fedatest.feda.croco.net. It's like turned off.
reply
From Andrey Stolyarov
Fri Jun 26 17:08:19 2026 UTC
in reply to
this comment
Re: Re: Re: connection refused
You're right. I've just restarted it.
reply
From fedamember (unverified) Fri Jun 26 19:12:33 2026 UTC in reply to this comment
Re: Re: Re: Re: connection refused
fedatest.feda.croco.net ping 100% loss.
feda:c508:97b:d6c3:47a4:a317:3700:feda as well. 100% loss.
feda:c508:97b:d6c3:47a4:a317:feda:feda is okay.
My day starting from ping your nodes=)
reply
From Andrey Stolyarov
Sat Jun 27 14:33:42 2026 UTC
in reply to
this comment
Re: connection refused
Yeah, I forgot to make the connection persistent on the machine which serves the point 55 (0x37), so when the node crashed and got restarted later, the point didn't connect to it. Thanks for reporting.
reply
From Yury K. (unverified) Wed Jun 24 09:24:03 2026 UTC
Another test site :)
When 3700:feda stopped working, I found that http://[feda:c508:97b:d6c3:47a4:a317:feda:feda]/ works, so I used it to test if my fedanet instance works. :-D
reply
From Andrey Stolyarov
Wed Jun 24 10:38:15 2026 UTC
in reply to
this comment
Re: Another test site :)
Argh, this is unintentional, that Apache instance shouldn't have listened on IPv6 at all. Anyway, this is not THAT interesting, as only confirms connectivity with the node instance, and the node instance is probably connected directly. This is generally not what FEDAnet is about.
reply