Услуги по регистрации физических лиц-предпринимателей
Ëèêâèäèðîâàíèå ïðåäïðèÿòèé âñåõ ôîðì ñîáñòâåííîñòè âî âñåõ ðåãèîíàõ Óêðàèíû · Óñëóãè ïî ïðåêðàùåíèþ äåÿòåëüíîñòè ïðåäïðèÿòèé · Óñëóãè ïî óñêîðåííîé ëèêâèäàöèè · Ïðåêðàùåíèå äåÿòåëüíîñòè ïðåäïðèÿòèé ïóòåì âûêóïà (îò 6000 ãðí) Óñëóãè ïî ðåãèñòðàöèè íîâîãî ïðåäïðèÿòèÿ ñ îôîðìëåíèåì ñâèäåòåëüñòâà ïëàòåëüùèêà ÍÄÑ · Óñëóãè ïî ñîçäàíèþ íîâîãî þðèäè÷åñêîãî ëèöà ÎÎÎ, ×Ï, ×ÀÎ, ÏÀÎ ñ îôîðìëåíèåì ñâèäåòåëüñòâà ïëàòåëüùèêà ÍÄÑ · Óñëóãè ïî ðåãèñòðàöèè ôèçè÷åñêèõ ëèö-ïðåäïðèíèìàòåëåé Íàøè êîíòàêòû: 0 44 219 11 74 Êèåâ Êèåâñòàð0 98 846 76 54 0 56 372 83 87 Äíåïðîïåòðîâñê 0 48 730 53 80 Îäåññà ÌÒÑ0 99 214 26 60 0 62 332 35 58 Äîíåöê ÌÒÑ0 99 362 50 57 Ïðåäîñòàâèì ïîëíóþ è áåñïëàòíóþ êîíñóëüòàöèþ ïî êàæäîìó èç âàðèàíòîâ.
Ports security updates in 5.1 or 5.2
Hi, I currently follow STABLE branch for openbsd (and so, for ports too), which is OPENBSD_5_1. But, I saw that the last security updates for ports go to OPENBSD_5_2 and not to OPENBSD_5_1. According to the FAQ (http://www.openbsd.org/faq/faq15.html#PortsSecurity), only the current and last release are updated. But the current release is OPENBSD_5_1 (see http://www.openbsd.org/). Should I expect security updates will arrived somedays to OPENBSD_5_1 ? (but I doubt) Should I switch to OPENBSD_5_2 (for base and ports) ? And if yes, should I fetch + build from source, like doing old-stable to stable update (and build from source all my ports) ? Thanks. -- Sebastien Marie
High RTT/Latency pings post 5.0
Hi Misc@, Did anyone experience a high latency pings on em(4) interface post 5.0? We have several machines on i386 -current with em(4) experiencing high latency/RTT pings, and its really bothering our clients. Then we moved the traffic/vlan to sk(4) interface and pings goes to the expected behavior (compared to switch to switch ICMP pings). We applied altq bw management for ICMP, and we tried to remove the bandwidth management before switching to sk(4), but still no change on pings RTT. OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 23 16:25:52 WIT 2012 r...@border-rf.x.net:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error ffixed_disk,invalid_time cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu0: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF real mem = 2142711808 (2043MB) avail mem = 2096783360 (1999MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @ 0x7fbe4000 (43 entries) bios0: vendor Intel Corporation version S3000.86B.02.00.0054.061120091710 date 06/11/2009 bios0: Intel S3000AH acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT SSDT HEST BERT ERST EINJ acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4) UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu1: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu2: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu3: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 5 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus -1 (PEX2) acpiprt5 at acpi0: bus -1 (PEX3) acpiprt6 at acpi0: bus 2 (PEX4) acpiprt7 at acpi0: bus 3 (PEX5) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpicpu2 at acpi0: PSS acpicpu3 at acpi0: PSS acpibtn0 at acpi0: SLPB bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1800 0xcb800/0x1000 cpu0: Enhanced SpeedStep 2401 MHz: speeds: 2394, 1596 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel E7230 Host rev 0x00 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 5 int 17 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 5 int 17 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:fc em1 at pci2 dev 0 function 1 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 17, address 00:15:17:86:52:fd ppb2 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01: apic 5 int 16 pci3 at ppb2 bus 3 em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:49:04:0d Intel 82573E Serial rev 0x03 at pci3 dev 0 function 3 not configured Intel 82573E KCS rev 0x03 at pci3 dev 0 function 4 not configured uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 5 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 5 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 5 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 5 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 5 int 23 ehci0: timed out waiting for BIOS usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci4 at ppb3 bus 4 skc0 at pci4 dev 0 function 0 D-Link DGE-530T B1 rev 0x11, Yukon Lite (0x9): apic 5 int 21 sk0 at skc0 port A: address 00:1c:f0:11:6c:d4 eephy0 at sk0 phy 0: 88E1011 Gigabit PHY, rev. 5 em3 at
Re: More sensible and consistent rc.conf.local
I'm just thinking that from a layman's perspective named_flags= doesn't make as much sense as named=YES if all you want to do is start named. The way it is right now seems more like monkey patching from the days before OpenBSD became popular. I acknowledge the whole it's been like this for ages, but it's 2012 - it's time to make some power moves. If OpenBSD was on Git / at GitHub, youngins like me would have patched this baby up a long time ago. Mikkel 2012/8/29 Stuart Henderson s...@spacehopper.org: On 2012-08-25, Mikkel Bang facebookman...@gmail.com wrote: Hello! Is there a way to make my rc.conf.local more sensible and consistent, i.e. not pf=YES sshd= named_flags= but rather pf=YES sshd=YES named=YES? How about something like this? # system options pf=YES # daemons sshd_flags= named_flags=
setting WOL for Realtek 8168
While I can set wol for this interface, the setting does not survive shutdown. I have found no bios settings that seem to pertain. This system is not dual-boot. Is this a quirk of the 8168? Do I need to look for jumpers? ;-) -- Edward Ahlsen-Girard Ft Walton Beach, FL OpenBSD 5.2-current (GENERIC.MP) #3: Fri Aug 24 14:18:41 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2110259200 (2012MB) avail mem = 2031722496 (1937MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf06d0 (43 entries) bios0: vendor American Megatrends Inc. version 0504 date 10/05/2009 bios0: ASUSTeK Computer INC. P-P5G41 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SSDT acpi0: wakeup devices P0P2(S4) P0P3(S4) P0P1(S4) UAR1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) EUSB(S4) MC97(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933.62 MHz 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,SSE4.1,XSAVE,NXE,LONG,LAHF cpu0: 3MB 64b/line 8-way L2 cache cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933.30 MHz 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF cpu1: 3MB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus -1 (P0P3) acpiprt3 at acpi0: bus 2 (P0P4) acpiprt4 at acpi0: bus -1 (P0P5) acpiprt5 at acpi0: bus 1 (P0P6) acpiprt6 at acpi0: bus -1 (P0P7) acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS aibs0 at acpi0: RTMP RVLT RFAN GGRP GITM SITM aibs0: FSIF: invalid package acpibtn0 at acpi0: PWRB cpu0: Enhanced SpeedStep 2933 MHz: speeds: 2936, 2670, 2403, 2136, 1870, 1603 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel G41 Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel G41 Video rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 Intel G41 Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: msi azalia0: codecs: Realtek ALC888 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: msi pci2 at ppb1 bus 1 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x02: RTL8168C/8111C (0x3c00), apic 2 int 18, address 48:5b:39:c5:63:95 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci3 at ppb2 bus 3 pcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide1: using apic 2 int 19 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: SAMSUNG HM641JI wd0: 16-sector PIO, LBA48, 610480MB, 1250263728 sectors atapiscsi0 at pciide1 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, DV-W524GS, BT11 ATAPI 5/cdrom removable wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6 cd0(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: apic 2 int 19 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 spdmem1 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-5300CL5 usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision
Re: setting WOL for Realtek 8168
On 08/29/12 06:56, Ed Ahlsen-Girard wrote: While I can set wol for this interface, the setting does not survive shutdown. I have found no bios settings that seem to pertain. This system is not dual-boot. Is this a quirk of the 8168? Do I need to look for jumpers? As far as I can tell from my attempts on setting WOL on linux the NIC driver resets the WOL flag on system start I think I saw the same in the OBSD code. windows drivers also do the same, so I am guessing it's normal. just reactivate the WOL flag in rc.local. finally even though it did not work out for me. ( my nics were nfe(4) which has no WOL bits in OBSD, I blame nvidia, those secretive assholes.) I do love the ifconfig based wol syntax, miles ahead of the linux bullshit
Re: High RTT/Latency pings post 5.0
Hi Misc@, I had to add that the corresponding em(4) are (on all machines); em4 at pci4 dev 5 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 5 int 17, address 00:15:17:49:04:0e em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:25:0a:9d em1 at pci1 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:94 Thanks, Insan Praja On Wed, 29 Aug 2012 16:35:38 +0700, Insan Praja SW insan.pr...@gmail.com wrote: Hi Misc@, Did anyone experience a high latency pings on em(4) interface post 5.0? We have several machines on i386 -current with em(4) experiencing high latency/RTT pings, and its really bothering our clients. Then we moved the traffic/vlan to sk(4) interface and pings goes to the expected behavior (compared to switch to switch ICMP pings). We applied altq bw management for ICMP, and we tried to remove the bandwidth management before switching to sk(4), but still no change on pings RTT. OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 23 16:25:52 WIT 2012 r...@border-rf.x.net:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error ffixed_disk,invalid_time cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu0: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF real mem = 2142711808 (2043MB) avail mem = 2096783360 (1999MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @ 0x7fbe4000 (43 entries) bios0: vendor Intel Corporation version S3000.86B.02.00.0054.061120091710 date 06/11/2009 bios0: Intel S3000AH acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT SSDT HEST BERT ERST EINJ acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4) UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu1: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu2: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu3: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 5 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus -1 (PEX2) acpiprt5 at acpi0: bus -1 (PEX3) acpiprt6 at acpi0: bus 2 (PEX4) acpiprt7 at acpi0: bus 3 (PEX5) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpicpu2 at acpi0: PSS acpicpu3 at acpi0: PSS acpibtn0 at acpi0: SLPB bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1800 0xcb800/0x1000 cpu0: Enhanced SpeedStep 2401 MHz: speeds: 2394, 1596 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel E7230 Host rev 0x00 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 5 int 17 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 5 int 17 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:fc em1 at pci2 dev 0 function 1 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 17, address 00:15:17:86:52:fd ppb2 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01: apic 5 int 16 pci3 at ppb2 bus 3 em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:49:04:0d Intel 82573E Serial rev 0x03 at pci3 dev 0 function 3 not configured Intel 82573E KCS rev 0x03 at pci3 dev 0 function 4 not configured uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 5 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 5 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 5 int 18 uhci3 at pci0 dev 29 function
Re: More sensible and consistent rc.conf.local
Mikkel Bang wrote: I'm just thinking that from a layman's perspective named_flags= doesn't make as much sense as named=YES if all you want to do is start named. The way it is right now seems more like monkey patching from the days before OpenBSD became popular. I acknowledge the whole it's been like this for ages, but it's 2012 - it's time to make some power moves. If OpenBSD was on Git / at GitHub, youngins like me would have patched this baby up a long time ago. Mikkel named_flags=NO gives ONE way of NOT starting named. Why should there only be ONE way to start named? Power Moves is to limit named to NO command line parameters???
Re: More sensible and consistent rc.conf.local
Le 2012-08-29 09:57, Mikkel Bang a écrit : If OpenBSD was on Git / at GitHub, youngins like me would have patched this baby up a long time ago. Sadly, a good argument against moving to Git. Simon
Re: More sensible and consistent rc.conf.local
On Wed, Aug 29, 2012 at 9:57 AM, Mikkel Bang facebookman...@gmail.com wrote: I'm just thinking that from a layman's perspective named_flags= doesn't make as much sense as named=YES if all you want to do is start named. The way it is right now seems more like monkey patching from the days before OpenBSD became popular. I acknowledge the whole it's been like this for ages, but it's 2012 - it's time to make some power moves. If OpenBSD was on Git / at GitHub, youngins like me would have patched this baby up a long time ago. I believe you can still submit patches even if it's not on Git... And I believe if OpenBSD was at GitHub, you will still need approvals before it can be part of the main tree. So what's stopping you...?
Re: More sensible and consistent rc.conf.local
On 2012 Aug 29 (Wed) at 15:57:09 +0200 (+0200), Mikkel Bang wrote: :If OpenBSD was on Git / at GitHub, youngins like me would have patched :this baby up a long time ago. 1) Here's a nickle, go learn to use cvs. 2) We'd reject the patch anyways. -- Stop searching. Happiness is right next to you.
Re: More sensible and consistent rc.conf.local
On Wed, Aug 29, 2012 at 11:22:38AM -0400, Simon Perreault wrote: Le 2012-08-29 09:57, Mikkel Bang a ?crit : If OpenBSD was on Git / at GitHub, youngins like me would have patched this baby up a long time ago. Sadly, a good argument against moving to Git. Simon Whatcha 'git agit gitting over to Git? Ya git sumthin gitty in ur git-along? :)
Re: one keydisk to access multiple encrypted systems
On Sat, Aug 25, 2012 at 05:08:31PM +0200, Erling Westenvik wrote: On Sat, Aug 25, 2012 at 07:03:42AM -0600, Aaron wrote: It is possible if you use different partitions on the same drive, however, you would have to run -P twice ( once for each volume ). Sorry for not mentioning that I'm aware about the possibility of having several mini partitions on the key disk, one for each encrypted machine. Also, the -P switch in bioctl(4) has nothing to do with the creation of a key disk since the passphrase is generated automatically when invoking # bioctl -C force -c C -l /dev/wd0d -k /dev/sd0d softraid0 What I'm looking for is a way to have only one key disk partition for multiple machines. (Perhaps also a way to manually specify a passphrase in case of a lost/forgotten key disk, or a way to create a new key disk in case of a corrupted image. But I may be way out on this one..) There is no (easy) way of doing either of these things currently. Your best option would be to create multiple partitions and have a keydisk for each crypto volume, but on the same USB key/memory card.
net.inet.ip.ifq.maxlen was WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost
How much can I increase net.inet.ip.ifq.maxlen ? I'm now at 2048 and still seeing increase in net.inet.ip.ifq.drops. This morning, it was at 21280 and now at 21328. I've change the système for a temporary more powerfull one (core 2 quad + 2 dual 82571EB) while I'm commanding and building new server and now the congestion have dropped from 3.9 to 0.8. Something I must specify, I use bi-nat to save public ip address and have thousand of bi-nat rule divided in some anchors. Thanks Michel Le 2012-08-19 08:21, Stuart Henderson a écrit : On 2012-08-14, Michel Blais mic...@targointernet.com wrote: I maybe found something, congestion seem high when I check with pftcl -si. I don't think it's hardware related since CPU is under 50% use. I saw this tread where Henning suggest to raise net.inet.ip.ifq.maxlen so I raided it to 512 instead of 256. http://old.nabble.com/PF-congestion-question-td7088168.html It's a old thread so I wanted to know if it's still a good idea to raise this sysctl value. If you are seeing increases in net.inet.ip.ifq.drops, then yes it usually is a good idea to increase the queue length.
Re: More sensible and consistent rc.conf.local
On Aug 29, 2012, at 6:57, Mikkel Bang facebookman...@gmail.com wrote: I'm just thinking that from a layman's perspective named_flags= doesn't make as much sense as named=YES if all you want to do is start named. I can't tell if you're trolling or not. Seriously, tho: is uninformed beginners would think it should be like X how you think highly sophisticated technical projects should be designed? Just saying. Ben :wq
Como Manejar con Exito Actos Publicos en Panama
Cómo Manejar con Éxito Actos Públicos en Panamá Panama 05 de Septiembre, 2012 SHERATON PANAMA HOTEL CONVENTION CENTER El curso más completo para conocer y actualizarse en los procesos y reglamentos de ADQUISICIONES DE BIENES Y SERVICIOS en las Instituciones del Estado! Este interesante curso es para todo tipo de empresas que participan---o quieren participar en actos públicos con el Gobierno de PANAMÁ, aquí conocerá las regulaciones que rigen las COMPRAS en Panamá y su impacto con la Ley 22 de Junio de 2006 y sus nuevas adecuaciones. ¡Obtenga las herramientas para ser un Licitante y Proveedor Ganador del Gobierno en Panamá!, Incluyendo: - Lo que usted debe saber para hacer bien su trabajo y no tener problemas con la autoridad - Entendimiento claro y preciso de las diferentes opciones que las empresas privadas pueden venderle al Gobierno, así como sus alcances y compromisos para ambas partes - Manejo adecuado de los procesos de COMPRAS GUBERNAMENTALES - Cómo preparar propuestas solventes y ganar contratos en las Entidades del Estado - Cuáles son los puntos críticos para evitar que sus propuestas sean desechadas - Cuándo es procedente la inconformidad y cuando es conveniente llevarla a cabo - Modelos y formalización de contratos con el Gobierno - 20 prácticos consejos para convertir al Gobierno en su mejor cliente Reciba en este momento el folleto completo! Únicamente responda con su Nombre, Puesto, Empresa y Teléfono, o Comuníquese al (507) 279-1083 / 279-0258 / 279-0887 Reciba un muy cordial saludo! Para des suscribirse de estas invitaciones, solo responda este correo con el asunto noinvitar y automáticamente quedará fuera de nuestras listas. Este correo ha sido enviado a: misc@openbsd.org
Procesos Clave para Solventar Observaciones
copy; 2012 Conference Corporativo S.C. Asista a los 44 Mejores Cursos en Meacute;xico de la Serie: ADQUISICIONES Y OBRAS PUacute;BLICAS Incluye Temas Criacute;ticos Sobre: Cierre de Gestioacute;n, Observaciones y Responsabilidades Cursos, Contenidos y Metodologiacute;as Desarrollados en Alianza con las Mejores Universidades Europeas con Calidad ISO 9000. Haga click para desplegar informacioacute;n Curso 1 Coacute;mo Solventar Observaciones. (Poliacute;tica Cero Pendientes y Responsabilidades) Curso 2 Libro Blanco y las Memorias Documentales del Sector Puacute;blico Mexicano. (NUEVO) Curso 3 Elaboracioacute;n Puntual de las Memorias Documentales. (NUEVO) Curso 4 Acta de Entrega Recepcioacute;n y Rendicioacute;n de Cuentas. (NUEVO) Curso 5 Servicio Profesional de Carrera. Curso 6 (Nueva)Investigacioacute;n de Mercados y los Criterios de Evaluacioacute;n para Adquisiciones. Curso 7 (Nueva)Ley Federal Anticorrupcioacute;n. Curso 8 COMPRANET 5.0 (Licitaciones Electroacute;nicas de las Adquisiciones).
Re: one keydisk to access multiple encrypted systems
On Thu, Aug 30, 2012 at 02:31:53AM +1000, Joel Sing wrote: On Sat, Aug 25, 2012 at 05:08:31PM +0200, Erling Westenvik wrote: On Sat, Aug 25, 2012 at 07:03:42AM -0600, Aaron wrote: It is possible if you use different partitions on the same drive, however, you would have to run -P twice ( once for each volume ). Sorry for not mentioning that I'm aware about the possibility of having several mini partitions on the key disk, one for each encrypted machine. Also, the -P switch in bioctl(4) has nothing to do with the creation of a key disk since the passphrase is generated automatically when invoking # bioctl -C force -c C -l /dev/wd0d -k /dev/sd0d softraid0 What I'm looking for is a way to have only one key disk partition for multiple machines. (Perhaps also a way to manually specify a passphrase in case of a lost/forgotten key disk, or a way to create a new key disk in case of a corrupted image. But I may be way out on this one..) There is no (easy) way of doing either of these things currently. Your best option would be to create multiple partitions and have a keydisk for each crypto volume, but on the same USB key/memory card. Ok. Thank you, guys. I'll settle with that, feeling confident that functionality like this surely must exist on the sketchboard and will become features as projects develop. Reminder to self: start donating!
Re: Ports security updates in 5.1 or 5.2
Le Wed, 29 Aug 2012 09:59:46 +0200, Sebastien Marie semarie-open...@latrappe.fr a écrit : Hello, I currently follow STABLE branch for openbsd (and so, for ports too), which is OPENBSD_5_1. But, I saw that the last security updates for ports go to OPENBSD_5_2 and not to OPENBSD_5_1. Any examples ? The probleme may not be present in 5.1. According to the FAQ (http://www.openbsd.org/faq/faq15.html#PortsSecurity), only the current and last release are updated. But the current release is OPENBSD_5_1 (see http://www.openbsd.org/). Should I expect security updates will arrived somedays to OPENBSD_5_1 ? (but I doubt) Yes you can expect it, see the commits on 5.1 ports: http://www.freshbsd.org/search?project=openbsd-portsbranch=OPENBSD_5_1 Regards.
smtpd queue encryotion (was: Re: CVS: cvs.openbsd.org: src)
Over on source-changes, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote: I don't disagree with using AES-128 as default on a possibly busy mail server. I was just wondering why the word obsolete was used and if it was simply because twofish and AES are faster. Blowfish is older, not standardized, and hasn't received the attention from the cryptographic community that AES has. Blowfish was interesting back when 3DES was the standard, but everybody has moved on. Speedwise, Blowfish and AES are similar, but AES is more the focus of optimized implementations and can benefit from AES-NI hardware acceleration. -- Christian naddy Weisgerber na...@mips.inka.de
Re: smtpd queue encryotion
Christian Weisgerber wrote: Over on source-changes, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote: I don't disagree with using AES-128 as default on a possibly busy mail server. I was just wondering why the word obsolete was used and if it was simply because twofish and AES are faster. (careful, you trimmed out where he mentioned blowfish, and I was thinking you misread it, since you left in him mentioning twofish...) Blowfish is older, not standardized, and hasn't received the attention from the cryptographic community that AES has. Blowfish was interesting back when 3DES was the standard, but everybody has moved on. Blowfish isn't standardized? Not being chosen as a standard doesn't mean that everyone is using an incompatible version of something. Have I been missing all the rogue versions of blowfish encryption all this time? And I'm fairly certain blowfish did get a lot of attention. And since bcrypt is reasonably popular, I'd imagine blowfish *still* gets attention from the cryptographic community. And AES-128 (and only that flavor of AES, so far) has a crack making decrypting it significantly quicker. And I don't see any cracks of the full-round version of blowfish used. Speedwise, Blowfish and AES are similar, but AES is more the focus of optimized implementations and can benefit from AES-NI hardware acceleration. My understanding is that actually, blowfish is significantly slower. Mainly because of the setup required for each new key. I seem to recall that was part of why blowfish didn't become AES. --Kurt
Re: High RTT/Latency pings post 5.0
I have both latency and paquet drop problem on 5.1 on card using em(4). Tryed both 82571EB and 82546GB. It was worst with 82546GB. Mailing list subject : WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost net.inet.ip.ifq.maxlen was WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost. I only writed about paquet lost since I think both are related. Maybe it's related. If I test from my lan or from my DMZ up to our ISPs (fiber link not overload) gateways (tryed both gateway), I see latency up to over 50 ms with most between 1 and 2 ms and sometime, paquets lost. Real time communication like VoIP are affected by this. Le 2012-08-29 10:59, Insan Praja SW a écrit : Hi Misc@, I had to add that the corresponding em(4) are (on all machines); em4 at pci4 dev 5 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 5 int 17, address 00:15:17:49:04:0e em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:25:0a:9d em1 at pci1 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:94 Thanks, Insan Praja On Wed, 29 Aug 2012 16:35:38 +0700, Insan Praja SW insan.pr...@gmail.com wrote: Hi Misc@, Did anyone experience a high latency pings on em(4) interface post 5.0? We have several machines on i386 -current with em(4) experiencing high latency/RTT pings, and its really bothering our clients. Then we moved the traffic/vlan to sk(4) interface and pings goes to the expected behavior (compared to switch to switch ICMP pings). We applied altq bw management for ICMP, and we tried to remove the bandwidth management before switching to sk(4), but still no change on pings RTT. OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 23 16:25:52 WIT 2012 r...@border-rf.x.net:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error ffixed_disk,invalid_time cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu0: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF real mem = 2142711808 (2043MB) avail mem = 2096783360 (1999MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @ 0x7fbe4000 (43 entries) bios0: vendor Intel Corporation version S3000.86B.02.00.0054.061120091710 date 06/11/2009 bios0: Intel S3000AH acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT SSDT HEST BERT ERST EINJ acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4) UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu1: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu2: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu3: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 5 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus -1 (PEX2) acpiprt5 at acpi0: bus -1 (PEX3) acpiprt6 at acpi0: bus 2 (PEX4) acpiprt7 at acpi0: bus 3 (PEX5) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpicpu2 at acpi0: PSS acpicpu3 at acpi0: PSS acpibtn0 at acpi0: SLPB bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1800 0xcb800/0x1000 cpu0: Enhanced SpeedStep 2401 MHz: speeds: 2394, 1596 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel E7230 Host rev 0x00 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 5 int 17 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 5 int 17 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address
Re: High RTT/Latency pings post 5.0
Oups, sorry. It's OpenBSD 5.0, not 5.1. Le 2012-08-29 17:05, Michel Blais a écrit : I have both latency and paquet drop problem on 5.1 on card using em(4). Tryed both 82571EB and 82546GB. It was worst with 82546GB. Mailing list subject : WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost net.inet.ip.ifq.maxlen was WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost. I only writed about paquet lost since I think both are related. Maybe it's related. If I test from my lan or from my DMZ up to our ISPs (fiber link not overload) gateways (tryed both gateway), I see latency up to over 50 ms with most between 1 and 2 ms and sometime, paquets lost. Real time communication like VoIP are affected by this. Le 2012-08-29 10:59, Insan Praja SW a écrit : Hi Misc@, I had to add that the corresponding em(4) are (on all machines); em4 at pci4 dev 5 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 5 int 17, address 00:15:17:49:04:0e em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:25:0a:9d em1 at pci1 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:94 Thanks, Insan Praja On Wed, 29 Aug 2012 16:35:38 +0700, Insan Praja SW insan.pr...@gmail.com wrote: Hi Misc@, Did anyone experience a high latency pings on em(4) interface post 5.0? We have several machines on i386 -current with em(4) experiencing high latency/RTT pings, and its really bothering our clients. Then we moved the traffic/vlan to sk(4) interface and pings goes to the expected behavior (compared to switch to switch ICMP pings). We applied altq bw management for ICMP, and we tried to remove the bandwidth management before switching to sk(4), but still no change on pings RTT. OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 23 16:25:52 WIT 2012 r...@border-rf.x.net:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error ffixed_disk,invalid_time cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu0: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF real mem = 2142711808 (2043MB) avail mem = 2096783360 (1999MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @ 0x7fbe4000 (43 entries) bios0: vendor Intel Corporation version S3000.86B.02.00.0054.061120091710 date 06/11/2009 bios0: Intel S3000AH acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT SSDT HEST BERT ERST EINJ acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4) UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu1: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu2: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu3: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 5 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus -1 (PEX2) acpiprt5 at acpi0: bus -1 (PEX3) acpiprt6 at acpi0: bus 2 (PEX4) acpiprt7 at acpi0: bus 3 (PEX5) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpicpu2 at acpi0: PSS acpicpu3 at acpi0: PSS acpibtn0 at acpi0: SLPB bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1800 0xcb800/0x1000 cpu0: Enhanced SpeedStep 2401 MHz: speeds: 2394, 1596 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel E7230 Host rev 0x00 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 5 int 17 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 5 int 17 pci2 at ppb1 bus 2 em0 at pci2 dev 0
Re: High RTT/Latency pings post 5.0
To prevent lockup situations with full send queues when further interrupts fail to appear, the em(4) http://www.openbsd.org/cgi-bin/man.cgi?query=emmanpath=OpenBSD%20Currentsektion=4format=html driver's start routine is triggered after the link status has been updated. No longer attempt to enable MSI on 82571/82572 em(4) http://www.openbsd.org/cgi-bin/man.cgi?query=emmanpath=OpenBSD%20Currentsektion=4format=html Gigabit ethernet controllers (to workaround Byte Enables 2 and 3 Are Not Set hardware bug). Source : http://www.openbsd.org/plus52.html Are those related ? Le 2012-08-29 17:08, Michel Blais a écrit : Oups, sorry. It's OpenBSD 5.0, not 5.1. Le 2012-08-29 17:05, Michel Blais a écrit : I have both latency and paquet drop problem on 5.1 on card using em(4). Tryed both 82571EB and 82546GB. It was worst with 82546GB. Mailing list subject : WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost net.inet.ip.ifq.maxlen was WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost. I only writed about paquet lost since I think both are related. Maybe it's related. If I test from my lan or from my DMZ up to our ISPs (fiber link not overload) gateways (tryed both gateway), I see latency up to over 50 ms with most between 1 and 2 ms and sometime, paquets lost. Real time communication like VoIP are affected by this. Le 2012-08-29 10:59, Insan Praja SW a écrit : Hi Misc@, I had to add that the corresponding em(4) are (on all machines); em4 at pci4 dev 5 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 5 int 17, address 00:15:17:49:04:0e em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573E) rev 0x03: msi, address 00:15:17:25:0a:9d em1 at pci1 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 0x06: apic 5 int 16, address 00:15:17:86:52:94 Thanks, Insan Praja On Wed, 29 Aug 2012 16:35:38 +0700, Insan Praja SW insan.pr...@gmail.com wrote: Hi Misc@, Did anyone experience a high latency pings on em(4) interface post 5.0? We have several machines on i386 -current with em(4) experiencing high latency/RTT pings, and its really bothering our clients. Then we moved the traffic/vlan to sk(4) interface and pings goes to the expected behavior (compared to switch to switch ICMP pings). We applied altq bw management for ICMP, and we tried to remove the bandwidth management before switching to sk(4), but still no change on pings RTT. OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 23 16:25:52 WIT 2012 r...@border-rf.x.net:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error ffixed_disk,invalid_time cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu0: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF real mem = 2142711808 (2043MB) avail mem = 2096783360 (1999MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @ 0x7fbe4000 (43 entries) bios0: vendor Intel Corporation version S3000.86B.02.00.0054.061120091710 date 06/11/2009 bios0: Intel S3000AH acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT SSDT HEST BERT ERST EINJ acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4) UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu1: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu2: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (GenuineIntel 686-class) 2.41 GHz cpu3: FPU,V86,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,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 5 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1)
boot panic with qemu, -current guest on a Linux host
Hi!
I'm just curious if this is something that could get fixed (or maybe
danced around):
@linux $ qemu-kvm -enable-kvm -cpu host -smp 2 -m 512 \
-hda openbsd-current.img \
-net nic,model=e1000,macaddr=52:54:00:12:34:56 \
-net tap,ifname=tap0,script=no,downscript=no -curses
iPXE v1.0.0-591-g7aee315
iPXE (http://ipxe.org) 00:03.0 C900 PCI2.10 PnP PMM+1FFC82A0+1FF882A0 C900
Booting from Hard Disk...
Using drive 0, partition 3.
Loading...
probing: pc0 com0 apm pci mem[637K 510M a20=on]
disk: hd0+
OpenBSD/i386 BOOT 3.18
boot
booting hd0a:/bsd: 8354720+1102340 [52+376992+363706]=0x9b9ca8
entry point at 0x200120
[ using 741124 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org
OpenBSD 5.2-current (GENERIC.MP) #6: Mon Aug 27 20:40:45 MDT 2012
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: AMD Phenom(tm) II X4 B50 Processor (AuthenticAMD 686-class, 512KB L2 cac
he) 3.11 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,FFXSR,3DNOW2,3DNOW,SSE3,CX16,POPCNT,LAHF,CMPLEG,
SVM,AMCR8,ABM,SSE4A,MASSE,3DNOWP
real mem = 536395776 (511MB)
avail mem = 516698112 (492MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/23/99, BIOS32 rev. 0 @ 0xff046, SMBIOS
rev. 2.4 @ 0xfd900 (11 entries)
bios0: vendor Bochs version Bochs date 01/01/2007
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
kernel: protection fault trap, code=0
Stopped at viac3_rnd+0x9f: rdmsr
viac3_rnd(d0b025a0,d09e3268,d08f384b,3,4) at viac3_rnd+0x9f
amd64_errata(d0b025a0,d0b025a0,d0f8,d078eb77,d0b025a0) at amd64_errata+0xb9
cpu_init(d0b025a0,0,2000,0,d0bbbc04) at cpu_init+0x19
cpu_attach(d164bfc0,d155e400,d0bbbc4c,d03ee29b,d078de30) at cpu_attach+0x297
config_attach(d164bfc0,d09d45c0,d0bbbc4c,d078cb20,800,0,0,d08f3129,0,1,d09f21c0
,100f42,78bfbff) at config_attach+0x1bb
mpbios_cpu(f51a5a9c,d16737c0,2,1,2) at mpbios_cpu+0x85
mpbios_scan(d16737c0,d16737c0,d0bbbd60,d03ee29b,0) at mpbios_scan+0x2dc
config_attach(d164bf80,d09d45a0,d0bbbd60,d0789d30,b) at config_attach+0x1bb
biosattach(d164bfc0,d164bf80,d0bbbe58,d03ee29b,0) at biosattach+0x517
config_attach(d164bfc0,d09d4560,d0bbbe58,d05afb60,3000) at config_attach+0x
1bb
ddb{0}
The host has an AMD Phenom(tm) II X4 B50 Processor.
The guest OpenBSD tries to boot a -current bsd.mp. This works with other
cpu types specified (like kvm32, or qemu32...), I just wanted to try out
if the guest would be faster with the 'phenom' or 'host' cpu type.
Has anyone experimented with this kind of or similar setup?
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Votre Facture SFR N�: 53314961NK
SFR Chèr(e) Client, SFR Neufbox Nous avons constater que le règlement de la facture mentionnée ci-dessus a été rejété par votre banque pour le motif suivant : Réfus : Transaction Non Permise Au Porteur. Nous vous invitons à verifier dès aujourd'hui auprès de votre banque la bonne prise en compte de votre autorisation de prélèvement pour vos prochains règlements. Nous vous informons que votre mode de paiement a été modifié en TIP / CHEQUE. Dès régularisation, votre mode de paiement habituel sera retabli. Sachez que vous pouvez effectuer le paiement de votre facture par carte bancaire en toute sécurite. Afin de continuer à profiter de l'ensemble de vos services, effectuez votre paiement dès aujourd'hui. Sans règlement de votre part, conformément aux conditions générales dinscription, nous nous réservons le droit de restreindre ou suspendre vos services. Nous vous invitons à cliquer ici pour la régler Nous vous prions d'agréer, Chèr(e) Client, l'expression de nos salutations distinguées. Pour plus d'informations, vous pouvez consulter notre site officiel sfr.fr Très cordialement, [IMAGE] Dominique REMOND Directeur Service Client * Important: SFR - Service Client neufbox et fixe, TSA 94 065, 77214 Avon Cedex. Nous vous informons que, pour les forfaits et options tarifaires, les factures sont payables d'avance. Les communications passées, sans forfait, au delà du forfait ou non comprises dans le forfait, sont à régler à terme échu. Les factures sont payées par prélèvement automatique, TIP ou chèque dans un délai de quinze jours suivant la date d'émission de la facture correspondante. Pour le règlement de votre facture : SFR - Service Encaissement, TSA 80 002, 41901 Blois Cedex 09. Le motif du rejet mentionné ci-dessus nous a été retourné par votre banque, n'hésitez pas à vérifier auprès de celle-ci la cause de ce rejet.
Re: smtpd queue encryotion
On Wed, Aug 29, 2012 at 16:34, Kurt Mosiejczuk wrote: And I'm fairly certain blowfish did get a lot of attention. And since bcrypt is reasonably popular, I'd imagine blowfish *still* gets attention from the cryptographic community. The security of bcrypt is almost completely unrelated to the security of blowfish as an encrpytion cipher. My understanding is that actually, blowfish is significantly slower. Mainly because of the setup required for each new key. I seem to recall that was part of why blowfish didn't become AES. blowfish was never submitted as an entry for AES. Being a 64-bit cipher, it wasn't even eligible.
