Re: newfs block device
On Wed, Apr 22, 2009 at 02:02:43PM -0700, John Brahy wrote: | # newfs /dev/wd0f | newfs: /dev/wd0f: block device | # | | I thought that I have done that before. Have we lost functionality in | 4.5 or just my mind? A bug that allowed newfs'ing block devices was fixed. We did not lose functionality, we gained stability. Your perspective is skewed ;) The archives will tell you what could go wrong when running newfs on a block device. Someone explained it very well, I believe it was o...@. Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: autowhitelister for spamd needs testing
Dave Anderson wrote: On Wed, 22 Apr 2009, jared r r spiegel wrote: On Thu, Apr 23, 2009 at 12:30:28AM +, Stuart Henderson wrote: I see a tiny little problem with this method... sometimes people send spam from domains whose DNS they control. +1 i think part of the success i experience using SPF as a means to create whitelists is in the fact that i maintain the list of domains i fancy whitelisting. unfortunately, it would be trivial for someone to take advantage of an spf-based automatic whitelist to slip right on thru spamd(8). it's a pisser. No it's not. What might make sense is to alter the script to generate a list of canditates for whitelisting, but only apply any of them after they are manually approved. Dave And that's what I did it for, really. -- With best regards, Gregory Edigarov
Re: autowhitelister for spamd needs testing
Stuart Henderson wrote: On 2009-04-22, Gregory Edigarov wrote: Hello list, I think spamd users would like to try this small utility. Although its development is in the very beginning it does its job quite well for me it was written for the case where a big mass mailer like google is trying to send us mail. The utility notices such mailers and white lists it by adding its allowed nets taken through spf queries to the white list. i.e. it reads output of spamdb, then checks spf records for all greylisted mails and produces 'whitelist.auto' file which can then be used with spamd-setup. it is small, so I put it into attachment. I see a tiny little problem with this method... sometimes people send spam from domains whose DNS they control. See, in the case of spam there is absolutely no silver bullet. Even with my current setup I get 5-10 spam messages into my personal accounts + tons of spam to role accounts like postmaster, hostmaster etc But at some time I got tired of adding the web-frontedned-mail -senders-which-never-repeat-mail-from-the-same-ip to the whitelist. So I wrote this little thingy. -- With best regards, Gregory Edigarov
syslogd listens on udp 514 without -u
Dear List, This is the command i start syslogd with: syslogd -a /var/spool/postfix/dev/log -a /var/empty/dev/log As you can see i ommit the -u flag, but syslogd opens an udp socket on port 514 regardless. I'm running 4.4. Any ideas? Thank You!
Re: PF and H.323 / Videoconference systems
El jue, 23-04-2009 a las 00:34 +0200, Dorian BC Fernando Alvarez schrieb: > > Hi all, > > > > I've trying to configure an OpenBSD box to allow PF to pass > > video-conference traffic through a NATed network without success. > > > > I tried to setup the most basic configuration in order to find out where > > the problem could be. Last test I did, I configured an OpenBSD box with > > two network interfaces ($if_int and $if_ext) and PF enabled. NAT is done > > on $if_ext, and all the traffic is redirected from LAN to the videoconf > > PC. > > > > [VideoConf PC][OpenBSD box]-LAN > > 192.168.10.2/24 .10 172.22.1.200/16 > > > > -> When I try to call (using Netmeeting and other H.323 software) from > > the VideoconfPC to a PC, the other party answers and audio flows only in > > one direction: The PC in the LAN hears what I say, but nothing is heard > > in the VideoConf PC. > > > > <- When I try to call from the LAN to the VideoConf PC (using OBSD's > > external IP as address) Netmeeting says the other party is not > > responding. > > > > Tcpdump does not show any blocked packet and the rdr seems to work > > properly. As you can see bellow, my pf.conf is very simple: > > > > Any ideas? What do you think I've misconfigured? > > > > pf.conf > > - > > # interfaces > > if_ext = "pcn0" > > if_int = "pcn1" > > > > videoconf = 192.168.10.2 > > > > nat log on $if_ext from $videoconf to any -> $if_ext > > rdr log on $if_ext -> $videoconf > > > > pass log all > > -- > > > > Thanks in advance, > > > > Fernando Alvarez > > > Hi Fernando, > > you could google for "H.323 over NAT" and find tons of hits, none of > them giving you an easy answer. The problem is, that the nat device > rewrites the source ip address in the tcp-header, while it does not > inspect the H.323 packet's Protocol data unit which also contains the > source ip address. This is most likely irritating your apps. > > Several workarounds exist: > - use H.323 aware firewall > - stick with a provider that lets you use his session border controller > - check your apps if you could propably go with public stun servers > - give gnu gatekeeper a try, which is in ports > http://www.gnugk.org/h323-proxy.html > - ... (i.e. put netmeeting in a dmz) > > Regards, > Dorian > Hi Dorian, Thanks for your reply. I will take a look to gnu gatekeeper. Is anybody already using it with PF? Should I setup a new OpenBSD machine with a dedicated Internet connection? Best option for me would be to use only one firewall for all the needs (one machine to administrate, less to pay for electricity...) About the DMZ option, you mean not using PF at all, do you? Because if I use OpenBSD and PF, I'm in the same case as before :-\ Regards, Fernando
missing SA name in isakmpd.result
Moin, i have a runnig ipsec setup on an OpenBSD 4.4 box. The isakmpd.conf looks like this: .. [Phase 1] 5.6.7.8=ISAKMP-peer-one [Phase 2] Passive-connections=IPsec-me-one [ISAKMP-peer-one] Phase=1 Local-address=1.2.3.4 Address=5.6.7.8 .. [IPsec-me-one] Phase=2 ISAKMP-peer=ISAKMP-peer-one Configuration=Default-quick-mode Local-ID=Net-me Remote-ID=Net-one .. My problem is the output of isakmpd in isakmpd.result after "echo S > /var/run/isakmpd.fifo". SA name: ISAKMP-peer-one (Phase 1/Responder) src: 1.2.3.4 dst: 5.6.7.8 Lifetime: 86400 seconds ... SA name: (Phase 2) src: 1.2.3.4 dst: 5.6.7.8 Lifetime: 3600 seconds ... Why is the SA for Phase 2 "unnamed" but Phase 1 is named? How do I setup a usefull name for Phase 2? Many thanks Matthias
Re: OpenBSD as Wireless access point
Netgear WG511T. I'm using it at home, it works flawlessly and it took me 45 seconds or so to set up. Manuel - Original Message > From: Parvinder Bhasin > To: misc > Sent: Thursday, April 23, 2009 1:56:47 AM > Subject: OpenBSD as Wireless access point > > All, > > Can someone suggest me a good WORKING wireless PCI or USB card (PCI > preferred) > that I could use for setting up machine as Wireless access point? > I have tried 3-4 cards already and learnt that they were not supported for > the > AP mode. > > Thanks
question about net.inet.carp.preempt
Hallo! I would like to confirm my understanding of how carp works and if the following holds generally true. After having on all participating nodes set to # sysctl -w net.inet.carp.preempt=0 one could change advskew value and actually no carp takeover takes place automatically until issuing on the becoming master node # ifconfig carp-interface-name state master or on becoming backup node # ifconfig carp-interface-name state backup After that the carp master and backup change roles. On the other hand, if all participating nodes are set to # sysctl -w net.inet.carp.preempt=1 then under similar changes in advskew carp takeover happes automatically .i.e master and backup change roles and 'state master' or 'state backup' aint needed to be issued manually. (As merriam-webster says in one case for preemtive being 'marked by the seizing of the initiative; initiated by oneself') Imre PS The scope of this experiment is takeover within paticular carp group (practically between two physical interfaceses) and not for all carp groups as in case with firewall with several physical interfaces.
Re: Live OpenBSD Bootable i386 CD
Hi On Sun, Apr 19, 2009 at 09:59:02AM -0700, new_guy wrote: > I'm interested in building a live, bootable OpenBSD CD for forensics, cloning > and data recovery. Basically, boot and try to automatically bring up any > existing network interface. I'm not interesated in a GUI or play things... > only good, old-fashioned Unix tools like dd, netcat, md5, etc. > > I've googled and found some older info about building live CDs from OpenBSD, > but I wanted to ask misc to see what folks think... good idea or bad? If it > seems a reasonable task and I am able to do it, I'd like to do it so that it > is easy to follow -current. So when -current get's new hardware support, I > can redo my live CD to take advantage of that. The is also (nearly) -current info on this subject: http://www.openbsd-wiki.org/index.php?title=LiveCD Will be updated for 4.5 once it is out. > I think OpenBSD is a good choice for something like this as it is very > simple and straight-forward, but again, I wanted to ask here for other's > opinions before doing much. > > Thanks, > -- Regards, ahb
Re: syslogd listens on udp 514 without -u
On Thu, Apr 23, 2009 at 11:32:18AM +0200, Mate Gabri wrote: | Dear List, | | This is the command i start syslogd with: | | syslogd -a /var/spool/postfix/dev/log -a /var/empty/dev/log | | As you can see i ommit the -u flag, but syslogd opens an udp socket on | port 514 regardless. | | I'm running 4.4. | | Any ideas? I have the great idea of searching the archives ! http://marc.info/?l=openbsd-misc&m=110817759325986&w=2 -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: question about net.inet.carp.preempt
On Thu, Apr 23, 2009 at 12:05 PM, Imre Oolberg wrote: > Hallo! > > I would like to confirm my understanding of how carp works and if the > following holds generally true. > > After having on all participating nodes set to > > # sysctl -w net.inet.carp.preempt=0 AFAIK CARP preempt has meaning only in the context of the machine to which it applies. When CARP preempt is enabled, in a machine with multiple CARP interfaces, whenever one CARP interface fails over, all other CARP interfaces in the machine fail over too. I'm using this on my 2-firewall configuration (active-passive) where each machine has two CARP interfaces: internal interface and Internet-facing interface. Whenever one of the interfaces failover, the other does too. This way, both interfaces are either master or backup, at the same time. This avoids the case where the internal interface is master and the Internet-facing interface is backup (or the opposite). > > one could change advskew value and actually no carp takeover takes place > automatically until issuing on the becoming master node > > # ifconfig carp-interface-name state master > > or on becoming backup node > > # ifconfig carp-interface-name state backup > > After that the carp master and backup change roles. > > On the other hand, if all participating nodes are set to > > # sysctl -w net.inet.carp.preempt=1 > > then under similar changes in advskew carp takeover happes automatically > .i.e master and backup change roles and 'state master' or 'state backup' > aint needed to be issued manually. (As merriam-webster says in one case for > preemtive being 'marked by the seizing of the initiative; initiated by > oneself') > > > Imre > > PS The scope of this experiment is takeover within paticular carp group > (practically between two physical interfaceses) and not for all carp groups > as in case with firewall with several physical interfaces. > > -- http://www.felipe-alfaro.org/blog/disclaimer/
Re: Live OpenBSD Bootable i386 CD
2009/4/23 Andreas Bihlmaier > Hi > > On Sun, Apr 19, 2009 at 09:59:02AM -0700, new_guy wrote: > > I'm interested in building a live, bootable OpenBSD CD for forensics, > cloning > > and data recovery. Basically, boot and try to automatically bring up any > > existing network interface. I'm not interesated in a GUI or play > things... > > only good, old-fashioned Unix tools like dd, netcat, md5, etc. > > > > I've googled and found some older info about building live CDs from > OpenBSD, > > but I wanted to ask misc to see what folks think... good idea or bad? If > it > > seems a reasonable task and I am able to do it, I'd like to do it so that > it > > is easy to follow -current. So when -current get's new hardware support, > I > > can redo my live CD to take advantage of that. > > The is also (nearly) -current info on this subject: > http://www.openbsd-wiki.org/index.php?title=LiveCD > > Will be updated for 4.5 once it is out. > > > I think OpenBSD is a good choice for something like this as it is very > > simple and straight-forward, but again, I wanted to ask here for other's > > opinions before doing much. > Would it be hard to create a LiveCD which helps us boot a LiveUSBstick on systems which do not support boot from USB ? Or perhaps its usefull to boot the same stick on systems with differnt device names ? This way only people who can't boot from USBstick by default need a LiveCD. Just a thought!
Re: syslogd listens on udp 514 without -u
Thank You! Is it possible to disable the listening socket? I want to run syslog-ng on that port but use syslogd for local logging. > On Thu, Apr 23, 2009 at 11:32:18AM +0200, Mate Gabri wrote: > | Dear List, > | > | This is the command i start syslogd with: > | > | syslogd -a /var/spool/postfix/dev/log -a /var/empty/dev/log > | > | As you can see i ommit the -u flag, but syslogd opens an udp socket on > | port 514 regardless. > | > | I'm running 4.4. > | > | Any ideas? > > I have the great idea of searching the archives ! > > http://marc.info/?l=openbsd-misc&m=110817759325986&w=2 > > -- >>[<++>-]<+++.>+++[<-->-]<.>+++[<+ > +++>-]<.>++[<>-]<+.--.[-] > http://www.weirdnet.nl/ > > > !DSPAM:117,49f0425330475061910177!
Re: OpenBSD as Wireless access point
D-Link DWA-520 (it is Atheros-based wireless) works more or less OK. One issue - WPA2 is not working yet :( -- BR, Sergey Khentov 2009/4/23 Parvinder Bhasin : > All, > > Can someone suggest me a good WORKING wireless PCI or USB card (PCI > preferred) that I could use for setting up machine as Wireless access point? > I have tried 3-4 cards already and learnt that they were not supported for > the AP mode. > > Thanks
Problem with slow disk I/O
I'm getting horrible disk performance compared to Ubuntu on my system. I noticed this when extracting ports.tar.gz on the same machine with different OSs (this is something I did a while back to check for a possible hardware problem when OpenBSD crashed upon extracting ports.tar.gz). OpenBSD (ffs): $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user 0m6.95s system Ubuntu (ext3): $ time tar -zxf ports.tar.gz real 0m18.440s user 0m1.212s sys 0m2.596s 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same thing on the exact same hardware! Why the huge difference? Both are default installations, except softdep is turned on. Thanks for any pointers or advice. Thomas OpenBSD 4.5-current (GENERIC.MP) #13: Thu Apr 23 13:00:36 CEST 2009 tpf...@ws.tp76.info:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3152609280 (3006MB) avail mem = 3045097472 (2904MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06b0 (76 entries) bios0: vendor American Megatrends Inc. version "1704" date 11/27/2007 bios0: ASUSTeK Computer INC. P5B-E acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC MCFG OEMB HPET acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) PS2M(S4) EUSB(S4) USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) USB5(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz, 2135.29 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG cpu0: 2MB 64b/line 8-way L2 cache cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz, 2135.04 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG cpu1: 2MB 64b/line 8-way L2 cache ioapic0 at mainbus0 apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 5 (P0P1) acpiprt3 at acpi0: bus 4 (P0P4) acpiprt4 at acpi0: bus -1 (P0P5) acpiprt5 at acpi0: bus -1 (P0P6) acpiprt6 at acpi0: bus 3 (P0P7) acpiprt7 at acpi0: bus 2 (P0P8) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: PWRB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82G965 Host" rev 0x02 ppb0 at pci0 dev 1 function 0 "Intel 82G965 PCIE" rev 0x02: apic 2 int 16 (irq 11) pci1 at ppb0 bus 1 mem address conflict 0xc000/0x1000 vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 7600 GT" rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 16 (irq 11) uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x02: apic 2 int 17 (irq 5) ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x02: apic 2 int 18 (irq 15) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x02: apic 2 int 22 (irq 3) azalia0: codecs: Analog Devices AD1988A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x02: apic 2 int 16 (irq 11) pci2 at ppb1 bus 4 ppb2 at pci0 dev 28 function 3 "Intel 82801H PCIE" rev 0x02: apic 2 int 19 (irq 10) pci3 at ppb2 bus 3 age0 at pci3 dev 0 function 0 "Attansic Technology L1" rev 0xb0: apic 2 int 19 (irq 10), address 00:18:f3:9d:7d:04 atphy0 at age0 phy 0: F1 10/100/1000 PHY, rev. 5 ppb3 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev 0x02: apic 2 int 16 (irq 11) pci4 at ppb3 bus 2 jmb0 at pci4 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x02 ahci0 at jmb0: apic 2 int 16 (irq 11), AHCI 1.0 scsibus0 at ahci0: 32 targets pciide0 at jmb0: DMA, channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 2 int 16 (irq 11) for native-PCI interrupt atapiscsi0 at pciide0 channel 0 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 23 (irq 7) uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x02: apic 2 int 19 (irq 10) uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x02: apic 2 int 18 (irq 15) ehci1 at pci0 dev 29 function 7 "Intel 82801H USB" rev 0x02: apic 2 int 23 (irq 7) usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xf2 pci5 at ppb4 bus 5 re0 at pci5 dev 2 function 0 "D-Link Systems DGE-528T" rev 0x10: RTL8169
Re: Intel 82945GM video on -current?
On Sat, 18 Apr 2009 21:07:16 -0700 (PDT) Fred Snurd wrote: > I've installed the 15 April -current snapshot on an Acer Aspire One > D150-1165 (followed by downloading source & built kernel, userland, & > xenocara), & starting X through auto-detection or from a generated > xorg.conf via startx succeeds in displaying the default fvwm(1) > window manager, but the mouse is frozen. Sometimes I can move it an > inch or so after starting X, but it quickly freezes. I saw mention > of adding the following line in a different thread: > > Option "AccelMethod" "XAA" > > but this didn't change the behavior. I've also substituting in the > vesa(4) driver in the same Device section, but this didn't change the > behavior observed either. Below are dmesg(8) > & /var/log/Xorg.0.log.old outputs. > > Any insight on how to unfreeze the mouse/trackpad would be > appreciated. Unfortunately, you attached the Xorg.0.log file from when you were running the vesa driver, so debugging the intel(4) driver issues is a bit tough. If you can start X, and use ssh from another machine to grab the log file, it would help. Make sure you've created the /dev/drm0 device via MAKEDEV The new intel(4) driver does some (often buggy) rescaling based on the EDIF data presented by the display via DDC. There are two versions of DDC that can be used (v1 & v2), and they can be controlled via your xorg.conf file. Option "DDC" "false" # shut off both v1 and v2 Option "DDC1" "false" # shut off v1 Option "DDC2" "false" # shut off v2 I've had luck with the latter, DDC2 false, on an older intel chipset (845) attached to an old CRT. The new rescaling code in the intel(4) driver is for fixed format (read unforgiving) LCD displays which show garbage when you get the resolution/refresh settings wrong. Needless to say, the driver is not the best at getting things right. -- J.C. Roberts
Re: RAIDframe - screech, smash.
On Thu, 23 Apr 2009 13:33:26 +1000 Aaron Mason wrote: > Hey all, > > Lately I've been using VMware to delve into the murky waters of > creating and maintaining RAID arrays, and I thought I'd get a bit > adventurous. I compiled the kernel with the following config file: > > # cat /usr/src/sys/arch/i386/conf/GENERIC.RAID > > include "arch/i386/conf/GENERIC" > > pseudo-device raid 8 > option RAID_AUTOCONFIG > > # > > The commented out default in the GENERIC file says 4 - I figured if I > changed it to 8, I could get more RAIDs in there for a rather large > nested RAID setup. > You were 21 days too late. -- J.C. Roberts
Re: Problem with slow disk I/O
On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: > I'm getting horrible disk performance compared to Ubuntu on my system. > > I noticed this when extracting ports.tar.gz on the same machine with > different OSs (this is something I did a while back to check for > a possible hardware problem when OpenBSD crashed upon extracting > ports.tar.gz). > > OpenBSD (ffs): > > $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user > 0m6.95s system > > Ubuntu (ext3): > > $ time tar -zxf ports.tar.gz > real0m18.440s > user0m1.212s > sys 0m2.596s > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same > thing on the exact same hardware! Why the huge difference? Both are > default installations, except softdep is turned on. > > Thanks for any pointers or advice. > Try: time tar -zxf ports.tar.gz && sync
Re: Problem with slow disk I/O
On Thu, Apr 23, 2009 at 02:02:06PM +0200, Tobias Ulmer wrote: > On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: > > I'm getting horrible disk performance compared to Ubuntu on my system. > > > > I noticed this when extracting ports.tar.gz on the same machine with > > different OSs (this is something I did a while back to check for > > a possible hardware problem when OpenBSD crashed upon extracting > > ports.tar.gz). > > > > OpenBSD (ffs): > > > > $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user > > 0m6.95s system > > > > Ubuntu (ext3): > > > > $ time tar -zxf ports.tar.gz > > real 0m18.440s > > user 0m1.212s > > sys 0m2.596s > > > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same > > thing on the exact same hardware! Why the huge difference? Both are > > default installations, except softdep is turned on. > > > > Thanks for any pointers or advice. > > > Try: time tar -zxf ports.tar.gz && sync And include the output of mount and show the place where you are untarring. -Otto
Too many partitions?l
I set up a dual booting OpenBSD/ubuntu (only for the audio, I swear!)
install. I made sure to have the Ubuntu installer make an ext2 data
partition for sharing. For some reason OpenBSd couldn't see the ext2
partition until I added it manually. I would like to know why.
Here's my fdisk:
$ fdisk sd0
Disk: sd0 geometry: 19457/255/63 [312581808 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
0: 83 0 1 1 - 2431 254 63 [ 63:39070017 ] Linux files*
1: 05 2432 0 1 - 2674 254 63 [39070080: 3903795 ] Extended DOS
*2: A6 2675 0 1 - 5106 254 63 [42973875:39070080 ] OpenBSD
3: 83 5107 0 1 - 19456 254 63 [82043955: 230532750 ] Linux files*
Offset: 39070080Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
0: 82 2432 1 1 - 2674 254 63 [39070143: 3903732 ] Linux swap
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
$
and original disklabel:
$ disklabel sd0
# Extended partition 1: type 05 start 39070080 size 3903795
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: TOSHIBA MK1637GS
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 19457
total sectors: 312581808
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 1253070 42973875 4.2BSD 2048 163841
b: 1253070 44226945swap
c:3125818080 unused
d: 2329425 45480015 4.2BSD 2048 163841
e: 2329425 47809440 4.2BSD 2048 163841
f: 8530515 50138865 4.2BSD 2048 163841
g: 2104515 58669380 4.2BSD 2048 163841
h: 5285385 60773895 4.2BSD 2048 163841
i: 39070017 63 ext2fs
j: 3180870 66059280 4.2BSD 2048 163841
k: 3903732 39070143 unknown
l: 4209030 69240150 4.2BSD 2048 163841
m: 8594775 73449180 4.2BSD 2048 163841
I used the 'b' command to extend disklabel(8)'s idea of the OpenBSD
area, and then it let me add this:
n:230532750 82043955 ext2fs
and dmesg for good measure:
OpenBSD 4.5-current (GENERIC.MP) #80: Mon Apr 20 12:59:56 MDT 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
real mem = 1064202240 (1014MB)
avail mem = 1020690432 (973MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/30/07, BIOS32 rev. 0 @
0xfcb25, SMBIOS rev. 2.4 @ 0xec000 (40 entries)
bios0: vendor TOSHIBA version "Version 1.50" date 10/30/2007
bios0: TOSHIBA PORTEGE R500
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP SSDT APIC MCFG HPET TCPA SLIC SSDT SSDT
acpi0: wakeup devices USB1(S3) USB3(S3) USB4(S3) EHCI(S3) GLAN(S4)
WLAN(S4) LID_(S4) PWRB(S4) HS87(S4) HS86(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz ("GenuineIntel" 686-class) 1.20 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (PCIB)
acpiprt2 at acpi0: bus 1 (PEX1)
acpiprt3 at acpi0: bus 2 (MPEX)
acpitz0 at acpi0: critical temperature 102 degC
acpicpu0 at acpi0
acpicpu1 at acpi0
acpibtn0 at acpi0: LID_
acpibat0 at acpi0: BAT1 model "G71C00086210" serial 000796 type
Li-ION oem "0"
acpibtn1 at acpi0: PWRB
acpiac0 at acpi0: AC unit online
acpidock at acpi0 not configured
acpivideo at acpi0 not configured
bios0: ROM list: 0xc/0x1 0xe/0x1!
cpu0: unknown Enhanced SpeedStep CPU, msr 0x060b090e0600090e
cpu0: using only highest and
AX25
Hello all OpenBSDers! Is there AX25 (ham radio) support in OpenBSD? Regards, Coert OpenBSD newbie
Re: Live OpenBSD Bootable i386 CD
On Thu, 23 Apr 2009 13:10:23 +0200, Frans Haarman wrote > Would it be hard to create a LiveCD which helps us boot a > LiveUSBstick on systems which do not support boot from USB ? Not at all. You could do it yourself, by creating a bootable CD and using boot> boot -a And then selecting your root partition just before the kernel passes control to init(8).
Re: Problem with slow disk I/O
> -Urspr|ngliche Nachricht- > Von: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] > Im Auftrag von Tobias Ulmer > Gesendet: Donnerstag, 23. April 2009 14:02 > An: Thomas Pfaff > Cc: misc@openbsd.org > Betreff: Re: Problem with slow disk I/O > > > On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: > > I'm getting horrible disk performance compared to Ubuntu on > my system. > > > > I noticed this when extracting ports.tar.gz on the same > machine with > > different OSs (this is something I did a while back to check for a > > possible hardware problem when OpenBSD crashed upon extracting > > ports.tar.gz). > > > > OpenBSD (ffs): > > > > $ time tar -zxf ports.tar.gz 0m59.90s real > 0m1.00s user 0m6.95s system > > > > Ubuntu (ext3): > > > > $ time tar -zxf ports.tar.gz > > real 0m18.440s > > user 0m1.212s > > sys 0m2.596s > > > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the > exact same > > thing on the exact same hardware! Why the huge difference? > Both are > > default installations, except softdep is turned on. > > > > Thanks for any pointers or advice. > > > Try: time tar -zxf ports.tar.gz && sync > > better use parenthesis: time ( tar -zxf ports.tar.gz && sync ) Compare # time sleep 1 && sleep 5 0m1.01s real 0m0.00s user 0m0.01s system to # time ( sleep 1 && sleep 5 ) 0m6.01s real 0m0.00s user 0m0.03s system Christoph
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 14:13:18 +0200 Otto Moerbeek wrote: > On Thu, Apr 23, 2009 at 02:02:06PM +0200, Tobias Ulmer wrote: > > > On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: > > > I'm getting horrible disk performance compared to Ubuntu on my system. > > > > > > I noticed this when extracting ports.tar.gz on the same machine with > > > different OSs (this is something I did a while back to check for > > > a possible hardware problem when OpenBSD crashed upon extracting > > > ports.tar.gz). > > > > > > OpenBSD (ffs): > > > > > > $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user > > > 0m6.95s system > > > > > > Ubuntu (ext3): > > > > > > $ time tar -zxf ports.tar.gz > > > real0m18.440s > > > user0m1.212s > > > sys 0m2.596s > > > > > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same > > > thing on the exact same hardware! Why the huge difference? Both are > > > default installations, except softdep is turned on. > > > > > > Thanks for any pointers or advice. > > > > > Try: time tar -zxf ports.tar.gz && sync > > And include the output of mount and show the place where you are untarring. > $ mount /dev/wd0a on / type ffs (local, softdep) /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) $ pwd /home/tpfaff $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result 1m2.66s real 0m1.09s user 0m6.85s system $ time rm -rf ports 0m15.20s real 0m0.15s user 0m1.42s system
Re: Problem with slow disk I/O
On Thu, Apr 23, 2009 at 05:19:34PM +0200, Thomas Pfaff wrote: > On Thu, 23 Apr 2009 14:13:18 +0200 > Otto Moerbeek wrote: > > > On Thu, Apr 23, 2009 at 02:02:06PM +0200, Tobias Ulmer wrote: > > > > > On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: > > > > I'm getting horrible disk performance compared to Ubuntu on my system. > > > > > > > > I noticed this when extracting ports.tar.gz on the same machine with > > > > different OSs (this is something I did a while back to check for > > > > a possible hardware problem when OpenBSD crashed upon extracting > > > > ports.tar.gz). > > > > > > > > OpenBSD (ffs): > > > > > > > > $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user > > > > 0m6.95s system > > > > > > > > Ubuntu (ext3): > > > > > > > > $ time tar -zxf ports.tar.gz > > > > real 0m18.440s > > > > user 0m1.212s > > > > sys 0m2.596s > > > > > > > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same > > > > thing on the exact same hardware! Why the huge difference? Both are > > > > default installations, except softdep is turned on. > > > > > > > > Thanks for any pointers or advice. > > > > > > > Try: time tar -zxf ports.tar.gz && sync > > > > And include the output of mount and show the place where you are untarring. > > > > $ mount > /dev/wd0a on / type ffs (local, softdep) > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > > $ pwd > /home/tpfaff > > $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result > 1m2.66s real 0m1.09s user 0m6.85s system > $ time rm -rf ports > 0m15.20s real 0m0.15s user 0m1.42s system and on linux? [ remembered the () thing the very second i hit 'y' ;). I figured you're clever enough... ]
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 15:27:42 +0200 Thomas Pfaff wrote: > I'm getting horrible disk performance compared to Ubuntu on my system. > > I noticed this when extracting ports.tar.gz on the same machine with > different OSs (this is something I did a while back to check for > a possible hardware problem when OpenBSD crashed upon extracting > ports.tar.gz). This is on different hardware now, BTW (not the one that crashed).
Re: Problem with slow disk I/O
Thomas Pfaff wrote: On Thu, 23 Apr 2009 15:27:42 +0200 Thomas Pfaff wrote: I'm getting horrible disk performance compared to Ubuntu on my system. I noticed this when extracting ports.tar.gz on the same machine with different OSs (this is something I did a while back to check for a possible hardware problem when OpenBSD crashed upon extracting ports.tar.gz). This is on different hardware now, BTW (not the one that crashed). Is your chipset revision recognized by OpenBSD? I had a similar problem with a new motherboard and upgrading to the latest snapshot resolved it. A dmesg would be helpful. Regards,
Re: Too many partitions?l
> I set up a dual booting OpenBSD/ubuntu (only for the audio, I swear!) > install. I made sure to have the Ubuntu installer make an ext2 data > partition for sharing. For some reason OpenBSd couldn't see the ext2 > partition until I added it manually. I would like to know why. The exact way that this works is not well documented. Let me explain it here. I don't want to add this to any manual page, sorry. A MBR is found. If inside it we find a A6 partition we look for a disklabel at the right offset. If that disklabel is validated (checksums, etc) then we use that disklabel as read from the disk, exactly as it is. If any of the above fails then we generate a spoofed label. This is filled with information that we find from the MBR. (On other architectures without an MBR, we may also do some other kinds of spoofing). If you read a spoofed label, and modify it and write it out, it becomes a real label for the next boot, as described above. New MBR partitions will not be "noticed". > After adding partition 'n' I can mount and use my data drive fine. My > only guess was that I had too many partitions, but the FAQ says "up to > 'p'") which is greater than 'n' so that's not it. So any ideas why > OpenBSD didn't pick up the data partition on it's own? If you look > closely you'll see that it picked up the ubuntu root drive (as sd0i) > which was also not within the original disklabel(8) "b" limits. It was there originally. The other one was not. Hmm, there may be another problem in that it will only spoof 3 partitions (it should probably be able to spoof more).
Re: OpenBSD as Wireless access point
On Wed, Apr 22, 2009 at 4:56 PM, Parvinder Bhasin wrote: > All, > > Can someone suggest me a good WORKING wireless PCI or USB card (PCI > preferred) that I could use for setting up machine as Wireless access point? > I have tried 3-4 cards already and learnt that they were not supported for > the AP mode. > Linksys wmp54g seems to be working fine.
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 09:54:15 -0400 gjones wrote: > Thomas Pfaff wrote: > > On Thu, 23 Apr 2009 15:27:42 +0200 > > This is on different hardware now, BTW (not the one that crashed). > > > Is your chipset revision recognized by OpenBSD? I had a similar problem > with a new motherboard and upgrading to the latest snapshot resolved > it. A dmesg would be helpful. I provided that in my first post ;-)
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 15:31:58 +0200 Tobias Ulmer wrote: [...] > > > > Try: time tar -zxf ports.tar.gz && sync > > > > > > And include the output of mount and show the place where you are > > > untarring. > > > > > > > $ mount > > /dev/wd0a on / type ffs (local, softdep) > > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > > > > $ pwd > > /home/tpfaff > > > > $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result > > 1m2.66s real 0m1.09s user 0m6.85s system > > $ time rm -rf ports > > 0m15.20s real 0m0.15s user 0m1.42s system > > and on linux? First on Ubuntu: Script started on Thu 23 Apr 2009 03:50:27 PM CEST ~$ time (tar -zxf ports.tar.gz && sync) real0m47.784s user0m1.576s sys 0m5.024s ~$ time (rm -rf ports && sync) real0m1.883s user0m0.076s sys 0m1.664s time (tar -zxf ports.tar.gz && sync) real0m20.652s user0m1.240s sys 0m2.592s ~$ time (rm -rf && sync) real0m0.003s user0m0.004s sys 0m0.004s ~$ time tar -zxf ports.tar.gz real0m11.513s user0m1.268s sys 0m2.772s ~$ time rm -rf ports real0m1.752s user0m0.100s sys 0m1.648s ~$ time tar -zxf ports.tar.gz real0m14.400s user0m1.352s sys 0m2.560s ~$ time rm -rf ports real0m1.756s user0m0.076s sys 0m1.684s ~$ mount # watch your eyes! /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) udev on /dev type tmpfs (rw,mode=0755) devshm on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw) securityfs on /sys/kernel/security type securityfs (rw) gvfs-fuse-daemon on /home/tpfaff/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=tpfaff) ~$ pwd /home/tpfaff ~$ exit Script done on Thu 23 Apr 2009 03:53:20 PM CEST Then the same commands on OpenBSD: Script started on Thu Apr 23 17:55:53 2009 $ time (tar -zxf ports.tar.gz && sync) 1m2.62s real 0m1.15s user 0m7.15s system $ time (rm -rf ports && sync) 0m14.24s real 0m0.14s user 0m1.53s system $ time (tar -zxf ports.tar.gz && sync) 1m1.37s real 0m1.31s user 0m7.18s system $ time (rm -rf ports && sync) 0m14.72s real 0m0.12s user 0m1.82s system $ time tar -zxf ports.tar.gz 1m3.39s real 0m1.08s user 0m6.69s system $ time rm -rf ports 0m15.41s real 0m0.12s user 0m1.38s system $ time tar -zxf ports.tar.gz 1m2.62s real 0m1.19s user 0m6.80s system $ time rm -rf ports 0m15.63s real 0m0.10s user 0m1.79s system $ mount /dev/wd0a on / type ffs (local, softdep) /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) $ pwd /home/tpfaff $ exit Script done on Thu Apr 23 18:02:13 2009
Re: OpenBSD as Wireless access point
Rt 73USB working fine here too ;-) rum0 at uhub0 port 1 "Ralink 802.11 bg WLAN" rev 2.00/0.01 addr 2 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:1f:1f:10:b6:39 2009/4/23 Gerald Chudyk > On Wed, Apr 22, 2009 at 4:56 PM, Parvinder Bhasin > wrote: > > All, > > > > Can someone suggest me a good WORKING wireless PCI or USB card (PCI > > preferred) that I could use for setting up machine as Wireless access > point? > > I have tried 3-4 cards already and learnt that they were not supported > for > > the AP mode. > > > > Linksys wmp54g seems to be working fine.
Re: Broadcom BCM5784 rev 0x10 not configured, but listed as supported within LAN devices.. (4.4 / 4.5 k
Brad,
Please also paste us your code... ? Has it been tested?
Also.. I thought this was already supported by the 4.4 kernel as per the
man page for bge, it says "Support for BCM57xx" ??
Thank you.
Jose
On Wed, 22 Apr 2009 17:45:46 -0400, Brad wrote:
> On Tuesday 21 April 2009 18:46:58 Brad wrote:
>> Hi,
>>
>> with regard to your post this chipset is not supported yet.
>>
>> I've had a diff sitting around for awhile to start on support for
>> this but it is really new hardware and I don't have anything to
>> test with. If you could build a kernel and try it out on the
>> system in question and provide me with the resulting dmesg that
>> would be great. It won't actually fully attach yet but just try
>> to and print out some additional debug info for myself.
>
> I can also provide you with a pre-built kernel if you would like that.
>
>>
>> Index: if_bge.c
>> ===
>> RCS file: /cvs/src/sys/dev/pci/if_bge.c,v
>> retrieving revision 1.261
>> diff -u -p -r1.261 if_bge.c
>> --- if_bge.c 27 Jan 2009 09:17:51 - 1.261
>> +++ if_bge.c 21 Apr 2009 22:39:30 -
>> @@ -242,6 +242,7 @@ const struct pci_matchid bge_devices[] =
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5720 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5721 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5722 },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5723 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5750 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5750M },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5751 },
>> @@ -257,10 +258,15 @@ const struct pci_matchid bge_devices[] =
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5755 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5755M },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5756 },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5761 },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5761E },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5764 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5780 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5780S },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5781 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5782 },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5784 },
>> +{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5785 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5786 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5787 },
>> { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM5787F },
>> @@ -290,6 +296,9 @@ const struct pci_matchid bge_devices[] =
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5714|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5752|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5755|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5761|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5784|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5785|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5787|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5906)
>>
>> @@ -300,6 +309,9 @@ const struct pci_matchid bge_devices[] =
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5714|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5752|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5755|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5761|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5784|| \
>> + BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5785|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5787|| \
>> BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5906)
>>
>> @@ -1751,8 +1763,13 @@ bge_blockinit(struct bge_softc *sc)
>> /* Turn on send BD completion state machine */
>> CSR_WRITE_4(sc, BGE_SBDC_MODE, BGE_SBDCMODE_ENABLE);
>>
>> +val = BGE_SDCMODE_ENABLE;
>> +
>> +if (BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_BCM5761)
>> +val |= BGE_SDCMODE_CDELAY;
>> +
>> /* Turn on send data completion state machine */
>> -CSR_WRITE_4(sc, BGE_SDC_MODE, BGE_SDCMODE_ENABLE);
>> +CSR_WRITE_4(sc, BGE_SDC_MODE, val);
>>
>> /* Turn on send data initiator state machine */
>> CSR_WRITE_4(sc, BGE_SDI_MODE, BGE_SDIMODE_ENABLE);
>> @@ -1896,10 +1913,22 @@ bge_attach(struct device *parent, struct
>> /*
>> * Save ASIC rev.
>> */
>> -
>> sc->bge_chipid =
>> -pci_conf_read(pc, pa->pa_tag, BGE_PCI_MISC_CTL) &
>> -BGE_PCIMISCCTL_ASICREV;
>> +pci_conf_read(pc, pa->pa_tag, BGE_PCI_MISC_CTL) &
>> +BGE_PCIMISCCTL_ASICREV;
>> +
>> +printf(", chipid 0x%x asicrev 0x%x", sc->bge_chipid,
>> BGE_ASICREV(sc->bge_chipid)); +
>> +if (BGE_ASICREV(sc->bge_chipid) == BGE_ASICREV_USE_P
sudo won't work with login_fingerprint
Hi! I've set up this login_fingerprint port and it is working fine in console logins and with `su`, but with sudo I can't seem to get it to work. I've modified my /etc/login.conf like this: # Default allowed authentication styles auth-defaults:auth=-fingerprint,passwd,skey:\ :x-fingerprint=7: I've just added the fingerprint stuff. Now when running sudo, and typing in my password 3 times: $ sudo -l -fingerprint: challenge not supported sudo password(daniell): -fingerprint: response not supported Sorry, try again. -fingerprint: challenge not supported sudo password(daniell): -fingerprint: response not supported Sorry, try again. -fingerprint: challenge not supported sudo password(daniell): -fingerprint: response not supported Sorry, try again. sudo: 3 incorrect password attempts With `sudo -a` I can specify the "passwd" type, and can sudo with my password, so no big problem, I'm just wondering what special configuration is needed for sudo to work with this auth type. Any idead would be appreciated, thanks! Daniel -- LIVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
Two monitors with Intel GM45?
Hi all, I don't try it yet so you can kick my ass if I'm missing something ;-) Is there a possibility to just use xrandr(1) for switching between outputs if my X work out of the box without xorg.conf? Because I have 'not configured' for my Intel GM45.I read that support for this chipset isn't full yet.When I have laptop in docking station I have on HDMI-1 Dell E2209W with optimal resolution 1680x1050/60Hz,but both (HDMI-1 and LVDS) are working on 1024x768/60Hz which isn't so much usefull. $ dmesg | grep vga vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) intagp0 at vga1 inteldrm0 at vga1: apic 2 int 16 (irq 11) $ dmesg | grep GM45 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured $ $ xrandr --verbose Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440 VGA disconnected (normal left inverted right x axis y axis) Identifier: 0x3b Timestamp: -753984668 Subpixel: unknown Clones: CRTCs: 0 1 LVDS connected 1440x900+0+0 (0x40) normal (normal left inverted right x axis y axis) 304mm x 190mm Identifier: 0x3c Timestamp: -753984668 Subpixel: horizontal rgb Clones: CRTC: 1 CRTCs: 1 EDID_DATA: 0000320c4001 00120103901e13780ad7859359548c29 2250540001010101010101010101 010101010101b027a08051841a303020 360030be101ab027a0805184e731 3020aa0030be101a00fe0043 54303038803134315750320a 0002010a202000ea PANEL_FITTING: full supported: center full_aspect full BACKLIGHT_CONTROL: combination supported: native legacy combination kernel BACKLIGHT: 101 (0x0065) range: (0,101) 1440x900 (0x40) 101.6MHz +HSync -VSync *current +preferred h: width 1440 start 1488 end 1520 total 1824 skew0 clock 55.7KHz v: height 900 start 903 end 909 total 926 clock 60.2Hz 1440x900 (0x41) 101.6MHz +HSync -VSync h: width 1440 start 1488 end 1520 total 1824 skew0 clock 55.7KHz v: height 900 start 910 end 920 total 1387 clock 40.2Hz 1024x768 (0x42) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x43) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x44) 36.0MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz 640x480 (0x45) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz HDMI-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x3d Timestamp: -753984668 Subpixel: unknown Clones: HDMI-2 CRTCs: 0 1 HDMI-2 disconnected (normal left inverted right x axis y axis) Identifier: 0x3e Timestamp: -753984668 Subpixel: unknown Clones: HDMI-1 CRTCs: 0 1 TV disconnected (normal left inverted right x axis y axis) Identifier: 0x3f Timestamp: -753984668 Subpixel: unknown Clones: CRTCs: 0 1 BOTTOM: 37 (0x0025) range: (0,100) RIGHT: 46 (0x002e) range: (0,100) TOP: 36 (0x0024) range: (0,100) LEFT: 54 (0x0036) range: (0,100) TV_FORMAT: NTSC-M supported: NTSC-M NTSC-443 NTSC-J PAL-M PAL-NPAL $ $ uname -a OpenBSD FQDN 4.5 GENERIC.MP#78 i386 $ -- http://www.openbsd.org/lyrics.html
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 17:25:57 +0200 Jan Stary wrote: > On Apr 23 18:09:55, Thomas Pfaff wrote: > > First on Ubuntu: > > > /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) > > ~$ time (tar -zxf ports.tar.gz && sync) > > real0m47.784s > > user0m1.576s > > sys 0m5.024s > > > Then the same commands on OpenBSD: > > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > > $ time (tar -zxf ports.tar.gz && sync) > > 1m2.62s real 0m1.15s user 0m7.15s system > > So you have ~52 seconds on ext3 mounted 'realtime' (whatever that means), > versus ~63 seconds on ffs mounted with 'softdep'. > What was the problem again? That I cannot get the job done in less than a minute on OpenBSD while on Linux it takes only 18 seconds. > What happens with 'noatime' on the ffs partition? Script started on Thu Apr 23 19:35:37 2009 $ mount /dev/wd0a on / type ffs (local, softdep) /dev/wd0k on /home type ffs (local, noatime, nodev, nosuid, softdep) fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) $ pwd /home/tpfaff $ time tar -xzf ports.tar.gz 1m3.92s real 0m0.97s user 0m7.09s system $ time rm -rf ports 0m15.34s real 0m0.16s user 0m1.43s system $ exit Script done on Thu Apr 23 19:37:20 2009
IPsec Windows Vista client - OpenBSD, NAT-T problem
Hello, I'm trying to learn how to setup IPsec connection, therefore I stared with quite simple settings. I'd like to allow clients from outside to connect my OpenBSD server through encrypted channel, however I came across some difficulties I'm not able to solve. scheme of my environment is following: client (Windows Vista) - NAT (mikrotik) --- internet --- (public IP) OpenBSD I decided to use PSK to simplify my settings: my ipsec.conf file contains: ike passive from any to any \ main auth hmac-sha1 enc aes group modp1024 \ quick auth hmac-sha1 enc aes psk my_key From my understanding this should allow all clients to connect my server via encrypted channel. I started isakmpd and setup a client for Windows Vista - for beginning I used TheGreenBow IPSec VPN Client. After a few minutes I had working environment so I deiced to use native Windows Vista IPsec client and here is my problem: Vista client is not able to communicate with my OpenBSD server for some reason I do not see. I was checking settings of the client and did not find any problem, then I just tried to shutdown isakmpd and to start it again with -T flag without NAT-T support. Immediately after this change, Vista client successfully connected to OpenBSD and communication was encrypted and working. If I start isakmpd again with NAT-T support then Vista can not negotiate IPsec with OpenBSD. I think NAT-T is important for me, because if I understand it well, it should allow IPsec communication for more clients behind same NAT simultaneously, however from some reason if I allow NAT-T support in OpenBSD, Vista can not reach the server anymore. TheGreenBow IPSec VPN Client works just fine even with NAT-T. I'm out of ideas and I'd like to kindly ask you for any help. I started isakmpd with -L switch to provide some additional information for both clients (working GreenBow and Vista client) Best regards MK Vista- NAT-T not working: 0:25:01.013804 84.42.224.147.500 > 217.197.149.135.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1-> msgid: len: 232 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 24 payload: VENDOR len: 20 (supports NAT-T, RFC 3947) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 [ttl 0] (id 1, len 260) 00:25:01.014657 217.197.149.135.500 > 84.42.224.147.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: len: 188 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 20 (supports OpenBSD-4.0) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 (supports v3 NAT-T, draft-ietf-ipsec-nat-t-ike-03) payload: VENDOR len: 20 (supports NAT-T, RFC 3947) payload: VENDOR len: 20 (supports DPD v1.0) [ttl 0] (id 1, len 216) 00:25:01.078015 84.42.224.147.500 > 217.197.149.135.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: len: 260 payload: KEY_EXCH len: 132 payload: NONCE len: 52 payload: NAT-D len: 24 payload: NAT-D len: 24 [ttl 0] (id 1, len 288) 00:25:01.113648 217.197.149.135.4500 > 84.42.224.147.4500: [udp sum ok] udpencap: isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: len: 260 payload: KEY_EXCH len: 132 payload: NONCE len: 52 payload: NAT-D len: 24 payload: NAT-D len: 24 [ttl 0] (id 1, len 292) 00:25:01.175077 84.42.224.147.4500 > 217.197.149.135.45
Re: Two monitors with Intel GM45?
$ more .xinitrc /usr/X11R6/bin/xset b /usr/X11R6/bin/xset m 10/0 /usr/X11R6/bin/xset fp+ /usr/local/lib/X11/fonts/terminus /usr/X11R6/bin/xset fp+ /usr/local/openoffice/share/fonts/truetype xrandr --output LVDS --auto xrandr --output VGA --auto --right-of LVDS scrotwm On Thu, Apr 23, 2009 at 05:40:38PM +0200, Tom Bodr wrote: > Hi all, > > I don't try it yet so you can kick my ass if I'm missing something ;-) > > Is there a possibility to just use xrandr(1) for switching between > outputs if my X work out of the box without xorg.conf? > Because I have 'not configured' for my Intel GM45.I read that support > for this chipset isn't full yet.When I have laptop in > docking station I have on HDMI-1 Dell E2209W with optimal resolution > 1680x1050/60Hz,but both (HDMI-1 and LVDS) > are working on 1024x768/60Hz which isn't so much usefull. > > $ dmesg | grep vga > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > intagp0 at vga1 > inteldrm0 at vga1: apic 2 int 16 (irq 11) > $ dmesg | grep GM45 > pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured > $ > > $ xrandr --verbose > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440 > VGA disconnected (normal left inverted right x axis y axis) > Identifier: 0x3b > Timestamp: -753984668 > Subpixel: unknown > Clones: > CRTCs: 0 1 > LVDS connected 1440x900+0+0 (0x40) normal (normal left inverted right > x axis y axis) 304mm x 190mm > Identifier: 0x3c > Timestamp: -753984668 > Subpixel: horizontal rgb > Clones: > CRTC: 1 > CRTCs: 1 > EDID_DATA: > 0000320c4001 > 00120103901e13780ad7859359548c29 > 2250540001010101010101010101 > 010101010101b027a08051841a303020 > 360030be101ab027a0805184e731 > 3020aa0030be101a00fe0043 > 54303038803134315750320a > 0002010a202000ea > PANEL_FITTING: full > supported: center full_aspect full > BACKLIGHT_CONTROL: combination > supported: native legacy combination kernel > BACKLIGHT: 101 (0x0065) range: (0,101) > 1440x900 (0x40) 101.6MHz +HSync -VSync *current +preferred > h: width 1440 start 1488 end 1520 total 1824 skew0 clock > 55.7KHz > v: height 900 start 903 end 909 total 926 clock 60.2Hz > 1440x900 (0x41) 101.6MHz +HSync -VSync > h: width 1440 start 1488 end 1520 total 1824 skew0 clock > 55.7KHz > v: height 900 start 910 end 920 total 1387 clock 40.2Hz > 1024x768 (0x42) 65.0MHz -HSync -VSync > h: width 1024 start 1048 end 1184 total 1344 skew0 clock > 48.4KHz > v: height 768 start 771 end 777 total 806 clock 60.0Hz > 800x600 (0x43) 40.0MHz +HSync +VSync > h: width 800 start 840 end 968 total 1056 skew0 clock > 37.9KHz > v: height 600 start 601 end 605 total 628 clock 60.3Hz > 800x600 (0x44) 36.0MHz +HSync +VSync > h: width 800 start 824 end 896 total 1024 skew0 clock > 35.2KHz > v: height 600 start 601 end 603 total 625 clock 56.2Hz > 640x480 (0x45) 25.2MHz -HSync -VSync > h: width 640 start 656 end 752 total 800 skew0 clock > 31.5KHz > v: height 480 start 490 end 492 total 525 clock 59.9Hz > HDMI-1 disconnected (normal left inverted right x axis y axis) > Identifier: 0x3d > Timestamp: -753984668 > Subpixel: unknown > Clones: HDMI-2 > CRTCs: 0 1 > HDMI-2 disconnected (normal left inverted right x axis y axis) > Identifier: 0x3e > Timestamp: -753984668 > Subpixel: unknown > Clones: HDMI-1 > CRTCs: 0 1 > TV disconnected (normal left inverted right x axis y axis) > Identifier: 0x3f > Timestamp: -753984668 > Subpixel: unknown > Clones: > CRTCs: 0 1 > BOTTOM: 37 (0x0025) range: (0,100) > RIGHT: 46 (0x002e) range: (0,100) > TOP: 36 (0x0024) range: (0,100) > LEFT: 54 (0x0036) range: (0,100) > TV_FORMAT: NTSC-M > supported: NTSC-M NTSC-443 NTSC-J PAL-M >PAL-NPAL > $ > > $ uname -a > OpenBSD FQDN 4.5 GENERIC.MP#78 i386 > $ > > -- > http://www.openbsd.org/lyrics.html
Re: Two monitors with Intel GM45?
2009/4/23 Toma Bod ar : > Hi all, > > I don't try it yet so you can kick my ass if I'm missing something ;-) > > Is there a possibility to just use xrandr(1) for switching between > outputs if my X work out of the box without xorg.conf? > Because I have 'not configured' for my Intel GM45.I read that support > for this chipset isn't full yet.When I have laptop in > docking station I have on HDMI-1 Dell E2209W with optimal resolution > 1680x1050/60Hz,but both (HDMI-1 and LVDS) > are working on 1024x768/60Hz which isn't so much usefull. > > $ dmesg | grep vga > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > intagp0 at vga1 > inteldrm0 at vga1: apic 2 int 16 (irq 11) > $ dmesg | grep GM45 > pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured > $ > > $ xrandr --verbose > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440 > VGA disconnected (normal left inverted right x axis y axis) >Identifier: 0x3b >Timestamp: -753984668 >Subpixel: unknown >Clones: >CRTCs: 0 1 > LVDS connected 1440x900+0+0 (0x40) normal (normal left inverted right > x axis y axis) 304mm x 190mm >Identifier: 0x3c >Timestamp: -753984668 >Subpixel: horizontal rgb >Clones: >CRTC: 1 >CRTCs: 1 >EDID_DATA: >0000320c4001 >00120103901e13780ad7859359548c29 >2250540001010101010101010101 >010101010101b027a08051841a303020 >360030be101ab027a0805184e731 >3020aa0030be101a00fe0043 >54303038803134315750320a >0002010a202000ea >PANEL_FITTING: full >supported: center full_aspect full >BACKLIGHT_CONTROL: combination >supported: native legacy combination kernel >BACKLIGHT: 101 (0x0065) range: (0,101) > 1440x900 (0x40) 101.6MHz +HSync -VSync *current +preferred >h: width 1440 start 1488 end 1520 total 1824 skew0 clock 55.7KHz >v: height 900 start 903 end 909 total 926 clock 60.2Hz > 1440x900 (0x41) 101.6MHz +HSync -VSync >h: width 1440 start 1488 end 1520 total 1824 skew0 clock 55.7KHz >v: height 900 start 910 end 920 total 1387 clock 40.2Hz > 1024x768 (0x42) 65.0MHz -HSync -VSync >h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz >v: height 768 start 771 end 777 total 806 clock 60.0Hz > 800x600 (0x43) 40.0MHz +HSync +VSync >h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz >v: height 600 start 601 end 605 total 628 clock 60.3Hz > 800x600 (0x44) 36.0MHz +HSync +VSync >h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz >v: height 600 start 601 end 603 total 625 clock 56.2Hz > 640x480 (0x45) 25.2MHz -HSync -VSync >h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz >v: height 480 start 490 end 492 total 525 clock 59.9Hz > HDMI-1 disconnected (normal left inverted right x axis y axis) >Identifier: 0x3d >Timestamp: -753984668 >Subpixel: unknown >Clones: HDMI-2 >CRTCs: 0 1 > HDMI-2 disconnected (normal left inverted right x axis y axis) >Identifier: 0x3e >Timestamp: -753984668 >Subpixel: unknown >Clones: HDMI-1 >CRTCs: 0 1 > TV disconnected (normal left inverted right x axis y axis) >Identifier: 0x3f >Timestamp: -753984668 >Subpixel: unknown >Clones: >CRTCs: 0 1 >BOTTOM: 37 (0x0025) range: (0,100) >RIGHT: 46 (0x002e) range: (0,100) >TOP: 36 (0x0024) range: (0,100) >LEFT: 54 (0x0036) range: (0,100) >TV_FORMAT: NTSC-M >supported: NTSC-M NTSC-443 NTSC-J PAL-M > PAL-NPAL > $ > > $ uname -a > OpenBSD FQDN 4.5 GENERIC.MP#78 i386 > $ > Below is my xorg.conf. I have a dual head set up using xrandr and the same intel chip. Also, I've been using a diff that owain@ submitted for testing a while ago and it's done me well. Perhaps you should try it out, too. Here's a link: http://marc.info/?l=openbsd-tech&m=123307709522306&w=2 Good luck! -Neal 1 Section "ServerLayout" 2 Identifier "X.org Configured" 3 Screen 0 "Screen0" 0 0 4 InputDevice"Mouse0" "CorePointer" 5 InputDevice"Keyboard0" "CoreKeyboard" 6 EndSection 7 8 Section "Files" 9
Re: Two monitors with Intel GM45?
I forgot this piece from xorg.conf: ... standard xorg stuff ... Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Depth 24 Virtual 3600 1200 EndSubSection EndSection On Thu, Apr 23, 2009 at 10:52:09AM -0500, Marco Peereboom wrote: > $ more .xinitrc > > /usr/X11R6/bin/xset b > /usr/X11R6/bin/xset m 10/0 > /usr/X11R6/bin/xset fp+ /usr/local/lib/X11/fonts/terminus > /usr/X11R6/bin/xset fp+ /usr/local/openoffice/share/fonts/truetype > xrandr --output LVDS --auto > xrandr --output VGA --auto --right-of LVDS > scrotwm > > On Thu, Apr 23, 2009 at 05:40:38PM +0200, Tom Bodr wrote: > > Hi all, > > > > I don't try it yet so you can kick my ass if I'm missing something ;-) > > > > Is there a possibility to just use xrandr(1) for switching between > > outputs if my X work out of the box without xorg.conf? > > Because I have 'not configured' for my Intel GM45.I read that support > > for this chipset isn't full yet.When I have laptop in > > docking station I have on HDMI-1 Dell E2209W with optimal resolution > > 1680x1050/60Hz,but both (HDMI-1 and LVDS) > > are working on 1024x768/60Hz which isn't so much usefull. > > > > $ dmesg | grep vga > > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > > intagp0 at vga1 > > inteldrm0 at vga1: apic 2 int 16 (irq 11) > > $ dmesg | grep GM45 > > pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 > > vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > > "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured > > $ > > > > $ xrandr --verbose > > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440 > > VGA disconnected (normal left inverted right x axis y axis) > > Identifier: 0x3b > > Timestamp: -753984668 > > Subpixel: unknown > > Clones: > > CRTCs: 0 1 > > LVDS connected 1440x900+0+0 (0x40) normal (normal left inverted right > > x axis y axis) 304mm x 190mm > > Identifier: 0x3c > > Timestamp: -753984668 > > Subpixel: horizontal rgb > > Clones: > > CRTC: 1 > > CRTCs: 1 > > EDID_DATA: > > 0000320c4001 > > 00120103901e13780ad7859359548c29 > > 2250540001010101010101010101 > > 010101010101b027a08051841a303020 > > 360030be101ab027a0805184e731 > > 3020aa0030be101a00fe0043 > > 54303038803134315750320a > > 0002010a202000ea > > PANEL_FITTING: full > > supported: center full_aspect full > > BACKLIGHT_CONTROL: combination > > supported: native legacy combination kernel > > BACKLIGHT: 101 (0x0065) range: (0,101) > > 1440x900 (0x40) 101.6MHz +HSync -VSync *current +preferred > > h: width 1440 start 1488 end 1520 total 1824 skew0 clock > > 55.7KHz > > v: height 900 start 903 end 909 total 926 clock > > 60.2Hz > > 1440x900 (0x41) 101.6MHz +HSync -VSync > > h: width 1440 start 1488 end 1520 total 1824 skew0 clock > > 55.7KHz > > v: height 900 start 910 end 920 total 1387 clock > > 40.2Hz > > 1024x768 (0x42) 65.0MHz -HSync -VSync > > h: width 1024 start 1048 end 1184 total 1344 skew0 clock > > 48.4KHz > > v: height 768 start 771 end 777 total 806 clock > > 60.0Hz > > 800x600 (0x43) 40.0MHz +HSync +VSync > > h: width 800 start 840 end 968 total 1056 skew0 clock > > 37.9KHz > > v: height 600 start 601 end 605 total 628 clock > > 60.3Hz > > 800x600 (0x44) 36.0MHz +HSync +VSync > > h: width 800 start 824 end 896 total 1024 skew0 clock > > 35.2KHz > > v: height 600 start 601 end 603 total 625 clock > > 56.2Hz > > 640x480 (0x45) 25.2MHz -HSync -VSync > > h: width 640 start 656 end 752 total 800 skew0 clock > > 31.5KHz > > v: height 480 start 490 end 492 total 525 clock > > 59.9Hz > > HDMI-1 disconnected (normal left inverted right x axis y axis) > > Identifier: 0x3d > > Timestamp: -753984668 > > Subpixel: unknown > > Clones: HDMI-2 > > CRTCs: 0 1 > > HDMI-2 disconnected (normal left inverted right x axis y axis) > > Identifier: 0x3e > > Timestamp: -753984668 > > Subpixel: unknown > > Clones: HDMI-1 > > CRTCs: 0 1 > > TV disconnected (normal left inverted right x axis y axis) > >
Re: Problem with slow disk I/O
On Thu, 23.04.2009 at 19:40:34 +0200, Thomas Pfaff wrote: > On Thu, 23 Apr 2009 17:25:57 +0200 Jan Stary wrote: > > On Apr 23 18:09:55, Thomas Pfaff wrote: > > > First on Ubuntu: > > > /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) > > > ~$ time (tar -zxf ports.tar.gz && sync) > > > real 0m47.784s > > > user 0m1.576s > > > sys 0m5.024s 47.78 seconds wall clock time > > > Then the same commands on OpenBSD: > > > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > > > $ time (tar -zxf ports.tar.gz && sync) > > > 1m2.62s real 0m1.15s user 0m7.15s system ~ 1 minute 2.5 seconds wall clock time > > So you have ~52 seconds on ext3 mounted 'realtime' (whatever that means), > > versus ~63 seconds on ffs mounted with 'softdep'. > > What was the problem again? > > That I cannot get the job done in less than a minute on OpenBSD > while on Linux it takes only 18 seconds. This is a misconception, imho. Your test above shows that the performance difference is about 15 seconds, or roughly 25%. I can't see the 18 seconds anywhere except in your first email about your perceived performance for the task. It is imho useful to remember that Linux caches disk access much more aggressively than OpenBSD. So, in reality, you don't write that much faster to disk, but to RAM, and the OS flushes the buffers at it's own leisure, while you are working on something else. Which reminds me to ask what the state of having a UBC in OpenBSD is, please? -- Kind regards, --Toni++
Re: IPsec Windows Vista client - OpenBSD, NAT-T problem
Dear MK, There is a problem with the IPSec implementation on Vista and W2K8. Microsoft seems to have a patch. Please, see these articles: * http://support.microsoft.com/kb/957624/en-us * http://support.microsoft.com/kb/946887/en-us * http://technet.microsoft.com/en-us/library/bb878090.aspx If you try to connect to your VPN using XP or W2K clients it works fine. King regards, Marcello Cruz - Original Message - From: "MK" To: Sent: Thursday, April 23, 2009 12:49 PM Subject: IPsec Windows Vista client - OpenBSD, NAT-T problem Hello, I'm trying to learn how to setup IPsec connection, therefore I stared with quite simple settings. I'd like to allow clients from outside to connect my OpenBSD server through encrypted channel, however I came across some difficulties I'm not able to solve. scheme of my environment is following: client (Windows Vista) - NAT (mikrotik) --- internet --- (public IP) OpenBSD I decided to use PSK to simplify my settings: my ipsec.conf file contains: ike passive from any to any \ main auth hmac-sha1 enc aes group modp1024 \ quick auth hmac-sha1 enc aes psk my_key From my understanding this should allow all clients to connect my server via encrypted channel. I started isakmpd and setup a client for Windows Vista - for beginning I used TheGreenBow IPSec VPN Client. After a few minutes I had working environment so I deiced to use native Windows Vista IPsec client and here is my problem: Vista client is not able to communicate with my OpenBSD server for some reason I do not see. I was checking settings of the client and did not find any problem, then I just tried to shutdown isakmpd and to start it again with -T flag without NAT-T support. Immediately after this change, Vista client successfully connected to OpenBSD and communication was encrypted and working. If I start isakmpd again with NAT-T support then Vista can not negotiate IPsec with OpenBSD. I think NAT-T is important for me, because if I understand it well, it should allow IPsec communication for more clients behind same NAT simultaneously, however from some reason if I allow NAT-T support in OpenBSD, Vista can not reach the server anymore. TheGreenBow IPSec VPN Client works just fine even with NAT-T. I'm out of ideas and I'd like to kindly ask you for any help. I started isakmpd with -L switch to provide some additional information for both clients (working GreenBow and Vista client) Best regards MK Vista- NAT-T not working: 0:25:01.013804 84.42.224.147.500 > 217.197.149.135.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1-> msgid: len: 232 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 24 payload: VENDOR len: 20 (supports NAT-T, RFC 3947) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 [ttl 0] (id 1, len 260) 00:25:01.014657 217.197.149.135.500 > 84.42.224.147.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: len: 188 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 20 (supports OpenBSD-4.0) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 (supports v3 NAT-T, draft-ietf-ipsec-nat-t-ike-03) payload: VENDOR len: 20 (supports NAT-T, RFC 3947) payload: VENDOR len: 20 (supports DPD v1.0) [ttl 0] (id 1, len 216) 00:25:01.078015 84.42.224.147.500 > 217.197.149.135.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: 000
Re: AX25
On Thursday 23 April 2009 08:23:01 Coert Waagmeester wrote: > Hello all OpenBSDers! > > Is there AX25 (ham radio) support in OpenBSD? > > > Regards, > Coert > > OpenBSD newbie Nope. There was a thread on this some months ago. Look for TNC and you'll find it. Several hams have/are using OpenBSD with ham stuff. Look in the "comms" sections of the ports tree for the ham software thats available to you. 73, STeve Andre' (wb8wsf)
Re: Problem with slow disk I/O
On Thu, Apr 23, 2009 at 06:09:55PM +0200, Thomas Pfaff wrote: > On Thu, 23 Apr 2009 15:31:58 +0200 > Tobias Ulmer wrote: > [...] > > > > > Try: time tar -zxf ports.tar.gz && sync > > > > > > > > And include the output of mount and show the place where you are > > > > untarring. > > > > > > > > > > $ mount > > > /dev/wd0a on / type ffs (local, softdep) > > > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > > > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > > > > > > $ pwd > > > /home/tpfaff > > > > > > $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result > > > 1m2.66s real 0m1.09s user 0m6.85s system > > > $ time rm -rf ports > > > 0m15.20s real 0m0.15s user 0m1.42s system > > > > and on linux? > > First on Ubuntu: > > Script started on Thu 23 Apr 2009 03:50:27 PM CEST > ~$ time (tar -zxf ports.tar.gz && sync) > real 0m47.784s > user 0m1.576s > sys 0m5.024s > ~$ time (rm -rf ports && sync) > real 0m1.883s > user 0m0.076s > sys 0m1.664s > time (tar -zxf ports.tar.gz && sync) > real 0m20.652s > user 0m1.240s > sys 0m2.592s > ~$ time (rm -rf && sync) > real 0m0.003s > user 0m0.004s > sys 0m0.004s > ~$ time tar -zxf ports.tar.gz > real 0m11.513s > user 0m1.268s > sys 0m2.772s > ~$ time rm -rf ports > real 0m1.752s > user 0m0.100s > sys 0m1.648s > ~$ time tar -zxf ports.tar.gz > real 0m14.400s > user 0m1.352s > sys 0m2.560s > ~$ time rm -rf ports > real 0m1.756s > user 0m0.076s > sys 0m1.684s > ~$ mount # watch your eyes! > /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) > proc on /proc type proc (rw,noexec,nosuid,nodev) > /sys on /sys type sysfs (rw,noexec,nosuid,nodev) > varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) > varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) > udev on /dev type tmpfs (rw,mode=0755) > devshm on /dev/shm type tmpfs (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw) > securityfs on /sys/kernel/security type securityfs (rw) > gvfs-fuse-daemon on /home/tpfaff/.gvfs type fuse.gvfs-fuse-daemon > (rw,nosuid,nodev,user=tpfaff) > ~$ pwd > /home/tpfaff > ~$ exit > Script done on Thu 23 Apr 2009 03:53:20 PM CEST > > Then the same commands on OpenBSD: > > Script started on Thu Apr 23 17:55:53 2009 > $ time (tar -zxf ports.tar.gz && sync) > 1m2.62s real 0m1.15s user 0m7.15s system > $ time (rm -rf ports && sync) > 0m14.24s real 0m0.14s user 0m1.53s system > $ time (tar -zxf ports.tar.gz && sync) > 1m1.37s real 0m1.31s user 0m7.18s system > $ time (rm -rf ports && sync) > 0m14.72s real 0m0.12s user 0m1.82s system > $ time tar -zxf ports.tar.gz > 1m3.39s real 0m1.08s user 0m6.69s system > $ time rm -rf ports > 0m15.41s real 0m0.12s user 0m1.38s system > $ time tar -zxf ports.tar.gz > 1m2.62s real 0m1.19s user 0m6.80s system > $ time rm -rf ports > 0m15.63s real 0m0.10s user 0m1.79s system > $ mount > /dev/wd0a on / type ffs (local, softdep) > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > $ pwd > /home/tpfaff > $ exit > Script done on Thu Apr 23 18:02:13 2009 > ext3 and ffs are very different. So the same thing may take a different time to finish on either system because of different design decisions. >From your benchmark it seems your server's only purpose is to untar and remove ports.tar.gz in a loop or what are you trying to show? I'm very happy that OpenBSD ffs is a bit slower then Linux ext3. -- :wq Claudio
Re: Problem with slow disk I/O
Thomas Pfaff wrote: > On Thu, 23 Apr 2009 14:13:18 +0200 > Otto Moerbeek wrote: > > >> On Thu, Apr 23, 2009 at 02:02:06PM +0200, Tobias Ulmer wrote: >> >> >>> On Thu, Apr 23, 2009 at 03:27:42PM +0200, Thomas Pfaff wrote: >>> I'm getting horrible disk performance compared to Ubuntu on my system. I noticed this when extracting ports.tar.gz on the same machine with different OSs (this is something I did a while back to check for a possible hardware problem when OpenBSD crashed upon extracting ports.tar.gz). OpenBSD (ffs): $ time tar -zxf ports.tar.gz 0m59.90s real 0m1.00s user 0m6.95s system Ubuntu (ext3): $ time tar -zxf ports.tar.gz real 0m18.440s user 0m1.212s sys 0m2.596s 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the exact same thing on the exact same hardware! Why the huge difference? Both are default installations, except softdep is turned on. Thanks for any pointers or advice. >>> Try: time tar -zxf ports.tar.gz && sync >>> >> And include the output of mount and show the place where you are untarring. >> >> > > $ mount > /dev/wd0a on / type ffs (local, softdep) > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > > $ pwd > /home/tpfaff > > $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result > 1m2.66s real 0m1.09s user 0m6.85s system > $ time rm -rf ports > 0m15.20s real 0m0.15s user 0m1.42s system > > Sorry for the long message. I tried your test commands on three different servers -- two Dell servers and a generic box with Gigabyte motherboard. If there are any other tests I can run to help with this problem please let me know. Server1 has OpenBSD 4.4 -stable, GENERIC.MP, Dell 2950, PERC/6i, 15K SAS drives, two 146GB drives as RAID1 and another two 450GB drives as RAID1 On either RAID1 array, I get results similar to the following: server1$ time tar xzf ports.tar.gz 0m55.28s real 0m1.57s user 0m6.40s system server1$ time rm -rf ports 0m36.24s real 0m0.19s user 0m2.57s system Server2 has OpenBSD 4.5 GENERIC.MP#46 i386 (snapshot from April 12, 2009 or so), two 450GB drives as RAID1 and six 450GB drives as RAID6 On RAID1 array server2$ time tar xzf ports.tar.gz 0m56.95s real 0m1.47s user 0m6.08s system server2$ time rm -rf ports 0m32.44s real 0m0.19s user 0m2.50s system On RAID6 array server2$ time tar xzf ../ports.tar.gz 1m9.15s real 0m1.11s user 0m6.44s system server2$ time rm -rf ports 0m30.71s real 0m0.14s user 0m2.90s system On a new server (OpenBSD 4.4-stable, 320GB SATA drives), AHCI, test$ time tar xzf ports.tar.gz 5m12.78s real 0m1.39s user 0m5.04s system test# time rm -rf ports 2m34.91s real 0m0.15s user 0m2.59s system Because of the 103095897 bytes/sec transfer rate on the test box I thought that the test box would have faster writes but it seems to have taken 5 minutes compared to the Dell server which had a transfer rate of 75528478 bytes/sec. On Dell PE2950 servers with 15K RPM SAS drives I get $ dd if=/dev/arandom of=test.dat bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes transferred in 0.135 secs (75528478 bytes/sec) Here is the output of mount on server1 and server2 server1# mount /dev/sd0a on / type ffs (local) /dev/sd0h on /home type ffs (local, nodev, nosuid) /dev/sd0g on /tmp type ffs (local, nodev, nosuid) /dev/sd0d on /usr type ffs (local, nodev) /dev/sd0e on /var type ffs (local, nodev, nosuid) /dev/sd0f on /var/www type ffs (local, nodev, nosuid) /dev/sd1a on /apps type ffs (local, nodev, nosuid) /dev/sd1b on /source type ffs (local, nodev, nosuid) /dev/sd1d on /products type ffs (local, nodev, nosuid) /dev/sd1e on /storage type ffs (local, nodev, nosuid) server2# mount /dev/sd0a on / type ffs (local) /dev/sd0k on /home type ffs (local, nodev, nosuid) /dev/sd0d on /tmp type ffs (local, nodev, nosuid) /dev/sd0f on /usr type ffs (local, nodev) /dev/sd0g on /usr/X11R6 type ffs (local, nodev) /dev/sd0h on /usr/local type ffs (local, nodev) /dev/sd0j on /usr/obj type ffs (local, nodev, nosuid) /dev/sd0i on /usr/src type ffs (local, nodev, nosuid) /dev/sd0e on /var type ffs (local, nodev, nosuid) /dev/sd1f on /mnt type ffs (local) On a generic box (gigabyte motherboard, 320GB 7K RPM SAS drives etc.) I get test$ dd if=/dev/arandom of=test.dat bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes transferred in 0.099 secs (103095897 bytes/sec) Output of mount on test$ test$ mount /dev/sd0a on / type ffs (local) /dev/sd0h on /home type ffs (local, nodev, nosuid) /dev/sd0g on /tmp type ffs (local, nodev, nosuid) /dev/sd0d on /usr type ffs (local, nodev) /dev/sd0e on /var type ffs (loc
Re: OpenBSD as Wireless access point
On Wed, Apr 22, 2009 at 4:56 PM, Parvinder Bhasin wrote: All, Can someone suggest me a good WORKING wireless PCI or USB card (PCI preferred) that I could use for setting up machine as Wireless access point? I have tried 3-4 cards already and learnt that they were not supported for the AP mode. # dmesg | grep ral0 ral0 at pci0 dev 16 function 0 "Ralink RT2560" rev 0x01: irq 10, address 00:10:60:26:a6:30 ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 # Mini-PCI type III socket though... sniv...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Problem with slow disk I/O
> From your benchmark it seems your server's only purpose is to untar and > remove ports.tar.gz in a loop or what are you trying to show? > > I'm very happy that OpenBSD ffs is a bit slower then Linux ext3. He's showing that for his test case, he should be running Linux. Enjoy.
Re: Problem with slow disk I/O
On Thu, 23 Apr 2009 18:40:53 +0200 Claudio Jeker wrote: > ext3 and ffs are very different. So the same thing may take a different > time to finish on either system because of different design decisions. > From your benchmark it seems your server's only purpose is to untar and > remove ports.tar.gz in a loop or what are you trying to show? It's my workstation and I'm not trying to show anything. It was a simple observation I made and I was curious if there was something funny going on with my system, or if the performance difference in this particular case is considered normal.
DHCP versus PPPoE for ADSL.
Guten arben. I am wondering what the pros and cons are for using DHCP or PPPoE for connecting to an ISP via an ADSL modem. I expect like a lot of people I set my modem in bridge mode using PPPoE. In my particular case I use the DHCP server on the modem to assign an IP address to my desktop machine. When the session is running, my modem "passes on" the real world IP address assigned from the exchange to my desktop. I have noticed that some people use PPPoE rather than DHCP. I have read through the documentation - PPPOE(4) - and it looks a bit more involved than DHCP and has a few caveats (MTU/MSS ISSUES). I also read PPPOE(8) and it seems to be suited to userland and as I don't need a server doesn't appear to be worthwhile but I am not extremely familiar with all the implications. Can someone let me know if I am correct in assuming that if I want PPPoE in client mode only that PPPoE(4) is the way to go? Probably a more important question is what, if any, are the advantages or disadvantages compared to DHCP? Best wishes.
Re: newfs block device
John Brahy wrote: Have I completely lost my mind or should I be able to give newfs a block device? # df -ht ffs Filesystem SizeUsed Avail Capacity Mounted on /dev/wd0a 1006M203M753M21%/ /dev/wd0j 7.9G6.0G1.5G81%/home /dev/wd0i 1006M6.0K956M 0%/tmp /dev/wd0d 3.9G1.2G2.6G32%/usr /dev/wd0k 9.8G730M8.6G 8%/usr/local /dev/wd0f 2.0G 66.6M1.8G 3%/usr/obj /dev/wd0e 2.0G1.1G774M60%/usr/src /dev/wd0h 1006M123M833M13%/var /dev/wd0l 114G 78.4G 30.1G72%/virtualhosts /dev/wd1a 367G 84.9G264G24%/backups /dev/wd0g 2.0G221M1.7G12%/usr/ports # umount obj # newfs /dev/wd0f newfs: /dev/wd0f: block device # I thought that I have done that before. Have we lost functionality in 4.5 or just my mind? from newfs(8): The special file should be a raw device, for example /dev/rsd0a; if a relative path like sd0a is specified, the corresponding raw device is used. use /dev/rwd0f Tom
Re: IPsec Windows Vista client - OpenBSD, NAT-T problem
It solved my problem, thank you very much. _ MK -- From: "Marcello Cruz" Sent: Thursday, April 23, 2009 6:30 PM To: Cc: "MK" Subject: Re: IPsec Windows Vista client - OpenBSD, NAT-T problem Dear MK, There is a problem with the IPSec implementation on Vista and W2K8. Microsoft seems to have a patch. Please, see these articles: * http://support.microsoft.com/kb/957624/en-us * http://support.microsoft.com/kb/946887/en-us * http://technet.microsoft.com/en-us/library/bb878090.aspx If you try to connect to your VPN using XP or W2K clients it works fine. King regards, Marcello Cruz - Original Message - From: "MK" To: Sent: Thursday, April 23, 2009 12:49 PM Subject: IPsec Windows Vista client - OpenBSD, NAT-T problem Hello, I'm trying to learn how to setup IPsec connection, therefore I stared with quite simple settings. I'd like to allow clients from outside to connect my OpenBSD server through encrypted channel, however I came across some difficulties I'm not able to solve. scheme of my environment is following: client (Windows Vista) - NAT (mikrotik) --- internet --- (public IP) OpenBSD I decided to use PSK to simplify my settings: my ipsec.conf file contains: ike passive from any to any \ main auth hmac-sha1 enc aes group modp1024 \ quick auth hmac-sha1 enc aes psk my_key From my understanding this should allow all clients to connect my server via encrypted channel. I started isakmpd and setup a client for Windows Vista - for beginning I used TheGreenBow IPSec VPN Client. After a few minutes I had working environment so I deiced to use native Windows Vista IPsec client and here is my problem: Vista client is not able to communicate with my OpenBSD server for some reason I do not see. I was checking settings of the client and did not find any problem, then I just tried to shutdown isakmpd and to start it again with -T flag without NAT-T support. Immediately after this change, Vista client successfully connected to OpenBSD and communication was encrypted and working. If I start isakmpd again with NAT-T support then Vista can not negotiate IPsec with OpenBSD. I think NAT-T is important for me, because if I understand it well, it should allow IPsec communication for more clients behind same NAT simultaneously, however from some reason if I allow NAT-T support in OpenBSD, Vista can not reach the server anymore. TheGreenBow IPSec VPN Client works just fine even with NAT-T. I'm out of ideas and I'd like to kindly ask you for any help. I started isakmpd with -L switch to provide some additional information for both clients (working GreenBow and Vista client) Best regards MK Vista- NAT-T not working: 0:25:01.013804 84.42.224.147.500 > 217.197.149.135.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1-> msgid: len: 232 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 24 payload: VENDOR len: 20 (supports NAT-T, RFC 3947) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 payload: VENDOR len: 20 [ttl 0] (id 1, len 260) 00:25:01.014657 217.197.149.135.500 > 84.42.224.147.500: [udp sum ok] isakmp v1.0 exchange ID_PROT cookie: c8434925c7d015f1->fbb7ca86fb1f0a6b msgid: len: 188 payload: SA len: 60 DOI: 1(IPSEC) situation: IDENTITY_ONLY payload: PROPOSAL len: 48 proposal: 1 proto: ISAKMP spisz: 0 xforms: 1 payload: TRANSFORM len: 40 transform: 1 ID: ISAKMP attribute ENCRYPTION_ALGORITHM = AES_CBC attribute KEY_LENGTH = 128 attribute HASH_ALGORITHM = SHA attribute GROUP_DESCRIPTION = MODP_1024 attribute AUTHENTICATION_METHOD = PRE_SHARED attribute LIFE_TYPE = SECONDS attribute LIFE_DURATION = 0e10 payload: VENDOR len: 20 (supports OpenBSD-4.0) payload: VENDOR len: 20 (supports v2 NAT-T, draft-ietf-ipsec-nat-t-ike-02) payload: VENDOR len: 20 (supports v3 NAT-T, draft-ietf-ipsec-nat-t-ike-03) payload: VENDOR len: 20 (supports NAT-T, R
Choosing components for RAID array [Was: newfs changes fstype...]
Michal wrote (04/22/09 08:45): > So create an a and a d partition not an a and a b partition. Of > course, this guide is for 2 drives that are both bootable, yours will > be simpler of course but it should help you out. Thanks; that's helpful. I know that the array can be bootable, but the kernel must be located outside of the array, according to raidctl(8). My array will be for /home only. So it seems like there are two options: 1) Use wd1a and wd2a for the components of the array. 2) Use wd1d and wd2d as the components and setting up wd1a and wd2a with a 4.2BSD fs. The only dis/advantages I see would be that (1) maximizes the space for the array, but (2) leaves open the possibility that I could boot from wd1 or wd2 in the future by putting a basic OpenBSD installation in wd1a or wd2a. Are there any other considerations I should take into account? Or any advice on choosing between these two? Thanks!
Re: Problem with slow disk I/O
On Thu, Apr 23, 2009 at 12:35 PM, Vijay Sankar wrote: > Because of the 103095897 bytes/sec transfer rate on the test box I > thought that the test box would have faster writes but it seems to have > taken 5 minutes compared to the Dell server which had a transfer rate of > 75528478 bytes/sec. Sequential write speed has practically nothing to do with the time it takes to create or delete a directory structure.
Re: syslogd listens on udp 514 without -u
On 2009-04-23, Mate Gabri wrote: > Thank You! > > Is it possible to disable the listening socket? I want to run syslog-ng on > that port but use syslogd for local logging. >> http://marc.info/?l=openbsd-misc&m=110817759325986&w=2 there's no *listening* socket, it's just a socket. you're assuming that things which apply to TCP also apply to UDP; they don't. just bind syslog-ng to a specific IP address and leave syslogd alone.
Re: newfs block device
it used to be broken when it allowed newfs to non raw disks. On Wed, Apr 22, 2009 at 03:18:16PM -0600, Tom Rosso wrote: > John Brahy wrote: >> Have I completely lost my mind or should I be able to give newfs a block >> device? >> >> # df -ht ffs >> Filesystem SizeUsed Avail Capacity Mounted on >> /dev/wd0a 1006M203M753M21%/ >> /dev/wd0j 7.9G6.0G1.5G81%/home >> /dev/wd0i 1006M6.0K956M 0%/tmp >> /dev/wd0d 3.9G1.2G2.6G32%/usr >> /dev/wd0k 9.8G730M8.6G 8%/usr/local >> /dev/wd0f 2.0G 66.6M1.8G 3%/usr/obj >> /dev/wd0e 2.0G1.1G774M60%/usr/src >> /dev/wd0h 1006M123M833M13%/var >> /dev/wd0l 114G 78.4G 30.1G72%/virtualhosts >> /dev/wd1a 367G 84.9G264G24%/backups >> /dev/wd0g 2.0G221M1.7G12%/usr/ports >> # umount obj >> # newfs /dev/wd0f >> newfs: /dev/wd0f: block device >> # >> >> I thought that I have done that before. Have we lost functionality in >> 4.5 or just my mind? >> > > from newfs(8): > > The special file should be a raw device, for example /dev/rsd0a; if a > relative path like sd0a is specified, the corresponding raw device is > used. > > > use /dev/rwd0f > > Tom
Re: Problem with slow disk I/O
Those are my numbers.It was running during my normal work : 10 x Xterm in one of them is ogg123 playing song 1 x FF3 with 7 tabs 1 x Pidgin with 5 tabs 2 x rdesktop to Win servers 1 x ssh connection to company server 1 x vpnc softdep is on on all partitions I don't think that those numbers are bad,because ports.tar.gz has a lot of small files.And I use OpenBSD for many good reasons like stabitilty,security,quality,community and documentation.So if sometimes it's slower then other OS's I don't care if it isn't a bug ;-) $ uname -a OpenBSD hexempo.eu.tieto.com 4.5 GENERIC.MP#78 i386 $ $ dd if=/dev/arandom of=test.dat bs=1024 count=1 1+0 records in 1+0 records out 1024 bytes transferred in 0.106 secs (96246029 bytes/sec) $ $ time tar xzf ports.tar.gz 2m19.16s real 0m1.41s user 0m5.45s system $ 2009/4/23 Thomas Pfaff : > On Thu, 23 Apr 2009 18:40:53 +0200 > Claudio Jeker wrote: >> ext3 and ffs are very different. So the same thing may take a different >> time to finish on either system because of different design decisions. >> From your benchmark it seems your server's only purpose is to untar and >> remove ports.tar.gz in a loop or what are you trying to show? > > It's my workstation and I'm not trying to show anything. B It was a > simple observation I made and I was curious if there was something > funny going on with my system, or if the performance difference in > this particular case is considered normal. > > -- http://www.openbsd.org/lyrics.html
En buen momento llega este email...
[IMAGE] De nosotros depende que no se repita esta horrible historia, leelo y circzlalo. [demime 1.01d removed an attachment of type APPLICATION/DEFANGED]
Re: DHCP versus PPPoE for ADSL.
On Fri, Apr 24, 2009 at 02:25:50AM +0930, David Walker wrote: > Guten arben. > > I am wondering what the pros and cons are for using DHCP or PPPoE for > connecting to an ISP via an ADSL modem. > > I expect like a lot of people I set my modem in bridge mode using PPPoE. > In my particular case I use the DHCP server on the modem to assign an > IP address to my desktop machine. When the session is running, my > modem "passes on" the real world IP address assigned from the exchange > to my desktop. > > I have noticed that some people use PPPoE rather than DHCP. > I have read through the documentation - PPPOE(4) - and it looks a bit > more involved than DHCP and has a few caveats (MTU/MSS ISSUES). > I also read PPPOE(8) and it seems to be suited to userland and as I > don't need a server doesn't appear to be worthwhile but I am not > extremely familiar with all the implications. > > Can someone let me know if I am correct in assuming that if I want > PPPoE in client mode only that PPPoE(4) is the way to go? > Probably a more important question is what, if any, are the advantages > or disadvantages compared to DHCP? > The main encapsulation over ADSL is PPPoE or PPPoA only lately, with the spread of IPTV and VDSL, EFM (Ethernet First Mile) is used by some telcos. So it totaly depends on what your provider is giving you. -- :wq Claudio
Re: OpenBSD as Wireless access point
Thanks All for the replies. Really appreciate it. On Apr 23, 2009, at 4:22 AM, Sergey Khentov wrote: D-Link DWA-520 (it is Atheros-based wireless) works more or less OK. One issue - WPA2 is not working yet :( -- BR, Sergey Khentov 2009/4/23 Parvinder Bhasin : All, Can someone suggest me a good WORKING wireless PCI or USB card (PCI preferred) that I could use for setting up machine as Wireless access point? I have tried 3-4 cards already and learnt that they were not supported for the AP mode. Thanks
Re: autowhitelister for spamd needs testing
On Thu, Apr 23, 2009 at 03:32:49PM +1000, Aaron Mason wrote: > On Thu, Apr 23, 2009 at 10:30 AM, Stuart Henderson > wrote: > > > > I see a tiny little problem with this method... sometimes people send > > spam from domains whose DNS they control. > > If this is the case, then you have an almost direct pointer to the cause. > > The only way this wouldn't work is if the SPF records get spoofed as a > result of a lazy sysadmin not updating the DNS server with a more > secure version. Huh? Spammers have been using throw away domains for ages. Adding a SPF record to their own domains has been trivial. No spoofing required. Basically, you're accepting input from the bad guys and treating it as valid and trusted. Bad idea. > You could blacklist domains that fraudulently pass the SPF filter, but > that would defeat the purpose - you'd be working as hard as you would > be if you were maintaining manual whitelists or blacklists. Auto-whitelisting based on input from the spammer is bad. You may as well save yourself the trouble and not use spamd.
Re: autowhitelister for spamd needs testing
> Auto-whitelisting based on input from the spammer is bad. You may as > well save yourself the trouble and not use spamd. > Indeed. it is utterly mentally retarded. most spam is bogusly sent from real envelope senders. Smart spammers just randomize their recipient lists and use them as the envelope sender. doing this is dumb, sorry.
Entra no desafio Spacebox e vai de férias com o novo C3 Picasso
Este i o desafio que te langamos agora... o jogo vai comegar! Inspirado no novo Citroen C3 Picasso, o The Game tem como principal objectivo colocar o maior nzmero de elementos dentro do C3 Picasso. I simples, basta que sigas as pistas e descubras todos os elementos que enchem o SpaceBox. As pistas vco sendo reveladas na internet (Blogs, Youtube, Messenger, Facebook e Google Maps, etc). Participa que podes ir de firias com o C3 Picasso, ou ganhar um fim de semana para duas pessoas, ou um tratamento SPA, ou um jantar com os teus amigos (vj aqui todos os primios). Estas ` espera do quj para entrar no jogo? remova aqui o seu email
Unable to mount CD/DVD-RW drive in OpenBSD 4.4/i386.
I am unable to get OpenBSD 4.4/i386 to see my OptiArc DVD+/-RW AD-5540 drive on
a Dell Inspiron 6400 (E1505) notebook.
Everything else is functional on this system.
Neither /dev/cd0a nor /dev/cd0c work as /etc/fstab entries.
The kernel returns: Device not configured.
I also tried /dev/rcd0[n] (where n = a - p) as an /etc/fstab entry and it
returned an error stating: Device block required.
Below is an attachment of my dmesg file and /etc/fstab table.
-minsai
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
real mem = 2145820672 (2046MB)
avail mem = 2066497536 (1970MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/13/07, BIOS32 rev. 0 @ 0xffa10, SMBIOS
rev. 2.4 @ 0xf7980 (44 entries)
bios0: vendor Dell Inc. version "A17" date 06/13/2007
bios0: Dell Inc. MM061
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT
acpi0: wakeup devices LID_(S3) PBTN(S4) MBTN(S5) PCI0(S3) USB0(S0) USB1(S0)
USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S4) RP02(S3) RP03(S3)
RP04(S3) RP05(S3) RP06(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 3 (PCIE)
acpiprt3 at acpi0: bus 11 (RP01)
acpiprt4 at acpi0: bus -1 (RP02)
acpiprt5 at acpi0: bus -1 (RP03)
acpiprt6 at acpi0: bus 12 (RP04)
acpiprt7 at acpi0: bus -1 (RP05)
acpiprt8 at acpi0: bus -1 (RP06)
acpicpu0 at acpi0: C3
acpitz0 at acpi0: critical temperature 126 degC
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model " DELLPD9458" serial 987 type LION oem "Sanyo"
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
bios0: ROM list: 0xc/0x1
cpu0 at mainbus0
cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130c2606000c26
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 2000 MHz (1308 mV): speeds: 2000, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: irq 4
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 7300 Go" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: no integrated graphics
drm at vga1 unsupported
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: irq 11
azalia0: codec[s]: Sigmatel STAC9200, Conexant/0x2bfa, using Sigmatel STAC9200
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: irq 4
pci2 at ppb1 bus 11
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: irq 4,
MoW1, address 00:19:d2:bc:92:76
ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: irq 3
pci3 at ppb2 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: irq 10
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: irq 9
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: irq 7
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: irq 10
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe1
pci4 at ppb3 bus 3
bce0 at pci4 dev 0 function 0 "Broadcom BCM4401B1" rev 0x02: irq 5, address
00:19:b9:63:86:a4
bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0
"Ricoh 5C832 Firewire" rev 0x00 at pci4 dev 1 function 0 not configured
sdhc0 at pci4 dev 1 function 1 "Ricoh 5C822 SD/MMC" rev 0x19: irq 9
sdmmc0 at sdhc0
"Ricoh 5C843 MMC" rev 0x01 at pci4 dev 1 function 2 not configured
"Ricoh 5C592 Memory Stick" rev 0x0a at pci4 dev 1 function 3 not configured
"Ricoh 5C852 xD" rev 0x05 at pci4 dev 1 function 4 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x01: PM disabled
pciide0 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x01: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 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, initiator 7
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x01: irq 5
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
spdmem1 at iic0 addr 0x52: 1GB D
Re: autowhitelister for spamd needs testing
On 2009-04-23, Aaron Mason wrote: > On Thu, Apr 23, 2009 at 10:30 AM, Stuart Henderson > wrote: >> >> I see a tiny little problem with this method... sometimes people send >> spam from domains whose DNS they control. > > If this is the case, then you have an almost direct pointer to the cause. Sure. "the internet".
Re: Unable to mount CD/DVD-RW drive in OpenBSD 4.4/i386.
On Thu, Apr 23, 2009 at 12:13:06PM -0700, minsai0...@yahoo.com wrote: > /dev/cd0a /mnt/cdrom cd9660 ro,noauto 0 0 Does /mnt/cdrom exist?
rt.fm ftp server dumps core
Hi, For a while now I've been getting segmentation faults when I try to download snapshots from rt.fm ftp> mget *tgz mget base45.tgz? all Prompting off for duration of mget. local: base45.tgz remote: base45.tgz 150 Opening BINARY mode data connection for 'base45.tgz' (48267043 bytes). 100% |**| 47135 KB00:41 226 Transfer complete. 48267043 bytes received in 41.35 seconds (1.11 MB/s) local: comp45.tgz remote: comp45.tgz 150 Opening BINARY mode data connection for 'comp45.tgz' (90067409 bytes). 100% |**| 87956 KB01:12 421 Service not available, remote server has closed connection. Segmentation fault (core dumped) No problem with ftp.usa.openbsd.org in Boulder, which at only 100 miles away ought to be my closest mirror but sure isn't according to traceroute. Jeff
OpenBSD 4.5 @AR!
This morning I received the package :D Waiting for 05-01 to install. Greetings!
Re: Problem with slow disk I/O
--- On Thu, 4/23/09, Thomas Pfaff wrote: > From: Thomas Pfaff > Subject: Problem with slow disk I/O > To: misc@openbsd.org > Received: Thursday, April 23, 2009, 9:27 AM > I'm getting horrible disk performance > compared to Ubuntu on my system. > > I noticed this when extracting ports.tar.gz on the same > machine with > different OSs (this is something I did a while back to > check for > a possible hardware problem when OpenBSD crashed upon > extracting > ports.tar.gz). > > OpenBSD (ffs): > > $ time tar -zxf ports.tar.gz > 0m59.90s real 0m1.00s user >0m6.95s system > > Ubuntu (ext3): > > $ time tar -zxf ports.tar.gz > real0m18.440s > user0m1.212s > sys0m2.596s > > 1 minute on OpenBSD and 18.5 seconds on Ubuntu, doing the > exact same > thing on the exact same hardware! Why the huge > difference? Both are > default installations, except softdep is turned on. > > Thanks for any pointers or advice. > > Thomas > > OpenBSD 4.5-current (GENERIC.MP) #13: Thu Apr 23 13:00:36 > CEST 2009 > tpf...@ws.tp76.info:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 3152609280 (3006MB) > avail mem = 3045097472 (2904MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06b0 (76 entries) > bios0: vendor American Megatrends Inc. version "1704" date > 11/27/2007 > bios0: ASUSTeK Computer INC. P5B-E > acpi0 at bios0: rev 2 > acpi0: tables DSDT FACP APIC MCFG OEMB HPET > acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) > PS2M(S4) EUSB(S4) USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) > P0P7(S4) P0P8(S4) P0P9(S4) USB0(S4) USB1(S4) USB2(S4) > USB3(S4) USB4(S4) USB5(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz, 2135.29 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR,NXE,LONG > cpu0: 2MB 64b/line 8-way L2 cache > cpu0: apic clock running at 266MHz > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz, 2135.04 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR,NXE,LONG > cpu1: 2MB 64b/line 8-way L2 cache > ioapic0 at mainbus0 apid 2 pa 0xfec0, version 20, 24 > pins > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (P0P2) > acpiprt2 at acpi0: bus 5 (P0P1) > acpiprt3 at acpi0: bus 4 (P0P4) > acpiprt4 at acpi0: bus -1 (P0P5) > acpiprt5 at acpi0: bus -1 (P0P6) > acpiprt6 at acpi0: bus 3 (P0P7) > acpiprt7 at acpi0: bus 2 (P0P8) > acpicpu0 at acpi0 > acpicpu1 at acpi0 > acpibtn0 at acpi0: PWRB > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 82G965 Host" rev > 0x02 > ppb0 at pci0 dev 1 function 0 "Intel 82G965 PCIE" rev 0x02: > apic 2 int 16 (irq 11) > pci1 at ppb0 bus 1 > mem address conflict 0xc000/0x1000 > vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 7600 GT" rev > 0xa1 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev > 0x02: apic 2 int 16 (irq 11) > uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev > 0x02: apic 2 int 17 (irq 5) > ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev > 0x02: apic 2 int 18 (irq 15) > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 > azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" > rev 0x02: apic 2 int 22 (irq 3) > azalia0: codecs: Analog Devices AD1988A > audio0 at azalia0 > ppb1 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev > 0x02: apic 2 int 16 (irq 11) > pci2 at ppb1 bus 4 > ppb2 at pci0 dev 28 function 3 "Intel 82801H PCIE" rev > 0x02: apic 2 int 19 (irq 10) > pci3 at ppb2 bus 3 > age0 at pci3 dev 0 function 0 "Attansic Technology L1" rev > 0xb0: apic 2 int 19 (irq 10), address 00:18:f3:9d:7d:04 > atphy0 at age0 phy 0: F1 10/100/1000 PHY, rev. 5 > ppb3 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev > 0x02: apic 2 int 16 (irq 11) > pci4 at ppb3 bus 2 > jmb0 at pci4 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev > 0x02 > ahci0 at jmb0: apic 2 int 16 (irq 11), AHCI 1.0 > scsibus0 at ahci0: 32 targets > pciide0 at jmb0: DMA, channel 0 wired to native-PCI, > channel 1 wired to native-PCI > pciide0: using apic 2 int 16 (irq 11) for native-PCI > interrupt > atapiscsi0 at pciide0 channel 0 drive 0 > scsibus1 at atapiscsi0: 2 targets > cd0 at scsibus1 targ 0 lun 0: 1.00> ATAPI 5/cdrom removable > cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 > pciide0: channel 1 disabled (no drives) > uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev > 0x02: apic 2 int 23 (irq 7) > uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev > 0x02: apic 2 int 19
Re: RAIDframe - screech, smash.
On Thu, Apr 23, 2009 at 9:46 PM, J.C. Roberts wrote: > > > You were 21 days too late. > > -- > J.C. Roberts Thanks for getting straight to the point, however it's a tad vague, and I see no posts from 21 days before you emailed me that would suggest that I am "too late". Could you elaborate please? Thanks -- Aaron Mason AKA Absorbent Shoulder Man Oh, why does everything I whip leave me?
Re: autowhitelister for spamd needs testing
On Fri, Apr 24, 2009 at 4:39 AM, Dan Harnett wrote: > Huh? Spammers have been using throw away domains for ages. Adding a > SPF record to their own domains has been trivial. No spoofing required. > Basically, you're accepting input from the bad guys and treating it as > valid and trusted. Bad idea. If they use throw away domains, then another solution would be to go on the age of the domain - which a simple WHOIS check can obtain and would theoretically be very difficult to forge, especially if you go straight to one of the NICs for that info. This would come with some caveats - it would be easy to thwart by getting throwaway domain names and sitting on them for awhile in a sort of FIFO queue, adding new ones to the end when the first gets thrown away. On top of that, it would mean companies who are just getting a start in the online business could be waiting awhile to email potential clients whose mail servers are using this method to filter spam. On top of that, if VeriSign could be tricked into signing a fake Microsoft ActiveX key, can you really trust the authorities? The reality is that any solution to try and block spammers would be thwarted if a spammer were able to acquire the means to use it to validify themselves fraudulently. Spam is a battle - the least we can hope for is to make it a battle for them as well. -- Aaron Mason /Oh, why does everything I whip leave me?/
Re: autowhitelister for spamd needs testing
On Fri, Apr 24, 2009 at 10:13:38AM +1000, Aaron Mason wrote: > On Fri, Apr 24, 2009 at 4:39 AM, Dan Harnett wrote: > > Huh? Spammers have been using throw away domains for ages. Adding a > > SPF record to their own domains has been trivial. No spoofing required. > > Basically, you're accepting input from the bad guys and treating it as > > valid and trusted. Bad idea. > > If they use throw away domains, then another solution would be to go > on the age of the domain - which a simple WHOIS check can obtain and > would theoretically be very difficult to forge, especially if you go > straight to one of the NICs for that info. > > This would come with some caveats - it would be easy to thwart by > getting throwaway domain names and sitting on them for awhile in a > sort of FIFO queue, adding new ones to the end when the first gets > thrown away. On top of that, it would mean companies who are just > getting a start in the online business could be waiting awhile to > email potential clients whose mail servers are using this method to > filter spam. Or, you could just not auto-whitelist the bad guys while at the same time hurting deliverability from the good guys. Then again, do what you want. It doesn't effect me. > On top of that, if VeriSign could be tricked into signing a fake > Microsoft ActiveX key, can you really trust the authorities? Are you implying SPF records are validated somewhere and signed by a trusted third party? They're not. They're provided by the bad guys. A more proper analogy would be that you received an ActiveX control signed by "The Bad Guys Who Do Bad Things". They were nice enough to sign it, so you accept it. > The reality is that any solution to try and block spammers would be > thwarted if a spammer were able to acquire the means to use it to > validify themselves fraudulently. > > Spam is a battle - the least we can hope for is to make it a battle > for them as well. A battle where you shoot yourself in the head isn't much of a battle. Maybe you need an example. I'll run out and register 'asfjsakf1359.com'. Times are tough, but I think I can scrounge up the $9.99 GoDaddy wants for it. I'll use this domain to send you a single email. It'll pass greylisting, because I'm using a normal mail server with no funny tricks. It'll be a legit message, too. I just wanted to say "hi" and see how you were doing, and maybe talk about my cat. I've generously provided an SPF record to make things easier for you. It is my domain and I can advertise what I want in my domain. The SPF record will look like the following. asfjsakf1359.com TXT "v=spf1 a:mail.asfjsakf1359.com ip4:0.0.0.0/0 ~all" Now, you no longer have to worry about greylisting.
Re: Unable to mount CD/DVD-RW drive in OpenBSD 4.4/i386.
That wouldn't give device not configured. What does disklabel cd0 give? On 23/04/2009, Mike Erdely wrote: > On Thu, Apr 23, 2009 at 12:13:06PM -0700, minsai0...@yahoo.com wrote: >> /dev/cd0a /mnt/cdrom cd9660 ro,noauto 0 0 > > Does /mnt/cdrom exist?
Re: autowhitelister for spamd needs testing
On Fri, Apr 24, 2009 at 11:01 AM, Dan Harnett wrote: >> On top of that, if VeriSign could be tricked into signing a fake >> Microsoft ActiveX key, can you really trust the authorities? > > Are you implying SPF records are validated somewhere and signed by a > trusted third party? They're not. They're provided by the bad guys. A > more proper analogy would be that you received an ActiveX control signed > by "The Bad Guys Who Do Bad Things". They were nice enough to sign it, > so you accept it. > I was implying no such thing. I was referring to using WHOIS to block spammers on the basis of the date the domain was registered. > asfjsakf1359.com TXT "v=spf1 a:mail.asfjsakf1359.com ip4:0.0.0.0/0 ~all" Ok, now that gives us a pointer by which to block fraudulent folk. That record means anyone and everyone can send an email using that domain name. A proper SPF record wouldn't have an all-encompassing IP range. In fact, who in the world would have anything more than a /7 block? However that alone wouldn't deter any spammer - just limit the range to what's accepted and you're in. And any limit you set will only cause more dramas. Sure you could limit it to /24 and smaller, or even to single addresses, but what about those select folk who have been assigned /8 classless subnets? That's a whole lotta SPF records for one subdomain. No solution is perfect, but a small group of imperfect solutions is a far cry better than no solutions at all and our mailboxes being inundated with spam. The problem's here to stay, all we can do is deal with it as best we can. -- Aaron Mason AKA Absorbent Shoulder Man Oh, why does everything I whip leave me?
Re: Unable to mount CD/DVD-RW drive in OpenBSD 4.4/i386.
Hey, isn't it just cd0? On Fri, Apr 24, 2009 at 1:52 PM, Nick Guenther wrote: > That wouldn't give device not configured. > > What does disklabel cd0 give? > > On 23/04/2009, Mike Erdely wrote: >> On Thu, Apr 23, 2009 at 12:13:06PM -0700, minsai0...@yahoo.com wrote: >>> /dev/cd0a /mnt/cdrom cd9660 ro,noauto 0 0 >> >> Does /mnt/cdrom exist? > > -- Aaron Mason AKA Absorbent Shoulder Man Oh, why does everything I whip leave me?
[Way OT] Roadtrip...
Apologies to most people who won't give a shit but I'm finally moving to New Mexico and am posting updates at http://nbender.com more or less daily as we make our way across the country. Regards, -N
Re: [Way OT] Roadtrip...
On Fri, Apr 24, 2009 at 1:11 AM, Nick Bender wrote: > Apologies to most people who won't give a shit but I'm finally moving > to New Mexico... This is the sort of thing that gets me thinking really really seriously again about capital punishment. Who's with me? -- No no no, my fish's name is Eric, Eric the fish. He's an halibut. I am not a looney! Why should I be tarred with the epithet looney merely because I have a pet halibut?
Re: Problem with slow disk I/O
On Apr 23 18:09:55, Thomas Pfaff wrote: First on Ubuntu: /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) ~$ time (tar -zxf ports.tar.gz && sync) real0m47.784s 47.78 seconds wall clock time Then the same commands on OpenBSD: /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) $ time (tar -zxf ports.tar.gz && sync) 1m2.62s real 0m1.15s user 0m7.15s system ~ 1 minute 2.5 seconds wall clock time So you have ~52 seconds on ext3 mounted 'realtime' (whatever that means), versus ~63 seconds on ffs mounted with 'softdep'. What was the problem again? That I cannot get the job done in less than a minute on OpenBSD while on Linux it takes only 18 seconds. Also, doesn't ext2/3 run with everything mount async? A quick test with ffs in async mode (instead of, or added to softdep) would also be worth running, in order to see how much "grossly insecure I/O" lessens the perceived time. I am one of those who like to keep my files, so I wont recommend USING async, but for the sake of argument here, such a test might be in order. Which reminds me to ask what the state of having a UBC in OpenBSD is, please? There is nothing close to it yet, to my knowledge, but I am hosting the 2009 filesystem hackathon this autumn in hopes of getting 'better' I/O out of OpenBSD, with the help of a nice grant to that goal. Perhaps magic will come out of that. History (and undeadly =) will tell. Mind you, I did run UBC on my obsd amiga back in the short while when art@ had UBC in, which did wonders when you have lots (128M) of ram and a PIO mode 0 harddisk to boot.
Upgrade to -current
Currently I am using 4.2 stable and I am willing to upgrade to -current because of some new features which i need. According to faq (http://www.openbsd.org/faq/faq5.html#Bld) I should first upgrade to closest binary, which means upgrade from 4.2 to 4.3 and then to 4.4 ( Latest snapshot ) and finally Fetch & build *-current. Above process as you know will be a highly time consuming process and I prefer stick to my current 4.2 rather than going through that. why not just Fetch & build -cuurent directly? what is your recommended approach for upgrading to -cuurent ? thanks, Mani *
