Oh, also let's not forget the -r ftp option for retrying connections.
This is all assuming that the problem is indeed like Solene has foretold,
within ftp itself.



On Tue, Aug 20, 2024 at 06:36:40PM +0000, Anon Loli wrote:
> On Tue, Aug 20, 2024 at 07:54:19PM +0200, UDENIX wrote:
> > > > I wish OpenBSD supported using mirrors hosted on the Tor or I2P 
> > > > networks for
> > > > system and package installation and upgrades. For instance, Debian not 
> > > > only
> > > > supports but also maintains official mirrors on the Tor network.
> > > 
> > > Not going to happen. If you can find a trustworthy source of files on
> > > one of those networks you could download the img or iso and install
> > > from there, but the install kernel is a very constrained environment -
> > > there's no space to add things like that.
> > 
> > I'm not asking for Tor or I2P to be added to the base system, but rather for
> > the ability to use mirrors hosted on these networks without having to go
> > through a lot of steps [1]. Ideally, it should be as simple as installing
> > the necessary software (even if it's from the ports tree), configuring and
> > running it, and then adding the mirror address to installurl(5). This should
> > be sufficient to install and update the system and packages.
> > 
> > On the other hand, there are kernel drivers for WireGuard, but WireGuard is
> > not included in the base system because it violates OpenBSD's copyright
> > policy. In contrast, the Tor and I2Pd routing software is licensed under the
> > 3-Clause BSD license.
> > 
> > [1]
> > https://dataswamp.org/~solene/2024-05-25-openbsd-privacy-friendly-mirror.html
> > 
> 
> Actually even I do not know what you mean...
> I am perfectly fine with [1]
> I am fine if it were to actually... well.. like work all the time every time 
> xD
> 
> Solene from [1] says the following:
> > Note: from experience the I2P mirror works fine to install packages, but did
> > not play well with fw_update, syspatch and sysupgrade, maybe because they 
> > use
> > ftp command that seems to easily drop the connection. Downloading the files
> > locally using a proper HTTP client supporting transfer resume would be
> > better. On the other hand, this issue may be related to the current attack
> > the I2P network is facing as of the time of writing (May 2024).
> 
> So IDK where ftp source code is and what exactly needs to be adjusted.
> Like I said, while using I2P I get 2 bugs outside this main bug for which I
> started this thread:
> bug a) sysupgrade exits without anything printed out, I forgot to check what
> the exit code was..
> 
> bug b) sysupgrade in the place of kb/s prints 'stalled', and the connection
> never recovers. What does "easily drop the connection" here entail?
> Is there some sort of timeout that can be adjusted, or preferably we could
> have a flag for slow/extremely slow connections.
> 
> Actually while for the many times I searched the manual page of ftp, I always
> grepped, I didn't read the entire manual page, and if the following works, 
> then
> neither did Solene:
>   I read more and found that we might be able to fix this by using ftp options
>   -A and/or -k [seconds].
> 
> 
> 
> I'll be testing and playing with this, and if it works out, will we be able to
> say get an flag option for slow networks such as
>   '-p   Be patient with the connection. This is perfect for slow/unstable
>         networks'
> in sysupgrade(8)? By "get" I mean would a patch of my own making be approved 
> if
> I were to apply it?
> 
> By the way my brain can't computer if I need a number for -k higher than the
> default 60 or lower lmao... I guess I'll see, but right now I have to wait for
> new snapshots :d
> I guess this might take a few days to perfect? No idea.. there's like 2
> snapshots per day, or something like that, right?
> 
> 
> [1]
> https://dataswamp.org/~solene/2024-05-25-openbsd-privacy-friendly-mirror.html

Reply via email to