USB keyboard quirks may not be properly catered to in bsd.rd kernels (was: Re: bad first impression of OpenBSD at install time)
On Fri, Apr 26, 2024 at 06:52:38AM +0200, Lourens wrote: > I too experienced this issue during installation. > I simply plugged in an old Logitech keyboard to complete the installation > and after rebooting the previously 'problematic' keyboard was detected and > fully usable. Summing up, this sounds like the kernel configuration that was shoehorned into amd64 installer images (and possibly other platforms?) lacks some of the code that caters to the quirks that show up in certain (newer) USB keyboards. What is not clear to me is how common those keyboards are, as in is there significant risk that new users would encounter this in the wild, with a probability large enough that it would be useful to add a note about this to say https://www.openbsd.org/faq/faq4.html#bsd.rd somewhere? -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: bad first impression of OpenBSD at install time
On 25/04/2024 17:46, Harald Dunkel wrote: Hi folks, I posted this before, without any response from the community: At the boot> prompt of the installer image my USB keyboard still works, but at the install prompt the keyboard is ignored. I cannot press "i" to actually install OpenBSD. Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen worse. But if this would have been my first impression of OpenBSD I had given it the boot and used Linux instead. Regards Harri Hi, I too experienced this issue during installation. I simply plugged in an old Logitech keyboard to complete the installation and after rebooting the previously 'problematic' keyboard was detected and fully usable. My dmesg.txt was emailed as requested withe the issue mentioned in the Subject and is also available at : https://www.dropbox.com/scl/fo/q1dcoy2jofsjfbvrodf6b/AKvNhHpQLn60yKuu-G0Ajcw?rlkey=6pj6h8wxqtjso7ljdr5ucddzg&st=qzn47qxq&dl=0 Briefly: Micro-Star International Co., Ltd. MS-7B22 Keyboard branded as havit HV-KB366L Listed in dmesg as : uhidev0 at uhub0 port 1 configuration 1 interface 0 "BY Tech Usb Gaming Keyboard" rev 2.00/0.01 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes I have only been an openBSD user since 6.9 and have not prior to 7.5 seen this error. Thank you to all involved in this awesome project. Lourens * *
Re: Fwd: bad first impression of OpenBSD at install time
Дана 24/04/26 11:44AM, Alexis написа: > One thing not mentioned there is top-posting, which is common outside tech > communities, but often frowned upon within tech communities. 'Top-posting' > involves adding one's reply _before_ the message one is replying to, rather > than _after_. Some links on the subject: https://git-send-email.io/top-posting.html https://www.caliburn.nl/topposting.html @thread: I find the following article well worth reading when asking for help about anything related to computers: How To Ask Questions The Smart Way http://www.catb.org/~esr/faqs/smart-questions.html I feel that this part in particular is relevant for this thread: If You Can't Get An Answer http://www.catb.org/~esr/faqs/smart-questions.html#idm659 I posted a few questions on @misc and @bugs myself; one of them is still unanswered as of now. However, I understand that even though I supplied the necessary information, not everyone might know the answer, or the answer just might be that the unsupported piece of hardware in question does not have a driver written for it yet. This is something that someone with "years of experience" in using Unix-like OSes should already consider. During my time contributing to Artix Linux and helping with issues on their forum, there were a couple of threads with similar kind of "blackmail" as here: "If this doesn't work, I'll hop to another distro". I always felt this is a superficial and immature threat. For example, the reasons why I chose OpenBSD after years of using various flavors of (GNU/)Linux far outweigh this one problem I have on one of my machines. So, if you feel that strongly about your issue to abandon OpenBSD over it, **just do that.** Realistically nobody can stop you from doing it, just as nobody can stop you from having 10 different VMs with various OSes anyway.
Re: Fwd: bad first impression of OpenBSD at install time
Katherine Mcmillan writes: Hi Harald, I am compiling a qualitative list of experiences of those who have requested help from various user groups who/which have been rejected or ignored, to try to find similarities between the approaches used by the poster; a grounded theory methodology. Would it be okay if I included yours? Thank you for considering, Katie Hi Katherine, As someone who's been participating in multiple online tech fora for well over two decades, i'd like to make some comments, based on my own experiences. Some common problematic approaches taken by posters include: * Not demonstrating any awareness of group rules or culture. In the case of OpenBSD, the 'netiquette' for the mailing lists is laid out at https://www.openbsd.org/mail.html; each point is explained with a rationale. One thing not mentioned there is top-posting, which is common outside tech communities, but often frowned upon within tech communities. 'Top-posting' involves adding one's reply _before_ the message one is replying to, rather than _after_. There are a few reasons this is discouraged in tech contexts; one is that top-posting not only removes potentially important context, but often results in important questions not being answered. Many of those seeking help don't answer questions that they've been asked - questions that have been asked in order to diagnose what the problem might be. Top-posting seems to exacerbate this phenomenon, and it can be exhausting to try to help someone, only to find it's like pulling teeth. * Treating volunteer communities as though they consist of paid staff. OpenBSD is primarily a volunteer effort - the developers/maintainers, the documenters, the people trying to help out on the mailing lists. Yet people regularly interact with the OpenBSD community (and other volunteer-based tech communities) as though we're a business offering a product seeking 'market share' - and in a number of cases, act as though they're entitled to the sort of support one would might associate with a _paid_ support contract. But OpenBSD is developed/maintained _for the developers/maintainers themselves_, even if it's nonetheless made available for others who might also find it useful. * Assuming that "lack of response" must mean "being ignored" (often in a way that implies that the user feels entitled to others' volunteer time). There's a general phenomenon called "Warnock's dilemma": "Warnock's dilemma, named for its originator Bryan Warnock, is the problem of interpreting a lack of response to a posting in a virtual community. The term originally referred to mailing list discussions, but has been applied to Usenet posts, blogs, web forums, and online content in general. The dilemma arises because a lack of response does not necessarily imply that no one is interested in the topic, but could also mean for example that readers find the content to be exceptionally good (leaving nothing for commenters to add.)" -- https://en.wikipedia.org/wiki/Warnock's_dilemma In the specific case of people asking for help, people will usually not answer with "Hmm, I don't know", just for the sake of answering - that would flood the group with useless messages. Additionally, however, there are common behaviours that can result in volunteers not feeling inclined to put in the effort to help someone, which are described on the "I downvoted because ..." site: https://idownvotedbecau.se/ Hope that helps - please feel free to contact me off-list with any followup questions. Alexis.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
> Hello, > > Remember softraid isn't the same as hw raid and I will always chose hw over > soft this includes zfs. > > Chris I am sorry, but what relevance does your personal preferences have to anything regarding this issue? FWIW, I have seen more than one example of some really crappy hardware raid controllers that I wouldn't hesitate a split second to replace with ZFS.
bad first impression [ ...] Fwd: [HUNSN RJ43: USB keyboard lost at boot time]
Attached Harald Dunkels original message from a few days ago, taken from my offline @misc folder. It seems this is the message he mentioned in this current thread - strangely enough I couldn't find it anywhere in the marc.info archive. HTH Wolfgang - Forwarded message from Harald Dunkel - Date: Sat, 20 Apr 2024 18:01:04 +0200 From: Harald Dunkel Subject: HUNSN RJ43: USB keyboard lost at boot time To: misc@openbsd.org User-Agent: Betterbird (Linux) Hi folks, This morning I've got a HUNSN RJ43 network appliance with N100 and 4 2.5Gbit network interfaces. Problem: The keyboard is lost at boot time. It still worked at the boot> prompt, but in OpenBSD's installer menu or at the login prompt it is ignored. I have to pull it out and plug it into another socket to make OpenBSD 7.5 recognize it, but even this workaround fails sometimes. *If* it works, then usbdevs shows (before and after): pablo# usbdevs -vv Controller /dev/usb0: addr 01: 8086: Intel, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 port 01: .02a0 power Rx.detect port 02: .02a0 power Rx.detect port 03: .0503 connect enabled recovery port 04: .02a0 power Rx.detect port 05: 0011.02a0 power Rx.detect port 06: .02a0 power Rx.detect port 07: .02a0 power Rx.detect port 08: .02a0 power Rx.detect port 09: .02a0 power Rx.detect port 10: .02a0 power Rx.detect port 11: .02a0 power Rx.detect port 12: .02a0 power Rx.detect port 13: .02a0 power Rx.detect port 14: .02a0 power Rx.detect port 15: .02a0 power Rx.detect port 16: .02a0 power Rx.detect addr 02: 05e3:0748 Generic, USB Storage high speed, power 500 mA, config 1, rev 12.09, iSerial 1209 driver: umass0 # plug it in pablo# usbdevs -vv Controller /dev/usb0: addr 01: 8086: Intel, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 port 01: .02a0 power Rx.detect port 02: .02a0 power Rx.detect port 03: .0503 connect enabled recovery port 04: .02a0 power Rx.detect port 05: 0011.02a0 power Rx.detect port 06: .0103 connect enabled recovery port 07: .02a0 power Rx.detect port 08: .02a0 power Rx.detect port 09: .02a0 power Rx.detect port 10: .02a0 power Rx.detect port 11: .02a0 power Rx.detect port 12: .02a0 power Rx.detect port 13: .02a0 power Rx.detect port 14: .02a0 power Rx.detect port 15: .02a0 power Rx.detect port 16: .02a0 power Rx.detect addr 02: 05e3:0748 Generic, USB Storage high speed, power 500 mA, config 1, rev 12.09, iSerial 1209 driver: umass0 addr 03: 12c9:6001 SINO WEALTH, Newmen Bluetooth Keyboard full speed, power 500 mA, config 1, rev 30.04 driver: uhidev0 driver: uhidev1 (I know it says Bluetooth, but its connected via cable. No BT dongle involved.) dmesg shows on detecting the keyboard: uhidev0 at uhub0 port 6 configuration 1 interface 0 "SINO WEALTH Newmen Bluetooth Keyboard" rev 1.10/30.04 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 uhidev1 at uhub0 port 6 configuration 1 interface 1 "SINO WEALTH Newmen Bluetooth Keyboard" rev 1.10/30.04 addr 3 uhidev1: iclass 3/0, 13 report ids uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0 ucc0 at uhidev1 reportid 2: 573 usages, 20 keys, array wskbd1 at ucc0 mux 1 wskbd1: connecting to wsdisplay0 uhid1 at uhidev1 reportid 5: input=0, output=0, feature=5 ukbd1 at uhidev1 reportid 6: 120 variable keys, 0 key codes wskbd2 at ukbd1 mux 1 wskbd2: connecting to wsdisplay0 uhid2 at uhidev1 reportid 9: input=0, output=0, feature=255 uhid3 at uhidev1 reportid 10: input=0, output=0, feature=41 uhid4 at uhidev1 reportid 11: input=0, output=0, feature=255 uhid5 at uhidev1 reportid 12: input=0, output=0, feature=255 ums0 at uhidev1 reportid 13: 5 buttons, Z and W dir wsmouse0 at ums0 mux 0 Another 15+ years old USB keyboard works out of the box, so maybe the keyboard is to blame here. It worked fine on other hosts running OpenBSD 7.4 or 7.5, though. BIOS had been reset to the defaults. dmesg output is attached, of course. Every helpful idea is highly appreciated. I would be glad to help to track down this problem. Harri OpenBSD 7.5 (RAMDISK_CD) #76: Wed Mar 20 15:53:54 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 34069209088 (32490MB) avail mem = 33032028160 (31501MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x73ba9000 (117 entries) bios0: vendor American Megatrends International, LLC
bad impression [etc ..] Fwd: [HUNSN RJ43: USB keyboard lost at boot time]
Attached Harald Dunkels original message from a few days ago, taken from my offline @misc folder. It seems this is the message Harald mentioned in this current thread - strangely enough I couldn't find it anywhere in the marc.info archive. HTH Wolfgang - Forwarded message from Harald Dunkel - Date: Sat, 20 Apr 2024 18:01:04 +0200 From: Harald Dunkel Subject: HUNSN RJ43: USB keyboard lost at boot time To: misc@openbsd.org User-Agent: Betterbird (Linux) Hi folks, This morning I've got a HUNSN RJ43 network appliance with N100 and 4 2.5Gbit network interfaces. Problem: The keyboard is lost at boot time. It still worked at the boot> prompt, but in OpenBSD's installer menu or at the login prompt it is ignored. I have to pull it out and plug it into another socket to make OpenBSD 7.5 recognize it, but even this workaround fails sometimes. *If* it works, then usbdevs shows (before and after): pablo# usbdevs -vv Controller /dev/usb0: addr 01: 8086: Intel, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 port 01: .02a0 power Rx.detect port 02: .02a0 power Rx.detect port 03: .0503 connect enabled recovery port 04: .02a0 power Rx.detect port 05: 0011.02a0 power Rx.detect port 06: .02a0 power Rx.detect port 07: .02a0 power Rx.detect port 08: .02a0 power Rx.detect port 09: .02a0 power Rx.detect port 10: .02a0 power Rx.detect port 11: .02a0 power Rx.detect port 12: .02a0 power Rx.detect port 13: .02a0 power Rx.detect port 14: .02a0 power Rx.detect port 15: .02a0 power Rx.detect port 16: .02a0 power Rx.detect addr 02: 05e3:0748 Generic, USB Storage high speed, power 500 mA, config 1, rev 12.09, iSerial 1209 driver: umass0 # plug it in pablo# usbdevs -vv Controller /dev/usb0: addr 01: 8086: Intel, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 port 01: .02a0 power Rx.detect port 02: .02a0 power Rx.detect port 03: .0503 connect enabled recovery port 04: .02a0 power Rx.detect port 05: 0011.02a0 power Rx.detect port 06: .0103 connect enabled recovery port 07: .02a0 power Rx.detect port 08: .02a0 power Rx.detect port 09: .02a0 power Rx.detect port 10: .02a0 power Rx.detect port 11: .02a0 power Rx.detect port 12: .02a0 power Rx.detect port 13: .02a0 power Rx.detect port 14: .02a0 power Rx.detect port 15: .02a0 power Rx.detect port 16: .02a0 power Rx.detect addr 02: 05e3:0748 Generic, USB Storage high speed, power 500 mA, config 1, rev 12.09, iSerial 1209 driver: umass0 addr 03: 12c9:6001 SINO WEALTH, Newmen Bluetooth Keyboard full speed, power 500 mA, config 1, rev 30.04 driver: uhidev0 driver: uhidev1 (I know it says Bluetooth, but its connected via cable. No BT dongle involved.) dmesg shows on detecting the keyboard: uhidev0 at uhub0 port 6 configuration 1 interface 0 "SINO WEALTH Newmen Bluetooth Keyboard" rev 1.10/30.04 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 uhidev1 at uhub0 port 6 configuration 1 interface 1 "SINO WEALTH Newmen Bluetooth Keyboard" rev 1.10/30.04 addr 3 uhidev1: iclass 3/0, 13 report ids uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0 ucc0 at uhidev1 reportid 2: 573 usages, 20 keys, array wskbd1 at ucc0 mux 1 wskbd1: connecting to wsdisplay0 uhid1 at uhidev1 reportid 5: input=0, output=0, feature=5 ukbd1 at uhidev1 reportid 6: 120 variable keys, 0 key codes wskbd2 at ukbd1 mux 1 wskbd2: connecting to wsdisplay0 uhid2 at uhidev1 reportid 9: input=0, output=0, feature=255 uhid3 at uhidev1 reportid 10: input=0, output=0, feature=41 uhid4 at uhidev1 reportid 11: input=0, output=0, feature=255 uhid5 at uhidev1 reportid 12: input=0, output=0, feature=255 ums0 at uhidev1 reportid 13: 5 buttons, Z and W dir wsmouse0 at ums0 mux 0 Another 15+ years old USB keyboard works out of the box, so maybe the keyboard is to blame here. It worked fine on other hosts running OpenBSD 7.4 or 7.5, though. BIOS had been reset to the defaults. dmesg output is attached, of course. Every helpful idea is highly appreciated. I would be glad to help to track down this problem. Harri OpenBSD 7.5 (RAMDISK_CD) #76: Wed Mar 20 15:53:54 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 34069209088 (32490MB) avail mem = 33032028160 (31501MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x73ba9000 (117 entries) bios0: vendor American Megatrends International,
Re: bad first impression of OpenBSD at install time
Hello, Please don't bash the OS based on unsupported HW or not I knowing what HW is or not supported before I stalling it that's the users fault. Blame the companies that fail to provide documentation to make oss drivers etc.. as you use any BSD you will learned that looking through the current drivers is crucial. I use openbsd for pretty much everything however I tend to buy hw that is found using the approps command and not just any HW. P.S I'm a 90% disabled vet so sorry for typos :( Chris Sent from Proton Mail Android Original Message On 4/25/24 1:28 PM, Peter N. M. Hansteen wrote: > On Thu, Apr 25, 2024 at 05:46:04PM +0200, Harald Dunkel wrote: > > > > I posted this before, without any response from the community: > > > > At the boot> prompt of the installer image my USB keyboard still works, > > but at the install prompt the keyboard is ignored. I cannot press "i" > > to actually install OpenBSD. > > I remember vaguely something that matches the description, and I think > the feedback then too was that more information about the hardware involved > would be needed in order to help. Preferably full sendbug output, but > a dmesg (preferably from OpenBSD but even from some other unixlike like > Linux will do). > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > >
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
Hello, Remember softraid isn't the same as hw raid and I will always chose hw over soft this includes zfs. Chris Sent from Proton Mail Android Original Message On 4/25/24 3:14 PM, Martin wrote: > > On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > > > > > I checked, the softraid manual page already has an example installboot > > > invocation in EXAMPLES, which should be clear enough. > > > > > > Regardless, I've tweaked the wording a bit. Hopefully more clear now. > > Indeed :) Thank you very much! > >
Re: NAT on CARP interface
> On Apr 25, 2024, at 10:36 AM, Radek wrote: > > Thank you for all your hints. > >> match out on egress from $lan_if:network to any nat-to (egress:0) > This rule doesn't work. change $lan_if to $int_if, change (egress:0) to $ext_carpif, and it will work as the rule you say works. fwiw, the $lan_if came from your configs existing “match” https://www.openbsd.org/faq/pf/filter.html#syntax - under “interface” you can find out about “egress”. I definitely prefer it to hard coding an interface in yet another line of a pf.conf I was presuming you didnt mind matching to $ext_if’s ip for new sessions outbound, hence (egress:0). Matching to the carp ip works. (this is basically a source nat rule in commercial-network-vendor speak) > >> ext_if=em0 >> int_if=vlan2 >> ext_carpIf=carp0 >> match out on $ext_if inet from $int_if:network to any nat-to $ext_carpIf > This rule works as expected.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
> On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > > > I checked, the softraid manual page already has an example installboot > > invocation in EXAMPLES, which should be clear enough. > > > Regardless, I've tweaked the wording a bit. Hopefully more clear now. Indeed :) Thank you very much!
Re: bad first impression of OpenBSD at install time
On Thu, Apr 25, 2024 at 05:46:04PM +0200, Harald Dunkel wrote: > > I posted this before, without any response from the community: > > At the boot> prompt of the installer image my USB keyboard still works, > but at the install prompt the keyboard is ignored. I cannot press "i" > to actually install OpenBSD. I remember vaguely something that matches the description, and I think the feedback then too was that more information about the hardware involved would be needed in order to help. Preferably full sendbug output, but a dmesg (preferably from OpenBSD but even from some other unixlike like Linux will do). -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Fwd: bad first impression of OpenBSD at install time
I do not compile a qualitative list of bullshits, but this got a place on some imaginary bullshit list for sure. From: Katherine Mcmillan Sent: Thursday, April 25, 2024 12:30:03 PM To: Harald Dunkel Subject: Re: bad first impression of OpenBSD at install time Hi Harald, I am compiling a qualitative list of experiences of those who have requeste= d help from various user groups who/which have been rejected or ignored, to= try to find similarities between the approaches used by the poster; a grou= nded theory methodology. Would it be okay if I included yours? Thank you for considering, Katie From: owner-m...@openbsd.org on behalf of Harald D= unkel Sent: Thursday, April 25, 2024 11:46:04 AM To: misc@openbsd.org Subject: bad first impression of OpenBSD at install time Attention : courriel externe | external email Hi folks, I posted this before, without any response from the community: At the boot> prompt of the installer image my USB keyboard still works, but at the install prompt the keyboard is ignored. I cannot press "i" to actually install OpenBSD. Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen worse. But if this would have been my first impression of OpenBSD I had given it the boot and used Linux instead. Regards Harri
Re: NAT on CARP interface
Thank you for all your hints.
> match out on egress from $lan_if:network to any nat-to (egress:0)
This rule doesn't work.
> ext_if=em0
> int_if=vlan2
> ext_carpIf=carp0
> match out on $ext_if inet from $int_if:network to any nat-to $ext_carpIf
This rule works as expected.
On Wed, 24 Apr 2024 17:14:49 -0400
Mike wrote:
> This command should help but you may need to add some "log" to your rules:
>
> tcpdump -nettti pflog0 will probably tell you.
>
> I don't have a bsd VM around to test but your int_if and ext_if should
> still refer to the underlying interface, not the carp.
>
> I'd change:
>
> ext_if=em0
> int_if=vlan2
> ext_carpIf=carp0
>
> match out on $ext_if inet from 10.0.2.0/24 to any nat-to $ext_carpIf
>
>
>
>
>
>
> On Wed, Apr 24, 2024, 4:50 PM Radek wrote:
>
> > Hi everyone,
> > it's a lab, the goal is a redundant firewalls with CARP and PFSYNC, I'm
> > trying to configure the master box. On the LAN side I have created carp2 on
> > vlan2 interface and it works as expected.
> > On the WAN side I can't figure out how to make NAT work on carp0 interface.
> > Can someone tell me where I have the wrong or missing configuration?
> >
> > OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > # cat /etc/hostname.em1
> > -inet
> > up
> >
> > # cat /etc/hostname.vlan2
> > -inet
> > vnetid 2 parent em1 description "Interface VLAN-KRZ_LAN" up
> >
> > # cat /etc/hostname.carp2
> > -inet
> > inet 10.0.2.254 255.255.255.0 NONE vhid 2 advbase 1 advskew 0 carpdev
> > vlan2 pass test54321
> >
> >
> > # cat /etc/hostname.em0
> > -inet
> > up
> >
> > # cat /etc/hostname.carp0
> > -inet
> > inet 10.0.15.216 255.255.255.0 NONE description "WAN_KRZ" vhid 1 advbase 1
> > advskew 0 carpdev em0 pass test678
> >
> >
> > # cat /etc/pf.conf
> > ext_if = "carp0"
> > lan_if = "carp2"
> > pfsync_if = "em3"
> > internal_if = "vlan1010"
> > set skip on { lo0 vlan em3}
> > # pfsync and carp
> > pass quick on { $pfsync_if } proto pfsync #keep state (no-sync)
> > pass on { $internal_if } proto carp keep state (no-sync)
> > # nat
> > match out on $ext_if from $lan_if:network to any nat-to $ext_if
> > pass out
> >
> > # pfctl -s rules
> > pass quick on em3 proto pfsync all
> > pass on vlan1010 proto carp all keep state (no-sync)
> > match out on carp0 inet from 10.0.2.0/24 to any nat-to 10.0.15.216
> > pass out all flags S/SA
> >
> > # route -n show
> > Routing tables
> >
> > Internet:
> > DestinationGatewayFlags Refs Use Mtu Prio
> > Iface
> > 224/4 127.0.0.1 URS0 72 32768 8 lo0
> > 10.0.2/24 10.0.2.254 UCn10 -19
> > carp2
> > 10.0.2.201 18:03:73:b4:fa:c1 UHLc 011815 -18
> > carp2
> > 10.0.2.254 00:00:5e:00:01:02 UHLl 0 36 - 1
> > carp2
> > 10.0.2.255 10.0.2.254 UHb04 - 1
> > carp2
> > [snip]
> >
> > Radek
> >
> >
Radek
Re: bad first impression of OpenBSD at install time
On 25.4.2024 17:46, Harald Dunkel wrote: Hi folks, I posted this before, without any response from the community: And where did you post it exactly as there is nothing from you this year in archives except of this new message on misc@ ;-) At the boot> prompt of the installer image my USB keyboard still works, but at the install prompt the keyboard is ignored. I cannot press "i" to actually install OpenBSD. Installer image, ISO, what platform, release or current of OpenBSD, Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen worse. But if this would have been my first impression of OpenBSD I had given it the boot and used Linux instead. Then you should know in general status of drivers and/or documentation in this arena and why they are so happy to keep it closed aka making it harder for projects like OpenBSD to support them Regards Harri
[no subject]
subscribe openbsd-misc
Fwd: bad first impression of OpenBSD at install time
From: Katherine Mcmillan Sent: Thursday, April 25, 2024 12:30:03 PM To: Harald Dunkel Subject: Re: bad first impression of OpenBSD at install time Hi Harald, I am compiling a qualitative list of experiences of those who have requested help from various user groups who/which have been rejected or ignored, to try to find similarities between the approaches used by the poster; a grounded theory methodology. Would it be okay if I included yours? Thank you for considering, Katie From: owner-m...@openbsd.org on behalf of Harald Dunkel Sent: Thursday, April 25, 2024 11:46:04 AM To: misc@openbsd.org Subject: bad first impression of OpenBSD at install time Attention : courriel externe | external email Hi folks, I posted this before, without any response from the community: At the boot> prompt of the installer image my USB keyboard still works, but at the install prompt the keyboard is ignored. I cannot press "i" to actually install OpenBSD. Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen worse. But if this would have been my first impression of OpenBSD I had given it the boot and used Linux instead. Regards Harri
Re: bad first impression of OpenBSD at install time
On Thu, Apr 25, 2024 at 05:46:04PM +0200, Harald Dunkel wrote: > Hi folks, > > I posted this before, without any response from the community: > > At the boot> prompt of the installer image my USB keyboard still works, > but at the install prompt the keyboard is ignored. I cannot press "i" > to actually install OpenBSD. > > Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen > worse. But if this would have been my first impression of OpenBSD I > had given it the boot and used Linux instead. > Without providing at least a dmesg of that system there is no way we can help you. It is not even clear what kind of system or arch it is? -- :wq Claudio
bad first impression of OpenBSD at install time
Hi folks, I posted this before, without any response from the community: At the boot> prompt of the installer image my USB keyboard still works, but at the install prompt the keyboard is ignored. I cannot press "i" to actually install OpenBSD. Fortunately I am with BSD since Ultrix and SunOS 4.0.3. I've seen worse. But if this would have been my first impression of OpenBSD I had given it the boot and used Linux instead. Regards Harri
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
On Thu, Apr 25, 2024 at 09:12:47AM +0200, Stefan Sperling wrote: > I checked, the softraid manual page already has an example installboot > invocation in EXAMPLES, which should be clear enough. Regardless, I've tweaked the wording a bit. Hopefully more clear now.
Re: Getting "Boot error" after replacing a disk in softraid [SOLVED]
On Thu, Apr 25, 2024 at 03:27:29AM +, Martin wrote: > I eventually found out what was going on. > > The FreeBSD boot problem was not related at all. > > Long story short and for future reference, installboot needs > to be run on the softraid volume, NOT on the physical disk. And this > has to be repeated after a softraid volume rebuild in order for the new > disk to be bootable too. > > This cannot be done from the boot media, but one can boot from media > and then mount the softraid with the working disk and then chroot into > that and run 'installboot sd2' (or whatever device name the softraid > volume has). > > This was not obvious to me. Perhaps because with GRUB one has to install > the bootloader and boot code on each single disk in a mdadm volume and > not on the volume itself. Ah, indeed. Thanks for reporting back with the solution. This should be obvious but it's understandable that new users might miss it. I checked, the softraid manual page already has an example installboot invocation in EXAMPLES, which should be clear enough.
Re: maximum file system size
On Thu, Apr 25, 2024 at 07:26:41AM +0200, Peter J. Philipp wrote: > On Thu, Apr 25, 2024 at 12:45:29AM -0300, Gustavo Rios wrote: > > Hi folks! > > > > What is the maximum file size in OpenBSD ? > > > > Thanks a lot. > > > > -- > > The lion and the tiger may be more powerful, but the wolves do not perform > > in the circus > > There is this comment in /usr/include/ufs/ffs/fs.h: > > /* Maximum file size the kernel allows. > * Even though ffs can handle files up to 16TB, we do limit the max file > * to 2^31 pages to prevent overflow of a 32-bit unsigned int. The buffer > * cache has its own checks but a little added paranoia never hurts. > */ > #define FS_KERNMAXFILESIZE(pgsiz, fs) ((u_int64_t)0x8000 * \ > MIN((pgsiz), (fs)->fs_bsize) - 1) > > > Now page sizes differ within OpenBSD, so then it depends between 8 TB (4096 > bytes page size) and higher perhaps? > > Best Regards, > -pjp > > -- > my associated domains: callpeter.tel|centroid.eu|dtschland.eu|mainrechner.de > dumpfs /dev/rsd0a | grep maxfilesize tells you the answer for a specific filesystem. A mentiomned in the code commment, it depends on the blocksize used by the filesystem and the page size of the platform. -Otto
