Re: [mpv] --vo=gpu not working, permission denied
hi sorry it was a chown problem because tty0 and fbtab, someone else helped thanks for time question: vulken error is OK if you don't have vulkaninfo installed, yes? On Tue, February 27, 2024 5:49 am, Jose Maldonado wrote: > El Mon, 26 Feb 2024 21:54:43 - > beecdadd...@danwin1210.de escribió: >> hi list >> >> mpv does not work OpenBSD -current updated 2 days ago, pkg_add -u was >> done now Thinkpad T400 laptop with Intep GPU >> say if you need more info than this and down >> >> mpv gives this error (+) Video --vid=1 (*) (vp8 240x424 30.000fps) >> (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz) >> libEGL warning: MESA-LOADER: failed to retrieve device information >> >> libEGL warning: failed to open /dev/dri/card0: Permission denied >> >> libEGL warning: DRI2: could not open /dev/dri/card0 (Permission denied) >> [vo/gpu/opengl] Suspected software renderer or indirect >> context. [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL): >> VK_ERROR_INITIALIZATION_FAILED >> (../libplacebo-6.338.2/src/vulkan/context.c:984) >> [vo/gpu/libplacebo] Found no suitable device, giving up. >> [vo/gpu/libplacebo] Failed initializing vulkan device >> [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL): >> VK_ERROR_INITIALIZATION_FAILED >> (../libplacebo-6.338.2/src/vulkan/context.c:984) >> [vo/gpu] Failed initializing any suitable GPU context! >> Error opening/initializing the selected video_out (--vo) device. >> Video: no video >> Exiting... (Errors when loading file) >> >> >> >> >> dmesg gave this error, not fresh >> drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm] *ERROR* >> [CRTC:45:pipe A] flip_done timed out >> drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential >> atomic update failure on pipe A >> > > Hi! > > > Can you provide your mpv.conf and the exact output for theses > commands? > > 1) mpv -v --vo=gpu --gpu-api=opengl your_video > > > 2) mpv -v --vo=gpu --gpu-api=vulkan your_video > > > 3) glxinfo > > > 4) vulkaninfo > > > Please provide the info in separate files > > > -- > * > Dios en su cielo, todo bien en la Tierra > > >
[Fwd: Re: [mpv] --vo=gpu not working, permission denied]
Original Message Subject: Re: [mpv] --vo=gpu not working, permission denied From:beecdadd...@danwin1210.de Date:Tue, February 27, 2024 10:24 am To: "Stefan Hagen" -- thanks! I remember doing in past and looking at GiveConsole I can't believe I forgot about this of course I didn't know why it happened it fixes this yes can I ask why does console tty0 do that and not others, what is the purpose? best regards On Tue, February 27, 2024 6:00 am, Stefan Hagen wrote: > beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET): >> libEGL warning: failed to open /dev/dri/card0: Permission denied > > You can fix it with: chown /dev/dri/card0 /dev/dri/renderD128 > > > Xenodm does this automatically when you log in. > See /etc/X11/xenodm/GiveConsole > > > The permission are also set when you log in on ttyC0. > See /etc/fbtab and fbtab(5) > > > Therefore the permissions are changing when you jump out of X > with ctrl+alt+f1 and log in as root. When you hop back into X, the > permissions are wrong. > > This only happens on the first console. Use another one instead > (ctrl+alt+f2,3,4) while using X. > > > Best Regards, > Stefan
Re: [mpv] --vo=gpu not working, permission denied
you are faster than me asking questions well maybe a warning in dmesg or something will be nice so you don't get same people asking this fix? or save the initial user who owned /dev/dri/.. and then chown back to that after exit or something? On Tue, February 27, 2024 6:13 am, Theo de Raadt wrote: > This is because the fbtab subsystem is quite broken. No good > alternative designs have come forward. > > Stefan Hagen wrote: > > >> beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET): >>> libEGL warning: failed to open /dev/dri/card0: Permission denied >> >> You can fix it with: chown /dev/dri/card0 /dev/dri/renderD128 >> >> >> Xenodm does this automatically when you log in. >> See /etc/X11/xenodm/GiveConsole >> >> >> The permission are also set when you log in on ttyC0. >> See /etc/fbtab and fbtab(5) >> >> >> Therefore the permissions are changing when you jump out of X >> with ctrl+alt+f1 and log in as root. When you hop back into X, the >> permissions are wrong. >> >> This only happens on the first console. Use another one instead >> (ctrl+alt+f2,3,4) while using X. >> >> >> Best Regards, >> Stefan >> >> > >
[mpv] --vo=gpu not working, permission denied
hi list mpv does not work OpenBSD -current updated 2 days ago, pkg_add -u was done now Thinkpad T400 laptop with Intep GPU say if you need more info than this and down mpv gives this error (+) Video --vid=1 (*) (vp8 240x424 30.000fps) (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz) libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to open /dev/dri/card0: Permission denied libEGL warning: DRI2: could not open /dev/dri/card0 (Permission denied) [vo/gpu/opengl] Suspected software renderer or indirect context. [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL): VK_ERROR_INITIALIZATION_FAILED (../libplacebo-6.338.2/src/vulkan/context.c:984) [vo/gpu/libplacebo] Found no suitable device, giving up. [vo/gpu/libplacebo] Failed initializing vulkan device [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL): VK_ERROR_INITIALIZATION_FAILED (../libplacebo-6.338.2/src/vulkan/context.c:984) [vo/gpu] Failed initializing any suitable GPU context! Error opening/initializing the selected video_out (--vo) device. Video: no video Exiting... (Errors when loading file) dmesg gave this error, not fresh drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A
where is serious sam package?
hi list I don't know how long it takes for ports to be added, I just want to know it's not forgotten https://www.mail-archive.com/ports@openbsd.org/msg122960.html there is also non-alpha version of the game here and apparently supports OpenBSD https://github.com/tx00100xt/SeriousSamClassic-VK thanks have nice day
Re: [net/nheko] is crashes after login can't use dbus?
On Sun, February 25, 2024 3:46 pm, Klemens Nanni wrote: > On Sun, Feb 25, 2024 at 03:43:39PM -, beecdadd...@danwin1210.de > wrote: > >> hi list nheko crashes after a register/login complaining about secret >> storage keyring >> >> here is error messsage Nheko could not connect to the secure storage to >> save encryption secrets to. This can have multiple reasons. Check if >> your D-Bus service is running and you have configured a service like >> KWallet, Gnome Keyring, KeePassXC >> or the equivalent for your platform. If you are having trouble, feel >> free to open an issue here: https://github.com/Nheko-Reborn/nheko/issues >> > > That's not a crash. > > > Configure D-Bus/whatever accordingly or disable secret service > functionality: you mean the readme on https://openports.pl/path/x11/dbus ? I almost did that, does it works? this is a bug, software should work out of the box, or at least get https://openports.pl/path/x11/dbus readme message when installing nheko, if it fixes bug(didn't test) > > > $ head -n2 ~/.config/nheko/nheko.conf > [General] > run_without_secure_secrets_service=true thanks it works! > >> here is same issue https://github.com/Nheko-Reborn/nheko/issues/1609 >> mentions permissions.. >> >> console says this [db] [error] Restoring secret >> 'nheko.BIGNUMBER=.pickle_secret' failed (7): Unknown error >> >
[net/nheko] is crashes after login can't use dbus?
hi list nheko crashes after a register/login complaining about secret storage keyring here is error messsage Nheko could not connect to the secure storage to save encryption secrets to. This can have multiple reasons. Check if your D-Bus service is running and you have configured a service like KWallet, Gnome Keyring, KeePassXC or the equivalent for your platform. If you are having trouble, feel free to open an issue here: https://github.com/Nheko-Reborn/nheko/issues here is same issue https://github.com/Nheko-Reborn/nheko/issues/1609 mentions permissions.. console says this [db] [error] Restoring secret 'nheko.BIGNUMBER=.pickle_secret' failed (7): Unknown error
Re: [NEW PORT] graphics/glad - Multi-Language Vulkan/GL/GLES/EGL/GLX/WGL Loader-Generator
there is Rust code on it's github, does it have Rust as a dependency? if it has Rust as dependency or cargo or whatever, I am deleting mpv and never using it again can I block some dependencies or langs from building/installing? I want that if it doesn't exist, it wouldn't be hard to write a bit of code to search trough the list of dependencies and check with name, maybe if it doesn't exist the blacklist could be in /usr/ports/Makefile or something? I would like to know thanks and sorry if there is answer on internet, I tried looking many times for compiling ports and flags On Mon, February 12, 2024 5:42 pm, Jose Maldonado wrote: > > Hello everyone! Another new port here! > > > In this case I bring graphics/glad [1] a Multi-Language > Vulkan/GL/GLES/EGL/GLX/WGL Loader-Generator that is part of the new > dependencies to build libplacebo (>=v6.338.0) and therefore necessary to > build mpv (v0.37.0) > > Built and tested, take a look and feedback is welcome. > > > [1] https://github.com/Dav1dde/glad > > > -- > * > Dios en su cielo, todo bien en la Tierra > >
[yt-dlp][patch] add 3 .i2p adresses to extractor/youtube.py
hello list, I mailed the yt-dlp developer with the attached diff patch, not sure when the patch will be applied and it maybe take months? so now have this and maybe remove when it is merged in next release? I don't compile myself and others might like this I am sorry directory structure in diff maybe not right and because of how I2P works, not every site has a working .i2p domain, so we have to include .b32.i2p main address for every .i2p domain example: http://inv.vern.i2p worked but now it redirects to http://vern.i2p, so I added the b32.i2p of the inv instance thanks and sorry if this isn't good because its temporarily fix--- youtube.py Sat Dec 30 22:43:13 2023 +++ youtube.py.new Sat Feb 10 19:11:05 2024 @@ -320,6 +320,9 @@ r'(?:www\.)?invidious\.ethibox\.fr', r'(?:www\.)?iv\.ggtyler\.dev', r'(?:www\.)?inv\.vern\.i2p', + r'(?:www\.)?verni6dr4qxjgjumnvesxerh5rvhv6oy5ddeibaqy5d7tgbiiyfa\.b32\.i2p', +r'(?:www\.)?tube\.i2p', + r'(?:www\.)?vipzc556nzjraiqsk5xwvyhz54fvtqt3vrepdarat3zsj4a6eypq\.b32\.i2p', r'(?:www\.)?am74vkcrjp2d5v36lcdqgsj2m6x36tbrkhsruoegwfcizzabnfgf5zyd\.onion', r'(?:www\.)?inv\.riverside\.rocks', r'(?:www\.)?invidious\.silur\.me',
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
I don't know, I told you, all I worked with are what you guys told me, what made sense and what I could found online I did not read code because I am not OS dev and don't have as much time as I would like, so this is the best I could do, Theo didn't tell me if I was wrong or right, he told me to make changes to source code and he is out.. does that mean I am right or to just read source code? I maybe make no sense always, but neither do you guys I am as friendly as I can be, I said what I tried and didn't try, and who I am and who I am not - best regards, I hope we can make friendships regardless of out differences and knowledge, enemies are easy to make On Tue, January 30, 2024 4:08 pm, Bruce Jagid wrote: > If you actually thought you knew what you were talking about, you wouldn’t > feel the need to insert “I’m not an OS Dev” after everything you say > > On Tue, Jan 30, 2024 at 11:05 AM wrote: > > >> oh, Theo, if I were to start changing thing to the perfect OS security-wise, >> it wouldn't even look like OpenBSD code anymore, but OpenBSD still best >> what world have to offer >> >> so do you agree with my logic? at least give me that at least tell me is >> this how things stand FD-wise/limit-wise/whatever, you probably know the >> best out of all I e-mailed with >> >> no attempt yet,in future I hope,it's not a I am too lazy reason >> >> On Tue, January 30, 2024 3:58 pm, Theo de Raadt wrote: >> >>> beecdadd...@danwin1210.de wrote: >>> I know system shares all resources including FDs as far as I know there's what kernel/OS needs and is using and the rest >> of users including but not limited to staff and daemon users/programs like i2pd all I was wondering is the limit or amount of FDs and other >> resources the rest of users of daemon can use in my head is a total amount which apparently is unknown (I have been told why, but how can anyone work >> with that? it's like relying on someone mentally unstable) which is then >> devided, kernel/OS gets all that it needs, users and daemons get the rest which >> IS >> DIVIDED (in my head) until there is no more to divide/give away/share am I close? okay maybe not make all available resources to 1 program is not how it works but why not if that's the only programs that's running? I do not understand if it's even possible to do what I'm asking or questioning, >> I am >> not a OS dev because of reasons, but I like discussing such because I >> like OS-dev and just because what I ask isn't how it works doesn't mean it's bad? it could mean >>> >>> You've been provided with all the source code. >>> >>> >>> >>> Where is your attempt to change things? >>> >>> >>> >>> >> >> >> >
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
oh, Theo, if I were to start changing thing to the perfect OS security-wise, it wouldn't even look like OpenBSD code anymore, but OpenBSD still best what world have to offer so do you agree with my logic? at least give me that at least tell me is this how things stand FD-wise/limit-wise/whatever, you probably know the best out of all I e-mailed with no attempt yet,in future I hope,it's not a I am too lazy reason On Tue, January 30, 2024 3:58 pm, Theo de Raadt wrote: > beecdadd...@danwin1210.de wrote: > >> I know system shares all resources including FDs >> as far as I know there's what kernel/OS needs and is using and the rest of >> users including but not limited to staff and daemon users/programs like >> i2pd all I was wondering is the limit or amount of FDs and other resources >> the rest of users of daemon can use in my head is a total amount which >> apparently is unknown (I have been told why, but how can anyone work with >> that? it's like relying on someone mentally unstable) which is then devided, >> kernel/OS gets all that it needs, users and daemons get the rest which IS >> DIVIDED (in my head) until there is no more to >> divide/give away/share am I close? >> >> okay maybe not make all available resources to 1 program is not how it >> works but why not if that's the only programs that's running? I do not >> understand if it's even possible to do what I'm asking or questioning, I am >> not a OS dev because of reasons, but I like discussing such because I like >> OS-dev >> >> >> and just because what I ask isn't how it works doesn't mean it's bad? it >> could mean > > You've been provided with all the source code. > > > Where is your attempt to change things? > > >
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
I know system shares all resources including FDs as far as I know there's what kernel/OS needs and is using and the rest of users including but not limited to staff and daemon users/programs like i2pd all I was wondering is the limit or amount of FDs and other resources the rest of users of daemon can use in my head is a total amount which apparently is unknown (I have been told why, but how can anyone work with that? it's like relying on someone mentally unstable) which is then devided, kernel/OS gets all that it needs, users and daemons get the rest which IS DIVIDED (in my head) until there is no more to divide/give away/share am I close? okay maybe not make all available resources to 1 program is not how it works but why not if that's the only programs that's running? I do not understand if it's even possible to do what I'm asking or questioning, I am not a OS dev because of reasons, but I like discussing such because I like OS-dev and just because what I ask isn't how it works doesn't mean it's bad? it could mean - best regards, my man On Tue, January 30, 2024 3:45 pm, Theo de Raadt wrote: > beecdadd...@danwin1210.de wrote: > >> maybe not automatically, but having a utility that does this for you and >> you can run it once after each hardare change to find out, but I am not sure >> you say it depends on use-case, I do not understand what you mean >> >> if you read my earlier replies, you would find out that I said I already >> tried searching online for like 1 hour, there is some sort of crazy formula >> one dude did a lot of math, snipets from code, is that what you mean? because >> what you say sound like there are multiple types of FDs, maybe network FDs >> and normal FDs? > > > You are failing to understand the operating system is intending to be a > "sharing" environment -- it is sharing limited resources among multiple > consumers. > > A large number of heuristics exist to defend this sharing, rather than > making resources available to just the 1 piece of software you want. > > What you want isn't how it works. > > > > >
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
human body changes: different energy levels, tiredness, soar muscle, andrenaline, weight of curls, type of curl like you said computer has same exact hardware every time unless changed like I mentioned nothing changes most servers have different and changing software programs on it, yes but we are talking about system hard limit, not soft limits, the hard limit should stay the same of course you're done, you make no sense to me maybe because you know more or you maybe misunderstand me I think this is far too off-topic and not for ports@ but let's end this topic so I can go maybe to tech@ and misc@ On Tue, January 30, 2024 3:39 pm, Bruce Jagid wrote: > no, YOU know more or less based on earlier curls, just like YOU know more or > less based on other programs you’ve run on your OS. And that guess would be > incredibly inaccurate. You can’t just ask for a concrete hard limit and then > relax the conditions such that it becomes a guesstimate. You don’t even > believe your own bs, I’m done arguing. > > On Tue, Jan 30, 2024 at 10:33 AM wrote: > > >> On Tue, January 30, 2024 3:25 pm, Bruce Jagid wrote: >> I'm also not a OS dev cannot the OS do some testing/benchmarking >to get a grasp on what the >>> limit could be? YOU are the OS in your example, and you >would know the limit >> when you >>> would do curls slower and maybe you would get more >and more pain.. and crash in >> your example would be your >muscle being in such pain you >>> wouldn't be able to do anything with your >arm/whatever >>> >>> So your body automatically benchmarks how many bicep curls you can do in >>> >> an >>> hour without you having to think about it? You use your body to measure >> the >>> bicep curls it can do, it doesn’t automatically do that. You can use >> your OS >>> to perform the benchmark, but to expect the OS to designate resources >>> automatically to benchmark itself is equal portions naïve and obtuse. >> You have >> >>> a very specific use-case, you should do the work to find your answer. >> >> it can know limit more-less, yes, based on earlier curls >> >> maybe not automatically, but having a utility that does this for you and you >> can run it once after each hardare change to find out, but I am not sure >> you say it depends on use-case, I do not understand what you mean >> >> if you read my earlier replies, you would find out that I said I already >> tried searching online for like 1 hour, there is some sort of crazy formula >> one dude did a lot of math, snipets from code, is that what you mean? because >> what you say sound like there are multiple types of FDs, maybe network FDs >> and normal FDs? >> >> - best regards >> >> >>> >>> >>> On Tue, Jan 30, 2024 at 10:20 AM wrote: >>> >>> >>> I'm also not a OS dev cannot the OS do some testing/benchmarking to get a grasp on what the >> limit could be? YOU are the OS in your example, and you would know the limit >> when you would do curls slower and maybe you would get more and more pain.. >> and crash in your example would be your muscle being in such pain you >> wouldn't be able to do anything with your arm/whatever so you're saying the only fucking way to know a true hardware limit is >> the worst that could be - a crash??? what if crash doesn't happen right >> away? in my case hardware ISP router could be limiting the potential of i2pd >> software or torrenting software boom corrupted data, processes, uncompleted >> important work, lost important work, pain in ass, etc literally couldn't that >> corrupt the entire system, a crash? tell me I am worrying too much, but even then a crash is the worst thing someone can rely on, I think it's unprofessional that the OS allows for >> that sort of insecurity if all you said and I said is correct, I consider >> that to be a security vulnerability at least, not to mention other vulnerabilities On Tue, January 30, 2024 1:32 pm, Bruce Jagid wrote: like I asked and no one answered: where >>>can I check HARD LIMIT of my computer? >>> >>> you can't really. you can try increasing >>until you run into >>> problems > and back >>> off a bit, but it probably depends on what >>else the kernel is >>> doing. > usual >>> approach is to restrict the software to >>using the resources >>> that you > expect it >>> to actually need and restrict it from making >>more demands than >>> that >>> to > orotect >>> the rest of the system. > >> this sounds like a bug to me hard limit must be known, else is like >> playing >>> cards, you never know when > you >> lose (you crash) and no one answered my question yet about >i2pd's >> connections to other > routhers >> with can well surpass 8192 up to +3 >connections, and if I am >>
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
I'm sorry, it felt applicable reasons outside of OpenBSD I got no problem with swearing back at me I felt kernel crashes are off-topic, I thought it would be fine because I didn't know it would go for so long this topic of course it is not your problem me crashing non-OpenBSD el-cheapo home router, but OpenBSD guys know networking and maybe routers the best, and maybe benefit others, do I do this on misc@ ? On Tue, January 30, 2024 3:26 pm, Ian Darwin wrote: > On 1/30/24 10:20, beecdadd...@danwin1210.de wrote: > >> so you're saying the only fucking way to know a true hardware limit is the >> worst that could be - a crash??? > > Once you start swearing, most people will tune you out. Others will > swear back at you. > > Neither is very productive. > > > Anyway, discussion of kernel crashes belongs on tech@, and discussion of > crashing your non-OpenBSD el-cheapo home router is not our problem anyway. >
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
On Tue, January 30, 2024 3:25 pm, Bruce Jagid wrote: >> I'm also not a OS dev >> cannot the OS do some testing/benchmarking >to get a grasp on what the > limit >> could be? YOU are the OS in your example, and you >would know the limit when >> you > would do >> curls slower and maybe you would get more >and more pain.. and crash in your >> example would be your >muscle being in such pain you > wouldn't >> be able to do anything with your >arm/whatever > > So your body automatically benchmarks how many bicep curls you can do in an > hour without you having to think about it? You use your body to measure the > bicep curls it can do, it doesn’t automatically do that. You can use your OS > to perform the benchmark, but to expect the OS to designate resources > automatically to benchmark itself is equal portions naïve and obtuse. You have > a very specific use-case, you should do the work to find your answer. it can know limit more-less, yes, based on earlier curls maybe not automatically, but having a utility that does this for you and you can run it once after each hardare change to find out, but I am not sure you say it depends on use-case, I do not understand what you mean if you read my earlier replies, you would find out that I said I already tried searching online for like 1 hour, there is some sort of crazy formula one dude did a lot of math, snipets from code, is that what you mean? because what you say sound like there are multiple types of FDs, maybe network FDs and normal FDs? - best regards > > > On Tue, Jan 30, 2024 at 10:20 AM wrote: > > >> I'm also not a OS dev >> cannot the OS do some testing/benchmarking to get a grasp on what the limit >> could be? YOU are the OS in your example, and you would know the limit when >> you would do curls slower and maybe you would get more and more pain.. and >> crash in your example would be your muscle being in such pain you wouldn't be >> able to do anything with your arm/whatever >> >> so you're saying the only fucking way to know a true hardware limit is the >> worst that could be - a crash??? what if crash doesn't happen right away? in >> my case hardware ISP router could be limiting the potential of i2pd software >> or torrenting software boom corrupted data, processes, uncompleted important >> work, lost important work, pain in ass, etc literally couldn't that corrupt >> the entire system, a crash? >> >> tell me I am worrying too much, but even then a crash is the worst thing >> someone can rely on, I think it's unprofessional that the OS allows for that >> sort of insecurity if all you said and I said is correct, I consider that >> to be a security vulnerability at least, not to mention other >> vulnerabilities >> >> On Tue, January 30, 2024 1:32 pm, Bruce Jagid wrote: >> >> >> >> like I asked and no one answered: where >>>can I check HARD LIMIT >> of >> my >> computer? > > you can't really. you can try increasing >>until you run into > problems >>> and back > off a bit, but it probably depends on what >>else the kernel is > doing. >>> usual > approach is to restrict the software to >>using the resources that > you >>> expect it > to actually need and restrict it from making >>more demands than that > >> to >>> orotect > the rest of the system. >>> this sounds like a bug to me hard limit must be known, else is like >> playing > cards, you never know when >>> you lose (you crash) and no one answered my question yet about >i2pd's connections to other >>> routhers with can well surpass 8192 up to +3 >connections, and if I am right >>> then each connection needs a FD? I worked with >networking and programming a >>> little, so this makes sense to me can anyone >verify? if yes, then yes this is >> a bug and I am >disappointed that the only way is >>> to run blindly and trust before crash >>> >>> I might be out of line here since I’m new to OS dev stuff, but what >>> >> you’re >>> asking doesn’t really make sense to me. A file descriptor is a software >>> abstraction built onto the hardware and the exact implementation changes >> from >>> case to case dependent on hardware. It’s like if I asked my doctor “give >> me >>> the exact limit of bicep curls I can do in an hour.” In the same way the >> body >>> has no conception of a bicep curl(only the fatigue from moving), the >> hardware >>> doesn’t know what you mean by a file descriptor(only the residual >> resources >>> needed to maintain one), and there’s like 20 ways of doing a bicep curl, >> so >>> demanding such a concrete hard limit number makes no sense. >>> >>> - Bruce >>> >>> >>> >>> On Tue, Jan 30, 2024 at 6:52 AM wrote: >>> >>> >>> On Tue, January 30, 2024 11:23 am, Stuart Henderson wrote: > On 2024/01/30 10:53, beecdadd...@danwin1210.de wrote: > > > >> I see the confusion I made I am sorry, when I said routers crash I >> meant actual ISP
Re: (changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
I'm also not a OS dev cannot the OS do some testing/benchmarking to get a grasp on what the limit could be? YOU are the OS in your example, and you would know the limit when you would do curls slower and maybe you would get more and more pain.. and crash in your example would be your muscle being in such pain you wouldn't be able to do anything with your arm/whatever so you're saying the only fucking way to know a true hardware limit is the worst that could be - a crash??? what if crash doesn't happen right away? in my case hardware ISP router could be limiting the potential of i2pd software or torrenting software boom corrupted data, processes, uncompleted important work, lost important work, pain in ass, etc literally couldn't that corrupt the entire system, a crash? tell me I am worrying too much, but even then a crash is the worst thing someone can rely on, I think it's unprofessional that the OS allows for that sort of insecurity if all you said and I said is correct, I consider that to be a security vulnerability at least, not to mention other vulnerabilities On Tue, January 30, 2024 1:32 pm, Bruce Jagid wrote: like I asked and no one answered: where >>>can I check HARD LIMIT of my computer? >>> >>> you can't really. you can try increasing >>until you run into problems > and back >>> off a bit, but it probably depends on what >>else the kernel is doing. > usual >>> approach is to restrict the software to >>using the resources that you > expect it >>> to actually need and restrict it from making >>more demands than that to > orotect >>> the rest of the system. > >> this sounds like a bug to me hard limit must be known, else is like playing >> >cards, you never know when > you >> lose (you crash) and no one answered my question yet about >i2pd's >> connections to other > routhers >> with can well surpass 8192 up to +3 >connections, and if I am right > then >> each connection needs a FD? I worked with >networking and programming a > little, >> so this makes sense to me can anyone >verify? if yes, then yes this is a bug >> and I am >disappointed that the only way is > to >> run blindly and trust before crash > > I might be out of line here since I’m new to OS dev stuff, but what you’re > asking doesn’t really make sense to me. A file descriptor is a software > abstraction built onto the hardware and the exact implementation changes from > case to case dependent on hardware. It’s like if I asked my doctor “give me > the exact limit of bicep curls I can do in an hour.” In the same way the body > has no conception of a bicep curl(only the fatigue from moving), the hardware > doesn’t know what you mean by a file descriptor(only the residual resources > needed to maintain one), and there’s like 20 ways of doing a bicep curl, so > demanding such a concrete hard limit number makes no sense. > > - Bruce > > > On Tue, Jan 30, 2024 at 6:52 AM wrote: > > >> On Tue, January 30, 2024 11:23 am, Stuart Henderson wrote: >> >>> On 2024/01/30 10:53, beecdadd...@danwin1210.de wrote: >>> >>> I see the confusion I made I am sorry, when I said routers crash I meant actual ISP hardware routers. >>> >>> For an ISP "customer premises equipment" router (home/officr router)? >>> That often means you made too many connections and exceeded the size of >>> NAT/firewall state table that they can cope with. Also for ISPs with >>> CGN, you might have a limited port-range that you're allowed to use and >>> can't make more connections once that has been exceeded. >> >> is there way to verify it's the 1st thing, which can be fixed by custom >> router, yes? any computer with 2 NICs can be a OpenBSD router, yes? I seen >> people do that, is cool >> >>> like I asked and no one answered: where can I check HARD LIMIT of my computer? >>> >>> you can't really. you can try increasing until you run into problems and >> back >>> off a bit, but it probably depends on what else the kernel is doing. >> usual >>> approach is to restrict the software to using the resources that you >> expect it >>> to actually need and restrict it from making more demands than that to >> orotect >>> the rest of the system. >> >> this sounds like a bug to me hard limit must be known, else is like playing >> cards, you never know when you lose (you crash) and no one answered my >> question yet about i2pd's connections to other routhers with can well surpass >> 8192 up to +3 connections, and if I am right then >> each connection needs a FD? I worked with networking and programming a >> little, so this makes sense to me can anyone verify? if yes, then yes this is >> a bug and I am disappointed that the only way is to run blindly and trust >> before crash >> >>> 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
Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
> I probably cannot verify the usage of I2Pd if it exceeds 8192 because my router goes stupid and crashes, can you? sorry I meant hardware router crashes, is stupid i2p term 'router' which means 'i2p router'
(changed subject) Re: net/i2pd: FD talk and limits and ISP routers too weak maybe
On Tue, January 30, 2024 11:23 am, Stuart Henderson wrote: > On 2024/01/30 10:53, beecdadd...@danwin1210.de wrote: > >> I see the confusion I made I am sorry, when I said routers crash I meant >> actual ISP hardware routers. > > For an ISP "customer premises equipment" router (home/officr router)? > That often means you made too many connections and exceeded the size of > NAT/firewall state table that they can cope with. Also for ISPs with > CGN, you might have a limited port-range that you're allowed to use and > can't make more connections once that has been exceeded. is there way to verify it's the 1st thing, which can be fixed by custom router, yes? any computer with 2 NICs can be a OpenBSD router, yes? I seen people do that, is cool > >> like I asked and no one answered: where can I check HARD LIMIT of my >> computer? > > you can't really. you can try increasing until you run into problems and back > off a bit, but it probably depends on what else the kernel is doing. usual > approach is to restrict the software to using the resources that you expect it > to actually need and restrict it from making more demands than that to orotect > the rest of the system. this sounds like a bug to me hard limit must be known, else is like playing cards, you never know when you lose (you crash) and no one answered my question yet about i2pd's connections to other routhers with can well surpass 8192 up to +3 connections, and if I am right then each connection needs a FD? I worked with networking and programming a little, so this makes sense to me can anyone verify? if yes, then yes this is a bug and I am disappointed that the only way is to run blindly and trust before crash > >> 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.. > > fstat shows per-process FD use, but the kernel backend for it is a bit buggy > and can sometimes crash the kernel, so it is best to avoid running it on an > important system. > > oh really I probably cannot verify the usage of I2Pd if it exceeds 8192 because my router goes stupid and crashes, can you? if you can't I'll give it a try, please tell me if you can.. I would try increasing bandwidth speed to X and transit tunnels to maybe 10k, try with a floodfill maybe, too.. because even many tunnels - there can be many to 1 i2pd peer(i2pd router) which translates to 1 FD, right? and if you go to web console of i2pd and go to Transit Tunnels tab, you can see => [some number like ID] 5.0 KiB, and then you see more of same, but the arrow '=>' is not there, so that maybe indicates it's the same peer/i2pd router that the following tunnels are to/from.. most have 1 tunnel, some have 6 tunnels, a lot have 2 tunnels but I am not getting FD count with fstat, the number is not the same with 'Routers' in web console of i2pd, so maybe I was wrong or maybe i2pd recycles FDs to be much better at efficiency so it has Routers stored addresses somewhere, and makes connections only if needed (which take up FD spots) - best regards, I like talking to you, you care about this and want to help, it can be seen
Re: [Fwd: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login]
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, open...@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 > 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, open...@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 beecdadd...@danwin1210.de wrote: >>> >>> > >>>> -- Original Message >>>> -- >>>> Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login >>>> From: beecdadd...@danwin1210.de >>>> Date: Sat, January 27, 2024 7:16 pm >>>> To: "Stuart Henderson" s...@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 ]
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
is good to know
some software does require a lot of file descriptors, and you might want to
get all potential out of software
On Mon, January 29, 2024 10:09 am, Stuart Henderson wrote:
> On 2024/01/28 20:09, beecdadd...@danwin1210.de wrote:
>
>> why are yo uignoring my reply? 4096 doesn't cover everyone like I said
>> people can become floodfills automatically and floodfills means 8192
>
> If 4096 is not enough and the software requires 8192 to work (which is
> above the default sysctl limit) we'd better just leave it in the readme and
> not
> add the login.conf.d file. Automating just half of it leaves users in a worse
> position than doing nothing.
>
> Really the software should not assume that it has unlimited resources,
> and scale back when it runs into limits. But that seems a hard concept for
> some
> programmers to understand.
>
>>
>> On Sun, January 28, 2024 7:52 pm, Klemens Nanni wrote:
>>
>>> On Sun, Jan 28, 2024 at 06:15:52PM +, Stuart Henderson wrote:
>>>
>>>
On 2024/01/27 21:54, open...@systemfailure.net wrote:
> According to i2pd's online documentation [1], the maximum number of
> open file descriptors is 4096 for a regular node, and 8192 for a
> floodfill [2].
>
>
>
> I have never measured how many FDs i2pd is really using, but this
> software for sure needs a lot of them.
>
> So I guess we can set 4096 as default value, and inform users in the
> README file that this value should be raised to 8192 for floodfills.
>
>
4096 doesn't seem too unreasonable, it's below default levels of
kern.maxfiles, so if that's enough for the software I'd be happy with
setting that in a login.conf.d file.
>>>
>>> Thanks for all you feedback.
>>> OK?
>>>
>>>
>>>
>>>
>>> Index: Makefile
>>> ===
>>> RCS file: /cvs/ports/net/i2pd/Makefile,v
>>> diff -u -p -r1.22 Makefile --- Makefile 13 Jan 2024 16:21:39 -
>>> 1.22 +++
>>> Makefile24 Jan 2024 22:21:26 -
>>> @@ -3,6 +3,7 @@ COMMENT = client for the I2P anonymous n
>>> GH_ACCOUNT =PurpleI2P
>>> GH_PROJECT =i2pd
>>> GH_TAGNAME =2.50.2
>>> +REVISION = 0
>>>
>>>
>>>
>>> CATEGORIES =net
>>> HOMEPAGE = https://i2pd.website
>>> Index: pkg/PLIST
>>> ===
>>> RCS file: /cvs/ports/net/i2pd/pkg/PLIST,v
>>> diff -u -p -r1.12 PLIST --- pkg/PLIST 20 Dec 2023 22:19:44 -
>>> 1.12 +++
>>> pkg/PLIST 24 Jan 2024 22:30:37 - @@ -237,3 +237,7 @@
>>> share/examples/i2pd/tunnels.conf @owner _i2pd
>>> @group _i2pd
>>> @sample ${SYSCONFDIR}/i2pd/tunnels.conf
>>> +@owner
>>> +@group
>>> +share/examples/login.conf.d/i2pd
>>> +@sample ${SYSCONFDIR}/login.conf.d/i2pd
>>> Index: pkg/README
>>> ===
>>> RCS file: /cvs/ports/net/i2pd/pkg/README,v
>>> diff -u -p -r1.3 README --- pkg/README 8 Nov 2022 12:41:42 -
>>> 1.3 +++
>>> pkg/README 28 Jan 2024 19:51:52 - @@ -5,20 +5,7 @@
>>> Resource Limits: File Descriptors
>>> =
>>>
>>>
>>>
>>> -By default, the i2pd process runs in the login(1) class of "daemon".
>>> -The default limits on file descriptors are insufficient to run i2pd;
>>> instead you -should put the _i2pd user and process in their own login(1)
>>> class with tuned -resources. -You should also raise the system-wide
>>> maxfiles limit. +You should raise the system-wide maxfiles limit:
>>>
>>>
>>>
>>> -1. Configure i2pd login class in the login.conf(5) file:
>>> -
>>> -i2pd:\
>>> -:openfiles-cur=8192:\
>>> -:openfiles-max=8192:\
>>> -:tc=daemon:
>>> -
>>> -2. Adjust kern.maxfiles, if needed:
>>> -
>>> - # sysctl kern.maxfiles=16000
>>> - # echo "kern.maxfiles=16000" >> /etc/sysctl.conf
>>> + # sysctl kern.maxfiles=8192
>>> + # echo "kern.maxfiles=8192" >> /etc/sysctl.conf
>>> Index: pkg/i2pd.login
>>> ===
>>> RCS file: pkg/i2pd.login
>>> diff -N pkg/i2pd.login --- /dev/null1 Jan 1970 00:00:00 - +++
>>> pkg/i2pd.login 28 Jan 2024 19:51:32 - @@ -0,0 +1,4 @@
>>> +i2pd:\
>>> + :openfiles-cur=4096:\
>>> + :openfiles-max=4096:\
>>> + :tc=daemon:
>>>
>>>
>>>
>>>
>>
>>
>
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
I took you for a serious man.. I guess I was wrong On Sun, January 28, 2024 9:22 pm, Theo de Raadt wrote: > there is another possibility is everyone is out to get you. > > beecdadd...@danwin1210.de wrote: > >> anyone who cares about it - is using i2pd, and those that don't should if >> you understand me >> >> not everyone knows ins and outs of everything or have time, by enabling >> their software to run at full potential should be priority >> >> unless there are some unknown to me consequences of high number of >> openfiles? I tried searching online but found little, why does a limit >> kern.maxfiles have to be manually set and how can someone even know the hard >> true limit that wouldn't cause crashes (I assume that's what happens when >> system runs out of file descriptors I read it) >> >> - best regards, didn't sleep who sleeps these days? >> >> >> On Sun, January 28, 2024 8:21 pm, Theo de Raadt wrote: >> >>> beecdadd...@danwin1210.de wrote: >>> why are yo uignoring my reply? 4096 doesn't cover everyone like I said people can become floodfills automatically and floodfills means 8192 >>> >>> the 1 person who cares can change the default. >>> >>> >> >> > >
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
anyone who cares about it - is using i2pd, and those that don't should if you understand me not everyone knows ins and outs of everything or have time, by enabling their software to run at full potential should be priority unless there are some unknown to me consequences of high number of openfiles? I tried searching online but found little, why does a limit kern.maxfiles have to be manually set and how can someone even know the hard true limit that wouldn't cause crashes (I assume that's what happens when system runs out of file descriptors I read it) - best regards, didn't sleep who sleeps these days? On Sun, January 28, 2024 8:21 pm, Theo de Raadt wrote: > beecdadd...@danwin1210.de wrote: > >> why are yo uignoring my reply? 4096 doesn't cover everyone like I said >> people can become floodfills automatically and floodfills means 8192 > > the 1 person who cares can change the default. > >
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
why are yo uignoring my reply? 4096 doesn't cover everyone like I said people
can become floodfills automatically and floodfills means 8192
On Sun, January 28, 2024 7:52 pm, Klemens Nanni wrote:
> On Sun, Jan 28, 2024 at 06:15:52PM +, Stuart Henderson wrote:
>
>> On 2024/01/27 21:54, open...@systemfailure.net wrote:
>>
>>> According to i2pd's online documentation [1], the maximum number of open
>>> file descriptors is 4096 for a regular node, and 8192 for a floodfill
>>> [2].
>>>
>>>
>>> I have never measured how many FDs i2pd is really using, but this
>>> software for sure needs a lot of them.
>>>
>>> So I guess we can set 4096 as default value, and inform users in the
>>> README file that this value should be raised to 8192 for floodfills.
>>>
>>
>> 4096 doesn't seem too unreasonable, it's below default levels of
>> kern.maxfiles, so if that's enough for the software I'd be happy with setting
>> that in a login.conf.d file.
>
> Thanks for all you feedback.
> OK?
>
>
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/net/i2pd/Makefile,v
> diff -u -p -r1.22 Makefile --- Makefile 13 Jan 2024 16:21:39 -
> 1.22
> +++ Makefile 24 Jan 2024 22:21:26 -
> @@ -3,6 +3,7 @@ COMMENT = client for the I2P anonymous n
> GH_ACCOUNT = PurpleI2P
> GH_PROJECT = i2pd
> GH_TAGNAME = 2.50.2
> +REVISION = 0
>
>
> CATEGORIES = net
> HOMEPAGE =https://i2pd.website
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/net/i2pd/pkg/PLIST,v
> diff -u -p -r1.12 PLIST --- pkg/PLIST 20 Dec 2023 22:19:44 - 1.12
> +++ pkg/PLIST 24 Jan 2024 22:30:37 -
> @@ -237,3 +237,7 @@ share/examples/i2pd/tunnels.conf
> @owner _i2pd
> @group _i2pd
> @sample ${SYSCONFDIR}/i2pd/tunnels.conf
> +@owner
> +@group
> +share/examples/login.conf.d/i2pd
> +@sample ${SYSCONFDIR}/login.conf.d/i2pd
> Index: pkg/README
> ===
> RCS file: /cvs/ports/net/i2pd/pkg/README,v
> diff -u -p -r1.3 README --- pkg/README8 Nov 2022 12:41:42 -
> 1.3
> +++ pkg/README28 Jan 2024 19:51:52 -
> @@ -5,20 +5,7 @@
> Resource Limits: File Descriptors
> =
>
>
> -By default, the i2pd process runs in the login(1) class of "daemon".
> -The default limits on file descriptors are insufficient to run i2pd; instead
> you -should put the _i2pd user and process in their own login(1) class with
> tuned -resources.
> -You should also raise the system-wide maxfiles limit.
> +You should raise the system-wide maxfiles limit:
>
>
> -1. Configure i2pd login class in the login.conf(5) file:
> -
> -i2pd:\
> -:openfiles-cur=8192:\
> -:openfiles-max=8192:\
> -:tc=daemon:
> -
> -2. Adjust kern.maxfiles, if needed:
> -
> - # sysctl kern.maxfiles=16000
> - # echo "kern.maxfiles=16000" >> /etc/sysctl.conf
> + # sysctl kern.maxfiles=8192
> + # echo "kern.maxfiles=8192" >> /etc/sysctl.conf
> Index: pkg/i2pd.login
> ===
> RCS file: pkg/i2pd.login
> diff -N pkg/i2pd.login --- /dev/null 1 Jan 1970 00:00:00 -
> +++ pkg/i2pd.login28 Jan 2024 19:51:32 -
> @@ -0,0 +1,4 @@
> +i2pd:\
> + :openfiles-cur=4096:\
> + :openfiles-max=4096:\
> + :tc=daemon:
>
>
>
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
can we stop thinking of 4096 because i2pd software routers can automatically become floodfilles so is 8192 at lowest, this is future-proof and other replies I sent should indicate possibly much more, no one answered yet, I do not understand OpenBSD well but something tells me each record of a i2pd software router has it's own file descriptor, I did some programming in past so this makes sense to me am I wrong? On Sun, January 28, 2024 6:15 pm, Stuart Henderson wrote: > On 2024/01/27 21:54, open...@systemfailure.net wrote: > >> According to i2pd's online documentation [1], the maximum number of open >> file descriptors is 4096 for a regular node, and 8192 for a floodfill [2]. >> >> I have never measured how many FDs i2pd is really using, but this software >> for sure needs a lot of them. >> >> So I guess we can set 4096 as default value, and inform users in the README >> file that this value should be raised to 8192 for floodfills. > > 4096 doesn't seem too unreasonable, it's below default levels of > kern.maxfiles, so if that's enough for the software I'd be happy with setting > that in a login.conf.d file. > >
Re: updatedb-0/+CONTENTS does not exist
I did, but when updating like 1 week ago or so. I ran the command again, and it seems to okay.. I hope so? On Sun, January 28, 2024 7:27 am, Greg Steuck wrote: > Anybody else got this with the recent update to > OpenBSD 7.4-current (GENERIC.MP) #1634: Sat Jan 27 20:29:34 MST 2024 ? > > > # pkg_add -ui > quirks-7.0:updatedb-0->0p0: ok > quirks-7.0 signed on 2024-01-27T13:35:18Z quirks-7.0->7.0: ok > ... > unzip-6.0p17-iconv->6.0p17-iconv (processing)|No change in > unzip-6.0p17-iconvWarning: couldn't read packing-list from installed package > updatedb-0 File /var/db/pkg/updatedb-0/+CONTENTS does not exist > Running tags: ok > Read shared items: ok > Updating font cache: ok > --- -dconf-0.40.0p0 --- > You should also run rm -rf /etc/dconf/db/* > You should also run rm -rf /etc/dconf/profile/* > pkg_add: can't locate updatedb-0 > > >
Re: net/i2pd: open file descriptors and problem of routers
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 connection checked on more devices and on every router internet connection goes On Sat, January 27, 2024 10:34 pm, open...@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 beecdadd...@danwin1210.de wrote: > >> -- Original Message >> -- >> Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login >> From:beecdadd...@danwin1210.de >> Date:Sat, January 27, 2024 7:16 pm >> To: "Stuart Henderson" >> >> -- >> >> > >> 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 ]
Re: [Fwd: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login]
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, open...@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 beecdadd...@danwin1210.de wrote: > >> -- Original Message >> -- >> Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login >> From:beecdadd...@danwin1210.de >> Date:Sat, January 27, 2024 7:16 pm >> To: "Stuart Henderson" >> >> -- >> >> > >> 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 ]
Re: net/i2pd: move login.conf(5) bits from README to i2pd.login
still no idea how can someone connect to +10k routers.. isn't every router a connection in need of a file-descriptor? I understand you see documentation, but how does one logic here? On Sat, January 27, 2024 9:54 pm, open...@systemfailure.net wrote: > According to i2pd's online documentation [1], the maximum number of open file > descriptors is 4096 for a regular node, and 8192 for a floodfill [2]. > > I have never measured how many FDs i2pd is really using, but this software > for sure needs a lot of them. > > So I guess we can set 4096 as default value, and inform users in the README > file that this value should be raised to 8192 for floodfills. > > Apart from that, Klemens' idea of moving the login class definition to > /etc/login.conf.d/i2pd seems right to me. In fact, I'm doing just that in an > ansible role I maintain [3] - and never thought of achieving that at the port > level. I tried the patch and it applies cleanly. > > [1] > https://i2pd.readthedocs.io/en/latest/user-guide/FAQ/#help-i2pd-is-not-workin > g-what-do-i-do > > [2] A floodfill is a special type of router (i2pd instance) which builds a > lot of tunnels to distribute the I2P network database: > https://geti2p.net/en/docs/how/network-database > > > [3] https://codeberg.org/systemfailure.net/ansible_i2pd > > > > > On 2024/01/25 08:05, Stuart Henderson wrote: > >> > >> On 2024/01/24 23:06, Klemens Nanni wrote: >> >>> Manual instructions are from 2020, we gained /etc/login.d/* support >>> in 2022, so automate it. >> > >> Comsidering that the default kern.maxfiles limit on amd64 is 7030, >> bumping maxfiles in login.conf to 8192 without making the sysctl change means >> that i2pd can consume all FDs in the system. >> > >> I think it would be better for the login.conf.d file to stick something >> lower if possible. 8192 seems a bit excessive. Is there someone using this >> software who can confirm how many FDs it *really* is likely to use? >> > >> If it really needs this many, perhaps it's better not to automate either >> setting, at least then users who bump into the limits will only have problems >> with i2pd not the rest of the system. >> > >>> diff -u -p -r1.3 README --- pkg/README 8 Nov 2022 12:41:42 - >>> 1.3 >>> +++ pkg/README 24 Jan 2024 22:24:29 - >>> @@ -5,20 +5,7 @@ >>> Resource Limits: File Descriptors >>> = >>> >>> > >>> -By default, the i2pd process runs in the login(1) class of "daemon". >>> -The default limits on file descriptors are insufficient to run i2pd; >>> instead you -should put the _i2pd user and process in their own login(1) >>> class with tuned -resources. >>> -You should also raise the system-wide maxfiles limit. >>> - >>> -1. Configure i2pd login class in the login.conf(5) file: >>> - >>> -i2pd:\ >>> -:openfiles-cur=8192:\ >>> -:openfiles-max=8192:\ >>> -:tc=daemon: >>> - >>> -2. Adjust kern.maxfiles, if needed: >>> +You should raise the system-wide maxfiles limit: >>> >>> > >>> # sysctl kern.maxfiles=16000 >>> # echo "kern.maxfiles=16000" >> /etc/sysctl.conf >>> Index: pkg/i2pd.login >>> === >>> RCS file: pkg/i2pd.login >>> diff -N pkg/i2pd.login --- /dev/null1 Jan 1970 00:00:00 - >>> +++ pkg/i2pd.login 24 Jan 2024 22:23:46 - >>> @@ -0,0 +1,4 @@ >>> +i2pd:\ >>> + :openfiles-cur=8192:\ >>> + :openfiles-max=8192:\ >>> + :tc=daemon: >>> >>> > >
[Fwd: Re: [qBittorrent] I2P features seems to not work]
Sorry http://openbsd.i2p seems to be down check by instead running curl --proxy "socks5h://127.0.0.1:4447" "http://reg.i2p; Or even better visit 127.0.0.1:7070 after changing proxy in your web browser -- Original Message -- Subject: Re: [qBittorrent] I2P features seems to not work From:beecdadd...@danwin1210.de Date:Sat, January 27, 2024 7:24 pm To: "Klemens Nanni" -- i2pd is easy, you edit /etc/i2pd/i2pd.conf to your ability. default speed is 32 KB/sec, maybe is too low, maybe you crash your system or router I2Pd is similar to Tor, but is it's own network and unless you specify an 'outproxy' in i2pd.conf, you cannot visit clerrnet sites, only eepsites ending in .i2pd like http://openbsd.i2p (remember I2P software has to run for a few minutes up to hours to integrate well into network) so maybe try that. I2Pd is not VPN, I replied to i2pd post recently. qBittorrent no special options or configuration other than what I said already. I did not find any I2P guides on qBittorrent, not any recent or official. There is under Connection I2P (experimental), I turned it on and that should be it? I don't know help me please On Wed, January 24, 2024 11:01 pm, Klemens Nanni wrote: > Please provide exact instructions on how to set up i2pd and qbittorrent. > > > I installed i2pd, followed its README, read the config and --help > output, looked through https://i2pd.website, but couldn't make a simple 'curl > --socks5 127.0.0.1:4447 openbsd.org' work (4447/tcp being i2pd's > default SOCKS5 port) -- the proxy connection works, but i2pd fails after that > and it constantly spews warning that don't help. > > On Wed, Jan 24, 2024 at 12:52:15PM -, beecdadd...@danwin1210.de wrote: > >> (After 1 week I figured out how to subscribe to a list by reading the >> entire OpenBSD's page until the end) >> >> Hello >> This is my 1st post to ports list, tell me if I'm missing anything. >> >> >> I am running -current both OpenBSD and ports(pkg_add). >> >> >> So the problem is that in qbittorrent the I2P experimental feature does >> not work like AT ALL.. I added 4 torrents over the biggest I2P tracker >> postman and I seem to only get 'Stalled' it says 0 peers I am running i2pd >> port on same machine Is this problem with qBittorrent libtorrent i2pd or >> some settings I didn't see anywhere that had to be enabled or disabled? I >> enabled the I2P experimental option, the port specified default port points >> to the SAM protocol Here is the full Execution log: >> >> >> >> UPnP/NAT-PMP port mapping failed. Message: "could not map port using >> UPnP[192.168.1.170]: no router found" >> UPnP/NAT-PMP port mapping failed. Message: "could not map port using >> UPnP[192.168.1.170]: no router found" >> Detected external IP. IP: "[REDACTED]" >> IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: >> [REDACTED] >> Restored torrent. Torrent: "[TUTORIAL] How to[REDACTED]" >> Restored torrent. Torrent: "Full[REDACTED]" >> Restored torrent. Torrent: "i2p[REDACTED]" >> Restored torrent. Torrent: "The[REDACTED]" >> Successfully listening on IP. IP: "fe80::1%lo0". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "fe80::1%lo0". Port: "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "::1". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "::1". Port: "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "192.168.1.170". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "192.168.1.170". Port: >> "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/[RANDOM-PORT]" >> UPnP/NAT-PMP support: ON >> Encryption support: ON >> Anonymous mode: ON >> Peer Exchange (PeX) support: ON >> Local Peer Discovery support: ON >> Distributed Hash Table (DHT) support: ON >> HTTP User-Agent: "qBittorrent/4.6.3" >> Peer ID: "[REDACTED]" >> Trying to listen on the following list of IP addresses: >> "0.0.0.0:[RANDOM-PORT],[::]:[RANDOM-PORT]" >> Using config directory: /home/[USER]/.config/qBittorrent >> qBittorrent v4.6.3 started >> >> >> Thanks for maintenance. >> >> >> >
[Fwd: Re: [qBittorrent] I2P features seems to not work]
-- Original Message -- Subject: Re: [qBittorrent] I2P features seems to not work From:beecdadd...@danwin1210.de Date:Sat, January 27, 2024 7:24 pm To: "Klemens Nanni" -- i2pd is easy, you edit /etc/i2pd/i2pd.conf to your ability. default speed is 32 KB/sec, maybe is too low, maybe you crash your system or router I2Pd is similar to Tor, but is it's own network and unless you specify an 'outproxy' in i2pd.conf, you cannot visit clerrnet sites, only eepsites ending in .i2pd like http://openbsd.i2p (remember I2P software has to run for a few minutes up to hours to integrate well into network) so maybe try that. I2Pd is not VPN, I replied to i2pd post recently. qBittorrent no special options or configuration other than what I said already. I did not find any I2P guides on qBittorrent, not any recent or official. There is under Connection I2P (experimental), I turned it on and that should be it? I don't know help me please On Wed, January 24, 2024 11:01 pm, Klemens Nanni wrote: > Please provide exact instructions on how to set up i2pd and qbittorrent. > > > I installed i2pd, followed its README, read the config and --help > output, looked through https://i2pd.website, but couldn't make a simple 'curl > --socks5 127.0.0.1:4447 openbsd.org' work (4447/tcp being i2pd's > default SOCKS5 port) -- the proxy connection works, but i2pd fails after that > and it constantly spews warning that don't help. > > On Wed, Jan 24, 2024 at 12:52:15PM -, beecdadd...@danwin1210.de wrote: > >> (After 1 week I figured out how to subscribe to a list by reading the >> entire OpenBSD's page until the end) >> >> Hello >> This is my 1st post to ports list, tell me if I'm missing anything. >> >> >> I am running -current both OpenBSD and ports(pkg_add). >> >> >> So the problem is that in qbittorrent the I2P experimental feature does >> not work like AT ALL.. I added 4 torrents over the biggest I2P tracker >> postman and I seem to only get 'Stalled' it says 0 peers I am running i2pd >> port on same machine Is this problem with qBittorrent libtorrent i2pd or >> some settings I didn't see anywhere that had to be enabled or disabled? I >> enabled the I2P experimental option, the port specified default port points >> to the SAM protocol Here is the full Execution log: >> >> >> >> UPnP/NAT-PMP port mapping failed. Message: "could not map port using >> UPnP[192.168.1.170]: no router found" >> UPnP/NAT-PMP port mapping failed. Message: "could not map port using >> UPnP[192.168.1.170]: no router found" >> Detected external IP. IP: "[REDACTED]" >> IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: >> [REDACTED] >> Restored torrent. Torrent: "[TUTORIAL] How to[REDACTED]" >> Restored torrent. Torrent: "Full[REDACTED]" >> Restored torrent. Torrent: "i2p[REDACTED]" >> Restored torrent. Torrent: "The[REDACTED]" >> Successfully listening on IP. IP: "fe80::1%lo0". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "fe80::1%lo0". Port: "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "::1". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "::1". Port: "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "192.168.1.170". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "192.168.1.170". Port: >> "TCP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/[RANDOM-PORT]" >> Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/[RANDOM-PORT]" >> UPnP/NAT-PMP support: ON >> Encryption support: ON >> Anonymous mode: ON >> Peer Exchange (PeX) support: ON >> Local Peer Discovery support: ON >> Distributed Hash Table (DHT) support: ON >> HTTP User-Agent: "qBittorrent/4.6.3" >> Peer ID: "[REDACTED]" >> Trying to listen on the following list of IP addresses: >> "0.0.0.0:[RANDOM-PORT],[::]:[RANDOM-PORT]" >> Using config directory: /home/[USER]/.config/qBittorrent >> qBittorrent v4.6.3 started >> >> >> Thanks for maintenance. >> >> >> >
[Fwd: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login]
-- Original Message -- Subject: Re: net/i2pd: move login.conf(5) bits from README to i2pd.login From:beecdadd...@danwin1210.de Date:Sat, January 27, 2024 7:16 pm To: "Stuart Henderson" -- 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 maintance On Thu, January 25, 2024 8:05 am, Stuart Henderson wrote: > On 2024/01/24 23:06, Klemens Nanni wrote: > >> Manual instructions are from 2020, we gained /etc/login.d/* support >> in 2022, so automate it. > > Comsidering that the default kern.maxfiles limit on amd64 is 7030, > bumping maxfiles in login.conf to 8192 without making the sysctl change means > that i2pd can consume all FDs in the system. > > I think it would be better for the login.conf.d file to stick something > lower if possible. 8192 seems a bit excessive. Is there someone using this > software who can confirm how many FDs it *really* is likely to use? > > If it really needs this many, perhaps it's better not to automate either > setting, at least then users who bump into the limits will only have problems > with i2pd not the rest of the system. > >> diff -u -p -r1.3 README --- pkg/README 8 Nov 2022 12:41:42 - >> 1.3 >> +++ pkg/README 24 Jan 2024 22:24:29 - >> @@ -5,20 +5,7 @@ >> Resource Limits: File Descriptors >> = >> >> >> -By default, the i2pd process runs in the login(1) class of "daemon". >> -The default limits on file descriptors are insufficient to run i2pd; >> instead you -should put the _i2pd user and process in their own login(1) >> class with tuned -resources. >> -You should also raise the system-wide maxfiles limit. >> - >> -1. Configure i2pd login class in the login.conf(5) file: >> - >> -i2pd:\ >> -:openfiles-cur=8192:\ >> -:openfiles-max=8192:\ >> -:tc=daemon: >> - >> -2. Adjust kern.maxfiles, if needed: >> +You should raise the system-wide maxfiles limit: >> >> >> # sysctl kern.maxfiles=16000 >> # echo "kern.maxfiles=16000" >> /etc/sysctl.conf >> Index: pkg/i2pd.login >> === >> RCS file: pkg/i2pd.login >> diff -N pkg/i2pd.login --- /dev/null 1 Jan 1970 00:00:00 - >> +++ pkg/i2pd.login 24 Jan 2024 22:23:46 - >> @@ -0,0 +1,4 @@ >> +i2pd:\ >> +:openfiles-cur=8192:\ >> +:openfiles-max=8192:\ >> +:tc=daemon: >> >> > >
[qBittorrent] I2P features seems to not work
(After 1 week I figured out how to subscribe to a list by reading the entire OpenBSD's page until the end) Hello This is my 1st post to ports list, tell me if I'm missing anything. I am running -current both OpenBSD and ports(pkg_add). So the problem is that in qbittorrent the I2P experimental feature does not work like AT ALL.. I added 4 torrents over the biggest I2P tracker postman and I seem to only get 'Stalled' it says 0 peers I am running i2pd port on same machine Is this problem with qBittorrent libtorrent i2pd or some settings I didn't see anywhere that had to be enabled or disabled? I enabled the I2P experimental option, the port specified default port points to the SAM protocol Here is the full Execution log: UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[192.168.1.170]: no router found" UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[192.168.1.170]: no router found" Detected external IP. IP: "[REDACTED]" IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: [REDACTED] Restored torrent. Torrent: "[TUTORIAL] How to[REDACTED]" Restored torrent. Torrent: "Full[REDACTED]" Restored torrent. Torrent: "i2p[REDACTED]" Restored torrent. Torrent: "The[REDACTED]" Successfully listening on IP. IP: "fe80::1%lo0". Port: "UTP/[RANDOM-PORT]" Successfully listening on IP. IP: "fe80::1%lo0". Port: "TCP/[RANDOM-PORT]" Successfully listening on IP. IP: "::1". Port: "UTP/[RANDOM-PORT]" Successfully listening on IP. IP: "::1". Port: "TCP/[RANDOM-PORT]" Successfully listening on IP. IP: "192.168.1.170". Port: "UTP/[RANDOM-PORT]" Successfully listening on IP. IP: "192.168.1.170". Port: "TCP/[RANDOM-PORT]" Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/[RANDOM-PORT]" Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/[RANDOM-PORT]" UPnP/NAT-PMP support: ON Encryption support: ON Anonymous mode: ON Peer Exchange (PeX) support: ON Local Peer Discovery support: ON Distributed Hash Table (DHT) support: ON HTTP User-Agent: "qBittorrent/4.6.3" Peer ID: "[REDACTED]" Trying to listen on the following list of IP addresses: "0.0.0.0:[RANDOM-PORT],[::]:[RANDOM-PORT]" Using config directory: /home/[USER]/.config/qBittorrent qBittorrent v4.6.3 started Thanks for maintenance.
[Fwd: Register me]
Original Message Subject: Register me From:beecdadd...@danwin1210.de Date:Fri, January 19, 2024 1:24 pm To: ports@openbsd.org -- register me please
qBittorrent
Hello This is my 1st post to ports list, tell me if these things are supposed to be 1v1 (with maintainer), but this might involve multiple ports, like 3.. I am running -current both OpenBSD and ports(pkg_add), I might be a few hours behind if that matters So the problem is that in qbittorrent the I2P experimental feature does not work like AT ALL.. I added 4 torrents over the biggest I2P tracker postman and I seem to only get 'Stalled' it says 0 peers I am running i2pd port on same machine Is this problem with qBittorrent libtorrent i2pd or some settings I didn't see anywhere that had to be enabled or disabled? Thanks for maintenance
Register me
register me please
