Anyone who wants to duplicate my results needs to do, is put IPFS on LAN w/ 
dual WAN where one IP addy is dynamic;



However. Unless you're on GPON you'll have to simulate the DHCP addy changing, 
depending which laser on the optical switch is talking to you.



There's your IPFS boot loop. Now anyone can see what I'm describing as a dog 
shaking off water only to get another bucket dumped on top of it.



But you'd have to post the HTTP link, as I did, to kick off the seeding. 
Alternatively, if you can get it on IPFS, pin it? I can't test that.


-Eric







---- On Sun, 21 Jul 2024 09:18:35 -0700 Eric J Bowman via illumos-discuss 
<discuss@lists.illumos.org> wrote ---



Nutshell: I discovered an IPFS boot loop.



-Eric







---- On Sun, 21 Jul 2024 08:21:33 -0700 Eric J Bowman via illumos-discuss 
<mailto:discuss@lists.illumos.org> wrote ---









https://illumos.topicbox.com/latest / illumos-discuss / see 
https://illumos.topicbox.com/groups/discuss + 
https://illumos.topicbox.com/groups/discuss/members + 
https://illumos.topicbox.com/groups/discuss/subscription 
https://illumos.topicbox.com/groups/discuss/T2c766ee23140896a-Mbf13c9536ad9e7f251b1a0a7


Sorry for the OT and the bumping but I'm barely online. That .iso I posted will 
be available "soon". Only one of my WAN links has a static IP address. So when 
I pinned that download, it didn't work because of "intermittency" which could 
have other causes besides the IP address, kinda hard to troubleshoot from out 
here over the edge.



The borked state of that 2GB file, means that at this point pretty much every 
IPFS node on the planet is trying to connect, getting a 256Kb chunk, encrypting 
it, reflecting it back to me, and yet even though it's now "assembled" on my TV 
(long story), every IPFS node on the planet is still trying to connect to do 
the same thing because overall, the operation is stuck at the final stage of 
completion.



I don't change router configurations lightly. I know what to do, and I know how 
to do it, but not until I've documented it out for myself and made backups etc. 
so this is my all-day project, but I need to restrict IPFS to my static-IP WAN 
port, because I "pinned" to self-host the file from my TV. Which costs nothing, 
for anyone, for as long as the file is retained, meaning in this case after the 
next release, this one will slowly fade away.



So I'm hoping folks will try it. I've long used bittorrent for but one purpose: 
distro sharing, even if I didn't like the distro, any distro I come across 
that's available via BT. I'm also really an HTTP guy when it comes to setting 
up a host to serve a file. I don't fall for protocol hype. Had I already known 
what I was doing when I posted the .iso, it would've shared right out there in 
the midst of all this, no problem.



Although, it will likely be the case that once I've reconfigured the router, it 
will only be available via IPFS, because those HTTP-IPFS gateways seem to be 
impacted by something which prevents them from being available long enough to 
transfer a 2GB file.



-Eric
------------------------------------------
illumos: illumos-discuss
Permalink: 
https://illumos.topicbox.com/groups/discuss/T2c766ee23140896a-Mbc8e2851e76b5ce447cebf58
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

Reply via email to