Re: nat trouble accessing web
I resolved this at least for now by setting no-df on my scrub, im
still investigating the mtu
On 26/06/07, Daniel Melameth [EMAIL PROTECTED] wrote:
Sounds like a possible MTU issue... Liberal use of tcpdump should
help in diagnosing the problem.
On 6/25/07, Lawrence Horvath [EMAIL PROTECTED] wrote:
Im having some trouble accessing certain sites from my laptop going
through a obsd router doing nat
I have 2 tested configurations
Laptop---Cisco1721[doing nat]---internet msn.com
and
Laptop---Cisco1721--(gre0)Openbsd[doing nat]---internet
msn.com
in the first setup, i have a local network behind a cisco1721, the
cisco does nat, and all works well
in the second setup, i have an internal network that spans via gre
from the cisco to an Openbsd router in colo which does the nat, this
is not working for me at all, when i try to go to msn.com, my browser
just sits there, i have tried this from 1 other computer as well
OpenBSD 4.0 GENERIC.MP#936 i386
# cat /etc/pf.conf.test
# Macros
# Tables
# Options
# Traffic Normalization(scrub)
# Queueing
# Translation(nat-binat-rdr)
# Packet Filtering
ext_if=tl0
tun_if=gre0
int_ip={ 10/8 192.168/16 }
natpool_ip=208.179.68.11
local_ip={ 10/8 192.168/16 208.179.68.8/29 208.179.25/24 }
set optimization high-latency
no nat on $ext_if from $local_ip to $local_ip
nat on $ext_if from $int_ip to any - $natpool_ip
pass in all
pass out all
im using ospfd to route over the gre
with either situation, i can get good name resolution, and i can
telnet to the msn server on 0 and issue a get request successfully i
can get to almost any other website in either config, google, yahoo,
etc, there are only a few i cant get to
if there is any other info requested, im happy to provide
thank you
--
-Lawrence
-Student ID 1028219
-CCNA
Re: IBM T60 - APM issues
atstake atstake wrote: On 6/27/07, viq [EMAIL PROTECTED] wrote: $ grep apmhalt /etc/sysctl.conf #machdep.apmhalt=1 # 1=powerdown hack, try if halt -p doesn't work Thanks but that didn't help. At the monent I'm thinking of re-compiling the kernel as someone mentioned (off the list) that I need to enable acpi in the kernel. I was wondering if there's something I could enable from the UKC prompt as mentioned here: http://openbsd.org/faq/faq5.html#Options and thus avoid re-compiling the kernel altogether. config -ef /mykernelname UKC enable acpi ### acpi enabled UKC quit writing modified kernel. Like that. or, for a one-shot testing, just give boot -c at the boot prompt to get into the UKC to test it once. If it works, run the above trick to make it stick.
4.0 sparc64 booting problems
i have an ultra 5 (440mhz/512mb/14.4GB IDE) with OpenBSD 4.0 installed. i never really had any problems with the machine for some months until earlier today. i couldn't access the machine so i connected through the serial port to find the machine stuck on the ok prompt. when i tried forcing a boot (boot disk) this is what I got: --- Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 File and args: -r OpenBSD IEEE 1275 Bootblock 1.1 ..Program terminated --- when i tried a reset on the ok prompt i got the following: Resetting ... Data Access Error i really don't know where to begin. what could have gone wrong with the system? is this something that indicates a hardware issue, or has something happened to the 4.0 installation?
Re: Spamd sync observations and differences and setup question.
hi! On Tue, Jun 26, 2007 at 07:04:29PM -0400, Daniel Ouellet wrote: I setup the spamd sync feature between two servers running 4.1 and I observe the following issues with the setup itself. Some setup based on the man page do not work for me anyway and some are not always reliable and some always work. See below. Example Interface facing the Internet: dc0. server1.test.com 1.1.1.2 server2.test.com 1.1.1.3 setup in rc.conf.local that always work. In server 1: spamd_flags=-y dc0 -Y 1.1.1.3 In server 2: spamd_flags=-y dc0 -Y 1.1.1.2 hmm, ok. i will look into this. = Setup that mostly work. Meaning if you reboot, it doesn't always start spamd and as far as I can tell, that's because the name resolutions do not work right away when the query is requested, or something like that. This configuration will not always work and be reliable on reboot of servers. However based on the man page, it should. if you do it on the command line it does. Just reboot doesn't always do it. In server 1: spamd_flags=-y dc0 -Y server2.test.com In server 2: spamd_flags=-y dc0 -Y server1.test.com == Setup that I never been able to get to work. I see the message that said the initial communications between the two servers, but never do I see any sync messages exchanged between the two on the multicast channel. Only the initial helo message, but never any updates. In server 1: spamd_flags=-y dc0 -Y dc0 In server 2: spamd_flags=-y dc0 -Y dc0 you have to enable ip multicast on the systems. by default, openbsd rejects any ip multicast traffic by adding a route route -qn add -net 224.0.0.0/4 -interface 127.0.0.1 -reject try to set multicast_host=dc0 in /etc/rc.conf or /etc/rc.conf.local Setup that I never got to work at all. Not even the initial help message at all. In server 1: spamd_flags=-y server1.test.com -Y server1.test.com -Y server2.test.com In server 2: spamd_flags=-y server2.test.com -Y server1.test.com -Y server2.test.com In theory the man page said that you should be able to do this. I get: spamd: sync init: Device not configured I am still puzzle as to why it also should send the updates to itself here. Meaning -Y server2.test.com when it's configure on server2? It's the one sending the updates, so it already know what it is sending. Anyway, that's what I got. Now in the final setup, I do see the sync messages in the first configuration above, but it's still not clear to me how I can see the results in the /var/db/spamd file, or may be in the pf table spamd-white. I try to add some address to see with spamdb -a 1.2.3.4 on one side and expected it to be added on the second server, but never see it in the spamdb. I don't see it in the pf table spamd-white either. Isn't it suppose to be there some how? Or may be I need to add something in the pf configuration to log it to the spamd-white table when the updates are coming in. That might be it, but the man page say nothing about that. Am I forgetting something here. All this is with brand new 4.1 install. did you upgrade it to 4.1-stable? there was a minor fix for spamd-sync after the release. Thanks Daniel
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Hi Maxim, Thanks for your suggestion, but I have 'enough' RAM installed and didn't configure a swap partition. There's only one partition on the mirror and I use it as /home. I did more tests and I figured out that one of my mirrored drives causes read errors, which in turn causes the CCD/kernel to panic. Marius Maxim Belooussov wrote: Hi Marius, My OpenBSD 4.1 Generic i386 box occasionally freezes completely, without any warning. Sorry for a dumb question, but is your swap located on raid? If yes, could system have a problem trying to mirror it? (disclaimer: I'm just a user, not developer, + very limited experience with raid setups) Maxim
panic on boot with plugged usb mouse on dell c521
Hi, I hope I'm not making any mistake ... I've installed openbsd/amd64 4.1 and moved to current with no mouse plugged. All the process went fine. Later I rebooted with the mouse plugged and then I got the panic message. I tried all the various usb port and even booted without keyboard but with mouse and ended up to the same result. I cannot send the trace and ps output as required as my keyboard (usb too) is unavailable after the panic. If I plug the mouse at the end of the boot (login prompt), everything is fine : no panic, pointer and buttons are working under X. The pseudo dmesg output with panic message (third attachment) is handwritten. Should I provide more infos or test anything, I am available. OpenBSD 4.1-current (GENERIC) #1126: Mon Jun 25 13:09:22 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1005056000 (958MB) avail mem = 964476928 (919MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf (62 entries) bios0: Dell Inc Dimension C521 acpi at mainbus0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3500+, 2204.88 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: PowerNow! K8 2204 MHz: speeds: 2200 2000 1800 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 NVIDIA C51 Host rev 0xa2 at pci0 dev 0 function 0 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 1 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 2 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 3 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 4 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 5 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 6 not configured NVIDIA C51 Memory rev 0xa2 at pci0 dev 0 function 7 not configured ppb0 at pci0 dev 2 function 0 NVIDIA C51 PCIE rev 0xa1 pci1 at ppb0 bus 1 ppb1 at pci0 dev 3 function 0 NVIDIA C51 PCIE rev 0xa1 pci2 at ppb1 bus 2 ppb2 at pci0 dev 4 function 0 NVIDIA C51 PCIE rev 0xa1 pci3 at ppb2 bus 3 vga1 at pci0 dev 5 function 0 NVIDIA GeForce 6150 LE rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) NVIDIA MCP51 Host rev 0xa2 at pci0 dev 9 function 0 not configured pcib0 at pci0 dev 10 function 0 NVIDIA MCP51 ISA rev 0xa3 nviic0 at pci0 dev 10 function 1 NVIDIA MCP51 SMBus rev 0xa3 iic0 at nviic0 iic1 at nviic0 NVIDIA MCP51 Memory rev 0xa3 at pci0 dev 10 function 2 not configured ohci0 at pci0 dev 11 function 0 NVIDIA MCP51 USB rev 0xa3: irq 5, version 1.0, legacy support ehci0 at pci0 dev 11 function 1 NVIDIA MCP51 USB rev 0xa3: irq 15 usb0 at ehci0: USB revision 2.0 uhub0 at usb0: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 pciide0 at pci0 dev 14 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA pciide0: using irq 10 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: WDC WD800JD-75MSA3 wd0: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVD+-RW GSA-H31N, B109 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide1 at pci0 dev 15 function 0 NVIDIA MCP51 SATA rev 0xa1: DMA pciide1: using irq 11 for native-PCI interrupt ppb3 at pci0 dev 16 function 0 NVIDIA MCP51 PCI-PCI rev 0xa2 pci4 at ppb3 bus 4 bce0 at pci4 dev 7 function 0 Broadcom BCM4401B1 rev 0x02: irq 5, address 00:1a:a0:0e:f8:29 bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0 ral0 at pci4 dev 9 function 0 Ralink RT2560 rev 0x01: irq 7, address 00:11:50:15:c6:2e ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 azalia0 at pci0 dev 16 function 1 NVIDIA MCP51 HD Audio rev 0xa2: irq 10 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: 0x8384/0x7618 (rev. 2.1), HDA version 1.0 audio0 at azalia0 pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 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 usb1 at ohci0: USB revision 1.0 uhub1 at usb1: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhidev0 at uhub1 port 5 configuration 1 interface 0 uhidev0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 2, iclass 3/1 ukbd0 at uhidev0: 8 modifier keys,
Re: 4.0 sparc64 booting problems
openbsd neophyte [EMAIL PROTECTED] writes: Date:Wed, 27 Jun 2007 00:12:53 PDT To: misc@openbsd.org From:openbsd neophyte [EMAIL PROTECTED] Subject: 4.0 sparc64 booting problems i have an ultra 5 (440mhz/512mb/14.4GB IDE) with OpenBSD 4.0 installed. i never really had any problems with the machine for some months until earlier today. i couldn't access the machine so i connected through the serial port to find the machine stuck on the ok prompt. when i tried forcing a boot (boot disk) this is what I got: --- Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 File and args: -r OpenBSD IEEE 1275 Bootblock 1.1 ..Program terminated --- when i tried a reset on the ok prompt i got the following: Resetting ... Data Access Error i really don't know where to begin. what could have gone wrong with the system? is this something that indicates a hardware issue, or has something happened to the 4.0 installation? You should power-cycle the machine. The prom environment is probably too corrupt to properly reset. If that doesn't work, consider doing these next: /1/ boot from removable media (after a power-on reset) /2/ check the cmos battery. renew if necessary. /3/ check other cables, memory modules, etc. try prom memory test. You may have a hardware problem. -Marcus
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Brian A. Seklecki wrote: This is the expected behavior for a failure on a CCD component. Try In this case, is there a difference between expected and desired behavior? cutting the SATA cable to a live system some time; watch the kernel panic there as well. Suddenly it cant stat() / or read/write from swap. Maybe this should be mentioned in the FAQ. (I expected it to run with one device and attract the admins/roots attention in a another way. In my case, the only way to recover was a hard reset.) You're playing with fire with CCD anyway: RAID0. The stuff in 4.1 wasn't touched for months...6, 10, 11, 11, look at the time between commits. There's some new recent activity. Things that old don't have to be bad..? At least I thought/was told so. Try RAIDFrame w/ raid0 for a little-more-active development. I considered raid frame, too, but didn't want to build a new kernel. But I'll give it a shot. Thank you. ~BAS Marius
looking for a good guide on driver writing
Hello, I am looking for a guide about driver writing for OpenBSD. I've found some info on NetBSD, so the question is: is the driver structure in NetBSD any different compared to OpenBSD? -- With best regards, Gregory Edigarov
Re: nat trouble accessing web
On 2007/06/26 23:40, Lawrence Horvath wrote: I resolved this at least for now by setting no-df on my scrub, im still investigating the mtu google: mtu eyechart
Re: IBM T60 - APM issues
On 6/27/07, Janne Johansson [EMAIL PROTECTED] wrote: or, for a one-shot testing, just give boot -c at the boot prompt to get into the UKC to test it once. If it works, run the above trick to make it stick. Thanks all for replying. It's still not working. Here's what I've tried so far along with some system information - o /etc/rc.shutdown - powedown=YES # cat /etc/sysctl.conf | grep apm machdep.apmwarn=10 # battery % when apm status messages enabled machdep.apmhalt=1 # 1=powerdown hack, try if halt -p doesn't wor o # dmesg | grep acpi acpi at mainbus0 not configured o sysctl -aA | grep acpi - gives nothing o sysctl -aA | grep apm - machdep.apmwarn=10 machdep.apmhalt=1 o when the system boots, it says APM error and this is before the boot prompt o Also tried to load bsd.mp - makes the system really slow o Also went to UKC enable apm it says - 298 apm already enabled o Also tried enabling acpi from UKC with no luck. Is there anything else I could try? Any help on this would be much appreciated. Thanks.
Re: IBM T60 - APM issues
On 27 Jun 2007 11:58:04 +0200, Artur Grabowski [EMAIL PROTECTED] wrote: If the T60 is anything like the X60, it doesn't have APM, only ACPI. Ok. I enabled ACPI from UKC and here's the dmesg - UKC enable acpi 386 acpi0 enabled UKC enable acpiverbose acpi0 at mainbus0: rev 2 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpitimer at acpi0 not configured acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 0 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpiec at acpi0 not configured acpibtn at acpi0 not configured acpibtn at acpi0 not configured acpibat at acpi0 not configured acpibat at acpi0 not configured acpiac at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured Is there any way I could power down the system by halt -p? Thanks for any help.
Re: Only one core of an amd X2 4600 is in use
On 2007/06/26 21:42, John Nietzsche wrote: I believed when openbsd kernel took control, it did not matter the bios stuff. that's not correct, the kernel has to pull information from the BIOS about multiprocessor setup, interrupt routing, etc. there are different ways of getting this - MP tables and ACPI. some BIOS have bogus information in one or other of these. sometimes this gets fixed in newer BIOS revisions. not directly for the multiprocessor side of things, but this paper has some information about MP/ACPI and might be interesting to people who want to learn about interrupts on x86: PCI Interrupts for x86 Machines under FreeBSD http://people.freebsd.org/~jhb/papers/bsdcan/2007/article/article.html (much of it applies to any OS).
Re: 4.0 sparc64 booting problems
i stumbled upon RESET SC Control= from someplace. while i'm not sure exactly what it does, i think it does some pretty low level reset. interestingly enough the first boot using this command booted the system right into the OS (4.0) but any subsequent try has failed as well. i tried the following to pull more output to see what was going on, but, well here, this is what happened: - ok setenv mfg-mode on mfg-mode =on ok setenv diag-switch? true diag-switch? =true ok setenv auto-boot? false auto-boot? = false ok reset-all Resetting ... Software Power ON @(#) Sun Ultra 5/10 UPA/PCI 3.31 Version 0 created 2001/07/25 20:36 Clearing E$ Tags Done Clearing I/D TLBs Done Probing Memory Done MEM BASE = ..1000. MEM SIZE = ..1000. 11-Column Mode Enabled MMUs ON Copy Done PC = .01ff.f000.201c PC = ...2060 Decompressing into Memory Done Size = ..0006.eba0 ttya initialized Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 UltraSPARC-IIi 2-2 module Probing Memory Bank #0 128 + 128 : 256 Megabytes Probing Memory Bank #2 128 + 128 : 256 Megabytes Probing UPA Slot at 1e,0 Nothing There Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 1 pci108e,1000 network Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 2 SUNW,m64B Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 3 ide disk cdrom Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED] at Device 1 Data Access Error ok obdiag stdin: fffe1ba8 stdout: fffe1bb0 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED] loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],3043bc loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],3062f8 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],40 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],1 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],3023f0 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/SUNW,[EMAIL PROTECTED],20 loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED] loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/disk loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/cdrom loading code into: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/SUNW,[EMAIL PROTECTED] Debugging enabled OBDiag Menu 0 . PCI/Cheerio 1 . EBUS DMA/TCR Registers 2 . Ethernet 3 . Keyboard 4 . Mouse 5 . Floppy 6 . Parallel Port 7 . Serial Port A 8 . Serial Port B 9 . NVRAM 10 . Audio 11 . EIDE Fast Data Access MMU Miss ok -- i'm kinda at a loss here. ... Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 1 pci108e,1000 network ... Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED] at Device 1 Data Access Error ... i don't know why this device is listed twice. i'm leaning towards the mainboard, but if the problem is with this NIC, then it makes things a whole hell of a lot easier to deal with. -sameer On 6/27/07, Marcus Watts [EMAIL PROTECTED] wrote: openbsd neophyte [EMAIL PROTECTED] writes: Date:Wed, 27 Jun 2007 00:12:53 PDT To: misc@openbsd.org From:openbsd neophyte [EMAIL PROTECTED] Subject: 4.0 sparc64 booting problems i have an ultra 5 (440mhz/512mb/14.4GB IDE) with OpenBSD 4.0installed. i never really had any problems with the machine for some months until earlier today. i couldn't access the machine so i connected through the serial port to find the machine stuck on the ok prompt. when i tried forcing a boot (boot disk) this is what I got: --- Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 File and args: -r OpenBSD IEEE 1275 Bootblock 1.1 ..Program terminated --- when i tried a reset on the ok prompt i got the following: Resetting ... Data Access Error i really don't know where to begin. what could have gone wrong with the system? is this something that indicates a hardware issue, or has something happened to the 4.0 installation? You should power-cycle the machine. The prom environment is probably too corrupt to properly reset. If that doesn't work, consider doing these next: /1/ boot from removable media (after a power-on reset) /2/ check the cmos battery. renew if necessary. /3/ check other cables, memory modules, etc. try prom memory test. You may have a hardware problem. -Marcus
Highpoint RocketRAID 1740.
Hi all!! I have got hold of a Highpoint RocketRAID 1740 SATA disk controller. Is there anyone out there thats got a driver for it? /Hasse -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: looking for a good guide on driver writing
* Gregory Edigarov [EMAIL PROTECTED] [070627 05:31]: Hello, I am looking for a guide about driver writing for OpenBSD. I've found some info on NetBSD, so the question is: is the driver structure in NetBSD any different compared to OpenBSD? -- With best regards, Gregory Edigarov Short answer: yes there are differences (depends on how deep you look). Long answer: IMO reading Net|Free documentation will help put things in perspective. In my experience (very limited) I found reading the code to be best. I understand that doesn't help when you have zero knowledge of writing drivers though. I flailed at it for a couple months of and on before I had a reasonable clue. From there I got dangerous real quick. It's a journey and I personally still have quite a ways to go. There's no short cuts. Jim
Re: 4.0 sparc64 booting problems
openbsd neophyte wrote: would you be surprised if i said yes? :) i'm pretty sure there's an issue with the board. ok RESET SC Control= Resetting ... Software Power ON @(#) Sun Ultra 5/10 UPA/PCI 3.31 Version 0 created 2001/07/25 20:36 Clearing E$ Tags Done Clearing I/D TLBs Done Probing Memory Done MEM BASE = ..1000. MEM SIZE = ..1000. 11-Column Mode Enabled MMUs ON Copy Done PC = .01ff.f000.201c PC = ...2060 Decompressing into Memory Done Size = ..0006.eba0 ttya initialized Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0 UltraSPARC-IIi 2-2 module Probing Memory Bank #0 128 + 128 : 256 Megabytes Probing Memory Bank #2 128 + 128 : 256 Megabytes Probing UPA Slot at 1e,0 Nothing There Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 1 pci108e,1000 network Probing /[EMAIL PROTECTED], 0/[EMAIL PROTECTED],1 at Device 2 SUNW,m64B Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 at Device 3 ide disk cdrom Probing /[EMAIL PROTECTED],0/[EMAIL PROTECTED] at Device 1 Data Access Error - I read that as your hard drive. Have you tried to replace your drive yet? the odd thing is the first time i tried the RESET SC Control= it booted up without any problems, but the subsequent times have given me the same problem. Ok, then do it again, and fsck? this output redirected back to Device 1, does that mean that NIC i have mounted in there is bad, or could the actual PCI port be bad? any ideas? Typically when machines stop booting one day, it's a drive error. Granted, that's not always the case, but there's an easy test in this case. Drop another drive in, install, and you should have your answer in under 30 min. On 6/27/07, * Nicholas Shank* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: openbsd neophyte wrote: i didn't want to hear this. unfortunately, i expected it was the case. the drives are these problematic older IBM drives that have had all sorts of issues. i guess i'll pop in another drive and see what happens. thanks. On 6/27/07, *Nicholas Shank* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: openbsd neophyte wrote: i have an ultra 5 (440mhz/512mb/14.4GB IDE) with OpenBSD 4.0 installed. i never really had any problems with the machine for some months until earlier today. i couldn't access the machine so i connected through the serial port to find the machine stuck on the ok prompt. when i tried forcing a boot (boot disk) this is what I got: --- Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 File and args: -r OpenBSD IEEE 1275 Bootblock 1.1 ..Program terminated --- when i tried a reset on the ok prompt i got the following: Resetting ... Data Access Error i really don't know where to begin. what could have gone wrong with the system? is this something that indicates a hardware issue, or has something happened to the 4.0 installation? Sounds like a hardware error. Try replacing the dive, load it, and see what happens. If you can't boot the install CD, then I would say you have other issues. Nick Would you like me to lie to you? :) Nick
Rename multiple files at once
Hi there, How do I rename multiple files at once? I want to rename a list of files like: file.jpg file1.jpg file_2.jpg to: file_thumb.jpg file1_thumb.jpg file_2_thumb.jpg man mv(1) says nothing about REGEX. (although I don't know REGEX (yet)) Kind regard, Pieter Verberne
Re: Rename multiple files at once
On Wednesday 27 June 2007 14:37:07 Pieter Verberne wrote: Hi there, How do I rename multiple files at once? I want to rename a list of files like: file.jpg file1.jpg file_2.jpg to: file_thumb.jpg file1_thumb.jpg file_2_thumb.jpg man mv(1) says nothing about REGEX. (although I don't know REGEX (yet)) Use basename(1). Something like (ugly, NOT TESTED!): $ for i in *.jpg ; do mv $i `basename $i .jpg`_thumb.jpg ; done -- Antoine
Re: Rename multiple files at once
2007/6/27, Pieter Verberne [EMAIL PROTECTED]: How do I rename multiple files at once? I want to rename a list of files like: mmv is in ports. Best Martin
Re: Rename multiple files at once
On Wed, Jun 27, 2007 at 02:37:07PM +0200, Pieter Verberne wrote:
How do I rename multiple files at once? I want to rename a list of
files like:
file.jpg
file1.jpg
file_2.jpg
to:
file_thumb.jpg
file1_thumb.jpg
file_2_thumb.jpg
Using bash, you can do something like that:
for file in file.jpg file1.jpg file_2.jpg; do
mv $file ${file/.jpg/_thumb.jpg}
done
--
Olivier Mehani [EMAIL PROTECTED]
PGP fingerprint: 3720 A1F7 1367 9FA3 C654 6DFB 6845 4071 E346 2FD1
[demime 1.01d removed an attachment of type application/pgp-signature]
Re: Rename multiple files at once
On Wed, Jun 27, 2007 at 02:37:07PM +0200, Pieter Verberne wrote:
How do I rename multiple files at once?
This is a function of your shell, not mv. See ksh(1), zsh(1), etc...
Alternatively, you could write a simple script/function to address
the same problem:
for FILE in *jpg; do
NEW=$(echo $FILE | sed -e 's/\.jpg$/_thumb.jpg/')
mv ${FILE} ${NEW}
done
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: Rename multiple files at once
2007/6/27, Martin Schrvder [EMAIL PROTECTED]: 2007/6/27, Pieter Verberne [EMAIL PROTECTED]: How do I rename multiple files at once? I want to rename a list of files like: mmv is in ports. Or, if you're lazy and use X and all that kind of fancy stuff, you can use x11/xfce4/thunar, a file-manager with a builtin batch-renamer : http://thunar.xfce.org/documentation/C/advanced-topics.html#to-bulk-rename-fi les Landry
Re: Rename multiple files at once
Pieter Verberne([EMAIL PROTECTED]) on 2007.06.27 14:37:07 +:
Hi there,
How do I rename multiple files at once? I want to rename a list of
files like:
man mv(1) says nothing about REGEX. (although I don't know REGEX
(yet))
I like this one, from the Perl Cookbook, Chap. 9.9.
#!/usr/bin/perl -w
# rename - Larry's filename fixer
$op = shift or die Usage: rename expr [files]\n;
chomp(@ARGV = STDIN) unless @ARGV;
for (@ARGV) {
$was = $_;
eval $op;
die $@ if $@;
rename($was,$_) unless $was eq $_;
}
To do your rename:
file.jpg
file1.jpg
file_2.jpg
to:
file_thumb.jpg
file1_thumb.jpg
file_2_thumb.jpg
you could then do
rename 's/\.jpg/_thumb.jpg/' file.jpg file1.jpg file_2.jpg
The first argument of this rename command can be any valid perl expression
:-)
/B.
--
Sebastian Benoit [EMAIL PROTECTED]
Gegen Krisen kann keiner was!
Unverr|ckbar |ber uns; Stehen die Gesetze der Wirtschaft, unbekannte;
Wiederkehren in furchtbaren Zyklen; Katastrophen der Natur.
-- Berthold Brecht, Hl. Johanna der Schlachthvfe
[demime 1.01d removed an attachment of type application/pgp-signature]
Re: Rename multiple files at once
Hi Pieter,
On Wed, 27 Jun 2007 14:37:07 +0200, Pieter Verberne [EMAIL PROTECTED] wrote:
Hi there,
How do I rename multiple files at once? I want to rename a list of
files like:
file.jpg
file1.jpg
file_2.jpg
to:
file_thumb.jpg
file1_thumb.jpg
file_2_thumb.jpg
Assuming that your files have only one . in their filename (just foo.jpg, not
foo.bar.jpg), you could do this shell hack:
cd directory/with/your/files
for i in $(ls | cut -d. -f1); do echo renaming ${i}; mv ${i} ${i}_thumb.jpg;
done
This is bourne shell syntax (works in my bash) and assumes that you only have
one dot in your filename. Otherwise the ls | cut -d. -f1 thing wouldn't work
;)
Cheers,
./Marian
PS.: Yes, I know, there are probably safer ways of renaming :)
Re: Rename multiple files at once
On 27/06/07, Olivier Mehani [EMAIL PROTECTED] wrote:
On Wed, Jun 27, 2007 at 02:37:07PM +0200, Pieter Verberne wrote:
How do I rename multiple files at once? I want to rename a list of
files like:
file.jpg
file1.jpg
file_2.jpg
to:
file_thumb.jpg
file1_thumb.jpg
file_2_thumb.jpg
Using bash, you can do something like that:
for file in file.jpg file1.jpg file_2.jpg; do
mv $file ${file/.jpg/_thumb.jpg}
done
Assuming your files are matched by file*.jpg, you can do this in ksh
(the default shell in OpenBSD):
for f in file*.jpg; do
mv $f ${f%.jpg}_thumb.jpg
done
Cheers,
Andreas
--
Andreas Kahari
Somewhere in the general Cambridge area, UK
Re: Rename multiple files at once
On 6/27/07, Will Maier [EMAIL PROTECTED] wrote:
On Wed, Jun 27, 2007 at 02:37:07PM +0200, Pieter Verberne wrote:
How do I rename multiple files at once?
This is a function of your shell, not mv. See ksh(1), zsh(1), etc...
Alternatively, you could write a simple script/function to address
the same problem:
for FILE in *jpg; do
NEW=$(echo $FILE | sed -e 's/\.jpg$/_thumb.jpg/')
mv ${FILE} ${NEW}
done
Will, I like your use of sed on this. I did a similar thing with awk.
for i in *.jpg do
outfile=`echo $i | awk -F. '{print $1_thumb.jpg}'`
mv $i $outfile
done
Terry
Re: nat trouble accessing web
Hello Daniel,
i have the following configuration:
LAN[ProxyOpenBSD]---[FirewallOpenBSD]-(internet)
Your configuration is similar to mine, on the Proxy machine i do not use nat (i
dont need it), the proxy machine is my default gateway.On the Firewall i have a
rule that allows pass all the traffic that comes from the proxy.
Just for giving you a clue, i will post my pf.conf from my firewall.
I guess you have to set up your cisco to allow pass just the traffic you want,
and tells the bsd to let pass what comes from cisco to any distanation.
My proxy is just a router, with few rules that blocks source and destinations.
I hope this can help ...
# Macros
ext_if=xl0
dmz_if=fxp0
int_if=fxp0
ext_ip=x.x.x.x
#External NAME SERVERS
NsV={ 200.75.51.132 , 200.75.51.133 ,200.21.200.2 }
Lan=192.168.0.0/24
#SSH from LAN
SshC=192.168.0.3
#dmz
SdOd=192.168.10.252
Proxy=10.4.1.3
#OPtioins
#Don't Filter on the loopback interface
set block-policy drop
set skip on lo
scrub in all
scrub out on $ext_if all random-id
nat on $ext_if from !($ext_if) - $ext_ip
block in on { rl0, fxp0, xl0 } all
block out on { rl0, fxp0, xl0 } all
pass out keep state
#pass quick on $int_if
antispoof quick for { lo $int_if $dmz_if}
# HTTP, HTTPS
pass in on $int_if proto tcp from $Proxy to any port {80,8880,443 ,1863} keep
state
pass out on $ext_if proto tcp from $Proxy to any port {80,8880,443 ,1863} keep
state
#dns
pass in on $int_if proto udp from $Unxs to $NsV port 53 keep state
pass out on $ext_if proto udp from $Unxs to $NsV port 53 keep state
Laptop---Cisco1721--(gre0)Openbsd[doing nat]---internet
msn.com
Original-Nachricht
Datum: Tue, 26 Jun 2007 21:30:52 -0600
Von: Daniel Melameth [EMAIL PROTECTED]
An: misc@openbsd.org
Betreff: Re: nat trouble accessing web
Sounds like a possible MTU issue... Liberal use of tcpdump should
help in diagnosing the problem.
On 6/25/07, Lawrence Horvath [EMAIL PROTECTED] wrote:
Im having some trouble accessing certain sites from my laptop going
through a obsd router doing nat
I have 2 tested configurations
Laptop---Cisco1721[doing nat]---internet msn.com
and
Laptop---Cisco1721--(gre0)Openbsd[doing nat]---internet
msn.com
in the first setup, i have a local network behind a cisco1721, the
cisco does nat, and all works well
in the second setup, i have an internal network that spans via gre
from the cisco to an Openbsd router in colo which does the nat, this
is not working for me at all, when i try to go to msn.com, my browser
just sits there, i have tried this from 1 other computer as well
OpenBSD 4.0 GENERIC.MP#936 i386
# cat /etc/pf.conf.test
# Macros
# Tables
# Options
# Traffic Normalization(scrub)
# Queueing
# Translation(nat-binat-rdr)
# Packet Filtering
ext_if=tl0
tun_if=gre0
int_ip={ 10/8 192.168/16 }
natpool_ip=208.179.68.11
local_ip={ 10/8 192.168/16 208.179.68.8/29 208.179.25/24 }
set optimization high-latency
no nat on $ext_if from $local_ip to $local_ip
nat on $ext_if from $int_ip to any - $natpool_ip
pass in all
pass out all
im using ospfd to route over the gre
with either situation, i can get good name resolution, and i can
telnet to the msn server on 0 and issue a get request successfully i
can get to almost any other website in either config, google, yahoo,
etc, there are only a few i cant get to
if there is any other info requested, im happy to provide
thank you
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
Re: Rename multiple files at once
Pieter Verberne wrote:
How do I rename multiple files at once? I want to rename a list
of files like:
file.jpg
file1.jpg
file_2.jpg
to:
file_thumb.jpg
file1_thumb.jpg
file_2_thumb.jpg
for i in *.jpg; do
echo mv $i ${i%.jpg}_thumb.jpg
done
# Han
Double mails from mailing list
I'm getting some mails double from [EMAIL PROTECTED] In the header is this: X-Loop: misc@openbsd.org Does that say enough? P. Verberne
Re: Double mails from mailing list
On Wed, Jun 27, 2007 at 04:57:17PM +0200, Pieter Verberne wrote:
I'm getting some mails double from [EMAIL PROTECTED] In the
header is this:
X-Loop: misc@openbsd.org
Does that say enough?
Some people are setting To: to misc@openbsd.org and adding you to
the Cc:.
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: pxeboot hanging on WRAP board
Stuart Henderson wrote: On 2007/06/22 12:15, Heinrich Rebehn wrote: Stuart Henderson wrote: On 2007/06/22 09:59, Heinrich Rebehn wrote: i am trying to get my new WRAP board to boot via pxe. pxeboot loads fine but seems to stall at the point where memory should be probed. enable the serial console in $TFTPROOT/etc/boot.conf. I tried that, but the WRAP does not even try to access etc/boot.conf at this time (according to tcpdump(1) on the server). Also, pxeboot hangs in the middle of the probing:... line. Try a new etherboot from rom-o-matic.net then, you'll need to piece it together with the files from wbios11.zip on pcengines.ch and xmodem it across. You'll need to use the options detailed in README.TXT in rom-o-matic (they're in a different order to listed now, the console ones are at the bottom of the web page). I have successfully booted pxeboot from 4.1 on a WRAP.1E with Etherboot 5.4.3 I have updated Etherboot to 5.4.3 and i can now boot bsd.rd, but only after appending 2 dummy bytes to pxeboot (saw this somewhere on the net). Thanks to all who helped! --Heinrich
Problem with Intel PRO Wireless 2100 card on HP nx7010
Hi all, I installed successfull OpenBSD on my HP nx7010 (Intel Centrino) but I had a problem with the Intel PRO Wireless 2100 integrated card... I saw the card but I can't use it and the message cannot read firmware appeared on the console and in dmesg output. I found this article: http://damien.bergamini.free.fr/ipw/ipw-openbsd.html that seem applies to my case and I followed the instructions (install firmware with pkg_add http://damien.bergamini.free.fr/ipwfw/OpenBSD/ipw-firmware-1.3.tgz) The problem of message cannot read firmware disappeared but when I take up the interface with ifconfig ipw0 up the OS freeze (only keyboard input is detected and displayed on screen, cannot switch to another tty,... just power off the lap-top) Does anyone know this issue and help me tracking the problem? What I'm wrong? Here above the output of dmesg after firmware install. If more informations needed, please ask me! Andrea -- OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1600MHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,EST,TM2 real mem = 1073115136 (1047964K) avail mem = 971776000 (949000K) using 4278 buffers containing 53780480 bytes (52520K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 11/17/03, BIOS32 rev. 0 @ 0xf, SMBIOS rev. 2.3 @ 0xfa1b6 (17 entries) bios0: Hewlett-Packard 0860 apm0 at bios0: Power Management spec V1.2 (BIOS managing devices) apm0: AC on, battery charge unknown apm0: flags 130102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x2000 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0840/176 (9 entries) pcibios0: bad IRQ table checksum pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf99f0/176 (9 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801DBM LPC rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0x1 acpi at mainbus0 not configured cpu0 at mainbus0 cpu0: Enhanced SpeedStep 1600 MHz (1484 mV): speeds: 1600, 1400, 1200, 1000, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82855PE Hub rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82855PE AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon Mobility M9 Lf rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 5 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 5 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 5 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci2 at ppb1 bus 2 VIA VT6306 FireWire rev 0x80 at pci2 dev 0 function 0 not configured re0 at pci2 dev 1 function 0 Realtek 8139 rev 0x20: RTL8139C+ (0x7480), irq 10, address 00:02:3f:6a:75:cc rlphy0 at re0 phy 0: RTL internal PHY ipw0 at pci2 dev 2 function 0 Intel PRO/Wireless 2100 rev 0x04: irq 11, address 00:0c:f1:09:a8:8a cbb0 at pci2 dev 4 function 0 ENE CB-1410 CardBus rev 0x01: irq 5 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: FUJITSU MHT2060AT PL wd0: 16-sector PIO, LBA, 57231MB, 117210240 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SONY, DVD+RW DW-P50A, 1.8e SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x01: irq 10 iic0 at ichiic0 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x01: irq 10, ICH4 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo audio0 at auich0 Intel 82801DB Modem rev 0x01
Re: Double mails from mailing list
* Pieter Verberne [EMAIL PROTECTED] [070627 11:02]: I'm getting some mails double from [EMAIL PROTECTED] In the header is this: X-Loop: misc@openbsd.org Does that say enough? P. Verberne Add this to your .procmailrc ## # Drop Duplicates found in an 8KB cache # ## :0 Wh: msgid.lock | formail -D 8192 msgid.cache HTH, Jim
i386 performance degradation since recent snapshots
Hello, i'm encountering a real performance problem since a recent update : - previous snapshots dated around 22 may was working perfectly, launching my session (xfce) took around 10-15sec. Launching firefox took around 5secs - updated last week on 20 of june, launching my session takes around 1 minute and a half, launching ffx takes 20sec - re-updated today (saw recent x*41.tgz sets update), no improvements I'm using GENERIC recompiled with acpi devices enabled : option ACPIVERBOSE option ACPI_ENABLE acpi0 at mainbus? acpitimer* at acpi? acpihpet* at acpi? acpiac* at acpi? acpibat*at acpi? acpibtn*at acpi? acpicpu*at acpi? acpidock* at acpi? acpiec* at acpi? acpiprt*at acpi? acpitz* at acpi? (i know, everything != GENERIC is not supported, but acpi still needs testers..) Who should i blame ? X ? gtk ? Myself ? I didn't see much changes in the ports i'm using, and system is generally slower in X. maybe acpi regression ? The only notable change i see in dmesg is the addition of CPU states (acpicpu0 at acpi0 C3, C3, C2, C1, FVS) Attached two (lengthy..) dmesg, one from my previous kernel which worked, and one from -current of today. Thanks for any hints Landry May 25 17:05:20 begbie syslogd: start May 25 17:05:20 begbie /bsd: OpenBSD 4.1-current (GENERIC) #1: Fri May 25 11:53:04 CEST 2007 May 25 17:05:20 begbie /bsd: [EMAIL PROTECTED] :/usr/src/sys/arch/i386/compile/GENERIC May 25 17:05:20 begbie /bsd: cpu0: Intel(R) Pentium(R) M processor 2.00GHz(GenuineIntel 686-class) 2 GHz May 25 17:05:20 begbie /bsd: cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 May 25 17:05:20 begbie /bsd: real mem = 2138472448 (2039MB) May 25 17:05:20 begbie /bsd: avail mem = 1945001984 (1854MB) May 25 17:05:20 begbie /bsd: using 4278 buffers containing 107048960 bytes (104540K) of memory May 25 17:05:20 begbie /bsd: mainbus0 (root) May 25 17:05:20 begbie /bsd: bios0 at mainbus0: AT/286+ BIOS, date 09/28/05, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf7810 (60 entries) May 25 17:05:20 begbie /bsd: bios0: Dell Inc. Latitude D410 May 25 17:05:20 begbie /bsd: pcibios0 at bios0: rev 2.1 @ 0xf/0x1 May 25 17:05:20 begbie /bsd: pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfb2d0/176 (9 entries) May 25 17:05:20 begbie /bsd: pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) May 25 17:05:20 begbie /bsd: pcibios0: PCI bus #3 is the last bus May 25 17:05:20 begbie /bsd: bios0: ROM list: 0xc/0xf800! 0xcf800/0x800 May 25 17:05:20 begbie /bsd: acpi0 at mainbus0: rev 0 May 25 17:05:20 begbie /bsd: acpi0: tables DSDT FACP APIC ASF! MCFG SSDT SSDT SSDT May 25 17:05:20 begbie /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table DSDT not configured May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table FACP not configured May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table APIC not configured May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table ASF! not configured May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table MCFG not configured May 25 17:05:20 begbie /bsd: acpi device at acpi0 from table SSDT not configured May 25 17:05:20 begbie last message repeated 2 times May 25 17:05:20 begbie /bsd: acpiprt0 at acpi0: bus 0 (PCI0) May 25 17:05:20 begbie /bsd: acpiprt1 at acpi0: bus 2 (PCIE) May 25 17:05:20 begbie /bsd: acpicpu0 at acpi0: CPU0: 2000, 1600, 1333, 1067, 800 MHz May 25 17:05:20 begbie /bsd: acpicpu1 at acpi0: CPU1: May 25 17:05:20 begbie /bsd: acpitz0 at acpi0, critical temperature: 100 degC May 25 17:05:20 begbie /bsd: acpiac0 at acpi0: AC unit offline May 25 17:05:20 begbie /bsd: acpibat0 at acpi0: BAT0: model: DELL U58676 serial: 20326 type: LION oem: Sony May 25 17:05:20 begbie /bsd: acpibat1 at acpi0: BAT1: not present May 25 17:05:20 begbie /bsd: acpibtn0 at acpi0: LID_ May 25 17:05:20 begbie /bsd: acpibtn1 at acpi0: PBTN May 25 17:05:21 begbie /bsd: acpibtn2 at acpi0: SBTN May 25 17:05:21 begbie /bsd: acpidock0 at acpi0: GDCK: not docked (0) May 25 17:05:21 begbie /bsd: cpu0 at mainbus0 May 25 17:05:21 begbie /bsd: pci0 at mainbus0 bus 0: configuration mode 1 (no bios) May 25 17:05:21 begbie /bsd: pchb0 at pci0 dev 0 function 0 Intel 82915GM/PM/GMS Host rev 0x03 May 25 17:05:21 begbie /bsd: vga1 at pci0 dev 2 function 0 Intel 82915GM/GMS Video rev 0x03: aperture at 0xdff0, size 0x1000 May 25 17:05:21 begbie /bsd: wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) May 25 17:05:21 begbie /bsd: wsdisplay0: screen 1-5 added (80x25, vt100 emulation) May 25 17:05:21 begbie /bsd: Intel 82915GM/GMS Video rev 0x03 at pci0 dev 2 function 1 not configured May 25 17:05:21 begbie /bsd: ppb0 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x03 May 25 17:05:21 begbie /bsd: pci1 at ppb0 bus 1 May 25 17:05:21 begbie /bsd: bge0 at pci1 dev 0
Re: Highpoint RocketRAID 1740.
On Tuesday 26 June 2007 14:26:18 Hans Almqvist wrote: Hi all!! I have got hold of a Highpoint RocketRAID 1740 SATA disk controller. Is there anyone out there thats got a driver for it? /Hasse First, you should always look at http://openbsd.org/plat.html and pick the platform you want to look at for hardware support. Second, read the entire FAQ -- it's great reading, and says a lot. I don't see that model listed. If its a raid card, then I doubt it. I got an IDE version once, which had a FreeBSD binary blob, but that was all. --STeve Andre'
Re: nfe0 problem (obsd 4.1)
On Wednesday 27 June 2007 10:50, Tony Lambiris wrote: You might be interested in some unofficial patches I had created when experiencing the same thing. I hadn't officially released these because of the awful DELAY() timeout hack taken from the original nfe code from DragonFly BSD. Most of the updates were taken from NetBSD. Either way, what you would be interested in is the encap_delay stuff, specifically the part in nfe.c where it actually assigns the variable: case PCI_PRODUCT_NVIDIA_CK804_LAN1: case PCI_PRODUCT_NVIDIA_CK804_LAN2: + sc-sc_encap_delay = 10; + break; You would obviously have to locate where your interface matches and assign it there. For me, my interface is a CK804. Not sure if it was LAN1 or LAN2, but I assigned the delay to both anyway. These patches seemed to work good for me, didn't experience any timeouts, YMMV. Let me know if this works. These will apply cleanly against 4.1-RELEASE. I downloaded your patches and would like to try it out. Thanks very much. Because I don't know what I am doing here, I need a bit more help. How can I find out whether my interface is also a CK804? scanpci -v gave me the following: pci bus 0x cardnum 0x08 function 0x00: vendor 0x10de device 0x0373 nVidia Corporation MCP55 Ethernet CardVendor 0x1043 card 0x8239 (ASUSTeK Computer Inc., Card unknown) STATUS0x00b0 COMMAND 0x0007 CLASS 0x06 0x80 0x00 REVISION 0xa2 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 BASE0 0xfe02a000 addr 0xfe02a000 MEM BASE1 0xb001 addr 0xb000 I/O BASE2 0xfe029000 addr 0xfe029000 MEM BASE3 0xfe028000 addr 0xfe028000 MEM MAX_LAT 0x14 MIN_GNT 0x01 INT_PIN 0x01 INT_LINE 0x0a BYTE_00x43 BYTE_1 0x10 BYTE_2 0x39 BYTE_3 0x82 pci bus 0x cardnum 0x09 function 0x00: vendor 0x10de device 0x0373 nVidia Corporation MCP55 Ethernet CardVendor 0x1043 card 0x8239 (ASUSTeK Computer Inc., Card unknown) STATUS0x00b0 COMMAND 0x0007 CLASS 0x06 0x80 0x00 REVISION 0xa2 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 BASE0 0xfe027000 addr 0xfe027000 MEM BASE1 0xac01 addr 0xac00 I/O BASE2 0xfe026000 addr 0xfe026000 MEM BASE3 0xfe025000 addr 0xfe025000 MEM MAX_LAT 0x14 MIN_GNT 0x01 INT_PIN 0x01 INT_LINE 0x0a BYTE_00x43 BYTE_1 0x10 BYTE_2 0x39 BYTE_3 0x82 dmesg shows nfe0 at pci0 dev 8 function 0 NVIDIA MCP55 LAN rev 0xa2: irq 10, address 00:17:31:cb:ee:d1 eephy0 at nfe0 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1 nfe1 at pci0 dev 9 function 0 NVIDIA MCP55 LAN rev 0xa2: irq 10, address 00:17:31:cb:dd:7a eephy1 at nfe1 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1 http://lysergik.com/~tony/openbsd/ On 6/25/07, patrick keshishian [EMAIL PROTECTED] wrote: On 6/24/07, Vijay Sankar [EMAIL PROTECTED] wrote: On Sunday 24 June 2007 13:50, patrick keshishian wrote: Hi, I've been noticing some strange problems with the built-in nfe0 interface on my desktop. Actually I've seen it on two such computers, but the description below is for my current desktop PC. The PC is running `cvs up -dP -rOPENBSD_4_1' built. I'm including netstat, ifconfig output[1] and dmesg below[2]. I've noticed that once in a while the nfe0 interface will stop sending and receiving data. At this point I can not make it work again. The only solution I have is to reboot the box. I have installed a dc0 card in the box since. The problem seemed intermittent and not reliably reproducible. But I think I found a way to reproduce this problem on demand (at least for the time being). I have an ssh session to another box, on which I run '/usr/bin/nm somelib.so'. After a page or two of output the terminal hangs. At this point nfe0 becomes unresponsive. I switch to the dc0 interface and the terminal finishes the output. Running the nm command while using the dc0 interface doesn't cause any problems. I experienced similar problems last year and can empathize. The following items improved my situation somewhat: 1) BIOS upgrade 2) Removing dual boot (I had both OpenBSD and Windows 2003 on one machine. There were more errors if I did not power off after shutting down Windows 2003 and just did a restart from within Windows. If I did not unplug the machine after shutting down Windows, most of the time I saw watchdog timeouts but if I powered off the host, and then powered it back on, there were fewer errors) Both boxes I have run solely OpenBSD. One thing that I did notice was that after switching to the dc0 interface for a short while (5 min or so?), I could switch back to the nfe0 and it would start responding again. Basically: # /sbin/ifconfig dc0 delete # /sbin/route delete default # /sbin/ifconfig nfe0 inet IP netmask netmask up # /sbin/route add
Re: nfe0 problem (obsd 4.1)
You might be interested in some unofficial patches I had created when experiencing the same thing. I hadn't officially released these because of the awful DELAY() timeout hack taken from the original nfe code from DragonFly BSD. Most of the updates were taken from NetBSD. Either way, what you would be interested in is the encap_delay stuff, specifically the part in nfe.c where it actually assigns the variable: case PCI_PRODUCT_NVIDIA_CK804_LAN1: case PCI_PRODUCT_NVIDIA_CK804_LAN2: + sc-sc_encap_delay = 10; + break; You would obviously have to locate where your interface matches and assign it there. For me, my interface is a CK804. Not sure if it was LAN1 or LAN2, but I assigned the delay to both anyway. These patches seemed to work good for me, didn't experience any timeouts, YMMV. Let me know if this works. These will apply cleanly against 4.1-RELEASE. http://lysergik.com/~tony/openbsd/ On 6/25/07, patrick keshishian [EMAIL PROTECTED] wrote: On 6/24/07, Vijay Sankar [EMAIL PROTECTED] wrote: On Sunday 24 June 2007 13:50, patrick keshishian wrote: Hi, I've been noticing some strange problems with the built-in nfe0 interface on my desktop. Actually I've seen it on two such computers, but the description below is for my current desktop PC. The PC is running `cvs up -dP -rOPENBSD_4_1' built. I'm including netstat, ifconfig output[1] and dmesg below[2]. I've noticed that once in a while the nfe0 interface will stop sending and receiving data. At this point I can not make it work again. The only solution I have is to reboot the box. I have installed a dc0 card in the box since. The problem seemed intermittent and not reliably reproducible. But I think I found a way to reproduce this problem on demand (at least for the time being). I have an ssh session to another box, on which I run '/usr/bin/nm somelib.so'. After a page or two of output the terminal hangs. At this point nfe0 becomes unresponsive. I switch to the dc0 interface and the terminal finishes the output. Running the nm command while using the dc0 interface doesn't cause any problems. I experienced similar problems last year and can empathize. The following items improved my situation somewhat: 1) BIOS upgrade 2) Removing dual boot (I had both OpenBSD and Windows 2003 on one machine. There were more errors if I did not power off after shutting down Windows 2003 and just did a restart from within Windows. If I did not unplug the machine after shutting down Windows, most of the time I saw watchdog timeouts but if I powered off the host, and then powered it back on, there were fewer errors) Both boxes I have run solely OpenBSD. One thing that I did notice was that after switching to the dc0 interface for a short while (5 min or so?), I could switch back to the nfe0 and it would start responding again. Basically: # /sbin/ifconfig dc0 delete # /sbin/route delete default # /sbin/ifconfig nfe0 inet IP netmask netmask up # /sbin/route add default gateway Therefore, a reboot isn't the only way to fix the problem (reset the interface) as I had previously thought. I am not sure exactly what causes the interface to reset: idle time, no carrier, or something completely random? Either way, thanks for all the replies! I experimented with different combinations and different switches (10/100/1000, 10/100, and 10-Base-T). When all the hosts connected to a 10/100 switch were running at 100 MB/s then changing nfe0 from autoselect to full-duplex using ifconfig nfe0 media 100baseTX mediaopt full-duplex seemed to eliminate nfe0 hangs as well as timeouts completely. I am not sure whether this has any rational basis or is specific to some weird situation in my network, but that has been my experience. Vijay Interestingly enough, if I redirect the output of nm to a file and subsequently cat the file the nfe0 interface doesn't seem to exhibit the same problem. I am not sure how to diagnose this problem further. I've enabled debug on the nfe0 interface (/sbin/ifconfig nfe0 debug), but don't see any output. Any and all suggestions are welcome. --patrick
Re: nfe0 problem (obsd 4.1)
After applying the patches, you want to go into if_nfe.c, and after line 244 (PCI_PRODUCT_NVIDIA_MCP55_LAN2) you would want to put sc-sc_encap_delay = 10; On 6/27/07, Vijay Sankar [EMAIL PROTECTED] wrote: On Wednesday 27 June 2007 10:50, Tony Lambiris wrote: You might be interested in some unofficial patches I had created when experiencing the same thing. I hadn't officially released these because of the awful DELAY() timeout hack taken from the original nfe code from DragonFly BSD. Most of the updates were taken from NetBSD. Either way, what you would be interested in is the encap_delay stuff, specifically the part in nfe.c where it actually assigns the variable: case PCI_PRODUCT_NVIDIA_CK804_LAN1: case PCI_PRODUCT_NVIDIA_CK804_LAN2: + sc-sc_encap_delay = 10; + break; You would obviously have to locate where your interface matches and assign it there. For me, my interface is a CK804. Not sure if it was LAN1 or LAN2, but I assigned the delay to both anyway. These patches seemed to work good for me, didn't experience any timeouts, YMMV. Let me know if this works. These will apply cleanly against 4.1-RELEASE. I downloaded your patches and would like to try it out. Thanks very much. Because I don't know what I am doing here, I need a bit more help. How can I find out whether my interface is also a CK804? scanpci -v gave me the following: pci bus 0x cardnum 0x08 function 0x00: vendor 0x10de device 0x0373 nVidia Corporation MCP55 Ethernet CardVendor 0x1043 card 0x8239 (ASUSTeK Computer Inc., Card unknown) STATUS0x00b0 COMMAND 0x0007 CLASS 0x06 0x80 0x00 REVISION 0xa2 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 BASE0 0xfe02a000 addr 0xfe02a000 MEM BASE1 0xb001 addr 0xb000 I/O BASE2 0xfe029000 addr 0xfe029000 MEM BASE3 0xfe028000 addr 0xfe028000 MEM MAX_LAT 0x14 MIN_GNT 0x01 INT_PIN 0x01 INT_LINE 0x0a BYTE_00x43 BYTE_1 0x10 BYTE_2 0x39 BYTE_3 0x82 pci bus 0x cardnum 0x09 function 0x00: vendor 0x10de device 0x0373 nVidia Corporation MCP55 Ethernet CardVendor 0x1043 card 0x8239 (ASUSTeK Computer Inc., Card unknown) STATUS0x00b0 COMMAND 0x0007 CLASS 0x06 0x80 0x00 REVISION 0xa2 BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00 BASE0 0xfe027000 addr 0xfe027000 MEM BASE1 0xac01 addr 0xac00 I/O BASE2 0xfe026000 addr 0xfe026000 MEM BASE3 0xfe025000 addr 0xfe025000 MEM MAX_LAT 0x14 MIN_GNT 0x01 INT_PIN 0x01 INT_LINE 0x0a BYTE_00x43 BYTE_1 0x10 BYTE_2 0x39 BYTE_3 0x82 dmesg shows nfe0 at pci0 dev 8 function 0 NVIDIA MCP55 LAN rev 0xa2: irq 10, address 00:17:31:cb:ee:d1 eephy0 at nfe0 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1 nfe1 at pci0 dev 9 function 0 NVIDIA MCP55 LAN rev 0xa2: irq 10, address 00:17:31:cb:dd:7a eephy1 at nfe1 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1 http://lysergik.com/~tony/openbsd/ On 6/25/07, patrick keshishian [EMAIL PROTECTED] wrote: On 6/24/07, Vijay Sankar [EMAIL PROTECTED] wrote: On Sunday 24 June 2007 13:50, patrick keshishian wrote: Hi, I've been noticing some strange problems with the built-in nfe0 interface on my desktop. Actually I've seen it on two such computers, but the description below is for my current desktop PC. The PC is running `cvs up -dP -rOPENBSD_4_1' built. I'm including netstat, ifconfig output[1] and dmesg below[2]. I've noticed that once in a while the nfe0 interface will stop sending and receiving data. At this point I can not make it work again. The only solution I have is to reboot the box. I have installed a dc0 card in the box since. The problem seemed intermittent and not reliably reproducible. But I think I found a way to reproduce this problem on demand (at least for the time being). I have an ssh session to another box, on which I run '/usr/bin/nm somelib.so'. After a page or two of output the terminal hangs. At this point nfe0 becomes unresponsive. I switch to the dc0 interface and the terminal finishes the output. Running the nm command while using the dc0 interface doesn't cause any problems. I experienced similar problems last year and can empathize. The following items improved my situation somewhat: 1) BIOS upgrade 2) Removing dual boot (I had both OpenBSD and Windows 2003 on one machine. There were more errors if I did not power off after shutting down Windows 2003 and just did a restart from within Windows. If I did not unplug the machine after shutting down Windows, most of the time I saw watchdog timeouts but if I powered off the host, and then powered it back on, there were fewer errors) Both boxes I have run solely OpenBSD. One thing that I did notice was that after switching to the dc0 interface for a short while (5 min or so?), I could switch
Re: Rename multiple files at once
for FILE in *jpg; do
NEW=$(echo $FILE | sed -e 's/\.jpg$/_thumb.jpg/')
mv ${FILE} ${NEW}
done
There is no need for echo and sed. OpenBSD sh and ksh support
${var%suffix} which evaluates to the contents of var less the suffix.
for f in *.jpg; do mv $f ${f%.jpg}_thumb.jpg; done
does the trick in one line.
// marc
Intel Core 2
Various developers are busy implimenting workarounds for serious bugs in Intel's Core 2 cpu. These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code. As is typical, BIOS vendors will be very late providing workarounds / fixes for these processors bugs. Some bugs are unfixable and cannot be worked around. Intel only provides detailed fixes to BIOS vendors and large operating system groups. Open Source operating systems are largely left in the cold. Full (current) errata from Intel: http://download.intel.com/design/processor/specupdt/31327914.pdf - We bet there are many more errata not yet announced -- every month this file gets larger. - Intel understates the impact of these erraata very significantly. Almost all operating systems will run into these bugs. - Basically the MMU simply does not operate as specified/implimented in previous generations of x86 hardware. It is not just buggy, but Intel has gone further and defined new ways to handle page tables (see page 58). - Some of these bugs are along the lines of buffer overflow; where a write-protect or non-execute bit for a page table entry is ignored. Others are floating point instruction non-coherencies, or memory corruptions -- outside of the range of permitted writing for the process -- running common instruction sequences. - All of this is just unbelievable to many of us. An easier summary document for some people to read: http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif Note that some errata like AI65, AI79, AI43, AI39, AI90, AI99 scare the hell out of us. Some of these are things that cannot be fixed in running code, and some are things that every operating system will do until about mid-2008, because that is how the MMU has always been managed on all generations of Intel/AMD/whoeverelse hardware. Now Intel is telling people to manage the MMU's TLB flushes in a new and different way. Yet even if we do so, some of the errata listed are unaffected by doing so. As I said before, hiding in this list are 20-30 bugs that cannot be worked around by operating systems, and will be potentially exploitable. I would bet a lot of money that at least 2-3 of them are. For instance, AI90 is exploitable on some operating systems (but not OpenBSD running default binaries). At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too).
Are Intel PWLA8391GT PRO/1000 GT desktop NICs supported on i386?
Does anyone know if Intel PWLA8391GT PRO/1000 GT desktop NICs are supported on the i386 platform? If not, can anyone make a recommendation of a PCI 10/100/1000 NIC? (I'm building a 4-zone border router with 4 NICs, and it'd be great to use well-known NICs if I can't get my current ones to work. Regards, Lloyd
Re: Spamd sync observations and differences and setup question.
Reyk Floeter wrote: you have to enable ip multicast on the systems. Shouldn't it be included in the man page then? May be I miss it, but I read them many times over to try to figure it out. I sure will test tonight when the servers are a bit less use. by default, openbsd rejects any ip multicast traffic by adding a route route -qn add -net 224.0.0.0/4 -interface 127.0.0.1 -reject One question however. CARP also use multicast and didn't need this, only net.inet.carp.preempt=1 in that specific case. I guess I am not understanding something here, or just not clear to me. Should it be rejected in CARP case as well then? I know both are not related, but I am more referring at the logic of how each work and both use multicast and in one case, the man page said to enable net.inet.carp.preempt=1 and nothing about adding multicast as well. Or is that does the same thing here? try to set multicast_host=dc0 in /etc/rc.conf or /etc/rc.conf.local I sure will try. In any case, I sure can use unicast only as well. But I will try to know for sure. did you upgrade it to 4.1-stable? there was a minor fix for spamd-sync after the release. No yet. (; I install about 20 of them all default install for now. Massive roll out last weekend. All new fresh wipe clean. My mistakes here, sorry. Thanks for the updates, Daniel
Re: Intel Core 2
On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too). so what laptop would you recommend to buy? -- almir
Re: Intel Core 2
On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too). so what laptop would you recommend to buy? I don't make recommendations.
Re: Intel Core 2
As is typical, BIOS vendors will be very late providing workarounds / fixes for these processors bugs. Some bugs are unfixable and cannot be worked around. Intel only provides detailed fixes to BIOS vendors and large operating system groups. Open Source operating systems are largely left in the cold. Is it know how many bugs are fixed by the BIOS updates that many vendors are releasing? For example, http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67648
Re: 4.0 sparc64 booting problems
openbsd neophyte wrote: Fast Data Access MMU Miss ok -- i'm kinda at a loss here. I do not have the Sun 5, but on some other Sun, when I get the Fast Data Access MMU Miss and other error like that. I do the steps like you did, but one more that correct it. Not sure that apply to your hardware here, but just in case, here it is anyway: Hope it help you some, if not, sorry for the noise. Daniel == LOM to console and back #. init 0 ok setenv auto-boot? false #depending on which Hardware and OBP Version you are running it is either or ( I do both in order to be sure on my SunFire) ok reset ok reset-all when the OBP is back you can run eg ok probe-scsi-all
Re: Spamd sync observations and differences and setup question.
On Wed, Jun 27, 2007 at 02:37:25PM -0400, Daniel Ouellet wrote: Reyk Floeter wrote: you have to enable ip multicast on the systems. Shouldn't it be included in the man page then? May be I miss it, but I read them many times over to try to figure it out. I sure will test tonight when the servers are a bit less use. by default, openbsd rejects any ip multicast traffic by adding a route route -qn add -net 224.0.0.0/4 -interface 127.0.0.1 -reject One question however. CARP also use multicast and didn't need this, only net.inet.carp.preempt=1 in that specific case. I guess I am not understanding something here, or just not clear to me. Should it be rejected in CARP case as well then? I know both are not related, but I am more referring at the logic of how each work and both use multicast and in one case, the man page said to enable net.inet.carp.preempt=1 and nothing about adding multicast as well. Or is that does the same thing here? The reject route only triggers for UDP traffic. So carp (which runs inside the kernel) and ospfd (uses a raw socket) are not affected. On the other hand ripd/routed and other tools using multicast over UDP hit that route and when sending all packets are discrded. try to set multicast_host=dc0 in /etc/rc.conf or /etc/rc.conf.local I sure will try. In any case, I sure can use unicast only as well. But I will try to know for sure. I prefer to add a specific host route to 127.0.0.1 to let specific multicast traffic through the box. ripd -- as it already plays around with the routing table -- add such a route on startup but I think that's overkill for spamd. -- :wq Claudio
Re: Only one core of an amd X2 4600 is in use
On 6/27/07, Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/06/26 21:42, John Nietzsche wrote: I believed when openbsd kernel took control, it did not matter the bios stuff. that's not correct, the kernel has to pull information from the BIOS about multiprocessor setup, interrupt routing, etc. there are different ways of getting this - MP tables and ACPI. some BIOS have bogus information in one or other of these. sometimes this gets fixed in newer BIOS revisions. not directly for the multiprocessor side of things, but this paper has some information about MP/ACPI and might be interesting to people who want to learn about interrupts on x86: PCI Interrupts for x86 Machines under FreeBSD http://people.freebsd.org/~jhb/papers/bsdcan/2007/article/article.html (much of it applies to any OS). Definately update your BIOS to the latest version. I remember when the X2 series came out there were some very weird issues with certain motherboards such as only one core even showing up or being utilized, even if the board claimed to recognize two cores properly.
Re: Intel Core 2
http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif Show stopper Potentially Catastrophic Those are some warm and fuzzy words =) Geez, that's a whole lot of bugs... I never imagined that processors could be so bugged. Theo says that AMD is getting less helpful towards open source OS. Well, that's great. We only have 2 big proc developers for i386, and now those two are turning out crap products with diminishing documentation =( I wonder where this road will lead us. -- An OpenBSD user... and that's all you need to know =) Please, send private emails to [EMAIL PROTECTED]
Re: Intel Core 2
On 6/27/07, Leonardo Rodrigues [EMAIL PROTECTED] wrote: Theo says that AMD is getting less helpful towards open source OS. Well, that's great. We only have 2 big proc developers for i386, and now those two are turning out crap products with diminishing documentation =( I wonder where this road will lead us. Well, there's always via, and I think we still like them... :) -- This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation.
Re: Intel Core 2
2007/6/27, Leonardo Rodrigues [EMAIL PROTECTED]: Theo says that AMD is getting less helpful towards open source OS. Well, that's great. We only have 2 big proc developers for i386, and now those two are turning out crap products with diminishing documentation =( I wonder where this road will lead us. To sparc64? ;) Anyway, what about Transmeta? -- Daniel 'Shinden' Horecki http://morr.pl
Re: Intel Core 2
On 27/06/07, Daniel Horecki [EMAIL PROTECTED] wrote: Anyway, what about Transmeta? Check the news: On February 7, 2007, Transmeta closed its engineering services departments and terminated 75 employees. The company announced that it would no longer develop and sell hardware, but would focus on the development and licensing of intellectual property. http://en.wikipedia.org/wiki/Transmeta C.
Re: Spamd sync observations and differences and setup question.
Claudio Jeker wrote: The reject route only triggers for UDP traffic. So carp (which runs inside the kernel) and ospfd (uses a raw socket) are not affected. On the other hand ripd/routed and other tools using multicast over UDP hit that route and when sending all packets are discrded. Thanks for the clarification Claudio! May be a suggestion, a quick addition to man 8 spamd in regards to enable ip multicast on the systems might be welcome. I sure overlook that for sure and looking at the man page again. I see no reference to it. Obviously, I should have thought about it, but just didn't. I assume I wouldn't be the only one going forward either. I prefer to add a specific host route to 127.0.0.1 to let specific multicast traffic through the box. ripd -- as it already plays around with the routing table -- add such a route on startup but I think that's overkill for spamd. Good inside.
Re: Intel Core 2
On Wednesday 27 June 2007 13:08:16 Theo de Raadt wrote: Various developers are busy implimenting workarounds for serious bugs in Intel's Core 2 cpu. These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code. As is typical, BIOS vendors will be very late providing workarounds / fixes for these processors bugs. Some bugs are unfixable and cannot be worked around. Intel only provides detailed fixes to BIOS vendors and large operating system groups. Open Source operating systems are largely left in the cold. When it becomes known that a fix/workaround is being horded and not distributed, I hope we hear of it quickly. It will be time for the user community to start talking with Intel. Or has this already started? --STeve Andre'
Re: pkg_add on macppc stall at end of ftp
The FTP problem has been fixed (worked around) in -current AFAIK. See the archives for ports@ -- Antti Harri
Re: pkg_add on macppc stall at end of ftp
The FTP problem has been fixed (worked around) in -current AFAIK. See the archives for ports@ Thank you!
Re: Intel Core 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus Leonardo Rodrigues [EMAIL PROTECTED] spake on Wed, 27 Jun 2007 16:25:08 -0300: http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif Show stopper Potentially Catastrophic Those are some warm and fuzzy words =) Geez, that's a whole lot of bugs... I never imagined that processors could be so bugged. Theo says that AMD is getting less helpful towards open source OS. Well, that's great. We only have 2 big proc developers for i386, and now those two are turning out crap products with diminishing documentation =( I wonder where this road will lead us. MIPS64. Just wait for the chinese to save the world from Chipzilla :) (And yes, MIPS is a really nice design, btw) iD8DBQFGgs/P689t39h/zfARAhiVAJ9WNAVmt9Ncv98Kycm1/VJ6dJ6zfwCg5Apu vwVNYZxxmaLhOVCZeg8ySBc= =BzkT -END PGP SIGNATURE-
Re: Spamd sync observations and differences and setup question.
On Wed, Jun 27, 2007 at 04:05:06PM -0400, Daniel Ouellet wrote: Thanks for the clarification Claudio! May be a suggestion, a quick addition to man 8 spamd in regards to enable ip multicast on the systems might be welcome. I sure overlook that for sure and looking at the man page again. I see no reference to it. Obviously, I should have thought about it, but just didn't. I assume I wouldn't be the only one going forward either. The following example will accept incoming multicast and unicast synchronisation messages, and send outgoing multicast messages through the network interface em0: the reader should suppose that this will only work on machines which enable ip multicast on the systems. and then man -k multicast should get you going... jmc
Re: Intel Core 2
On Wed, Jun 27, 2007 at 12:45:10PM -0600, Theo de Raadt wrote: On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too). so what laptop would you recommend to buy? I don't make recommendations. Ok, rephrase the question (and I don't do laptop): What computer/processor (any arch, not limited to i386) has the power to do typical desktop stuff (browse the web, watch DVDs, edit photos) and at the same time has been great to port/develop for? Anything other than the desktop stuff above works just fine on my 486 with OBSD (thanks again all). Other than Intel and AMD, is there a third CPU maker that makes good CPUs that work in systems that will then run OBSD? For example, I note that the IBM PowerPC is _not_ listed as a port and I know that there must be a reason for this. If there was such a vendor and a port didn't exist, perhaps a discussion on what a port would take would be in order? Just my 2c, and I already bought my new box for this decade (AMD Athlon 64). Doug.
Re: Intel Core 2
Ok, rephrase the question (and I don't do laptop): What computer/processor (any arch, not limited to i386) has the power to do typical desktop stuff (browse the web, watch DVDs, edit photos) and at the same time has been great to port/develop for? Anything other than the desktop stuff above works just fine on my 486 with OBSD (thanks again all). Other than Intel and AMD, is there a third CPU maker that makes good CPUs that work in systems that will then run OBSD? For example, I note that the IBM PowerPC is _not_ listed as a port and I know that there must be a reason for this. If there was such a vendor and a port didn't exist, perhaps a discussion on what a port would take would be in order? Just my 2c, and I already bought my new box for this decade (AMD Athlon 64). Doug. I am a little shocked there are so many serious issues with the dual core processors. Though, I do have a laptop with a duo core, running OBSD without any problems. What I will say; it is shocking, but for normal usage, most users will never notice these issues. What will not mean that I will ask the next time before I buy another computer Jan
Re: Spamd sync observations and differences and setup question.
Jason McIntyre wrote: On Wed, Jun 27, 2007 at 04:05:06PM -0400, Daniel Ouellet wrote: Thanks for the clarification Claudio! May be a suggestion, a quick addition to man 8 spamd in regards to enable ip multicast on the systems might be welcome. I sure overlook that for sure and looking at the man page again. I see no reference to it. Obviously, I should have thought about it, but just didn't. I assume I wouldn't be the only one going forward either. The following example will accept incoming multicast and unicast synchronisation messages, and send outgoing multicast messages through the network interface em0: the reader should suppose that this will only work on machines which enable ip multicast on the systems. and then man -k multicast should get you going... Thanks. I sure don't want to make a big deal of anything here. I did read that. Same as in CARP use multicast as well, but in CARP there was reference to enabling additional feature to make it work. Both use multicast. In one cast nothing else was needed to make it work, as Claudio clarify for me earlier, it's done in the kernel for CARP, oppose to here, witch (uses a raw socket). I accept my stupidity here for sure, but it just didn't occur to me as I didn't make the link between multicast use for CARP and multicast use here for spamd-sync that needed something else, specially that I saw in my tests the helo message when I start the spamd-sync, but just couldn't see the sync messages at all. I agree with you, now that I know I can get it going and realize my stupid mistake. I only pointed out that I may not be the only one. I even saw the same question not answered on google before and contacted the person with the same results as well or still not working. http://archives.neohapsis.com/archives/openbsd/2007-05/1102.html So, I did my homework, just a simple hint would have helped me. I simply didn't put 2 and 2 together here. Thanks all and many thanks for your time as well. Best, Daniel
hoststated and UDP
Hello, I've setup hoststated for load balancing of some services, and it works well. If I'm not missing something hoststated actually works just for TCP. Is there any plan to implement UDP support? ciao Luca
Re: Intel Core 2
Lontronics Mailinglist account wrote: I am a little shocked there are so many serious issues with the dual core processors. when competition is involved companies develop products as quickly as they can to keep up with the joneses. if your product(s) lack the bells and whistles the competition has, joey bagoconsumer will not buy your stuff b/c he's been successfully brainwashed into thinking feature X will make his life better. for an average computer user multicore processing doesn't do a whole lot besides compensate for slugware-driven OSes that are built like amUrican cars, whose primary purpose is to build product dependency and require replacement 4-5 years down the road. same lesson henry ford learned with the model t applies to large-scale hardware manufacturing. you make more money if your widgets break because your new widget is vastly improved. new packaging, same great defects! cheers, jake Though, I do have a laptop with a duo core, running OBSD without any problems. What I will say; it is shocking, but for normal usage, most users will never notice these issues. What will not mean that I will ask the next time before I buy another computer Jan
Re: Rename multiple files at once
On Wed, Jun 27, 2007 at 02:37:07PM +0200, Pieter Verberne wrote: How do I rename multiple files at once? I want to rename a list of files like: file.jpg file1.jpg file_2.jpg to: file_thumb.jpg file1_thumb.jpg file_2_thumb.jpg given that no funny filenames (with space, quotes etc.) are around, and that i'm not mistyping the following line: ls *.jpg | sed '[EMAIL PROTECTED](.*\)[EMAIL PROTECTED] \1_thumb.jpg@' | sh
Re: Intel Core 2
On 27/06/07, Jacob Yocom-Piatt [EMAIL PROTECTED] wrote: you make more money if your widgets break because your new widget is vastly improved. new packaging, same great defects! The best thing about computer parts randomly failing will hit us in a few years, due to RoHS directives: http://en.wikipedia.org/wiki/RoHS#Impact_on_reliability http://en.wikipedia.org/wiki/Whisker_%28metallurgy%29 Another problem that lead-free solders face is the growth of tin whiskers. These thin strands of tin can grow and make contact with an adjacent trace, developing a short circuit. Tin whiskers have already been responsible for at least one failure at a nuclear power plant. Other documented failures include satellites in orbit, aircraft in flight, and implanted medical pacemakers. Reliability decay of low-lead materials may be economically desirable for some consumer product companies because it provides a mechanism to enforce planned obsolescence and replacement. Ironically, this is the opposite of the claimed intent of RoHS legislation. C.
Re: Intel Core 2
On 6/27/07, Jacob Yocom-Piatt [EMAIL PROTECTED] wrote: when competition is involved companies develop products as quickly as they can to keep up with the joneses. if your product(s) lack the bells and whistles the competition has, joey bagoconsumer will not buy your stuff b/c he's been successfully brainwashed into thinking feature X will make his life better. for an average computer user multicore processing doesn't do a whole lot besides compensate for slugware-driven OSes that are built like amUrican cars, whose primary purpose is to build product dependency and require replacement 4-5 years down the road. same lesson henry ford learned with the model t applies to large-scale hardware manufacturing. you make more money if your widgets break because your new widget is vastly improved. new packaging, same great defects! But I need two cores because I want to run youtube AND the Explorer! Meanwhile, I think the real problem here is them not releasing much documentation on the problems to the public. Bugs will happen, yeah, some are pretty bad; and yeah, part of the cause of it is that they have unecessarily close deadlines (unecessarily in the sense that the world doesn't really need the next generation of processors real soon). But those are not the only reasons for a buggy hardware, it's also a matter of human limitation. It's unrealistic to think your hardware will be perfect. All in all, the intel's core 2 clearly is not prepared for some critical uses. That does not mean that you can't successfuly run it in your desktop or even some servers. You'll most likely have much more dangerous vulnerabilities in the software you're using anyway.
Re: Intel Core 2
On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: Various developers are busy implimenting workarounds for serious bugs in Intel's Core 2 cpu. These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code. As is typical, BIOS vendors will be very late providing workarounds / fixes for these processors bugs. Some bugs are unfixable and cannot be worked around. Intel only provides detailed fixes to BIOS vendors and large operating system groups. Open Source operating systems are largely left in the cold. Full (current) errata from Intel: http://download.intel.com/design/processor/specupdt/31327914.pdf - We bet there are many more errata not yet announced -- every month this file gets larger. - Intel understates the impact of these erraata very significantly. Almost all operating systems will run into these bugs. - Basically the MMU simply does not operate as specified/implimented in previous generations of x86 hardware. It is not just buggy, but Intel has gone further and defined new ways to handle page tables (see page 58). - Some of these bugs are along the lines of buffer overflow; where a write-protect or non-execute bit for a page table entry is ignored. Others are floating point instruction non-coherencies, or memory corruptions -- outside of the range of permitted writing for the process -- running common instruction sequences. - All of this is just unbelievable to many of us. An easier summary document for some people to read: http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif Note that some errata like AI65, AI79, AI43, AI39, AI90, AI99 scare the hell out of us. Some of these are things that cannot be fixed in running code, and some are things that every operating system will do until about mid-2008, because that is how the MMU has always been managed on all generations of Intel/AMD/whoeverelse hardware. Now Intel is telling people to manage the MMU's TLB flushes in a new and different way. Yet even if we do so, some of the errata listed are unaffected by doing so. As I said before, hiding in this list are 20-30 bugs that cannot be worked around by operating systems, and will be potentially exploitable. I would bet a lot of money that at least 2-3 of them are. For instance, AI90 is exploitable on some operating systems (but not OpenBSD running default binaries). At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too). So who currently (if anybody) is cooperating nicely? This is a sad state of affairs.
USB200M (linksys) reporting device problem, disabling port
hello.. i just installed OpenBSD 4.1 from an original CD. My USB ethernet adapter, a Linksys USB200M is a known good working adapter (verified on Mac OS X 10.4 and FreeBSD 6.2). I am building a gateway with OpenBSD and this hardware has only one builtin ethernet adapter (rl0) and will require a 2nd. PCI ethernet is not an option (it's a small form factor fanless PC). I require the USB200M to operate or a suitable alternative must be found. A default install produces the following in dmesg: uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x1a: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub0: port 1, set config at addr 2 failed uhub0: device problem, disabling port 1 The final two lines are relevant. I receive the same message no matter what usb port the USB200M is attached to. The documentation confirms the USB200M is supported via the axe(4) driver. The FAQ, mailing list archives, and google have produced no answers. They seem to produce results stating either that the USB200M is supported via axe(4) or that the axe(4) driver has been committed (in the 3.x branches). Almost all of the available information is relating to the introduction of axe(4) in 3.x. Some results refer to this issue, but have no replies which resolve the problem. Is this a configuartion problem or does axe(4) not fully support the Linksys USB200M Thank You. Please assist Appreciations in advance. /eric smith
Re: Intel Core 2
On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: Various developers are busy implimenting workarounds for serious bugs in Intel's Core 2 cpu. These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code. Full (current) errata from Intel: http://download.intel.com/design/processor/specupdt/31327914.pdf An easier summary document for some people to read: http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif This summary is for the core duo, but the errata is for. How do you know the bugs are all the same? I mean, seeing as it's a large monopolistic corp, I'm sure many of the same mistakes were carried over, but all of them? I don't know much about the recent history of these chips. Are there any good summaries around? -Nick
Re: Intel Core 2
via C7 a C3 questions? they work well? they give support? thanks On 6/27/07, Nick Price [EMAIL PROTECTED] wrote: On 6/27/07, Theo de Raadt [EMAIL PROTECTED] wrote: Various developers are busy implimenting workarounds for serious bugs in Intel's Core 2 cpu. These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code. As is typical, BIOS vendors will be very late providing workarounds / fixes for these processors bugs. Some bugs are unfixable and cannot be worked around. Intel only provides detailed fixes to BIOS vendors and large operating system groups. Open Source operating systems are largely left in the cold. Full (current) errata from Intel: http://download.intel.com/design/processor/specupdt/31327914.pdf - We bet there are many more errata not yet announced -- every month this file gets larger. - Intel understates the impact of these erraata very significantly. Almost all operating systems will run into these bugs. - Basically the MMU simply does not operate as specified/implimented in previous generations of x86 hardware. It is not just buggy, but Intel has gone further and defined new ways to handle page tables (see page 58). - Some of these bugs are along the lines of buffer overflow; where a write-protect or non-execute bit for a page table entry is ignored. Others are floating point instruction non-coherencies, or memory corruptions -- outside of the range of permitted writing for the process -- running common instruction sequences. - All of this is just unbelievable to many of us. An easier summary document for some people to read: http://www.geek.com/images/geeknews/2006Jan/core_duo_errata__2006_01_21__full.gif Note that some errata like AI65, AI79, AI43, AI39, AI90, AI99 scare the hell out of us. Some of these are things that cannot be fixed in running code, and some are things that every operating system will do until about mid-2008, because that is how the MMU has always been managed on all generations of Intel/AMD/whoeverelse hardware. Now Intel is telling people to manage the MMU's TLB flushes in a new and different way. Yet even if we do so, some of the errata listed are unaffected by doing so. As I said before, hiding in this list are 20-30 bugs that cannot be worked around by operating systems, and will be potentially exploitable. I would bet a lot of money that at least 2-3 of them are. For instance, AI90 is exploitable on some operating systems (but not OpenBSD running default binaries). At this time, I cannot recommend purchase of any machines based on the Intel Core 2 until these issues are dealt with (which I suspect will take more than a year). Intel must be come more transparent. (While here, I would like to say that AMD is becoming less helpful day by day towards open source operating systems too, perhaps because their serious errata lists are growing rapidly too). So who currently (if anybody) is cooperating nicely? This is a sad state of affairs.
Re: USB200M (linksys) reporting device problem, disabling port
On Wed, Jun 27, 2007 at 09:45:17PM -0400, Eric wrote: hello.. i just installed OpenBSD 4.1 from an original CD. My USB ethernet adapter, a Linksys USB200M is a known good working adapter (verified on Mac OS X 10.4 and FreeBSD 6.2). I am building a gateway with OpenBSD and this hardware has only one builtin ethernet adapter (rl0) and will require a 2nd. PCI ethernet is not an option (it's a small form factor fanless PC). I require the USB200M to operate or a suitable alternative must be found. A default install produces the following in dmesg: uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x1a: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub0: port 1, set config at addr 2 failed uhub0: device problem, disabling port 1 The final two lines are relevant. I receive the same message no matter what usb port the USB200M is attached to. The documentation confirms the USB200M is supported via the axe(4) driver. The FAQ, mailing list archives, and google have produced no answers. They seem to produce results stating either that the USB200M is supported via axe(4) or that the axe(4) driver has been committed (in the 3.x branches). Almost all of the available information is relating to the introduction of axe(4) in 3.x. Some results refer to this issue, but have no replies which resolve the problem. Is this a configuartion problem or does axe(4) not fully support the Linksys USB200M Thank You. Please assist Appreciations in advance. /eric smith I can't tell if you have a USB2 (ehci) controller, you didn't include a full dmesg. But if you don't perhaps there is an issue with usb/uhci code not properly handling high speed devices on low speed controllers.
SSH brute force attacks no longer being caught by PF rule
The rule I've had in my pf.conf file to catch and block forceful SSH attempts no longer appears to be working. I see the entries in my authlog, but the IPs are no longer getting added to my table. I suspect I screwed something up, but so far I am at a loss to see where. Could someone pass another set of eyes over the relevant parts of my pf.conf? ## SSH Hackers - blocked IPs table scanners persist file /etc/tables/scanners ## Packet Filtering ## block quick from scanners block in all ## Pass SSH traffic ## pass in log on $ext_if inet proto tcp from any to any port = ssh flags S/SA keep state (source-track rule, max-src-conn 10, max-src-conn-rate 5/60, overload scanners flush global, if-bound, sr c.track 60) Steve
Re: SSH brute force attacks no longer being caught by PF rule
Steve B wrote: The rule I've had in my pf.conf file to catch and block forceful SSH attempts no longer appears to be working. I see the entries in my authlog, but the IPs are no longer getting added to my table. I suspect I screwed something up, but so far I am at a loss to see where. Could someone pass another set of eyes over the relevant parts of my pf.conf? Put quickly as an example, but you can try: # Define some variable for clarity SSH_LIMIT=(max-src-conn-rate 3/30, overload scanners flush global) ## SSH Hackers - blocked IPs table scanners persist file /etc/tables/scanners # Block ssh access to bad ssh scanner block drop in log quick on $ext_if inet proto tcp \ from scanners to any port ssh # Allow quick valid traffic to ssh but log all attempts as well pass in log quick on $ext_if inet proto tcp from ! scanners \ to $ext_if port ssh flags S/SA keep state \ $SSH_LIMIT You may also want to add a section to always make sure you will have SSH access to your box before you block all SSH access like you did should someone spoof your source IP to log yourself out as well with may be something like: # Allow quick ssh access to good guys on main interface. pass in quick on $ext_if inet proto tcp from goodguys \ to $ext_if port ssh flags S/SA keep state Daniel
