Re: wacom CTH-470, works only as mouse and with finger (not stylus)

2023-12-08 Thread Katherine Mcmillan
Try it with Linux if you can't get it to work with OpenBSD (keep trying with 
OpenBSD, someone here may have some advice).

-Katie

From: Abel Abraham Camarillo Ojeda 
Sent: 08 December 2023 18:16
To: Katherine Mcmillan 
Cc: misc@openbsd.org 
Subject: Re: wacom CTH-470, works only as mouse and with finger (not stylus)

Attention : courriel externe | external email


On Fri, Dec 8, 2023 at 5:09 PM Katherine Mcmillan 
mailto:kmcmi...@uottawa.ca>> wrote:
Hi Abel,

I can offer a tiny bit of assistance:

I recommend reading the article here about your device: 
https://news.sophos.com/en-us/2020/02/07/wacom-driver-caught-monitoring-third-party-software-use/

It's always good to be an informed consumer. :)

I think your approach is smart to try to get this to work with OpenBSD.  If 
that doesn't work: https://linuxwacom.github.io/

-Katie

>From a quick read it seems to affect official wacom drivers, xorg in openbsd 
>uses usbtablet and uhid which I don't think include
wacom corp code...

so, how is this relevant to the question?

I know I could use it on linux.

regards


Re: wacom CTH-470, works only as mouse and with finger (not stylus)

2023-12-08 Thread Katherine Mcmillan
Hi Abel,

I can offer a tiny bit of assistance:

I recommend reading the article here about your device: 
https://news.sophos.com/en-us/2020/02/07/wacom-driver-caught-monitoring-third-party-software-use/

It's always good to be an informed consumer. :)

I think your approach is smart to try to get this to work with OpenBSD.  If 
that doesn't work: https://linuxwacom.github.io/

-Katie

From: owner-m...@openbsd.org  on behalf of Abel Abraham 
Camarillo Ojeda 
Sent: 08 December 2023 17:50
To: OpenBSD Misc 
Subject: wacom CTH-470, works only as mouse and with finger (not stylus)

Attention : courriel externe | external email

Hi misc,

I'm trying to use a wacom CTH-470 (oldish model) with OpenBSD, I think I've
never manage to get it to work before

I've read the following:

https://marc.info/?l=openbsd-misc&m=146882849030078&w=2

and used a symlink from /dev/ttyJ0 to /dev/uhid15

and used the following:

$ cat /usr/X11R6/share/X11/xorg.conf.d/99-stylus.conf
Section "InputDevice"
Identifier "w_stylus"
Driver "usbtablet"
Option "Type" "stylus"
Option "Device" "/dev/ttyJ0"
Option "Mode" "Absolute"
EndSection

Section "ServerLayout"
Identifier "X.org Configured"
InputDevice"w_stylus" "SendCoreEvents"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "True"
EndSection
$

But xorg complains with:

[144738.406] (II) Using input driver 'usbtablet' for 'w_stylus'
[144738.407] (**) Option "SendCoreEvents"
[144738.407] (**) w_stylus: always reports core events
[144738.407] (**) Stylus: always reports core events
[144738.407] (**) Stylus device is /dev/ttyJ0
[144738.407] (**) Stylus is in absolute mode
[144738.407] (==) Stylus: threshold = 5
[144738.407] (==) Stylus: suppress = 2
[144738.407] (II) XINPUT: Adding extended input device "Stylus" (type:
TABLET, id 6)
[144738.407] (**) Option "Device" "/dev/ttyJ0"
[144738.407] (EE) /dev/ttyJ0 has no X, Y, or In_Range report
[144738.408] (EE) Couldn't init device "Stylus"
[144738.408] (II) UnloadModule: "usbtablet"

The bamboo tablet works as a mouse pointer _only_ when using my finger over
it, not
with the stylus (although led brights white when i put the stylus on)

The tablet attaches lots of uhid devs I don't know if I should try each of
them one by one.

$ for i in `jot - 2 16 -`; do echo usbhidctl -f $i -r; done | doas sh -x
2>&1
+ usbhidctl -f 2 -r
Report descriptor:
Collection page=Digitizer usage=Digitizer
Collection page=Digitizer usage=Digitizer
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
End collection
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 9 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 3 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 4 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 5 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 6 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 2 bytes
+ usbhidctl -f 7 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x

