Index | Thread | Search

From:
beecdaddict@danwin1210.de
Subject:
Re: [Fwd: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login]
To:
openbsd@systemfailure.net
Cc:
ports@openbsd.org
Date:
Tue, 30 Jan 2024 10:53:35 -0000

Download raw body.

Thread
I see the confusion I made I am sorry, when I said routers crash I meant
actual ISP hardware routers.

not sure how torrenting with i2pd should increase crashing risk as connections
are pre-made with I2P, so qBitorrent I think is just using a proxy and
connections being made shouldn't increase FD count? I am not sure exactly, but
something tells me that the connections being made by torrenting and thus FD
count increased is pre-handled by i2pd already as I2Pd has connections
in-place already? I am not sure but this makes some sense

it should be the ideal OS choice because security shouldn't come with
compromises, and those that do are uncapable of divine intellect creation!
I think OpenBSD should suffice for the use-case, not sure.
if something crashes or is not at 100% potential, something should be fixed.

like I asked and no one answered: where can I check HARD LIMIT of my computer?
what it depends on, on CPU? where is utility that shows max FDs, and
per-running-process FD usage and their max setting?
if this does not exist, I think why not?
I think if user has to manually set FD limits and know potential of programs
and OpenBSD and hardware, where is utility to help with that? I did search on
the internet, all shit..

- best regards and with hope because I thought no one interested

On Mon, January 29, 2024 10:23 pm, openbsd@systemfailure.net wrote:
> As I implied in another message, this file limit problem, causing your i2pd
> instance to crash, is not related to i2pd itself but to torrenting. I guess
> OpenBSD, with its strict security defaults, may not be the ideal operating
> system for high volume torrenting...
>
>
> On Sunday, January 28th, 2024 at 11:41 AM, beecdaddict at danwin1210.de
> <beecdaddict_at_danwin1210_de_lytbt@simplelogin.co> wrote:
>
>
>> and that doesn't cover routers crashing/rebooting? is there anything to be
>> done about that? router als ocrashes with high normal clernet traffic
>> torrenting.. a little off topic so sorry, perhaps router ran out of file
>> descriptors xd
>>
>
>> On Sat, January 27, 2024 10:34 pm, openbsd@systemfailure.net wrote:
>>
>>
>
>>> i2pd has always been working fine for me with the port's default values
>>> of openfiles-cur=8192, openfiles-max=8192 and kern.maxfiles=16000. These
>>> values are probably even overkill according to i2pd's documentation.
>>>
>
>>> But I'm not using it for torrenting, and my router is not a floodfill. I
>>> guess that torrenting may exhaust available file descriptors pretty
>>> quickly.
>>>
>
>>> My 2 cents.
>>>
>>>
>
>>> On 2024-01-27 19:29 beecdaddict@danwin1210.de wrote:
>>>
>>>
>
>>>> ------------------------------ Original Message
>>>> ------------------------------
>>>> Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
>>>>  From: beecdaddict@danwin1210.de
>>>> Date: Sat, January 27, 2024 7:16 pm
>>>> To: "Stuart Henderson" stu@spacehopper.org
>>>> ------------------------------------------------------------------------
>>>> ----
>>>> --
>>>>
>>>
>
>>>> this software crashes all lower-bandwidth routers I tried using it on.
>>>> my computer crashed a few times, but probably not because of what you
>>>> said.. I did have kern.maxfiles set to 65565 or something like that,
>>>> which probably was able to cause the crash.. so I ask how can someone
>>>> check how many openfiles are supported? What depends on how many you can
>>>> have?
>>>
>
>>>> i2pd is something similar to torrenting, but anonymous meaning it
>>>> protects us from anyone including abusive governments and people you
>>>> make connection to routers(other peers runing I2P software like i2pd)
>>>> and do it so many times how many connections you make depends on how
>>>> many tunnels you allow (default
>>>> 5000) and probably speed bandwidth
>>>>
>>>
>
>>>> It can use as much as someone allows it.. which be tricky on openbsd
>>>> because user has to set openfiles, cannot be flexible at runtime. and no
>>>> idea what counts as openfile in i2pd, tunnels? routers maybe, too? so by
>>>> default if tunnels 5000 unchange from i2pd.conf, could up to 15k
>>>> openfiles, who knows? But default speed is I think 32 KB/sec, which is
>>>> very low, so almost everyone increases it.
>>>
>
>>>> would love to know how to find out what best number your computer can
>>>> handle openfiles, what about shminfo? maxproc? maxvnodes? somaxconn?
>>>
>
>>>> how can find out max connections my router can handle? maybe router
>>>> overheat? he does same with qbittorrent, internet connection goes
>>>> goodbye
>>>
>
>>>> i2pd very very good project, worked on by Russians, they have no
>>>> freedom of speech
>>>
>
>>>> I updated to -current and I still have to set /etc/login.conf.d/i2pd
>>>> manually, otherwise I2Pd status is "no descriptors"
>>>
>
>>>> so yes 8192 seems low, not excessive, is similar to running webserver
>>>> maybe
>>>
>
>>>> and if OpenBSD crashes because of whoops no openfiles to give, CRASH,
>>>> that is bad need fix
>>>
>
>>>> hope this helps, thanks for maintenance.
>>
>
>>
>
>> [ REDACTED ]