Re: type checking/signalling shell and utilities?
On Fri, Nov 19, 2021 at 02:40:45PM +1059, Reuben ua Bríġ wrote: > > Date: Thu, 18 Nov 2021 21:20:36 +0100 > > From: Andreas Kusalananda Kähäri > > > > > all very well if you only need one array of strings, but useless if > > > you need more. > > > > What is the "more" you need? > > A greater number of arrays. Using -- is a programming hack/trick that > allows .one. arbitrary array of arbitrary strings (a list) to be past. > Say I had a compiler of sorts that takes multiple input files of > differing types. There is no way I can expect a command like > > compile -type1 * -type2 2/* Ah, so you are talking about options that takes multiple option-arguments. That's not how options usually work on Unix, at least not with utilities that uses standard command line parsing. Note that if some option, -a, takes an option-argument, then there is no issue if that argument looks like an option, so utility -a -a ... would call utility with the option -a, and "-a" would be the option-argument to that option, and there would be no confusion. > > to work without first checking the names in '.', and even 'ti' if > compile takes arguments with '/' (if you cant think of any UNIX > utilities that do that, shame on you). I'm not seeing you giving an example. > Even a distributive operator allowing > > compile -type1^* -type2^2/* > > to be interpreted as > > compile -type 1 <*1> -type 1 <*2> ... > > would be useful with existing utilities, but Im not aware of any. Well, "shame on you" then. > --- > Im not asking anyway to program this, Im asking if anyone is aware of > anyone else having already programmed it. Please do read before writing. It's already been done by the people developing the zsh shell. compile dir1/*(P[-type1]) dir2/*(P[-type2]) This would append "-type1" before each name that dir1/* expands to, and similarly for the second globbing pattern. I'm assuming this is what you were looking for. If you want to match only regular files, include hidden names, and remove the pattern if there are no matches, compile dir1/*(.DNP[-type1]) dir2/*(.DNP[-type2]) -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: Supermicro IPMIView/iKVM
On Thu, Nov 18, 2021, at 6:36 PM, Allan Streib wrote: > Anyone successfully using SuperMicro's IPMIView20 java > application on OpenBSD with any of the jdk packages? I discovered that the noVNC package includes support for the ATEN iKVM vnc protocol variant used on some SuperMicro boards; this looks like it will work for me and be a preferable approach. Allan
Supermicro IPMIView/iKVM
Anyone successfully using SuperMicro's IPMIView20 java application on OpenBSD with any of the jdk packages? I have it basically working, I can log in to rempte BMC, see sensors and control power etc. but the iKVM remote console just silently fails. I have a ktrace file that I am digging through but nothing is really jumping out so far. Allan
Re: type checking/signalling shell and utilities?
On Thu, Nov 18, 2021 at 03:14:16AM +1100, Reuben ua Bríġ wrote: > > Date: Thu, 18 Nov 2021 01:30:25 +1100 > > From: Reuben ua Bríġ > > > > Does anyone know of any shell and utilities where, for example, if > > > > -rf > > > > is a file name, the rm utility will understand so, and not think it > > is a controlling flag (ugh! in-band signalling)? One where an array > > of strings can be past as a single argument? Etc? etc? > > > Date: Thu, 18 Nov 2021 01:38:14 +1100 > > From: Reuben ua Bríġ > > > > correction: is a file name expanded from a pattern, ... > > I have gotten a number of replies that quite miss the point. I gave rm > as a simple and readily understandable toy problem. The '--' trick is Using -- is not a "trick". > all very well if you only need one array of strings, but useless if you > need more. What is the "more" you need? > I felt a more elegant solution would be a shell that can pass an array > of strings as an argument, just as C can, and knows when to do so, > rather than having each string as an argument. I wanted to know if > there is already a shell that accomplishes that.--No need to reinvent > the shell if someone has done so already. Just make a habit of calling your utilities with -- to delimit options from operands, especially if the operands are supplied from patterns or other input that could result in words starting with a dash. This is not a trick. Just common sense shell scripting practice. > I do not need advice on how to use the UNIX shell and utilities. (Yuck!) You're implying otherwise. -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
Re: How to check that HT is working and used?
You are absolutely right! Now I see all the cores! Thank you, guys! чт, 18 нояб. 2021 г. в 16:28, Christer Solskogen < christer.solsko...@gmail.com>: > On Thu, Nov 18, 2021 at 1:50 PM Dev Op wrote: > >> Updated BIOS to the latest version for this server - P58 (08/16/2015). All >> the same. Tried changing the parameter MPS Table Mode in BIOS (the option >> was set to Disabled), after setting the value to Full Table APIC, dmesg >> changed, but the cores still did not appear: >> >> OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC >> >> > You are still using the SP-kernel. Try booting with bsd.mp instead. > -- Regards, Den
Re: type checking/signalling shell and utilities?
If you want to experiment in that direction, Tom Duff's 'rc' shell has 'list of words' as a primative, and avoids re-parsing strings. See https://en.wikipedia.org/wiki/Rc for more information. There doesn't seem to be an OpenBSD port of rc (but there is 'es', which claims to be derived from rc).
Re: Limit Mail Submission to inet4
On 2021-11-18, Simon Hoffmann wrote: > --TB36FDmn/VVEgNH/ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: 7bit > >> On Thu, Nov 18, 2021 at 10:55:00AM +0100, Simon Hoffmann wrote: >> > > >> > > >> > > >GMail still wont accept my IPv6 submitted mails. >> > > >> > > Are you using ipv6 connectivity over tunnel from tunnelbroker.net? >> > >> > Nope. My relays have "real" IPv6 /64 networks assigned to their interfaces >> > natively. >> > >> > However, I'd still like to only use IPv4 when sending messages. >> >> Why? Why not fix the IPv6 issue? Our servers deliver to gmail over IPv6 >> with >> no issues. Google certainly seem much more stringent about what mail they'll accept over v6. Several MTA now have a way to disable v6 / drop records that was *specifically* added to get around problems delivering to Google. > Hmm, thats interesting. The last time i googled it said that its a known > issue with > gmail and one should use IPv4. Also, the GMail help and the error message > were all to > no use. > > I will try sending via IPv6 later today and report back. > > If you like, you can lookup DNS recors for mxbackup.hetzner.hoffbox.net > Should be correct. PTR has the same name as A/AAAa, A and are present... Hetzner address space is not likely to have the best IP reputation on mail receivers.. -- Please keep replies on the mailing list.
Re: How to check that HT is working and used?
On Thu, Nov 18, 2021 at 1:50 PM Dev Op wrote: > Updated BIOS to the latest version for this server - P58 (08/16/2015). All > the same. Tried changing the parameter MPS Table Mode in BIOS (the option > was set to Disabled), after setting the value to Full Table APIC, dmesg > changed, but the cores still did not appear: > > OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > > You are still using the SP-kernel. Try booting with bsd.mp instead.
Re: How to check that HT is working and used?
Updated BIOS to the latest version for this server - P58 (08/16/2015). All the same. Tried changing the parameter MPS Table Mode in BIOS (the option was set to Disabled), after setting the value to Full Table APIC, dmesg changed, but the cores still did not appear: OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4276367360 (4078MB) avail mem = 4130840576 (3939MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (69 entries) bios0: vendor HP version "P58" date 08/16/2015 bios0: HP ProLiant DL360 G5 acpi0 at bios0: ACPI 3.0 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC BERT HEST SSDT acpi0: wakeup devices PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5430 @ 2.66GHz, 2667.15 MHz, 06-17-06 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,LONG,LAHF,PERF,SENSOR,MELTDOWN cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 333MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (IP2P) acpiprt2 at acpi0: bus 9 (PT02) acpiprt3 at acpi0: bus 10 (IPE4) acpiprt4 at acpi0: bus 11 (IPE1) acpiprt5 at acpi0: bus 16 (P2P2) acpiprt6 at acpi0: bus 6 (PT03) acpiprt7 at acpi0: bus 19 (PT04) acpiprt8 at acpi0: bus 3 (NB01) acpiprt9 at acpi0: bus 5 (NB02) acpipci0 at acpi0 PCI0 "IPI0001" at acpi0 not configured "PNP0A06" at acpi0 not configured acpicpu0 at acpi0: C1(1000@1 halt) acpitz0 at acpi0: critical temperature is 31 degC ipmi at mainbus0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 5000P Host" rev 0xb1 ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0xb1 pci1 at ppb0 bus 9 ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci2 at ppb1 bus 10 ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci3 at ppb2 bus 11 ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01 pci4 at ppb3 bus 14 ppb4 at pci2 dev 2 function 0 "Intel 6321ESB PCIE" rev 0x01 pci5 at ppb4 bus 15 ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01 pci6 at ppb5 bus 16 ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0xb1 pci7 at ppb6 bus 6 ciss0 at pci7 dev 0 function 0 "Hewlett-Packard Smart Array" rev 0x03: apic 8 int 16 ciss0: 1 LD, HW rev 3, FW 6.86/6.86, 64bit fifo scsibus1 at ciss0: 1 targets sd0 at scsibus1 targ 0 lun 0: sd0: 69973MB, 512 bytes/sector, 143305920 sectors ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE x8" rev 0xb1 pci8 at ppb7 bus 19 ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0xb1 pci9 at ppb8 bus 22 ppb9 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0xb1 pci10 at ppb9 bus 2 ppb10 at pci10 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 pci11 at ppb10 bus 3 bnx0 at pci11 dev 0 function 0 "Broadcom BCM5708" rev 0x12: apic 8 int 18 ppb11 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0xb1 pci12 at ppb11 bus 4 ppb12 at pci12 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 pci13 at ppb12 bus 5 bnx1 at pci13 dev 0 function 0 "Broadcom BCM5708" rev 0x12: apic 8 int 19 pchb1 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0xb1 pchb2 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0xb1 pchb3 at pci0 dev 16 function 2 "Intel 5000 Error Reporting" rev 0xb1 pchb4 at pci0 dev 17 function 0 "Intel 5000 Reserved" rev 0xb1 pchb5 at pci0 dev 19 function 0 "Intel 5000 Reserved" rev 0xb1 pchb6 at pci0 dev 21 function 0 "Intel 5000 FBD" rev 0xb1 pchb7 at pci0 dev 22 function 0 "Intel 5000 FBD" rev 0xb1 uhci0 at pci0 dev 29 function 0 "Intel 6321ESB USB" rev 0x09: apic 8 int 16 uhci1 at pci0 dev 29 function 1 "Intel 6321ESB USB" rev 0x09: apic 8 int 17 uhci2 at pci0 dev 29 function 2 "Intel 6321ESB USB" rev 0x09: apic 8 int 18 uhci3 at pci0 dev 29 function 3 "Intel 6321ESB USB" rev 0x09: apic 8 int 19 ehci0 at pci0 dev 29 function 7 "Intel 6321ESB USB" rev 0x09: apic 8 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb13 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xd9 pci14 at ppb13 bus 1 radeondrm0 at pci14 dev 3 function 0 "ATI ES1000" rev 0x02 drm0 at radeondrm0 radeondrm0: apic 8 int 23 "Compaq iLO"
Re: How to restore vendor-specified MAC address
On Wed, 17 Nov 2021 22:28:50 +0100 Radek wrote: > On Wed, 17 Nov 2021 17:33:25 - (UTC) > Stuart Henderson wrote: > > > On 2021-11-17, Radek wrote: > > > On Wed, 17 Nov 2021 11:22:42 +0100 > > > Denis Fondras wrote: > > > > > >> Le Wed, Nov 17, 2021 at 05:03:42AM +0100, Radek a écrit : > > >> > > > >> > How can I restore the vendor's MAC address? > > >> > It is 6.8/amd64. > > >> > > > >> > > >> Check dmesg, it will give you the original MAC address, then ifconfig > > >> lladdr... > > >> > > > > > > Hello Denis, > > > dmesg shows my new_MAC. > > > I know the value of my original MAC address but I used to think that > > > removing lladdr value from /etc/hostname.if and then reboot restores the > > > original MAC. I doesn't. > > > > How about a power-cycle (rather than just a reboot)? > I'll do it ASAP. I've tested the same thing on another box, 6.9/amd64: PC Engines apu1 coreboot build 20210709 BIOS version v4.14.0.4 SeaBIOS (version rel-1.14.0.1-0-g8610266a) Reboot doesn't reset the MAC address, but power-cycle does. > > > > > > Is there any way to "force" OS to restore original MAC address by reading > > > it from hardware/NIC instead of ifconfig lladdr ...? > > > > That's what it normally does. > > > > If it's somehow stuck on the new one and a power-cycle doesn't clear it then > > presumably using lladdr to reset it to the original will stick (look in old > > boot messages in /var/log/messages.*.gz, dhcp server logs, maybe printed > > on the motherboard, etc) > I have a copy of the original MAC and presumably it's not a problem to > restore it with ifconfig lladdr but I'm trying to find out why > /etc/netstart (and even reboot) doesn't clear it. > > > > > -- > > Please keep replies on the mailing list. > > > > > -- > Radek > -- Radek
Re: Limit Mail Submission to inet4
> On Thu, Nov 18, 2021 at 10:55:00AM +0100, Simon Hoffmann wrote: > > > > > > > > > >GMail still wont accept my IPv6 submitted mails. > > > > > > Are you using ipv6 connectivity over tunnel from tunnelbroker.net? > > > > Nope. My relays have "real" IPv6 /64 networks assigned to their interfaces > > natively. > > > > However, I'd still like to only use IPv4 when sending messages. > > Why? Why not fix the IPv6 issue? Our servers deliver to gmail over IPv6 with > no issues. Hmm, thats interesting. The last time i googled it said that its a known issue with gmail and one should use IPv4. Also, the GMail help and the error message were all to no use. I will try sending via IPv6 later today and report back. If you like, you can lookup DNS recors for mxbackup.hetzner.hoffbox.net Should be correct. PTR has the same name as A/AAAa, A and are present... > > > Suggestions? > > Set a fixed IPv4 source address using the src parameter in the action > directive > of your smtpd.conf. Yeah, thats a good idea, thanks! Will be my fallback if i cant get v6 to work. signature.asc Description: PGP signature
Re: Limit Mail Submission to inet4
On Thu, Nov 18, 2021 at 10:55:00AM +0100, Simon Hoffmann wrote: > > > > > > >GMail still wont accept my IPv6 submitted mails. > > > > Are you using ipv6 connectivity over tunnel from tunnelbroker.net? > > Nope. My relays have "real" IPv6 /64 networks assigned to their interfaces > natively. > > However, I'd still like to only use IPv4 when sending messages. Why? Why not fix the IPv6 issue? Our servers deliver to gmail over IPv6 with no issues. > Suggestions? Set a fixed IPv4 source address using the src parameter in the action directive of your smtpd.conf.
Re: How to check that HT is working and used?
On 2021/11/18 12:58, Dev Op wrote: > When upgrading OpenBSD 7.0/amd64, unfortunately, there is no bsd.mp among the > presented set of > files. Why? :( Although, it is in the image. EM64T (Intel 64) is definitely > supported by Intel > (R) Xeon(R) CPU E5430. There was nothing strange when installing the > distribution kit. I > downloaded install70.iso from https://ftp.yandex.ru/openbsd/7.0/amd64/ and > installed the > proposed set of files. Everything is as usual. > > Server is HP Proliant DL360G5 with one CPU E5430 (4-cores) on it. BIOS was > checked: "All > processor Cores Enabled". It looks like the acpicpu table provided by the machine firmware/bios is not reporting all cores. Suggest updating firmware (the newest for the machine seems to be https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_75580f5b91784d11b58f80d961) Certainly older versions on this machine didn't support quad core cpus. If it still only reports a single core after updating, use sendbug, run as root to include a copy of acpi tables. If mail isn't fully configured on the machine then it is usually simplest to use "sendbug -P > somefile" and copy that to another machine and send it with a normal mail client to b...@openbsd.org. > Here is full dmesg: > OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 4276432896 (4078MB) > avail mem = 4130902016 (3939MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (68 entries) > bios0: vendor HP version "P58" date 07/10/2009 > bios0: HP ProLiant DL360 G5 > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST BERT HEST SSDT > acpi0: wakeup devices PCI0(S5) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (IP2P) > acpiprt2 at acpi0: bus 9 (PT02) > acpiprt3 at acpi0: bus 10 (IPE4) > acpiprt4 at acpi0: bus 11 (IPE1) > acpiprt5 at acpi0: bus 16 (P2P2) > acpiprt6 at acpi0: bus 6 (PT03) > acpiprt7 at acpi0: bus 19 (PT04) > acpiprt8 at acpi0: bus 3 (NB01) > acpiprt9 at acpi0: bus 5 (NB02) > acpipci0 at acpi0 PCI0 > "IPI0001" at acpi0 not configured > "PNP0A06" at acpi0 not configured > acpicpu0 at acpi0: C1(1000@1 halt) > acpitz0 at acpi0: critical temperature is 31 degC > ipmi at mainbus0 not configured > cpu0 at mainbus0: (uniprocessor) > cpu0: Intel(R) Xeon(R) CPU E5430 @ 2.66GHz, 2667.12 MHz, 06-17-06 > 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,LONG,LAHF,PERF,SENSOR,MELTDOWN > cpu0: 6MB 64b/line 16-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 5000P Host" rev 0xb1 > ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0xb1 > pci1 at ppb0 bus 9 > ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 > pci2 at ppb1 bus 10 > ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 > pci3 at ppb2 bus 11 > ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01 > pci4 at ppb3 bus 14 > ppb4 at pci2 dev 2 function 0 "Intel 6321ESB PCIE" rev 0x01 > pci5 at ppb4 bus 15 > ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01 > pci6 at ppb5 bus 16 > ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0xb1 > pci7 at ppb6 bus 6 > ciss0 at pci7 dev 0 function 0 "Hewlett-Packard Smart Array" rev 0x03: irq 5 > ciss0: 1 LD, HW rev 3, FW 6.86/6.86, 64bit fifo > scsibus1 at ciss0: 1 targets > sd0 at scsibus1 targ 0 lun 0: > sd0: 69973MB, 512 bytes/sector, 143305920 sectors > ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE x8" rev 0xb1 > pci8 at ppb7 bus 19 > ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0xb1 > pci9 at ppb8 bus 22 > ppb9 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0xb1 > pci10 at ppb9 bus 2 > ppb10 at pci10 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 > pci11 at ppb10 bus 3 > bnx0 at pci11 dev 0 function 0 "Broadcom BCM5708" rev 0x12: irq 10 > ppb11 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0xb1 > pci12 at ppb11 bus 4 > ppb12 at pci12 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 > pci13 at ppb12 bus 5 > bnx1 at pci13 dev 0 function 0 "Broadcom BCM5708" rev 0x12: irq 10 > pchb1 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0xb1 > pchb2 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0xb1 > pchb3 at pci0 dev 16 function 2 "Intel 5000 Error Reporting" rev 0xb1 > pchb4 at pci0 dev 17 function 0 "Intel 5000 Reserved" rev 0xb1 > pchb5 at pci0 dev 19 function 0 "Intel 5000 Reserved" rev
Re: How to check that HT is working and used?
When upgrading OpenBSD 7.0/amd64, unfortunately, there is no bsd.mp among the presented set of files. Why? :( Although, it is in the image. EM64T (Intel 64) is definitely supported by Intel(R) Xeon(R) CPU E5430. There was nothing strange when installing the distribution kit. I downloaded install70.iso from https://ftp.yandex.ru/openbsd/7.0/amd64/ and installed the proposed set of files. Everything is as usual. Server is HP Proliant DL360G5 with one CPU E5430 (4-cores) on it. BIOS was checked: "All processor Cores Enabled". Here is full dmesg: OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4276432896 (4078MB) avail mem = 4130902016 (3939MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (68 entries) bios0: vendor HP version "P58" date 07/10/2009 bios0: HP ProLiant DL360 G5 acpi0 at bios0: ACPI 3.0 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST BERT HEST SSDT acpi0: wakeup devices PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (IP2P) acpiprt2 at acpi0: bus 9 (PT02) acpiprt3 at acpi0: bus 10 (IPE4) acpiprt4 at acpi0: bus 11 (IPE1) acpiprt5 at acpi0: bus 16 (P2P2) acpiprt6 at acpi0: bus 6 (PT03) acpiprt7 at acpi0: bus 19 (PT04) acpiprt8 at acpi0: bus 3 (NB01) acpiprt9 at acpi0: bus 5 (NB02) acpipci0 at acpi0 PCI0 "IPI0001" at acpi0 not configured "PNP0A06" at acpi0 not configured acpicpu0 at acpi0: C1(1000@1 halt) acpitz0 at acpi0: critical temperature is 31 degC ipmi at mainbus0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Xeon(R) CPU E5430 @ 2.66GHz, 2667.12 MHz, 06-17-06 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,LONG,LAHF,PERF,SENSOR,MELTDOWN cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 5000P Host" rev 0xb1 ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0xb1 pci1 at ppb0 bus 9 ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci2 at ppb1 bus 10 ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci3 at ppb2 bus 11 ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01 pci4 at ppb3 bus 14 ppb4 at pci2 dev 2 function 0 "Intel 6321ESB PCIE" rev 0x01 pci5 at ppb4 bus 15 ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01 pci6 at ppb5 bus 16 ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0xb1 pci7 at ppb6 bus 6 ciss0 at pci7 dev 0 function 0 "Hewlett-Packard Smart Array" rev 0x03: irq 5 ciss0: 1 LD, HW rev 3, FW 6.86/6.86, 64bit fifo scsibus1 at ciss0: 1 targets sd0 at scsibus1 targ 0 lun 0: sd0: 69973MB, 512 bytes/sector, 143305920 sectors ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE x8" rev 0xb1 pci8 at ppb7 bus 19 ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0xb1 pci9 at ppb8 bus 22 ppb9 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0xb1 pci10 at ppb9 bus 2 ppb10 at pci10 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 pci11 at ppb10 bus 3 bnx0 at pci11 dev 0 function 0 "Broadcom BCM5708" rev 0x12: irq 10 ppb11 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0xb1 pci12 at ppb11 bus 4 ppb12 at pci12 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc3 pci13 at ppb12 bus 5 bnx1 at pci13 dev 0 function 0 "Broadcom BCM5708" rev 0x12: irq 10 pchb1 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0xb1 pchb2 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0xb1 pchb3 at pci0 dev 16 function 2 "Intel 5000 Error Reporting" rev 0xb1 pchb4 at pci0 dev 17 function 0 "Intel 5000 Reserved" rev 0xb1 pchb5 at pci0 dev 19 function 0 "Intel 5000 Reserved" rev 0xb1 pchb6 at pci0 dev 21 function 0 "Intel 5000 FBD" rev 0xb1 pchb7 at pci0 dev 22 function 0 "Intel 5000 FBD" rev 0xb1 uhci0 at pci0 dev 29 function 0 "Intel 6321ESB USB" rev 0x09: irq 5 uhci1 at pci0 dev 29 function 1 "Intel 6321ESB USB" rev 0x09: irq 7 uhci2 at pci0 dev 29 function 2 "Intel 6321ESB USB" rev 0x09: irq 10 uhci3 at pci0 dev 29 function 3 "Intel 6321ESB USB" rev 0x09: irq 10 ehci0 at pci0 dev 29 function 7 "Intel 6321ESB USB" rev 0x09: irq 5 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb13 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xd9 pci14 at ppb13 bus 1 radeondrm0 at pci14 dev 3 function 0 "ATI ES1000" rev 0x02 drm0 at radeondrm0 radeondrm0: irq 7 "Compaq iLO" rev 0x03 at pci14 dev 4 function 0 not configured "Compaq iLO" rev 0x03 at pci14 dev 4 function 2
Re: Limit Mail Submission to inet4
> > > >GMail still wont accept my IPv6 submitted mails. > > Hi, > > Are you using ipv6 connectivity over tunnel from tunnelbroker.net? Nope. My relays have "real" IPv6 /64 networks assigned to their interfaces natively. However, I'd still like to only use IPv4 when sending messages. Suggestions? Thanks! Simon signature.asc Description: PGP signature
Re: Limit Mail Submission to inet4
>GMail still wont accept my IPv6 submitted mails. Hi, Are you using ipv6 connectivity over tunnel from tunnelbroker.net? They block port 25 (in both ways IIRC) due to some people using it to send spam, so you have to reach sage level on their ipv6 knowledge test and then email them asking to unblock it. Kind regards -- Łukasz Moskała
Limit Mail Submission to inet4
Hey, the earlier versions of opensmtpd (with the old config file syntax: accept from...) had the option to specify limit mta inet4 domain.com (from memory), or limit mta inet4 in general, to limit everything to IPv4. With the newer versions (I'm running 6.8.0) this seems no longer possible? What was the reason to remove this? GMail still wont accept my IPv6 submitted mails. Or am I just blind? :) Thanks! Simon signature.asc Description: PGP signature