Re: wacom CTH-470, works only as mouse and with finger (not stylus)

2023-12-08 Thread Abel Abraham Camarillo Ojeda
On Fri, Dec 8, 2023, 18:02 Katherine Mcmillan  wrote:

> Try it with Linux if you can't get it to work with OpenBSD (keep trying
> with OpenBSD, someone here may have some advice).
>

Just for the (non relevant record). I recall it worked on linux years ago.


> -Katie
> --
> *From:* Abel Abraham Camarillo Ojeda 
> *Sent:* 08 December 2023 18:16
> *To:* Katherine Mcmillan 
> *Cc:* misc@openbsd.org 
> *Subject:* Re: wacom CTH-470, works only as mouse and with finger (not
> stylus)
>
> *Attention : courriel externe | external email*
>
>
> On Fri, Dec 8, 2023 at 5:09 PM Katherine Mcmillan 
> wrote:
>
> Hi Abel,
>
> I can offer a tiny bit of assistance:
>
> I recommend reading the article here about your device:
> https://news.sophos.com/en-us/2020/02/07/wacom-driver-caught-monitoring-third-party-software-use/
>
> It's always good to be an informed consumer. :)
>
> I think your approach is smart to try to get this to work with OpenBSD.
> If that doesn't work: https://linuxwacom.github.io/
>
> -Katie
>
>
> From a quick read it seems to affect official wacom drivers, xorg in
> openbsd uses usbtablet and uhid which I don't think include
> wacom corp code...
>
> so, how is this relevant to the question?
>
> I know I could use it on linux.
>
> regards
>


Re: wacom CTH-470, works only as mouse and with finger (not stylus)

2023-12-08 Thread Abel Abraham Camarillo Ojeda
On Fri, Dec 8, 2023 at 5:09 PM Katherine Mcmillan 
wrote:

> Hi Abel,
>
> I can offer a tiny bit of assistance:
>
> I recommend reading the article here about your device:
> https://news.sophos.com/en-us/2020/02/07/wacom-driver-caught-monitoring-third-party-software-use/
>
> It's always good to be an informed consumer. :)
>
> I think your approach is smart to try to get this to work with OpenBSD.
> If that doesn't work: https://linuxwacom.github.io/
>
> -Katie
>

>From a quick read it seems to affect official wacom drivers, xorg in
openbsd uses usbtablet and uhid which I don't think include
wacom corp code...

so, how is this relevant to the question?

I know I could use it on linux.

regards


relayd https inspection certificate issue

2023-12-08 Thread Philipp Benner
Dear all,

 
I would like to use relayd as an outbound https proxy, so I configured it like 
shown in the last section of the relayd.conf(5) manpage.

This works fine for e.g. wikipedia.org. The certificate issued by my relay is 
nearly the same as the original, except oft he issuer of course.

But when I try to visit e.g. heise.de, at least all images refuse to load. 
After some research I found out the following.

When visiting the site directly without proxy, I can see that the images are 
loaded from https://heise.cloudimg.io. If I open an image in a new browser, I 
can also see that the certificates applicant is 2e26bae.cloudimg.io, 
alternative applicants are heise-aws.cloudimg.io and heise.cloudimg.io

Now if I use the relayd proxy and try to open an image in a seperate browser, 
the url is the same https://heise.cloudimg.io/... but the certificates is 
different. Its applicant now is a.248.e.akamai.net and alternatively 
*.akamaized.net and some other *.akamai…

So the self-issued certificate has completely other applicants than the 
original and of course doesn‘t match the actual server name and I get the error 
ERR_CERT_COMMON_NAME_INVALID

 
Can anybody help or give advice?

 
Thank you very much!


wacom CTH-470, works only as mouse and with finger (not stylus)

2023-12-08 Thread Abel Abraham Camarillo Ojeda
Hi misc,

I'm trying to use a wacom CTH-470 (oldish model) with OpenBSD, I think I've
never manage to get it to work before

I've read the following:

