Re: is SHA256 file used or not ?
I'm not sure I got it right, because I'm not familiar with the checksum procedure. I will make a short text below, to show how I see the process and maybe someone can pinpoint the mistakes. The *.tgz files are obtained by tree compilation so there is a new set and sha256s are compiled for each file. All new *.tgz are blended into *.iso file and a sha256 is compiled for this *.iso too. I think there are some mistakes in this scenario, since I observed that for example the bsd file from file by file download is different from the bsd file embedded into the *.iso file. I'm not trying to waste your time explaining me the whole process, but please tell me how to use this SHA256 file then? What to observe, what to match? Is it good only for file by file downloading? How to check the *.iso integrity then and how to check if *.iso is correctly imprinted on the CD after burning ? Many thanks.
Re: dell latitude d430 + port replicator -- is okay?
Sviatoslav Chagaev wrote: Hi, I want to buy a DELL Latitude D430 + a port replicator (for the DVI and LPT ports). Does this laptop work okay with OBSD? How about the port replicator? Does it need any kind of support from the OS (e.g. drivers) or is it just an electromechanical contraption? Thanks. I have loaded 4.6 or .7 on a D430 and don't remember any problems. Printer and serial worked, as did the optical drive I installed from. Ethernet and wifi worked on mine but wifi might depend on what adapter is in it. I never tried X or the DVI plug but X on other BSDs and UXes has worked fine in the past. Same for me. I use a DELL 420 (slightly different) with the small docking station and the larger one with CD/DVD and PCI slots. No problems - except UMTS, but I don't need it... Additional PCI-nics: yep. USB works fine too wpi0 (Intel PRO/Wireless 3945ABG) cause _sometimes_ trouble - a BIOS-setting problem with my 420. dmesg: OpenBSD 4.8 (GENERIC.MP) #359: Mon Aug 16 09:16:26 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz (GenuineIntel 686-class) 1.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM real mem = 794918912 (758MB) avail mem = 771932160 (736MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/18/06, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. 2.4 @ 0xf6f70 (61 entries) bios0: vendor Dell Inc. version A03 date 12/18/2006 bios0: Dell Inc. Latitude D420 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC SSDT acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S5) USB0(S0) USB1(S0) USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S3) RP02(S4) NIC_(S5) RP04(S3) RP05(S3) RP06(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 133MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz (GenuineIntel 686-class) 1.20 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PCIE) acpiprt2 at acpi0: bus 11 (RP01) acpiprt3 at acpi0: bus 12 (RP02) acpiprt4 at acpi0: bus 9 (PXP0) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature 107 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model DELL NX6267 serial 958 type LION oem Sanyo acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpidock0 at acpi0: GDCK docked (15) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: TV__ acpivout1 at acpivideo0: CRT_ acpivout2 at acpivideo0: LCD_ acpivout3 at acpivideo0: DVI_ acpivideo1 at acpi0: VID2 bios0: ROM list: 0xc/0xe800! 0xce800/0x1800 cpu0: Enhanced SpeedStep 1198 MHz: speeds: 1200, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 (irq 11) drm0 at inteldrm0 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: apic 2 int 21 (irq 10) azalia0: codecs: Sigmatel STAC9200 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 2 int 16 (irq 0) pci1 at ppb0 bus 11 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: apic 2 int 17 (irq 0) pci2 at ppb1 bus 12 wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 int 17 (irq 5), MoW2, address 00:19:d2:bc:72:25 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: apic 2 int 18 (irq 0) pci3 at ppb2 bus 9 bge0 at pci3 dev 0 function 0 Broadcom BCM5752 rev 0x02, BCM5752 A2 (0x6002): apic 2 int 18 (irq 3), address 00:18:8b:c5:3f:ca brgphy0 at bge0 phy 1: BCM5752 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 20 (irq 9) uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 21 (irq 10) uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 22 (irq 5) uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 23 (irq 3) ehci0 at pci0 dev 29 function 7 Intel 82801GB USB
Re: is SHA256 file used or not ?
On Mon, 7 Feb 2011 09:49:29 +0200 Mihai Popescu mihai...@gmail.com wrote: please tell me how to use this SHA256 file then? There was a thread recently about this where theo threatened to remove them, please don't. It is only guaranteed for releases and not snapshots, where it will be hit and miss. You can compare a SHA256 from various servers that you trust whilst getting the .iso from any mirror, bearing in mind that they aren't all in sync as the snapshots are released so often and even one server might have it's SHA256 out of sync with it's own .iso when you happen to come along.
Re: dell latitude d430 + port replicator -- is okay?
On Mon, Feb 7, 2011 at 10:50 AM, Andre Ruppert a...@in-telegence.net wrote: No problems - except UMTS, but I don't need it... Can you provide the output of usbdevs -dv? I think the umts minicard should work after my commit (see: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/umsm.c) Ciao, David
Re: is SHA256 file used or not ?
On Mon, Feb 07, 2011 at 10:27:52AM +, Kevin Chadwick wrote: On Mon, 7 Feb 2011 09:49:29 +0200 Mihai Popescu mihai...@gmail.com wrote: please tell me how to use this SHA256 file then? There was a thread recently about this where theo threatened to remove them, please don't. It is only guaranteed for releases and not snapshots, where it will be hit and miss. You can compare a SHA256 from various servers that you trust whilst getting the .iso from any mirror, bearing in mind that they aren't all in sync as the snapshots are released so often and even one server might have it's SHA256 out of sync with it's own .iso when you happen to come along. Maybe something should be put into the FAQ to prevent or shorten such threads in the future? Index: faq5.html === RCS file: /cvs/www/faq/faq5.html,v retrieving revision 1.182 diff -u -p -r1.182 faq5.html --- faq5.html 4 Feb 2011 03:25:14 - 1.182 +++ faq5.html 7 Feb 2011 11:34:14 - @@ -198,7 +198,8 @@ these are builds of whatever code is in builder grabbed a copy of the code for that particular platform. Remember, on some platforms, it may be DAYS before the snapshot build is completed and put out for distribution. There is no promise that the -snapshots are completely functional, or even install. Often, a change +snapshots are completely functional, or even install. Especially the +SHA256 might be out of sync. Often, a change that needs to be tested may trigger snapshot creation. Some platforms have snapshots built on an almost daily basis, others will be much less frequent. If you desire to run i-current/i, a recent
Re: Security List
On 6 February 2011 05:23, Alessandro Baggi alessandro.ba...@gmail.com wrote: Hi List, i had registered me to the security list: security-annou...@openbsd.org since 9 Genuary 2011, but any email come on my account. Some that had security list subscribtion, can tell me if since 09/01/2001 at today there are mails? I use a script which scrapes http://www.openbsd.org/errata48.html daily and emails me the changes as they occur. Shane
Re: is SHA256 file used or not ?
Hello. Mihai Popescu mihaipbs () gmail ! com wrote: Hello I'm installing ... from snapshots. SHA256 invalid checksums ... ... SHA256 from ftp.openbsd.org ... Some good search terms there. http://www.bing.com/search?q=site%3Aopenbsd.org+snapshot+install+sha256 http://www.bing.com/search?q=site%3Aopenbsd.org%2Ffaq+sha256 Can someone please, make some light in this matter. Is this SHA256 used anymore ? Maybe a FAQ entry will be useful. http://www.openbsd.org/faq/faq4.html 4.13.7 - I got an SHA256 mismatch during install! Checksums are embedded in the install kernels for the file sets that are used for the system install. Actual -release file sets should all match their stored checksums. At times, snapshots may not have proper checksums stored with the install kernels. This will happen for various reasons on the building side, and is not reason to panic for development snapshots. If you are concerned about this, wait for the next snapshot. Thanks Kevin Chadwick ma1l1ists () yahoo ! co ! uk wrote: There was a thread recently about this ... Yup. http://marc.info/?t=12871766371r=1w=2 Best wishes.
Re: is SHA256 file used or not ?
So the process I thought about it's not true. Better to remove the SHA256 then, what purpose can it serve if it is not syncronised? I still don't figure out why this checksum missmatch is ( on the same server, not among servers).
Re: is SHA256 file used or not ?
On Mon, Feb 07, 2011 at 12:38:37PM +0100, Benjamin Nadland wrote: On Mon, Feb 07, 2011 at 10:27:52AM +, Kevin Chadwick wrote: On Mon, 7 Feb 2011 09:49:29 +0200 Mihai Popescu mihai...@gmail.com wrote: please tell me how to use this SHA256 file then? There was a thread recently about this where theo threatened to remove them, please don't. It is only guaranteed for releases and not snapshots, where it will be hit and miss. You can compare a SHA256 from various servers that you trust whilst getting the .iso from any mirror, bearing in mind that they aren't all in sync as the snapshots are released so often and even one server might have it's SHA256 out of sync with it's own .iso when you happen to come along. Maybe something should be put into the FAQ to prevent or shorten such threads in the future? [...] Ouch. Disregard that. It is already there. (see FAQ4.13.7 - I got an SHA256 mismatch during install!)
Re: dell latitude d430 + port replicator -- is okay?
On Mon, Feb 7, 2011 at 10:50 AM, Andre Ruppert a...@in-telegence.net wrote: No problems - except UMTS, but I don't need it... Can you provide the output of usbdevs -dv? You're welcome ;-) Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x8086), rev 1.00 uhub0 port 1 powered port 2 addr 2: high speed, self powered, config 1, product 0xa005(0xa005), Dell(0x413c), rev 50.18 uhub5 port 1 powered port 2 addr 3: full speed, power 100 mA, config 1, Novatel Wireless HSDPA Modem(0x8137), Novatel Wireless(0x413c), rev 0.00, iSerialNumber Novatel Wireless HSDPA Modem ugen0 port 3 addr 4: full speed, power 200 mA, config 1, product 0x7761(0x7761), vendor 0x0b97(0x0b97), rev 1.10 uhub6 port 1 powered port 2 addr 5: full speed, self powered, config 1, O2Micro CCID SC Reader(0x7762), O2(0x0b97), rev 1.10 ugen1 port 3 powered port 4 addr 6: full speed, self powered, config 1, Bluetooth(0x8103), Dell(0x413c), rev 35.38 ubt0 port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 addr 7: high speed, self powered, config 1, product 0x0058(0x0058), Dell(0x413c), rev 10.00 uhub7 port 1 powered port 2 addr 8: high speed, self powered, config 1, product 0x0058(0x0058), Dell(0x413c), rev 10.00 uhub8 port 1 powered port 2 addr 9: low speed, power 100 mA, config 1, USB Optical Mouse(0x4d22), Primax Electronics(0x0461), rev 2.00 uhidev0 port 3 powered port 4 powered port 3 addr 10: high speed, self powered, config 1, A04(0x9001), Dell USB Drive(0x413c), rev 2.00 umass0 port 4 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 uhub2 port 1 powered port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 uhub3 port 1 powered port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 uhub4 port 1 powered port 2 powered I think the umts minicard should work after my commit (see: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/umsm.c) Thank you, I'll give it a try next weekend... Andre Ruppert
Re: is SHA256 file used or not ?
Howdy. Mihai Popescu mihaipbs () gmail ! com wrote: So the process I thought about it's not true. Better to remove the SHA256 then, what purpose can it serve if it is not syncronised? Some guy said ... Do you not want it to be there for official releases? How about if I remove the code now. Then 10 minutes before we make a release, we put it back in, find out that it makes the media not fit or some other issue has showed up http://marc.info/?l=openbsd-miscm=128719219216740w=2 I still don't figure out why this checksum missmatch is ( on the same server, not among servers). Some other guy said ... This file is provided for you to be able to check that you downloaded the files correctly. The installation media uses an internal source for the checksum information. http://marc.info/?l=openbsd-miscm=129701893809304w=2 Yet another guy said ... and the mirroring process isn't atomic. http://marc.info/?l=openbsd-miscm=129702183711918w=2 Some 'yahoo' said ... You can compare a SHA256 from various servers that you trust whilst getting the .iso from any mirror, bearing in mind that they aren't all in sync as the snapshots are released so often and even one server might have it's SHA256 out of sync with it's own .iso when you happen to come along. http://marc.info/?l=openbsd-miscm=129707462918858w=2 So on and so forth. Best wishes.
Re: is SHA256 file used or not ?
On Mon, Feb 7, 2011 at 3:46 AM, Mihai Popescu mihai...@gmail.com wrote: So the process I thought about it's not true. Better to remove the SHA256 then, what purpose can it serve if it is not syncronised? Practice for release, perhaps? If they cause too much of an uproar in snapshots, then they'll likely be killed completely, including from the releases, because trying to get them right in the release without the installer bits being regularly tested would be unsustainable. Sure, it would work fine in the 4.9 release, but with no testing between the 4.9 release and the 4.a^H^H^H5.0 release there's a not insignificant chance they wouldn't work then, and the probabilities get worse from there. I still don't figure out why this checksum missmatch is ( on the same server, not among servers). No x* entries in the separate SHA256 file, so you obviously grabbed the files between when a base build finished and when the following xenocara build did. As for other claimed mismatches: insufficient data. Philip Guenther
Cannot boot into bsd.rd 4.8
Hey there all on the misc, I am having problems booting into bsd.rd on my machine. Currently the machine holds OpenBSD 4.4 Generic and is working fine. But now I've decided to upgrade it (I will be doing a clean install) to version 4.8. So I've downloaded bsd.rd (4.8) into the machine and tried to boot into it, but the machine restarts itself in the middle of booting it. Can someone please point me into the right direction how can I resolve this? Here is the dmesg from it running 4.4: OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed real mem = 33124352 (31MB) avail mem = 22044672 (21MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/12/96, BIOS32 rev. 0 @ 0xf7318 pcibios0 at bios0: rev 2.1 @ 0xf7270/0x960 pcibios0: PCI BIOS has 6 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 9 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82439HX rev 0x03 vendor Siemens, unknown product 0x0005 (class undefined unknown subclass 0x00, rev 0x01) at pci0 dev 3 function 0 not conf igured vendor Siemens, unknown product 0x0005 (class undefined unknown subclass 0x00, rev 0x01) at pci0 dev 3 function 1 not conf igured pcib0 at pci0 dev 7 function 0 Intel 82371SB ISA rev 0x01 pciide0 at pci0 dev 7 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to com patibility wd0 at pciide0 channel 0 drive 0: WDC WD400JB-00JJC0 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 7 function 2 Intel 82371SB USB rev 0x01: irq 9 vga1 at pci0 dev 8 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) drm at vga1 unsupported bce0 at pci0 dev 18 function 0 Broadcom BCM4401 rev 0x01: irq 11, address 00:aa:bc:00:4e:01 bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0 rl0 at pci0 dev 19 function 0 Realtek 8139 rev 0x10: irq 10, address 00:e0:4c:14:e5:dc rlphy0 at rl0 phy 0: RTL internal PHY isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 biomask f3e5 netmask ffe5 ttymask softraid0 at root root on wd0a swap on wd0b dump on wd0b
Re: Cannot boot into bsd.rd 4.8
On Mon, Feb 07, 2011 at 04:56:28PM +0200, Tomas wrote: Hey there all on the misc, I am having problems booting into bsd.rd on my machine. Currently the machine holds OpenBSD 4.4 Generic and is working fine. But now I've decided to upgrade it (I will be doing a clean install) to version 4.8. So I've downloaded bsd.rd (4.8) into the machine and tried to boot into it, but the machine restarts itself in the middle of booting it. Can someone please point me into the right direction how can I resolve this? Here is the dmesg from it running 4.4: Hey Tomas, provide the 4.8 dmesg if you can - or take a picture of the screen, upload it and share the link with the list.
PostePay 2011
In conformit` con uso di PostePay e di garantire che l'account non h stato letto da posizioni fraudolente, accesso al vostro conto h stato limitato. L'accesso al conto rimarr` limitato fino a quando questo problema h stato risolto per favore. Si prega di scaricare il file allegato a questa email e compilare il modulo allegato. Vi ringraziamo per la vostra attenzione rapida a questa materia. Si prega di comprendere che questa h una misura di sicurezza destinate a proteggere voi e il vostro conto. Poste italiane 2011 - Partita Iva 01114601006 [demime 1.01d removed an attachment of type APPLICATION/DEFANGED which had a name of PostePay_2011.29328DEFANGED-html]
Re: Cannot boot into bsd.rd 4.8
On 02/07/2011 09:56 AM, Tomas wrote: Hey there all on the misc, I am having problems booting into bsd.rd on my machine. Currently the machine holds OpenBSD 4.4 Generic and is working fine. But now I've decided to upgrade it (I will be doing a clean install) to version 4.8. So I've downloaded bsd.rd (4.8) into the machine and tried to boot into it, but the machine restarts itself in the middle of booting it. Can someone please point me into the right direction how can I resolve this? Here is the dmesg from it running 4.4: OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed You have run into a bug on the 4.8 bsd.rd on Pentium 1 systems. NOT 486, not P-II or later, just the machines with the F00F bug. Easiest fix is to use a snapshot and install 4.9-beta on your system. If you install the regular GENERIC 4.8 kernel and userland manually, you will find it works just fine. It is just the bsd.rd (and thus, floppy and CD images) that don't work. Again, I'd recommend the snapshot, but if you REALLY want 4.8, install 4.7, then do a remote upgrade to 4.8, all will be fine. Of course, the reason that bug snuck out is that no one installed a snapshot on their older computer before 4.8-release. Nick. (guilty as anyone...)
Re: NFS mount can't read files.
On Sun, 06 Feb 2011 16:02:31 +0100, Pieter Verberne wrote: Hello, See thread at the bottom. I have also problems reading files while mounting from Ubuntu. I cannot read files larger than +/- 18KB. /etc/exports: /home/pieter localhost 10.0.0.1 10.0.0.2 10.0.2.15 On Ubuntu: $ sudo mount.nfs lilium:/home/pieter pieter_mount/ -w $ cat pieter_mount/test.txt # 17069 bytes [ output ] $ cat pieter_mount/test1.txt# 18483 bytes [ no output. cat keeps running; `ps aux | grep cat` pieter3095 0.0 0.0 3896 244 pts/15 D+ 15:35 0:00 cat pieter_mount/test1.txt ] When I mount the same export on the OpenBSD machine it works fine: $ sudo mount -t nfs localhost:/home/pieter/ /mount_test/ $ cat /mount_test/test1.txt [output] So could be an Ubuntu (and MacOS?) bug. I don't have another Unix/Linux computer to try on right now. Also, I'm not able to write on the exports. From both Ubuntu and OpenBSD(localhost). $ touch test touch: cannot touch `test': Read-only file system It says Read-only _file system_. Could this have anything to do with file permissions or the -maproot -allmap options? `portmap -d` and `mountd -d` gives no errors. I tried disabling pf. No result. No interesting things in /var/log/messages Thanks to Jason for a hint. I explicitly have to say to the nfs client to use UDP instead of TCP. It looks like TCP support is broken in some way? It doesn't work with Ubuntu, MacOS and I found out that mounting from a QNAP doesn't work either. And, is there a way to make nfs working with the pf scrub option? I'm using pppoe and have a NAT, see man 4 pppoe Problems can arise on machines with private IPs connecting to the Internet via a machine running both Network Address Translation (NAT) and pppoe. So in my pf.conf is match on $ext_if scrub (max-mss 1280) Is there any way to make nfs working on $ext_if?
Re: Security List
only openbsd src X. we suck in actually using it. security errata are so rare that there isn't really an established procedure, so don't rely on it too much. I am sure this has been suggested before, but why hasn't the security list been removed from list of mailing lists at http://www.openbsd.org/mail.html? It seems a little disingenuous to me to present announce-security like it is a good source of current security issues when it is in fact not. Speaking of, what is a good place to track any security related issues in Release of Stable? I have been using http://www.openbsd.org/errata.html. --Kevin
OpenVPN and traceroute: UDPv4: No buffer space available
Greetings, I found this explanation for the following OpenVPN error write UDPv4: No buffer space available (code=55) No buffer space available is reported by the kernel network layer when thekernel's transmit buffer is full - i.e. the network connection is running at full speed, and there's no space for more. This means that something is filling it, such as other OpenVPN requests, or simultaneous traffic. When this happens, the UDP packet is dropped, and the traffic is shaped to the size of the pipe it is travelling on. http://readlist.com/lists/lists.sourceforge.net/openvpn-users/0/4136.html I also got a very similar no buffer space available message while running traceroute earlier today. However, unlike the OP in the thread above, this is kicking my one VPN user off every couple of minutes. I have plenty of ram (4GB--full dmesg below) in these identical and CARPed firewalls--is there a sysctl I can bump to give the kernel more transmit space? Thanks, Jeff Ross OpenBSD 4.9-beta (GENERIC.MP) #764: Thu Jan 27 13:19:27 MST 2011 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 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,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR real mem = 3757522944 (3583MB) avail mem = 3685912576 (3515MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/29/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfa380 (61 entries) bios0: vendor American Megatrends Inc. version 080010 date 03/29/2005 bios0: SiMech R200 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC OEMB acpi0: wakeup devices PXHA(S4) PXHB(S4) EPA0(S4) EPA1(S4) EPB0(S4) EPB1(S4) EPC0(S4) P0P1(S4) MC97(S4) USB1(S1) U SB2(S1) EUSB(S4) PS2K(S4) PS2M(S4) P0PC(S4) SLPB(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 200MHz cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 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,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 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,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu3 at mainbus0: apid 7 (application processor) cpu3: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 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,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 11 pa 0xfec1, version 20, 24 pins ioapic1: misconfigured as apic 9, remapped to apid 11 ioapic2 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins ioapic2: misconfigured as apic 10, remapped to apid 9 ioapic3 at mainbus0: apid 10 pa 0xfec80400, version 20, 24 pins ioapic3: misconfigured as apic 11, remapped to apid 10 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (EPA0) acpiprt2 at acpi0: bus 3 (PXHA) acpiprt3 at acpi0: bus 2 (PXHB) acpiprt4 at acpi0: bus 4 (EPA1) acpiprt5 at acpi0: bus 6 (P0P1) acpiprt6 at acpi0: bus 5 (P0PC) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0x8000 0xc8000/0x800 0xc8800/0x1000 0xc9800/0x1000 ipmi at mainbus0 not configured pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel E7320 Host rev 0x0c ppb0 at pci0 dev 2 function 0 Intel E7520 PCIE rev 0x0c pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 Intel PCIE-PCIE rev 0x09 pci2 at ppb1 bus 3 mpi0 at pci2 dev 5 function 0 Symbios Logic 53c1030 rev 0xc1: apic 9 int 2 (irq 6) scsibus0 at mpi0: 16 targets, initiator 7 ppb2 at pci1 dev 0 function 2 Intel PCIE-PCIE rev 0x09 pci3 at ppb2 bus 2 em0 at pci3 dev 1 function 0 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 0 (irq 10), address 00:1b:21:15:6 a:82 em1 at pci3 dev 1 function 1 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 1 (irq 11), address 00:1b:21:15:6 a:83 ppb3 at pci0 dev 3 function 0 Intel E7520 PCIE rev 0x0c pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci5 at ppb4 bus 5 em2 at pci5 dev 1 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 2 (irq 9), address 00:30:48:87:2e :b0 em3 at pci5 dev 2 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 3 (irq 9), address 00:30:48:87:2e :b1 uhci0 at pci0 dev 29 function 0 Intel 6300ESB USB rev 0x02: apic 8 int 16 (irq 10) uhci1 at pci0 dev 29 function 1
Re: Cannot boot into bsd.rd 4.8
where is new bsd.rd placed? Is it on /. I placed it somewhere else so it is not confused with the 4.4 bsd.rd I remember that bsd.rd is checksummed against some files and there possibly would be a discrepancy leading to restart. floppy boot instead? network driver bce has been commented out from GENERIC, so your network won't work. You will have to compile kernel. http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/conf/GENERIC.diff?r1= 1.692;r2=1.693;f=h On Mon, Feb 7, 2011 at 8:56 AM, Tomas s.to...@gmail.com wrote: Hey there all on the misc, I am having problems booting into bsd.rd on my machine. Currently the machine holds OpenBSD 4.4 Generic and is working fine. But now I've decided to upgrade it (I will be doing a clean install) to version 4.8. So I've downloaded bsd.rd (4.8) into the machine and tried to boot into it, but the machine restarts itself in the middle of booting it. Can someone please point me into the right direction how can I resolve this? Here is the dmesg from it running 4.4: OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed real mem = 33124352 (31MB) avail mem = 22044672 (21MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/12/96, BIOS32 rev. 0 @ 0xf7318 pcibios0 at bios0: rev 2.1 @ 0xf7270/0x960 pcibios0: PCI BIOS has 6 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 9 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82439HX rev 0x03 vendor Siemens, unknown product 0x0005 (class undefined unknown subclass 0x00, rev 0x01) at pci0 dev 3 function 0 not conf igured vendor Siemens, unknown product 0x0005 (class undefined unknown subclass 0x00, rev 0x01) at pci0 dev 3 function 1 not conf igured pcib0 at pci0 dev 7 function 0 Intel 82371SB ISA rev 0x01 pciide0 at pci0 dev 7 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to com patibility wd0 at pciide0 channel 0 drive 0: WDC WD400JB-00JJC0 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 7 function 2 Intel 82371SB USB rev 0x01: irq 9 vga1 at pci0 dev 8 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) drm at vga1 unsupported bce0 at pci0 dev 18 function 0 Broadcom BCM4401 rev 0x01: irq 11, address 00:aa:bc:00:4e:01 bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0 rl0 at pci0 dev 19 function 0 Realtek 8139 rev 0x10: irq 10, address 00:e0:4c:14:e5:dc rlphy0 at rl0 phy 0: RTL internal PHY isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 biomask f3e5 netmask ffe5 ttymask softraid0 at root root on wd0a swap on wd0b dump on wd0b
Re: is SHA256 file used or not ?
Hello Philip Guenther, It looks like your answer is the most valuable for me. So, by my understanding, the developer compiles and gets the *.tgz files, uploads them to the ftp server but he doesn't compile the sha256 checksum each times for those files. I don't know why, because i'm not familiar with the entire distribution process, maybe they take to much time. But from time to time, the developer makes it somehow that SHA256 has the good checksums inside. Another thing I got recently from reading list is that *.iso file has its own cheksum mechanism once it is written to the cd so you don't need the actual sha256 for it. From my checks I can say that *.iso file may be older than actual individual files present on the ftp. From now on, as an *.iso user I don't need the SHA256 then. If I'm mistaken again, please correct me. For the other guys answering, a big thank you also, but your answers were placed to a high level for me. For the people with jokes in mind, don't waste your time for an answer that brings more confusion than clarity. thanks
Re: OpenVPN and traceroute: UDPv4: No buffer space available
On 7 February 2011 16:53, Jeff Ross jr...@openvistas.net wrote: Greetings, I found this explanation for the following OpenVPN error write UDPv4: No buffer space available (code=55) No buffer space available is reported by the kernel network layer when thekernel's transmit buffer is full - i.e. the network connection is running at full speed, and there's no space for more. This means that something is filling it, such as other OpenVPN requests, or simultaneous traffic. When this happens, the UDP packet is dropped, and the traffic is shaped to the size of the pipe it is travelling on. http://readlist.com/lists/lists.sourceforge.net/openvpn-users/0/4136.html I also got a very similar no buffer space available message while running traceroute earlier today. However, unlike the OP in the thread above, this is kicking my one VPN user off every couple of minutes. I have plenty of ram (4GB--full dmesg below) in these identical and CARPed firewalls--is there a sysctl I can bump to give the kernel more transmit space? Thanks, Jeff Ross OpenBSD 4.9-beta (GENERIC.MP) #764: Thu Jan 27 13:19:27 MST 2011 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR real mem = 3757522944 (3583MB) avail mem = 3685912576 (3515MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/29/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfa380 (61 entries) bios0: vendor American Megatrends Inc. version 080010 date 03/29/2005 bios0: SiMech R200 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC OEMB acpi0: wakeup devices PXHA(S4) PXHB(S4) EPA0(S4) EPA1(S4) EPB0(S4) EPB1(S4) EPC0(S4) P0P1(S4) MC97(S4) USB1(S1) U SB2(S1) EUSB(S4) PS2K(S4) PS2M(S4) P0PC(S4) SLPB(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 200MHz cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu3 at mainbus0: apid 7 (application processor) cpu3: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 11 pa 0xfec1, version 20, 24 pins ioapic1: misconfigured as apic 9, remapped to apid 11 ioapic2 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins ioapic2: misconfigured as apic 10, remapped to apid 9 ioapic3 at mainbus0: apid 10 pa 0xfec80400, version 20, 24 pins ioapic3: misconfigured as apic 11, remapped to apid 10 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (EPA0) acpiprt2 at acpi0: bus 3 (PXHA) acpiprt3 at acpi0: bus 2 (PXHB) acpiprt4 at acpi0: bus 4 (EPA1) acpiprt5 at acpi0: bus 6 (P0P1) acpiprt6 at acpi0: bus 5 (P0PC) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0x8000 0xc8000/0x800 0xc8800/0x1000 0xc9800/0x1000 ipmi at mainbus0 not configured pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel E7320 Host rev 0x0c ppb0 at pci0 dev 2 function 0 Intel E7520 PCIE rev 0x0c pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 Intel PCIE-PCIE rev 0x09 pci2 at ppb1 bus 3 mpi0 at pci2 dev 5 function 0 Symbios Logic 53c1030 rev 0xc1: apic 9 int 2 (irq 6) scsibus0 at mpi0: 16 targets, initiator 7 ppb2 at pci1 dev 0 function 2 Intel PCIE-PCIE rev 0x09 pci3 at ppb2 bus 2 em0 at pci3 dev 1 function 0 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 0 (irq 10), address 00:1b:21:15:6 a:82 em1 at pci3 dev 1 function 1 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 1 (irq 11), address 00:1b:21:15:6 a:83 ppb3 at pci0 dev 3 function 0 Intel E7520 PCIE rev 0x0c pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci5 at ppb4 bus 5 em2 at pci5 dev 1 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 2 (irq 9), address 00:30:48:87:2e :b0 em3 at pci5 dev 2 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 3 (irq 9), address
Re: Security List
On Mon, Feb 7, 2011 at 12:51 PM, woolsherpahat woolsherpa...@gmail.com wrote: only openbsd src X. we suck in actually using it. security errata are so rare that there isn't really an established procedure, so don't rely on it too much. I am sure this has been suggested before, but why hasn't the security list been removed from list of mailing lists at http://www.openbsd.org/mail.html? It seems a little disingenuous to me to present announce-security like it is a good source of current security issues when it is in fact not. Not only am I sure it has been suggested before, but I'm sure it was more than thoroughly discussed before.
vmware 4.9 strange message in shutdown
I'm getting the following error when I shutdown the machine (inside vmware WS 7.0) I issue: shutdown -hp now then I get: vmware: sending length failed , eax=m, ecx= vmt0: failed to send shutdown ping finally it shutdown but no so fast. this is because?
Re: vmware 4.9 strange message in shutdown
Sorry, I did not finish my first mail: I'm running 4.9-BETA inside VMWARE Workstation 7.0 (running windows 7) I'm getting the following error when I shutdown the machine (inside vmware WS 7.0) I issue: shutdown -hp now then I get: vmware: sending length failed , eax=m, ecx= vmt0: failed to send shutdown ping finally it shutdown but no so fast. this is because?
Re: OpenVPN and traceroute: UDPv4: No buffer space available
On 02/07/11 12:33, Christiano F. Haesbaert wrote: On 7 February 2011 16:53, Jeff Rossjr...@openvistas.net wrote: Greetings, I found this explanation for the following OpenVPN error write UDPv4: No buffer space available (code=55) No buffer space available is reported by the kernel network layer when thekernel's transmit buffer is full - i.e. the network connection is running at full speed, and there's no space for more. This means that something is filling it, such as other OpenVPN requests, or simultaneous traffic. When this happens, the UDP packet is dropped, and the traffic is shaped to the size of the pipe it is travelling on. http://readlist.com/lists/lists.sourceforge.net/openvpn-users/0/4136.html I also got a very similar no buffer space available message while running traceroute earlier today. However, unlike the OP in the thread above, this is kicking my one VPN user off every couple of minutes. I have plenty of ram (4GB--full dmesg below) in these identical and CARPed firewalls--is there a sysctl I can bump to give the kernel more transmit space? Thanks, Jeff Ross OpenBSD 4.9-beta (GENERIC.MP) #764: Thu Jan 27 13:19:27 MST 2011 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR real mem = 3757522944 (3583MB) avail mem = 3685912576 (3515MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/29/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfa380 (61 entries) bios0: vendor American Megatrends Inc. version 080010 date 03/29/2005 bios0: SiMech R200 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC OEMB acpi0: wakeup devices PXHA(S4) PXHB(S4) EPA0(S4) EPA1(S4) EPB0(S4) EPB1(S4) EPC0(S4) P0P1(S4) MC97(S4) USB1(S1) U SB2(S1) EUSB(S4) PS2K(S4) PS2M(S4) P0PC(S4) SLPB(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 200MHz cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR cpu3 at mainbus0: apid 7 (application processor) cpu3: Intel(R) Xeon(TM) CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS ,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 11 pa 0xfec1, version 20, 24 pins ioapic1: misconfigured as apic 9, remapped to apid 11 ioapic2 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins ioapic2: misconfigured as apic 10, remapped to apid 9 ioapic3 at mainbus0: apid 10 pa 0xfec80400, version 20, 24 pins ioapic3: misconfigured as apic 11, remapped to apid 10 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (EPA0) acpiprt2 at acpi0: bus 3 (PXHA) acpiprt3 at acpi0: bus 2 (PXHB) acpiprt4 at acpi0: bus 4 (EPA1) acpiprt5 at acpi0: bus 6 (P0P1) acpiprt6 at acpi0: bus 5 (P0PC) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0x8000 0xc8000/0x800 0xc8800/0x1000 0xc9800/0x1000 ipmi at mainbus0 not configured pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel E7320 Host rev 0x0c ppb0 at pci0 dev 2 function 0 Intel E7520 PCIE rev 0x0c pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 Intel PCIE-PCIE rev 0x09 pci2 at ppb1 bus 3 mpi0 at pci2 dev 5 function 0 Symbios Logic 53c1030 rev 0xc1: apic 9 int 2 (irq 6) scsibus0 at mpi0: 16 targets, initiator 7 ppb2 at pci1 dev 0 function 2 Intel PCIE-PCIE rev 0x09 pci3 at ppb2 bus 2 em0 at pci3 dev 1 function 0 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 0 (irq 10), address 00:1b:21:15:6 a:82 em1 at pci3 dev 1 function 1 Intel PRO/1000MT (82546GB) rev 0x03: apic 10 int 1 (irq 11), address 00:1b:21:15:6 a:83 ppb3 at pci0 dev 3 function 0 Intel E7520 PCIE rev 0x0c pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci5 at ppb4 bus 5 em2 at pci5 dev 1 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 2 (irq 9), address 00:30:48:87:2e :b0 em3 at pci5 dev 2 function 0 Intel PRO/1000MT (82541GI) rev 0x05: apic 11 int 3 (irq 9), address 00:30:48:87:2e :b1 uhci0 at pci0
Re: is SHA256 file used or not ?
* Mihai Popescu mihai...@gmail.com [2011-02-07 21:26]: It looks like your answer is the most valuable for me. So, by my understanding, the developer compiles and gets the *.tgz files, uploads them to the ftp server but he doesn't compile the sha256 checksum each times for those files. I don't know why, because i'm not familiar with the entire distribution process, maybe they take to much time. But from time to time, the developer makes it somehow that SHA256 has the good checksums inside. geez, how hard can it be. if you read the damn release manpage once and ran that process just ONCE you'd knew that the sha256 file is created as part of it. it is always good. minus X, since that is built seperately, usually not even by the same person. you have been pointed to the reason for the mismatches more than once, how hard can it be... i try it one last time, and please pplz, let this useless thread die then. 1) sometimes a new kernel is thrown in, since we want something tested quickly 2) I repeat ONCE AGAIN: the mirroring process is not atomic. think about it for a second and it'll be obvious. ok, that doesn't work apparently, so super duper obvious: INSTALL.*, SHA256, base*, bsd* are already synced. cdXZ.iso is in the process of syncing and the rest is old, as in, from a previous snap. do i need to point out now that the checksums in SHA256 won't match for cd49.iso and everything after? and the same for the checksums in bsd.rd? -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
Re: Security List
The last time someone brought up that there could be a bug in that the system did not work in the manner in which it was documented on the website, I believe something mature and well-thought-out like, Oh, yeah, shut up. was the response. On Mon, Feb 7, 2011 at 11:51 AM, woolsherpahat woolsherpa...@gmail.comwrote: only openbsd src X. we suck in actually using it. security errata are so rare that there isn't really an established procedure, so don't rely on it too much. I am sure this has been suggested before, but why hasn't the security list been removed from list of mailing lists at http://www.openbsd.org/mail.html? It seems a little disingenuous to me to present announce-security like it is a good source of current security issues when it is in fact not. Speaking of, what is a good place to track any security related issues in Release of Stable? I have been using http://www.openbsd.org/errata.html. --Kevin
Re: Security List
El 2011-02-07 21.41, patric conant escribis: The last time someone brought up that there could be a bug in that the system did not work in the manner in which it was documented on the website, I believe something mature and well-thought-out like, Oh, yeah, shut up. was the response. You're always complaining. Nice. -- I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain.
Re: Security List
I haven't been around here long enough, but having a list, even if it isn't currently used a lot isn't a bad thing. The fact that there isn't a lot of security holes in OpenBSD is a testament to how good a job the devs are doing. unfortunately, there are louts on every mailing list (even here). It is unfortunate but it is also a fact of life. The impression I am getting is that we should all do a little of the legwork ourselves BEFORE we bug the mailing lists about it. if it is beyond the level of skill that the person reporting the problem, then by all means, a little help is certainly welcome. its like me, I am getting some help trying to resolve an orca build problem on the PPC branch but it appears that it may be a hardware related issue. not much I can do about that right now. I do have a working VINUX installation on that powerbook G3 and have developed a work around for the dubs bug that makes the machine unresponsive after a random amount of time. I wish I could say the same thing for OpenBSD, but I am not yet familiar enough with its internal working to be more than a hobbyist user at best. btw, the person who was offering me as much help as he did was Super Bisquit. He also has an identical machine and encountered the exact same issues. the machine: a powerbook G3 (750 based CPU). He was going to help me with a freeBSD installation, but that is a far more advanced installation than I am willing to work on right now. For his help, I wish to express my great appreciation for his working with me. I need to dig up a spare HDD so I can keep my current install intact. oh yeah. the issues on installing or compiling for ports both involved random halts of the ATA bus or the random stopping of bm0 (the ethernet interface). the only recovery possible from either state involved a hard reboot and a pram reset. :( Nice OS, but I think the powerbook is just old enough to have some issues. -Eric On Feb 7, 2011, at 1:41 PM, patric conant wrote: The last time someone brought up that there could be a bug in that the system did not work in the manner in which it was documented on the website, I believe something mature and well-thought-out like, Oh, yeah, shut up. was the response. On Mon, Feb 7, 2011 at 11:51 AM, woolsherpahat woolsherpa...@gmail.comwrote: only openbsd src X. we suck in actually using it. security errata are so rare that there isn't really an established procedure, so don't rely on it too much. I am sure this has been suggested before, but why hasn't the security list been removed from list of mailing lists at http://www.openbsd.org/mail.html? It seems a little disingenuous to me to present announce-security like it is a good source of current security issues when it is in fact not. Speaking of, what is a good place to track any security related issues in Release of Stable? I have been using http://www.openbsd.org/errata.html. --Kevin
Re: vmware 4.9 strange message in shutdown
On 7 February 2011 21:51, Orestes Leal R. l...@cubacatering.avianet.cu wrote:
Sorry, I did not finish my first mail:
I'm running 4.9-BETA inside VMWARE Workstation 7.0 (running windows 7)
I'm getting the following error when I shutdown the machine (inside vmware
WS 7.0)
I issue: shutdown -hp now
then I get:
vmware: sending length failed , eax=m, ecx=
vmt0: failed to send shutdown ping
finally it shutdown but no so fast.
this is because?
x41:fred /usr/src find ./ -name vmt* -exec grep -C3 failed to send
shutdown ping {} \; -print
}
if (vm_rpc_send(sc-sc_tclo_rpc, NULL, 0) != 0) {
printf(%s: failed to send shutdown ping\n, DEVNAME(sc));
}
vm_rpc_close(sc-sc_tclo_rpc);
./sys/dev/vmt.c
hth
Fred
Test
-- people who love to spam me: mark.constant...@raywhite.com markconstant...@freeline.ws ma...@agathon.com.au i...@agathon.com.au mail2ji...@compuserve.com adult...@adultage.com cather...@ctynet.com sexy_ho...@wikupedia.ru
Re: Cannot boot into bsd.rd 4.8
Hey there all on the misc, I am having problems booting into bsd.rd on my machine. Currently the machine holds OpenBSD 4.4 Generic and is working fine. But now I've decided to upgrade it (I will be doing a clean install) to version 4.8. So I've downloaded bsd.rd (4.8) into the machine and tried to boot into it, but the machine restarts itself in the middle of booting it. Can someone please point me into the right direction how can I resolve this? Here is the dmesg from it running 4.4: Thanks to all who has answered. Today after work I will try a snapshot 4.9 and will let you know how it is going.
