Re: veb Interface Max Cache Size Restrict
On 2023-04-18, Samuel Jayden wrote: > > I want to switch from Cisco device to OpenBSD in a place where there are > more than 8 thousand MAC addresses, but I need to exceed this max cache > size value. I guess it depends on what exactly the traffic is, but software-bridging traffic from a network segment with >4k devices on OpenBSD seems a tad optimistic. Try with dlg's suggestion if you like, but maybe at a time when users of more than 8 thousand devices won't be too upset. Normally one would want to reduce the number of devices in the segment - realistically the broadcast or multicast traffic for address resolution will get a bit much (especially if wifi is involved) - and even ignoring that, it implies the amount of traffic is such that you'd usually want an actual switch (and a reasonably decent one at that).
Re: [arm64] [sound] simpleaudio, but no audio to attach
On 2023-04-18, S V wrote:
> Hello, misc@!
>
> I'm using ARM64/current and see that my audio chip got detected by simpleaudio
> but OpenBSD can't attach audio to it
>
> Any suggestions on there to start reading? I'm not developer,
> but I tried to read different match/attach functions
> in simpleaudio.c/audio.c with no result for now.
Fortunately you don't need to be a programmer to add some code that
will help you figure out more about what's going on.
Try adding printf()s to simpleaudio_attach_deferred() to check if that
function is called and, if so, see how far it gets.
I guess it might hit one of the "return"s before actually attaching, so
for example you could add printf before+after the various return
statements to see if they were triggered.
While you can just printf some text that you write to identify them,
you can save a bit of time by sprinkling some of these which use the
C features to include the function name/line number:
printf("... %s line %d\n", __func__, __LINE__);
Re: hardware
On 2023-04-19 01:40, folly bololey wrote: It doesn't matter whether the cat is black or white, as long as it catches mice. Black cat is more stealthy just a different hunting strategy and depends on the lighting. white cats would be stealthier in snow, or ambushing from above in the day time.
Re: growing an encrypted disk
On Tue, Apr 18, 2023 at 10:21:19AM -0300, Gabriel Busch de Brito wrote: Hi, Crystal shared this link with the list sometime ago that might help: https://research.exoticsilicon.com/articles/resizing_softraid_volumes Yes it does help, thank you! --
Re: veb Interface Max Cache Size Restrict
On Tue, Apr 18, 2023 at 07:51:08PM +, Samuel Jayden wrote:
> Hello,
> I have one veb interface in OpenBSD 7.2 and 5 ethernet ports are paired
> with this veb. As I understand from the ifconfig output, 4096 mac address
> cache values can be kept in this veb interface .
>
> ifconfig veb10
> veb10: flags=8843
> index 12 llprio 3
> groups: veb
> em3 flags=3
> port 4 ifpriority 0 ifcost 0
> em0 flags=3
> port 1 ifpriority 0 ifcost 0
> em1 flags=3
> port 2 ifpriority 0 ifcost 0
> ix3 flags=3
> port 8 ifpriority 0 ifcost 0
> ix2 flags=3
> port 7 ifpriority 0 ifcost 0
> Addresses (max cache: 4096, timeout: 240):
> 2c:f0:5d:73:f8:c4 em1 0 flags=0<>
>
>
> When I tried to extend this limit value with the command "ifconfig veb10
> maxaddr 4097", I got the following error message:
> "ifconfig: veb10: Invalid argument"
> The maximum value I can give without this error message is 4096. Isn't this
> value a bit narrow?
maybe. it seemed pretty high when i made it up.
> I have tested that the mac addresses of the connected devices are not
> recorded in the veb interface after exceeding the limit.
>
> I want to switch from Cisco device to OpenBSD in a place where there are
> more than 8 thousand MAC addresses, but I need to exceed this max cache
> size value.
> How can I increase this max cache size value 8192 or higher value?
you change 4096 to a bigger number in the code.
Index: if_etherbridge.c
===
RCS file: /cvs/src/sys/net/if_etherbridge.c,v
retrieving revision 1.7
diff -u -p -r1.7 if_etherbridge.c
--- if_etherbridge.c5 Jul 2021 04:17:41 - 1.7
+++ if_etherbridge.c19 Apr 2023 02:25:54 -
@@ -675,7 +676,7 @@ int
etherbridge_set_max(struct etherbridge *eb, struct ifbrparam *bparam)
{
if (bparam->ifbrp_csize < 1 ||
- bparam->ifbrp_csize > 4096) /* XXX */
+ bparam->ifbrp_csize > 16384) /* XXX */
return (EINVAL);
/* commit */
kshcolor - a script for decorating ksh shell programs and terminals
Hiya folks,
As a learning project to teach myself how to use the ksh shell I wrote a
helper script to set ansi colors and decorations that I'm calling
*kshcolor*.
The script is available here for anyone who is intrigued:
https://github.com/tbullock/kshcolor
The project includes a makefile to build the script, this was necessary
since manually typing ANSI escape sequences is annoying so I chose to
generate those rather than fail at typing them.
To install run `make install`
To run the included test run `make test`
The makefile will install the file kshcolor.sh in $(HOME)/bin
The script includes the following functions:
bk # Sets Black
rd # Sets Red
gr # Sets Green
ye # Sets Yellow
bl # Sets Blue
mg # Sets Magenta
cy # Sets Cyan
wh # Sets White
bg_bk # Sets background Black
bg_rd # Sets background Red
bg_gr # Sets background Green
bg_ye # Sets background Yellow
bg_bl # Sets background Blue
bg_mg # Sets background Magenta
bg_cy # Sets background Cyan
bg_wh # Sets background White
bold# Bold
dim # Dim
underline # Underline
blink # Blink (this may not be implemented by your terminal)
invert # Invert
hidden # Hidden
reset_decorations # clear inherited decorations
These functions do not directly make any visible changes to the
terminal, rather that is left to the function:
decorate# applies configured decorations to the first argument
The decorate function looks at the currently configured decorations
(colours and attributes) and applies the necessary ANSI escape sequences
to tell the terminal how it's argument is to be rendered. If the
terminal doesn't support at least the standard 8 ANSI colours this
become a no-op and leaves the variable undecorated.
The result can then be sent to echo or print or wherever your heart
desires them to go (maybe Narnia!?).
Example:
# Apply foreground and background colours separately
rd
bg_ye
text1=$(decorate "this text is red ")
# Change the background colour
bg_mg
text2=$(decorate "but the background changes")
# Display the decorated text
echo "${text1}${text2}"
reset_decorations
This project was largely an educational evening for me in how ksh
scripting works, if people find it useful, cute or want to use it to
splash the rainbow all over their terminal, then please let me know what
you come up with.
[arm64] [sound] simpleaudio, but no audio to attach
Hello, misc@!
I'm using ARM64/current and see that my audio chip got detected by simpleaudio
but OpenBSD can't attach audio to it
Any suggestions on there to start reading? I'm not developer,
but I tried to read different match/attach functions
in simpleaudio.c/audio.c with no result for now.
I got audio chip of my arm64 board
as
simpleaudio0 at mainbus0
eeprom says
Node 0x54f0
name: 'sound'
simple-audio-card,hp-det-gpio: 0014.001b.0001
simple-audio-card,bitclock-master: 0030
simple-audio-card,name: 'MITX-Sound-Card'
simple-audio-card,mic-det-gpio: 0014.001a.0001
simple-audio-card,format: 'i2s'
simple-audio-card,widgets: 'Microphone' + 'Mic Jack' + 'Headphone'
+ 'Headphones' + 'Speaker' + 'AUX Out' + 'Line' + 'Line In'
simple-audio-card,routing: 'Headphones' + 'RHP' + 'Headphones'
+ 'LHP' + 'AUX Out' + 'AUXOUT1' + 'AUX Out' + 'AUXOUT2' + 'L2'
+ 'Mic Jack' + 'R2' + 'Mic Jack' + 'Mic Jack' + 'Mic Bias' + 'LAUX'
+ 'Line In' + 'RAUX' + 'Line In'
compatible: 'simple-audio-card'
simple-audio-card,frame-master: 0030
Node 0x567c
name: 'simple-audio-card,cpu'
sound-dai: 0031
Node 0x56ac
name: 'simple-audio-card,codec'
phandle: 0030
sound-dai: 0032.
Looking at DTS I can identify it as Nuvoton Nau8822 sitting on i2c and/or i2s
nau8822@1a {
#sound-dai-cells = <0x01>;
compatible = "nuvoton,nau8822";
reg = <0x1a>;
phandle = <0x32>;
};
--
Nerfur Dragon
-==(UDIC)==-
Re: smtpd.conf examples - quoting question/inaccuracy?
Hi,
Thanks for validating my thoughts. I appreciate the time you took to reply.
Cheers,
Steve Williams
On 4/18/2023 2:25 AM, Omar Polo wrote:
On 2023/04/17 10:32:58 -0600, Steve Williams
wrote:
Hi,
I am working on making some changes to my smtpd.conf file and was looking
at the man page for it.
from:
https://man.openbsd.org/smtpd.conf
In the "Examples" section, there seems to be inconsistent use of
quotation marks. I'm not sure if there is any signficance to it, or
if there's a preferred approach.
action mda_with_aliases mda "/path/to/mda -f -" alias
action mda_without_aliases mda "/path/to/mda -f -"
action "outbound" relay
^^^ Why does "outbound" have quotes around it, but not the 2 lines
above in the mda_with_aliases and mda_without_aliases?
match for local action mda_with_aliases
match from any for domain example.com action mda_without_aliases
match for any action "outbound"
^^^ Similarily, the "outbound" has quotes, but the 2 "mda_with.."
lines don't have quotes.
Slightly confused, just wanting to understand precisely the config file.
While I agree that the example section could be more consistent in
this regard, I think this is already well explained at the top of the
man page:
[..] entire block. Argument names not beginning with a letter, digit, or
underscore, as well as reserved words (such as listen, match, and port),
must be quoted. Arguments containing whitespace should be surrounded by
double quotes (").
so except for the mda command string none of the argument in the bits
you mentioned strictly need quotations marks; it's just a matter of
personal style.
HTH
Re: dmesg and sensors for ODROID H3
On Tue, Apr 18, 2023 at 7:28 AM stolen data wrote: > > Everything seems to work. Only caveat noticed is that the firmware is > UEFI-only with no CSM/legacy mode, and it will only boot an OpenBSD > installation from GPT which must contain an EFI system partition holding > the bootloader. great choice. my ODROID H2+ is still holding strong with the add-in card for 4 extra NICs. it is a fine home firewall. my only complaint is sometimes having rge5: watchdog timeout rge2: watchdog timeout in dmesg and occasional link state issues, but i didn't dig into whether its from the rge driver or stuff i attached. if you can, provide an iperf3 result in both forward and reverse mode. here, i only have about 1.60 Gbit/s in both directions, but that's fine for my wan link. > > > sensors and timers: > > masheen# sysctl hw.sensors kern.timecounter.choice > hw.sensors.cpu0.temp0=25.00 degC > hw.sensors.cpu0.frequency0=8.00 Hz > hw.sensors.cpu1.frequency0=8.00 Hz > hw.sensors.cpu2.frequency0=8.00 Hz > hw.sensors.cpu3.frequency0=8.00 Hz > hw.sensors.acpitz0.temp0=27.80 degC (zone temperature) > hw.sensors.softraid0.drive0=online (sd1), OK > kern.timecounter.choice=i8254(0) tsc(2000) acpihpet0(1000) acpitimer0(1000) > > > dmesg: > > OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT 2023 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4115353600 (3924MB) > avail mem = 3971211264 (3787MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x78d74000 (138 entries) > bios0: vendor American Megatrends Inc. version "5.19" date 02/27/2023 > bios0: HARDKERNEL ODROID-H3 > efi0 at bios0: UEFI 2.7 > efi0: American Megatrends rev 0x50013 > acpi0 at bios0: ACPI 6.2 > acpi0: sleep states S0 S5 > acpi0: tables DSDT FACP MCFG FIDT SSDT SSDT SSDT HPET APIC PRAM SSDT SSDT > NHLT LPIT SSDT SSDT DBGP DBG2 SSDT DMAR SSDT TPM2 WSMT FPDT > acpi0: wakeup devices PEGP(S0) PEGP(S0) PEGP(S0) PEGP(S0) SIO1(S0) RP01(S0) > PXSX(S0) RP02(S0) PXSX(S0) RP03(S0) PXSX(S0) RP04(S0) PXSX(S0) RP05(S0) > PXSX(S0) RP06(S0) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xc000, bus 0-255 > acpihpet0 at acpi0: 1920 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 38MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.2.2.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.27 MHz, 06-9c-00 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX
veb Interface Max Cache Size Restrict
Hello, I have one veb interface in OpenBSD 7.2 and 5 ethernet ports are paired with this veb. As I understand from the ifconfig output, 4096 mac address cache values can be kept in this veb interface . ifconfig veb10 veb10: flags=8843 index 12 llprio 3 groups: veb em3 flags=3 port 4 ifpriority 0 ifcost 0 em0 flags=3 port 1 ifpriority 0 ifcost 0 em1 flags=3 port 2 ifpriority 0 ifcost 0 ix3 flags=3 port 8 ifpriority 0 ifcost 0 ix2 flags=3 port 7 ifpriority 0 ifcost 0 Addresses (max cache: 4096, timeout: 240): 2c:f0:5d:73:f8:c4 em1 0 flags=0<> When I tried to extend this limit value with the command "ifconfig veb10 maxaddr 4097", I got the following error message: "ifconfig: veb10: Invalid argument" The maximum value I can give without this error message is 4096. Isn't this value a bit narrow? I have tested that the mac addresses of the connected devices are not recorded in the veb interface after exceeding the limit. I want to switch from Cisco device to OpenBSD in a place where there are more than 8 thousand MAC addresses, but I need to exceed this max cache size value. How can I increase this max cache size value 8192 or higher value? Thank you in advance for your interest.
Re: hardware
> It doesn't matter whether the cat is black or white, as long as it > catches mice. Black cat is more stealthy
OT: Cyber Resilience Act freeing space for ChatGPT bots? :D
Hello, Briefly, I just came accross ths one: https://5md.at/l/cra Joking, there is argument to hope to free up space for bots, almost in EU, at time.. Meanwhile little stuff like DNSSEC remains to much complicated to deploy.. But the list can go longer to demo the *scarsity* of ideas there is around. Any more insight or thought about this *cra* ? -- Daniele Bonini
dmesg and sensors for ODROID H3
Everything seems to work. Only caveat noticed is that the firmware is UEFI-only with no CSM/legacy mode, and it will only boot an OpenBSD installation from GPT which must contain an EFI system partition holding the bootloader. sensors and timers: masheen# sysctl hw.sensors kern.timecounter.choice hw.sensors.cpu0.temp0=25.00 degC hw.sensors.cpu0.frequency0=8.00 Hz hw.sensors.cpu1.frequency0=8.00 Hz hw.sensors.cpu2.frequency0=8.00 Hz hw.sensors.cpu3.frequency0=8.00 Hz hw.sensors.acpitz0.temp0=27.80 degC (zone temperature) hw.sensors.softraid0.drive0=online (sd1), OK kern.timecounter.choice=i8254(0) tsc(2000) acpihpet0(1000) acpitimer0(1000) dmesg: OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4115353600 (3924MB) avail mem = 3971211264 (3787MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x78d74000 (138 entries) bios0: vendor American Megatrends Inc. version "5.19" date 02/27/2023 bios0: HARDKERNEL ODROID-H3 efi0 at bios0: UEFI 2.7 efi0: American Megatrends rev 0x50013 acpi0 at bios0: ACPI 6.2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP MCFG FIDT SSDT SSDT SSDT HPET APIC PRAM SSDT SSDT NHLT LPIT SSDT SSDT DBGP DBG2 SSDT DMAR SSDT TPM2 WSMT FPDT acpi0: wakeup devices PEGP(S0) PEGP(S0) PEGP(S0) PEGP(S0) SIO1(S0) RP01(S0) PXSX(S0) RP02(S0) PXSX(S0) RP03(S0) PXSX(S0) RP04(S0) PXSX(S0) RP05(S0) PXSX(S0) RP06(S0) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xc000, bus 0-255 acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.2.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.27 MHz, 06-9c-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Celeron(R) N5105 @ 2.00GHz, 798.28 MHz, 06-9c-00 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,RDSEED,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 12-way L2 cache, 4MB 64b/line 16-way L3 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpiprt0 at acpi0: bus 0 (PC00) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus -1 (RP06) acpiprt6 at
Re: hardware
I was always partial to the blue or purple ones. On April 18, 2023 3:42:58 AM MDT, Joel Carnat wrote: > >> Le 18 avr. 2023 à 11:30, Stuart Henderson a >> écrit : >> >> On 2023-04-18, Mischa wrote: On 2023-04-17 23:37, Mike Larkin wrote: On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: > Gustavo Rios wrote: > >> What is the best supported servers by OpenBSD ? > > The silver ones work a little bit better than the black ones. > disagree. All my long running servers are the black ones. >>> >>> I concur. The black ones are the best! >>> They also need to have blue blinkenlights. >> >> No love for the blue ones? > >If SunFire v100 count as blue, I do. > >
Re: growing an encrypted disk
Hi, Crystal shared this link with the list sometime ago that might help: https://research.exoticsilicon.com/articles/resizing_softraid_volumes Best, G On 18.04.2023 13:29, void wrote: > Hello misc@, > > Can an encrypted disk (it's an additional disk) be grown? > OpenBSD here is a virtualised instance. The host > filesystem is zfs, so the additional disk is also > zfs-backed. > > I've been reading https://www.openbsd.org/faq/faq14.html#GrowPartition > and later on in that page the encrypted whole disk setup > but am unsure if for example having the disk encrypted in the first place > will break the ability to grow partitions. > > thanks, > -- >
growing an encrypted disk
Hello misc@, Can an encrypted disk (it's an additional disk) be grown? OpenBSD here is a virtualised instance. The host filesystem is zfs, so the additional disk is also zfs-backed. I've been reading https://www.openbsd.org/faq/faq14.html#GrowPartition and later on in that page the encrypted whole disk setup but am unsure if for example having the disk encrypted in the first place will break the ability to grow partitions. thanks, --
Re: PC Engines APU2 infinite loop rebooting immediate after kernel loads
How is your /etc/boot.conf ? Did you include the output vídeo to com0 Port ? Best regards, Paulo. > Em 17 de abr. de 2023, à(s) 21:30, Jonathan Thornburg > escreveu: > > *Summary* > I have a PC Engines APU2 with a wierd problem: on power-on it starts > executing the PC Engines coreboot as it should, loads the OpenBSD boot > loader, and the OpenBSD boot loader then loads an OpenBSD kernel (either > 7.2/amd64 bsd.rd from an SD card *or* 7.3/amd64 bsd.rd from a USB stick). > But immediately after printing > entry point at 0x8100100 > the APU2 reboots. Memtest86 doesn't find anything wrong with the hardware. > Has anyone else seen these symptoms and/or have any suggestions for further > troubleshooting? > > > *Details* > The hardware is a PC Engines apu4d4 (4 ethernet ports, 2 USB, 4GB RAM) > with a 16GB SD card. I bought the hardware in mid-2022 but didn't get > it working them; alas I don't recall just what I did then. I'm now > returning to trying to get it operational. > > The PC Engines coreboot BIOS has an option to run memtest86; I did a > full cycle (about 1.5 hours wall-clock time) and it didn't find any > problems with the cpu/memory. > > There is a 7.2/amd64 bsd.rd on the SD card. If I power the apu2 on and > don't interrupt the startup sequence, it gets as far as the OpenBSD boot > loader loading that kernel and printing the kernel entry address, but then > the apu2 reboots (and the cycle repeats forever if I don't interrupt it). > Here's a transcript of the serial-port output showing the startup and > first reboot: > --- begin --- > ^@PC Engines apu4 > coreboot build 20202905 > BIOS version v4.12.0.1 > 4080 MB ECC DRAM > > ESCcESC[?7lESC[2JESC[0mSeaBIOS (version rel-1.12.1.3-0-g300e8b70) > > Press F10 key now for boot menu > > Booting from Hard Disk... > Using drive 0, partition 3. > Loading.. > probing: pc0 com0 com1 com2 com3 mem[639KKESC[08;42H 3325M 752M a20=on] > disk: hd0+ >>> OpenBSD/amd64 BOOT 3.55 > boot> > cannot open hd0a:/etc/random.seed: No such file or directory > booting hd0a:/7.2/amd64/bsd.rd: 3916484+1639424+3884040+0+704512 > [109+438912+292 > 606]=0xa61d70 > entry point at 0x8100100PC Engines apu4 > coreboot build 20202905 > BIOS version v4.12.0.1 > 4080 MB ECC DRAM > > ESCcESC[?7lESC[2JESC[0mSeaBIOS (version rel-1.12.1.3-0-g300e8b70) > --- end --- > > If this were the only problem, I could easily write it off as the > kernel on the SD card being corrupted, and/or the SD card being faulty. > But I get an almost-identical result if I follow > https://www.openbsd.org/faq/faq4.html#MkInsMedia > and try to boot from a 7.3/amd64 install73.img on a USB stick: > --- begin --- > ^@PC Engines apu4 > coreboot build 20202905 > BIOS version v4.12.0.1 > 4080 MB ECC DRAM > > ESCcESC[?7lESC[2JESC[0mSeaBIOS (version rel-1.12.1.3-0-g300e8b70) > > Press F10 key now for boot menu > > Select boot device: > > 1. USB MSC Drive Lexar USB Flash Drive 8.07 > 2. SD card SE16G 15193MiB > 3. Payload [setup] > 4. Payload [memtest] > > Booting from Hard Disk... > Using drive 0, partition 3. > Loading.. > probing: pc0 com0 com1 com2 com3 mem[639K 3325M 752M a20=on] > disk: hd0+ hd1+ >>> OpenBSD/amd64 BOOT 3.55 > boot> > cannot open hd0a:/etc/random.seed::ESC[19;35H No such file or directory > booting hd0a:/7.3/amd64/bsd.rd: 3924676+1647616+3886216+0+704512 > [109+440424+293 > 778]=0xa667f0 > entry point at 0x8100100PC Engines apu4 > coreboot build 20202905 > BIOS version v4.12.0.1 > 4080 MB ECC DRAM > > ESCcESC[?7lESC[2JESC[0mSeaBIOS (version rel-1.12.1.3-0-g300e8b70) > --- end --- > > Since two different kernels and boot devices result in the same > infinite-reboot loop, with the reboot happening at the same place > in the boot sequence (immediately after the kernel entry point address > is printed), I don't think my problem is a corrupted kernel file. > I've also tried swapping power supplies, with no change in the outcome. > > Has anyone seen this sort of problem (infinite reboot loop, rebooting > immediately after kernel entry point address is printed) before? Should > I be looking at reflashing the BIOS with a newer (or older) version? > > Thanks for any insights, > -- > -- "Jonathan Thornburg [remove color- to reply]" > > on the west coast of Canada, eh? > "!07/11 PDP a ni deppart m'I !pleH" -- slashdot.org page footer, 2022-10-16 > "eHpl !'I mrtpaep dnia P PD1 /107" -- slightly more plausible message > given PDP-11 little-endian byte order >
Re: hardware
On Mon, 2023-04-17 at 21:37 +, Mike Larkin wrote: > On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: > > Gustavo Rios wrote: > > > > > What is the best supported servers by OpenBSD ? > > > > The silver ones work a little bit better than the black ones. > > > > disagree. All my long running servers are the black ones. > > It doesn't matter whether the cat is black or white, as long as it catches mice.
Re: hardware
> Le 18 avr. 2023 à 11:30, Stuart Henderson a écrit > : > > On 2023-04-18, Mischa wrote: >>> On 2023-04-17 23:37, Mike Larkin wrote: >>> On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: Gustavo Rios wrote: > What is the best supported servers by OpenBSD ? The silver ones work a little bit better than the black ones. >>> >>> disagree. All my long running servers are the black ones. >> >> I concur. The black ones are the best! >> They also need to have blue blinkenlights. > > No love for the blue ones? If SunFire v100 count as blue, I do.
Re: hardware
Sure, the cobalt and electric blue ones are great. But also the dark red, green and dark blue ones. The silver / white ones are great to, specially if you need them in a modern or home office. > Am 18.04.2023 um 11:30 schrieb Stuart Henderson : > > On 2023-04-18, Mischa wrote: >>> On 2023-04-17 23:37, Mike Larkin wrote: >>> On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: Gustavo Rios wrote: > What is the best supported servers by OpenBSD ? The silver ones work a little bit better than the black ones. >>> >>> disagree. All my long running servers are the black ones. >> >> I concur. The black ones are the best! >> They also need to have blue blinkenlights. > > No love for the blue ones? > >
Re: hardware
On 2023-04-18, Mischa wrote: > On 2023-04-17 23:37, Mike Larkin wrote: >> On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: >>> Gustavo Rios wrote: >>> >>> > What is the best supported servers by OpenBSD ? >>> >>> The silver ones work a little bit better than the black ones. >>> >> >> disagree. All my long running servers are the black ones. > > I concur. The black ones are the best! > They also need to have blue blinkenlights. No love for the blue ones?
Re: hardware
On 2023-04-17 23:37, Mike Larkin wrote: On Mon, Apr 17, 2023 at 02:21:14PM -0600, Theo de Raadt wrote: Gustavo Rios wrote: > What is the best supported servers by OpenBSD ? The silver ones work a little bit better than the black ones. disagree. All my long running servers are the black ones. I concur. The black ones are the best! They also need to have blue blinkenlights. Mischa
Re: smtpd.conf examples - quoting question/inaccuracy?
On 2023/04/17 10:32:58 -0600, Steve Williams
wrote:
> Hi,
>
> I am working on making some changes to my smtpd.conf file and was looking
> at the man page for it.
>
> from:
> https://man.openbsd.org/smtpd.conf
>
> In the "Examples" section, there seems to be inconsistent use of
> quotation marks. I'm not sure if there is any signficance to it, or
> if there's a preferred approach.
>
> action mda_with_aliases mda "/path/to/mda -f -" alias
> action mda_without_aliases mda "/path/to/mda -f -"
> action "outbound" relay
>
> ^^^ Why does "outbound" have quotes around it, but not the 2 lines
> above in the mda_with_aliases and mda_without_aliases?
>
> match for local action mda_with_aliases
> match from any for domain example.com action mda_without_aliases
> match for any action "outbound"
>
> ^^^ Similarily, the "outbound" has quotes, but the 2 "mda_with.."
> lines don't have quotes.
>
> Slightly confused, just wanting to understand precisely the config file.
While I agree that the example section could be more consistent in
this regard, I think this is already well explained at the top of the
man page:
[..] entire block. Argument names not beginning with a letter, digit, or
underscore, as well as reserved words (such as listen, match, and port),
must be quoted. Arguments containing whitespace should be surrounded by
double quotes (").
so except for the mda command string none of the argument in the bits
you mentioned strictly need quotations marks; it's just a matter of
personal style.
HTH
Re: PC Engines APU2 infinite loop rebooting immediate after kernel loads
On Mon, Apr 17, 2023 at 05:23:05PM -0700, Jonathan Thornburg wrote: > *Summary* > I have a PC Engines APU2 with a wierd problem: on power-on it starts > executing the PC Engines coreboot as it should, loads the OpenBSD boot > loader, and the OpenBSD boot loader then loads an OpenBSD kernel (either > 7.2/amd64 bsd.rd from an SD card *or* 7.3/amd64 bsd.rd from a USB stick). > But immediately after printing > entry point at 0x8100100 > the APU2 reboots. Memtest86 doesn't find anything wrong with the hardware. > Has anyone else seen these symptoms and/or have any suggestions for further > troubleshooting? > Loading.. > probing: pc0 com0 com1 com2 com3 mem[639KKESC[08;42H 3325M 752M a20=on] > disk: hd0+ > >> OpenBSD/amd64 BOOT 3.55 > boot> > cannot open hd0a:/etc/random.seed: No such file or directory > booting hd0a:/7.2/amd64/bsd.rd: 3916484+1639424+3884040+0+704512 > [109+438912+292 > 606]=0xa61d70 > entry point at 0x8100100PC Engines apu4 > coreboot build 20202905 > BIOS version v4.12.0.1 > 4080 MB ECC DRAM You forgot about setting up the serial console in the boot loader: boot> stty com0 115200 boot> set tty com0 boot> boot bsd.rd
Re: Making MS teams work on openbsd
Le Fri, Mar 31, 2023 at 03:42:48PM +0200, Divan Santana a écrit : > > - if no audio, mute and unmute the tab > Thank you for the tip, it solved my audio issue. Unfortunately, I lost the mic in the battle :D So back to Firefox for Teams despite the screen sharing problem.
Re: login string size
Den mån 17 apr. 2023 kl 23:01 skrev Gustavo Rios : > > i meant not the time, but it's length: strlen(login). /usr/include/pwd.h will help here I guess. -- May the most significant bit of your life be positive.