https://marc.info/?l=openbsd-misc&m=146882849030078&w=2

and used a symlink from /dev/ttyJ0 to /dev/uhid15

and used the following:

$ cat /usr/X11R6/share/X11/xorg.conf.d/99-stylus.conf
Section "InputDevice"
Identifier "w_stylus"
Driver "usbtablet"
Option "Type" "stylus"
Option "Device" "/dev/ttyJ0"
Option "Mode" "Absolute"
EndSection

Section "ServerLayout"
Identifier "X.org Configured"
InputDevice"w_stylus" "SendCoreEvents"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "True"
EndSection
$

But xorg complains with:

[144738.406] (II) Using input driver 'usbtablet' for 'w_stylus'
[144738.407] (**) Option "SendCoreEvents"
[144738.407] (**) w_stylus: always reports core events
[144738.407] (**) Stylus: always reports core events
[144738.407] (**) Stylus device is /dev/ttyJ0
[144738.407] (**) Stylus is in absolute mode
[144738.407] (==) Stylus: threshold = 5
[144738.407] (==) Stylus: suppress = 2
[144738.407] (II) XINPUT: Adding extended input device "Stylus" (type:
TABLET, id 6)
[144738.407] (**) Option "Device" "/dev/ttyJ0"
[144738.407] (EE) /dev/ttyJ0 has no X, Y, or In_Range report
[144738.408] (EE) Couldn't init device "Stylus"
[144738.408] (II) UnloadModule: "usbtablet"

The bamboo tablet works as a mouse pointer _only_ when using my finger over
it, not
with the stylus (although led brights white when i put the stylus on)

The tablet attaches lots of uhid devs I don't know if I should try each of
them one by one.

$ for i in `jot - 2 16 -`; do echo usbhidctl -f $i -r; done | doas sh -x
2>&1
+ usbhidctl -f 2 -r
Report descriptor:
Collection page=Digitizer usage=Digitizer
Collection page=Digitizer usage=Digitizer
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Input   size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
End collection
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 9 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 3 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 4 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 5 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 bytes
+ usbhidctl -f 6 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 2 bytes
+ usbhidctl -f 7 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 16 bytes
+ usbhidctl -f 8 -r
Report descriptor:
Feature size=8 count=1 page=Microsoft usage=0x0001, logical range 0..255
Total   input size 0 bytes
Total  output size 0 bytes
Total feature size 1 by

Re: pkg_add - error while reading header / read short file / gzheader truncated

2023-12-08 Thread David Rinehart
On Fri, 2023-12-08 at 08:37 +, Stuart Henderson wrote:
> On 2023-12-07, David Rinehart  wrote:
> > 
> > I see the same with multiple installs - Started with 7.4.  No
> > modification to default installurl.
> 
> The contents of the 'default' installurl depend on whuch mirror you
> selected to install from.
> 

I select "disk" for file sets and do not recall selecting a mirror.  I
believe this puts https://cdn.openbsd.org/pub/OpenBSD in the file.

The issue may have started before 7.4, but was not seen at 7.3 release
timeframe.

After giving it more thought, I believe I started seeing errors on
package installation before 7.4 release.  I figured it was a web site
issue because I'm running -stable and no patches seemed related (so
more likely an external issue).  Then, the errors were familiar when I
did reinstalls with 7.4.  The errors are temporary and the package
installations will complete if run again, or maybe a couple times.

Thanks, for the reply and any help!
--
David Rinehart



Relayd - block bad bots

2023-12-08 Thread Michal

Hey

I'm running a small VM on OpenBSD where my site resides. My stack is
pf/relayd/httpd.

I see a significant traffic coming from bad bots, like mj12. I'd love
to completely block them and Relayd seems like the best place. I tried to
block by "User-Agent" header, however there is no support for globs
there. This means I would need to constantly adjust my filters when they
release new version into the wild.

Has anyone had any success with achieving something similiar? Frankly I
was a bit surprised that globs in value are not supported. Seems like a
great use case.

---

Michal



Re: ls in color

2023-12-08 Thread Jan Stary
On Dec 08 19:41:23, cahlu...@planet.nl wrote:
> In openBSD V7.4 I would like to see the output of ls in color, and therefore
> would like to know how to configure that. The output of "man ls" provides no
> information about this. Can anyone give me a tip?

Put your brown goggles on.



Re: ls in color

2023-12-08 Thread Otto Moerbeek
On Fri, Dec 08, 2023 at 07:45:06PM +0100, Karel Lucas wrote:

> 
> 
> Op 08-12-2023 om 19:42 schreef Theo de Raadt:
> > Karel Lucas  wrote:
> > 
> > > In openBSD V7.4 I would like to see the output of ls in color, and
> > > therefore would like to know how to configure that. The output of "man
> > > ls" provides no information about this. Can anyone give me a tip?
> > Black and white are also colours.
> > 
> That is not what I had in mind!

How about green or amber on black?

-Otto





Re: ls in color

2023-12-08 Thread Mike Larkin
On Fri, Dec 08, 2023 at 07:41:23PM +0100, Karel Lucas wrote:
>
> Hi all,
>
> In openBSD V7.4 I would like to see the output of ls in color, and therefore
> would like to know how to configure that. The output of "man ls" provides no
> information about this. Can anyone give me a tip?
>

pkg_add colorls

alias ls='/usr/local/bin/colorls -GF'



Re: ls in color

2023-12-08 Thread Allan Streib
On Fri, Dec 8, 2023, at 13:41, Karel Lucas wrote:

> In openBSD V7.4 I would like to see the output of ls in color, and 
> therefore would like to know how to configure that. The output of "man 
> ls" provides no information about this. Can anyone give me a tip?

You could install colorls from packages, and optionally alias
ls=/usr/local/bin/colorls



Re: ls in color

2023-12-08 Thread Karel Lucas




Op 08-12-2023 om 19:42 schreef Theo de Raadt:

Karel Lucas  wrote:


In openBSD V7.4 I would like to see the output of ls in color, and
therefore would like to know how to configure that. The output of "man
ls" provides no information about this. Can anyone give me a tip?

Black and white are also colours.


That is not what I had in mind!



Re: ls in color

2023-12-08 Thread Theo de Raadt
Karel Lucas  wrote:

> In openBSD V7.4 I would like to see the output of ls in color, and
> therefore would like to know how to configure that. The output of "man
> ls" provides no information about this. Can anyone give me a tip?

Black and white are also colours.



ls in color

2023-12-08 Thread Karel Lucas



Hi all,

In openBSD V7.4 I would like to see the output of ls in color, and 
therefore would like to know how to configure that. The output of "man 
ls" provides no information about this. Can anyone give me a tip?




Re: Weird network performance with iwn(4)

2023-12-08 Thread Lévai , Dániel
On Thursday, December 7th, 2023 at 19:28, Mihai Popescu
> Just a lucky guess, no offense please, are you using ftp2.eu.openbsd.org ?


Haha, no problem, it happens with everything, it's not about the mirrors, 
really, it's really just a frame of reference. Happens with my own mirror, too 
¯\_(ツ)_/¯

Daniel



Re: Weird network performance with iwn(4)

2023-12-08 Thread Stuart Henderson
I checked for openwrt support but your AP has a relatively uncommon
Realtek SoC and it seems fairly unlikely to happen so you're probably
stuck with the vendor firmware.

Maybe try forcing "mode 11n" or "mode 11g" with ifconfig and see if
that's any better.


On 2023-12-08, Lévai  Dániel  wrote:
> On Thursday, December 7th, 2023 at 17:10, Stefan Sperling  
> wrote:
>> 
>> 
>> On Thu, Dec 07, 2023 at 03:39:33PM +, Lévai, Dániel wrote:
>> 
>> > Hi all!
>> > 
>> > Recently my trusty T410 died (had iwn(4) in it) and had to switch to an 
>> > E450 - but this has iwm(4).
>> > Never had any issues with iwn(4) and iwm(4) seems to operate perfectly 
>> > fine in some scenarios, e.g. speedtest.net indicates 100/100Mbit down/up 
>> > speed.
>> 
>> > But downloading a base74.tgz set takes little more than 30 minutes - in 
>> > firefox and in console with ftp(1).
>> 
>> 
>> So you are getting 100/100 Mbit on iwm(4) in a speed test, and only 
>> downloading
>> base74.tgz is slow?
>
> Well, not quite - speedtest.net (whatever it does) seems to report good 
> results, browsing however is generally slow, but I can't really set precise 
> expectations for let's say "opening youtube.com". It's just slow compared to 
> other machines on the same network.
> The most concrete thing I could think of was to download the base set which 
> was surprisingly slow during the first upgrade after installation. That's why 
> I started to investigate; this I can measure and report.
>
> So generally speaking, everything is slow on iwm0 *except* what speedtest.net 
> seems to report.
>
>> The speed test being successful would imply that the wifi
>> layer is working just fine. If so then something else must be messing with
>> your base74.tgz download attempts.
>> 
>> What happens when you download base74.tgz over ethernet?
>
> No issue, perfect 100Mbit.
>
>> Or with iwm(4) via a different AP?
>> Or with iwm(4) via a different ISP?
>
> Thanks for the tips!
> I went ahead and tried my cell phone's mobile hotspot.
> Even though speedtest.net only reported 30/15Mbit down/up, the general 
> browsing experience was much better and managed to squeeze out 2-3MByte/sec 
> while downloading the base set from various mirrors.
>
> Switching back to my home AP seems to be the issue.
> It's a Zyxel NBG6615 (end of service by now, no newer firmware).
> Is there any debug sysctl's I can set on the laptop that could prove useful 
> in troubleshooting this? Maybe different settings for iwm(4) or the AP?
>
> Daniel
>
>


-- 
Please keep replies on the mailing list.



Re: Weird network performance with iwn(4)

2023-12-08 Thread Lévai , Dániel
On Thursday, December 7th, 2023 at 17:10, Stefan Sperling  
wrote:
> 
> 
> On Thu, Dec 07, 2023 at 03:39:33PM +, Lévai, Dániel wrote:
> 
> > Hi all!
> > 
> > Recently my trusty T410 died (had iwn(4) in it) and had to switch to an 
> > E450 - but this has iwm(4).
> > Never had any issues with iwn(4) and iwm(4) seems to operate perfectly fine 
> > in some scenarios, e.g. speedtest.net indicates 100/100Mbit down/up speed.
> 
> > But downloading a base74.tgz set takes little more than 30 minutes - in 
> > firefox and in console with ftp(1).
> 
> 
> So you are getting 100/100 Mbit on iwm(4) in a speed test, and only 
> downloading
> base74.tgz is slow?

Well, not quite - speedtest.net (whatever it does) seems to report good 
results, browsing however is generally slow, but I can't really set precise 
expectations for let's say "opening youtube.com". It's just slow compared to 
other machines on the same network.
The most concrete thing I could think of was to download the base set which was 
surprisingly slow during the first upgrade after installation. That's why I 
started to investigate; this I can measure and report.

So generally speaking, everything is slow on iwm0 *except* what speedtest.net 
seems to report.

> The speed test being successful would imply that the wifi
> layer is working just fine. If so then something else must be messing with
> your base74.tgz download attempts.
> 
> What happens when you download base74.tgz over ethernet?

No issue, perfect 100Mbit.

> Or with iwm(4) via a different AP?
> Or with iwm(4) via a different ISP?

Thanks for the tips!
I went ahead and tried my cell phone's mobile hotspot.
Even though speedtest.net only reported 30/15Mbit down/up, the general browsing 
experience was much better and managed to squeeze out 2-3MByte/sec while 
downloading the base set from various mirrors.

Switching back to my home AP seems to be the issue.
It's a Zyxel NBG6615 (end of service by now, no newer firmware).
Is there any debug sysctl's I can set on the laptop that could prove useful in 
troubleshooting this? Maybe different settings for iwm(4) or the AP?

Daniel



Configure and Access Keycloak

2023-12-08 Thread Tito Mari Francis Escaño
Hi everyone,
Recently exploring how to configure and administer Keycloak, can somebody
please point me to the resources for doing this in OpenBSD 7.4?
There seems to be no man pages for this purpose.
Would greatly appreciate all the help to make this work.
Thank you very much.


Re: Getting stuck on trying a fresh install to 7.4

2023-12-08 Thread Daniel Ouellet

On 12/8/23 3:34 AM, Stuart Henderson wrote:

On 2023-12-07, Daniel Ouellet  wrote:

On 12/7/23 7:37 AM, Stuart Henderson wrote:

On 2023-12-06, Daniel Ouellet  wrote:

Any suggestion woudl be greattly appreciated.


Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.


Specifically the interface used for communicating system
console information between the boot loader and the kernel was changed.
There was backwards compat but sadly it was removed after one single
release.

I think this brings the total number of people I know who have been
affected by this up to 6 now.


I didn't care what's on it now. All fresh install will do.
I have 22 to do. :(


You can copy a new bootloader to the old machines and run installboot.


Hi Stuart,

Just to be clear and to help others here.

You are talking about these two files only right?

/usr/mdec/boot
/usr/sbin/installboot

or should this one below be included too? I don't think it's needed, but
just want to be sure and make the info complete.

/usr/mdec/biosboot


Assuming standard partition table not GPT: /usr/mdec/boot and
/usr/mdec/biosboot. *Not* /usr/sbin/installboot, the new binary
is unlikely to run on new OS.



Thanks Stuart.

I will test it out. Plenty to test with anyway. (;



Re: Getting stuck on trying a fresh install to 7.4

2023-12-08 Thread Stuart Henderson
On 2023-12-07, Daniel Ouellet  wrote:
> On 12/7/23 7:37 AM, Stuart Henderson wrote:
>> On 2023-12-06, Daniel Ouellet  wrote:
> Any suggestion woudl be greattly appreciated.

 Old boot loaders cannot boot 7.4 kernels.
 Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
 skipping releases during upgrades applies). Then upgrade to 7.4.
>> 
>> Specifically the interface used for communicating system
>> console information between the boot loader and the kernel was changed.
>> There was backwards compat but sadly it was removed after one single
>> release.
>> 
>> I think this brings the total number of people I know who have been
>> affected by this up to 6 now.
>> 
>>> I didn't care what's on it now. All fresh install will do.
>>> I have 22 to do. :(
>> 
>> You can copy a new bootloader to the old machines and run installboot.
>
> Hi Stuart,
>
> Just to be clear and to help others here.
>
> You are talking about these two files only right?
>
> /usr/mdec/boot
> /usr/sbin/installboot
>
> or should this one below be included too? I don't think it's needed, but 
> just want to be sure and make the info complete.
>
> /usr/mdec/biosboot

Assuming standard partition table not GPT: /usr/mdec/boot and
/usr/mdec/biosboot. *Not* /usr/sbin/installboot, the new binary
is unlikely to run on new OS.



Re: pkg_add - error while reading header / read short file / gzheader truncated

2023-12-08 Thread Stuart Henderson
On 2023-12-07, David Rinehart  wrote:
>
> I see the same with multiple installs - Started with 7.4.  No
> modification to default installurl.

The contents of the 'default' installurl depend on whuch mirror you
selected to install from.



Re: Raspberry Pi Installation media gives blank screen on boot

2023-12-08 Thread Stuart Henderson
On 2023-12-07, Vilyaem  wrote:
> Hello,
> I am in the process of turning a Void Linux 
> Raspberry Pi 3 B server to one that runs
> OpenBSD 7.4. 
>
> However, when attempting to
> begin the installation process,
> after the install media boots, the screen
> goes blank, nothing else happens afterwards,
> the keyboard lights still strangely react
> to caps lock and such. The HDMI monitor doesnt
> outright lose signal, the screen just remains
> black.
>
> I did the following steps.
>
> 1. Download miniroot74.img and install74.img from
> openbsd.org arm64
> 2. Write miniroot74.img to an SD card using dd
> doas dd if=miniroot74.img of=/dev/sdb
> 3. Write install74.img to a USB using dd
> doas dd if=install74.img of=/dev/sdb
> 4. Put in the SD card and USB
> 5. Start the Raspberry Pi

See "Install on Raspberry Pi" on
https://ftp.openbsd.org/pub/OpenBSD/7.4/arm64/INSTALL.arm64