test envoi dolist
Ce message est au format HTML. Si vous ne parvenez pas ` le lire, cliquez ici. Offre riservie ` anciens materiaux renovation de normandie, M51KWOKP17 [IMAGE] Je souhaite recevoir des informations et offres promotionnelles ` cette adresse e-mail (misc@openbsd.org) de la part de Welcome Office. Confidentialiti des donnies : Conformiment ` la Loi Informatique et Libertis, vous disposez d'un droit d' acchs et de rectification aux donnies vous concernant. Par notre intermidiaire, vous serez susceptible de recevoir des offres d'autres sociitis. Si vous ne le souhaitez pas, il suffit de nous icrire. Vous recevez ce message car vous avez iti en contact avec le Service Commercial de Welcome Office ou de ses partenaires. Pour ne plus recevoir de messages de la part de Welcome Office, cliquez ici.
Re: ASUS P5L-MX
Frank Bax wrote: ... 2) is this a problem: cpu0: unknown Core FSB_FREQ value 0 (0x41c8) ... cpu0: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (GenuineIntel 686-class) 1.87 GHz This is one of the newer Intel Core 2 CPU's, with 266 MHz FSB. There is support for those in -current, but it didn't make it into 4.0, due to insufficient testing. You can try the following patch, which should apply to 4.0 release and stable. Note that you won't notice much, except for the message disappearing. The bus clock detection is currently only important for SpeedStep, and that doesn't work yet on MP kernels. Index: sys/arch/i386/i386/machdep.c === RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v retrieving revision 1.364 diff -u -d -p -r1.364 machdep.c --- sys/arch/i386/i386/machdep.c20 Aug 2006 01:42:51 - 1.364 +++ sys/arch/i386/i386/machdep.c20 Dec 2006 09:58:39 - @@ -2090,6 +2090,9 @@ p3_get_bus_clock(struct cpu_info *ci) case 3: bus_clock = 1; break; + case 0: + bus_clock = 2; + break; case 4: bus_clock = 3; break;
Looping in ksh
I needed some little script; and - as usual - tried it out by typing: i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done 1 2 3 4 5 6 7 8 9 10 So good, so far. So I put the history into a file; added #!/bin/sh and ran it. To my surprise, it is an endless loop printing 0. Typed again, works. Running the script: endless loop. Question: What is missing in the loop ? FYI: I tried all those variation of $i in the arithmetic expression, but I won't do the trick. It works properly as line-by-line and loops endlessly as script. I can make it work by changing it to ... echo $((i=i+1)) ... , but I still ask myself, why the arithmetic expression is not being evaluated within the script if not in combination with echo, e.g. ? Uwe
Re: ASUS P5L-MX
On Tue, Dec 19, 2006 at 04:23:50PM -0500, Frank Bax wrote: At 02:19 PM 12/16/06, Frank Bax wrote: Will OpenBSD 4.0 release run on ASUS P5L-MX? The asus website does not seem to mention which Gigabit chipset is used on this board. Anyone using this board? http://www.asus.com/products.aspx?l1=3l2=11l3=194model=1320modelmenu=2 1) Gigabit Lan not recognised on this board. unknown vendor 0x1969 product 0x1048 (class network subclass ethernet, rev 0xb0) at pci2 dev 0 function 0 not configured This is an Attsanic L1, a company that was a spinoff of Asus, now owned by Atheros. No wide availability or documentation, I rather doubt documentation will appear from our friends at Atheros somehow...
Re: Looping in ksh
Uwe Dippel([EMAIL PROTECTED]) on 2006.12.20 18:43:35 +: I needed some little script; and - as usual - tried it out by typing: ^^! #!/bin/sh ^^! Question: What is missing in the loop ? nothing, your shell ist ksh, not sh. /B. -- Sebastian Benoit [EMAIL PROTECTED]
Re: Looping in ksh
Uwe Dippel([EMAIL PROTECTED])@2006.12.20 18:43:35 +0800: I needed some little script; and - as usual - tried it out by typing: i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done 1 2 3 4 5 6 7 8 9 10 So good, so far. So I put the history into a file; added #!/bin/sh ^^^ tried /bin/ksh as shebang? cheers, teemu -- Don't be too proud of the technological terror you have constructed -- D. Vader [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Looping in ksh
On Wed, 20 Dec 2006, Uwe Dippel wrote: I needed some little script; and - as usual - tried it out by typing: i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done 1 2 3 4 5 6 7 8 9 10 So good, so far. So I put the history into a file; added #!/bin/sh and ran it. To my surprise, it is an endless loop printing 0. Typed again, works. Running the script: endless loop. (( .. )) is ksh specific. Put #!/bin/ksh in your scritp and you'll be fine. -Otto Question: What is missing in the loop ? FYI: I tried all those variation of $i in the arithmetic expression, but I won't do the trick. It works properly as line-by-line and loops endlessly as script. I can make it work by changing it to ... echo $((i=i+1)) ... , but I still ask myself, why the arithmetic expression is not being evaluated within the script if not in combination with echo, e.g. ? Uwe
Re: Looping in ksh
On Wednesday 20 December 2006 18:43, Uwe Dippel wrote: i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done #!/bin/ksh -- Warm regards, Kevin Foo Key fingerprint : 4B23 FC1C E50B 9693 CCDD 2A7D A048 E909 8924 9BDD Public key : http://keyserver.linux.it/pks/lookup?op=getsearch=0x89249BDD *Internet Email Confidentiality Footer * Legal Privilege Confidentiality --- This email contains privileged and/or confidential information. If you are not the intended recipient (or responsible for delivery of the message to such person) or if you have inadvertently received this email, you should destroy or delete this message and notify the sender by reply email accordingly. If you or your employer do not consent to using Internet email for messages of this kind please advise immediately by sending an email to the sender of this message . All opinions, conclusions and other information in this message that do not relate to the official business of Zaid Ibrahim Co shall be understood as neither given nor endorsed by Zaid Ibrahim Co. Our company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Caveat -WARNING: Computer viruses can be transmitted via email, and you should check this email and any attachments for the presence of viruses. Zaid Ibrahim Co accepts no liability for any damage caused by any virus transmitted by this email. Our employees are expressly required not to make defamatory statements nor infringe or authorise any infringement of copyright or any other legal right via any communications. Any such communication is contrary to our company policy and outside the scope of the employment of said individual. We will not be liable for such communication.
Re: Looping in ksh
L. Ahmadi schrieb: Hi, If you want to use /bin/sh, it works well if you replace ((i=i+1)) by let i=i+1 Or use I=$((I+1)) which works in sh/ksh/bash and should be pretty universal. - Michael
Re: Looping in ksh
2006/12/20, Uwe Dippel [EMAIL PROTECTED]: I needed some little script; and - as usual - tried it out by typing: i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done 1 2 3 4 5 6 7 8 9 10 Hi, This is a shell rewrite of jot(1). Try : $ jot 10 1 10 Best Regard, Bruno.
nice book about code auditing
Hi, Every once in a while the question how can I learn how to audit software comes up here. I just received The Art of Software Security Assesment by Mark Dowd et. al. I ordered it because another OpenBSd developer recommended it. Browsing through it it really seems a nice book. So I think I can recommend it to anybody wanting to learn code auditing. -Otto
Re: Looping in ksh
Otto Moerbeek wrote: (( .. )) is ksh specific. I know. Put #!/bin/ksh in your scritp and you'll be fine. Have you tried it ? I did. It doesn't work. Uwe
Re: Looping in ksh
L. Ahmadi wrote: If you want to use /bin/sh, No I don't (and didn't). But now I know my mistake: I had put #!/bin/ksh for a good reason, but I did call it with $ sh progname That's rather me stupid, then ! Thanks everyone for answering, Uwe
Re: Looping in ksh
On Wed, 20 Dec 2006, Uwe Dippel wrote: Otto Moerbeek wrote: (( .. )) is ksh specific. I know. Put #!/bin/ksh in your scritp and you'll be fine. Have you tried it ? I did. It doesn't work. Here it works. You must be doing something wrong. -Otto
ksh - ls NAME.* -Argument list too long
Hello everybody, I wanted to stress the Antivirus a littlebit and wanted to know how many Backdoors are in the Test-Archive for this case: mailgw $ ls | wc -l 10656 mailgw $ ls Backdoor.* | wc -l ksh: ls: Argument list too long 0 mailgw Could that be a Bug? The directory includes also normal Word-Macro Virii but I just wanted to count the Backdoors Kind regards, Sebastian
Re: ksh - ls NAME.* -Argument list too long
On Wednesday 20 December 2006 21:34, Sebastian Rother wrote: Could that be a Bug? No. ls cant take an infinite number of arguments. Just use grep to get the Backdoor entries. Lars Hansson
Re: Looping in ksh
On Wed, Dec 20, 2006 at 08:17:04PM +0800, Uwe Dippel wrote: | Otto Moerbeek wrote: | | (( .. )) is ksh specific. | | I know. | | Put #!/bin/ksh in your scritp and you'll be fine. | | Have you tried it ? I did. It doesn't work. It works. How are you running this test ? [EMAIL PROTECTED] $ cat test #!/bin/ksh i=0 uplim=10 while [ $i -lt $uplim ] do ((i=i+1)) echo $i done [EMAIL PROTECTED] $ chmod u+x test [EMAIL PROTECTED] $ ./test 1 2 3 4 5 6 7 8 9 10 [EMAIL PROTECTED] $ sh test 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ^C Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: ksh - ls NAME.* -Argument list too long
On 2006/12/20 14:34, Sebastian Rother wrote: mailgw $ ls | wc -l 10656 mailgw $ ls Backdoor.* | wc -l ksh: ls: Argument list too long 0 You exceeded ARG_MAX bytes; $ getconf ARG_MAX 262144 from sysconf(3): _SC_ARG_MAX The maximum bytes of arguments to exec(3) (including the environment). Could that be a Bug? no.
Re: revision control system for system administration
On Tue, Dec 19, 2006 at 06:23:16AM -0700, Clint Pachl wrote: A pull-only system assumes that the clients actually pull. What if they don't? How do you know when their last successful pull was? If you implement a push system, how do you know if something was actually pushed? What if something was pushed, how do you know the pushee did the right thing with what it was given? This argument goes both ways, but solved simply. A system should report what it does after it pushes or pulls. The other end should also report. So if the results show someone is pushing, but no one is pulling or visa-versa, you have a problem. This system could be implemented using mail or central syslog. A good argument for pull systems: http://www.infrastructures.org/bootstrap/pushpull.shtml What do others think about push vs pull management systems? What tools are you using to implement your push/pull management system? An orthogonal issue, which I don't think has been explicitly mentioned so far, is whether you make config changes on the central repository (and replicate them out to the target), or locally on the target system (and replicate them back to the central repository) From infrastructures.org: We have developed a rule that works very well in practice and saves us a lot of heartache: Never log into a machine to change anything on it. Always make the change on the gold server and let the change propagate out. That makes a lot of sense. But enforcing that policy might be difficult. This is important if you're relying on your gold server for disaster recovery purposes - if the target machines had some change made which nobody remembers and weren't reflected in the gold server, then any freshly-built machines will be non-functional. You could have some Tripwire-like system to monitor periodically for unauthorised changes, so you can slap the wrist of anyone who breaks the policy - and more importantly, bring the central repository back into sync with what was done. Or you could block root logins entirely, but then you need to carefully select a list of sudo actions which are needed for (e.g.) restarting daemons and diagnosing and correcting common problems. The alternative is that changes are allowed to be made on target machines, and then later checked into a central repository as a record after the fact. This makes it harder to make identical changes to a large number of machines in a cluster. It's also possible again to get out of sync between the real machine and the repository, if the procedures are not properly followed. A similar issue occurs with init scripts, interface configuration, and starting and stopping daemons. On many occasions I have come across problems where a box has been running perfectly for 2 years, but when it was rebooted for some reason, it stopped working. It turned out this was because someone made a manual change, such as starting some daemon perhaps with particular command-line flags, or changing filewall rules, but when the box rebooted it did not come up the same way at startup. Since the original change may have been made a long time ago by someone who has long-since left, you can end up with emergency situations which are difficult to fix quickly. This problem seems to be more difficult to solve. Ideally there would be a single interface through which you performed any sysadmin action, such as configuring an interface or starting a daemon, which kept a persistent record of this and performed the same action at startup. That would mean, for example, being forbidden to use 'ifconfig' directly, but being allowed to change /etc/hostname.* and run an rc script to apply the changes. This is more difficult with rc.conf: you would need a supervisor script which noticed (say) that run_foo=NO had changed to run_foo=YES, or vice versa, and performed the appropriate actions. It might actually be easier if using something like daemontools, which has separate control files for each daemon. I've never seen a centralised management system which works directly in this way, but I'd love to have one. Finally, a similar problem occurs when deciding how to do configuration management of, say, Cisco routers. However, your hand is forced a bit more there: you generally can't just push a new config out to each box, because to make the changes active you'd need to reboot it (a Cisco doesn't have the ability to take a diff between its current active state and a target state, and perform only the changes necessary to bring it up to that state) So often you end up having to make changes directly on the target device line by line, and then tftp'ing the updated configs back to a central repository. That is, the central repository is not the place where changes are made, but just a record of changes which were made. Again, you can get into problems with procedures not being followed and the repository coming out of sync with reality. Regards, Brian.
Re: nice book about code auditing
On 12/20/06, Otto Moerbeek [EMAIL PROTECTED] wrote: Hi, Every once in a while the question how can I learn how to audit software comes up here. I just received The Art of Software Security Assesment by Mark Dowd et. al. I ordered it because another OpenBSd developer recommended it. Browsing through it it really seems a nice book. So I think I can recommend it to anybody wanting to learn code auditing. -Otto I just recieved this book yesterday myself. I've only thumbed through it, but this is the best book on the subject out there. It's been placed on the top of my stack and will probobly stay there. Highly recommended.
Re: ksh - ls NAME.* -Argument list too long
On Wed, 20 Dec 2006, Lars Hansson wrote: On Wednesday 20 December 2006 21:34, Sebastian Rother wrote: Could that be a Bug? No. ls cant take an infinite number of arguments. Just use grep to get the Backdoor entries. find -name '
Re: ksh - ls NAME.* -Argument list too long
On Wed, 20 Dec 2006, Lars Hansson wrote: On Wednesday 20 December 2006 21:34, Sebastian Rother wrote: Could that be a Bug? No. ls cant take an infinite number of arguments. Just use grep to get the Backdoor entries. [sorry for the previous incomplete post] find . -name 'pattern' | wc -l -Otto
Re: revision control system for system administration
On Wed, Dec 20, 2006 at 02:31:09PM +, Brian Candler wrote:
That makes a lot of sense. But enforcing that policy might be
difficult. This is important if you're relying on your gold server
for disaster recovery purposes - if the target machines had some
change made which nobody remembers and weren't reflected in the
gold server, then any freshly-built machines will be
non-functional.
This is a cultural problem, but there's an adequate technical
solution: aggressively sync the client machines. Admins quickly
learn to make changes in the central when their changes get blown
away every hour.
At my last job, we used cfengine to manage a handful of Solaris
zones that bounced around a cluster of machines. Each zone would be
built and destroyed every time it moved from one machine to the
other, so any non-cfengine changes made to the system would be lost.
We hadn't been using cfengine for very long, but everyone picked up
on it quite rapidly. ;)
cfengine (and other configuration management thingies, I suppose)
can alert you when key files change. So if someone's mucking around
with /etc/rc on the machine, cfengine can back it up, put in the
'gold' copy, and whine about it.
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Termcap question
Hello, I'm trying to change termcap to work correctly with my xterm home and end keys. So I've added these keys to the xterm termcap entry: xterm|xterm terminal emulator (X Window System), kend=\E[4~, khome=\E[1~, use=xterm-r6, Then I rebuilt the termcap, termcap.db and terminfo.db files. The resulting termcap looks like: xterm|xterm terminal emulator (X Window System):\ :@7=\E[4~:kh=\E[1~:tc=xterm-r6: which is right. According to termcap man page: The capabilities given before tc override those in the terminal type invoked by tc. But when I do, for example, tset -s I see that entry contains both old and new key definitions: TERMCAP='xterm:@7=\E[4~:kh=\E[1~:am:bs:...:kh=\EOH:... And programs like midnight commander still expect \EOH for home key rather than \E[1~ Is this a bug or just my misunderstanding? Thanks, Andrey
Re: Negative temp sensor readings?
Will H. Backman wrote: Has anyone else seen negative temperature sensor readings through sysctl? hw.sensors.0=ipmi0, Temp, -54.00 degC, OK hw.sensors.1=ipmi0, Temp, -51.00 degC, OK hw.sensors.2=ipmi0, Temp, 40.00 degC, WARNING OpenBSD 4.0 (GENERIC.MP) #967: Sat Sep 16 20:38:15 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2146729984 (2096416K) avail mem = 1834881024 (1791876K) using 22937 buffers containing 214880256 bytes (209844K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x7ffbc000 (62 entries) bios0: Dell Inc. PowerEdge 2950 ipmi0 at mainbus0: version 2.0 interface KCS iobase 0xca8/8 spacing 4 mainbus0: Intel MP Specification (Version 1.4) (DELL PE 01B2 ) cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1596.14 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,NXE,LONG cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.93 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,NXE,LONG cpu1: 4MB 64b/line 16-way L2 cache cpu2 at mainbus0: apid 7 (application processor) cpu2: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.94 MHz cpu2: 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,NXE,LONG cpu2: 4MB 64b/line 16-way L2 cache cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.93 MHz cpu3: 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,NXE,LONG cpu3: 4MB 64b/line 16-way L2 cache mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type PCI mpbios: bus 6 is type PCI mpbios: bus 7 is type PCI mpbios: bus 8 is type PCI mpbios: bus 9 is type PCI mpbios: bus 10 is type PCI mpbios: bus 11 is type PCI mpbios: bus 12 is type PCI mpbios: bus 13 is type PCI mpbios: bus 14 is type PCI mpbios: bus 15 is type PCI mpbios: bus 16 is type PCI mpbios: bus 17 is type ISA ioapic0 at mainbus0 apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 ioapic1 at mainbus0 apid 9 pa 0xfec81000, version 20, 24 pins ioapic1: misconfigured as apic 0, remapped to apid 9 pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel 5000X Host rev 0x12 ppb0 at pci0 dev 2 function 0 Intel 5000 PCIE rev 0x12 pci1 at ppb0 bus 6 ppb1 at pci1 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci2 at ppb1 bus 7 ppb2 at pci2 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci3 at ppb2 bus 8 ppb3 at pci3 dev 0 function 0 ServerWorks PCIE-PCIX rev 0xc2 pci4 at ppb3 bus 9 bnx0 at pci4 dev 0 function 0 Broadcom BCM5708 rev 0x11: apic 8 int 16 (irq 11), address 00:18:8b:47:5c:ad brgphy0 at bnx0 phy 1: BCM5708C 10/100/1000baseT PHY, rev. 5 ppb4 at pci2 dev 1 function 0 Intel 6321ESB PCIE rev 0x01 pci5 at ppb4 bus 10 ppb5 at pci1 dev 0 function 3 Intel 6321ESB PCIE-PCIX rev 0x01 pci6 at ppb5 bus 11 ppb6 at pci0 dev 3 function 0 Intel 5000 PCIE rev 0x12 pci7 at ppb6 bus 1 ppb7 at pci7 dev 0 function 0 Intel IOP333 PCIE-PCIX rev 0x00 pci8 at ppb7 bus 2 mfi0 at pci8 dev 14 function 0 Dell PERC 5 rev 0x00: apic 9 int 14 (irq 5) mfi0: logical drives 2, version 5.0.2-0003, 256MB RAM scsibus0 at mfi0: 2 targets sd0 at scsibus0 targ 0 lun 0: DELL, PERC 5/i, 1.00 SCSI3 0/direct fixed sd0: 34176MB, 34176 cyl, 64 head, 32 sec, 512 bytes/sec, 69992448 sec total sd1 at scsibus0 targ 1 lun 0: DELL, PERC 5/i, 1.00 SCSI3 0/direct fixed sd1: 138752MB, 138752 cyl, 64 head, 32 sec, 512 bytes/sec, 284164096 sec total ppb8 at pci7 dev 0 function 2 Intel IOP333 PCIE-PCIX rev 0x00 pci9 at ppb8 bus 3 ppb9 at pci0 dev 4 function 0 Intel 5000 PCIE rev 0x12 pci10 at ppb9 bus 12 ppb10 at pci0 dev 5 function 0 Intel 5000 PCIE rev 0x12 pci11 at ppb10 bus 13 ppb11 at pci0 dev 6 function 0 Intel 5000 PCIE rev 0x12 pci12 at ppb11 bus 14 ppb12 at pci0 dev 7 function 0 Intel 5000 PCIE rev 0x12 pci13 at ppb12 bus 15 pchb1 at pci0 dev 16 function 0 Intel 5000 Error Reporting rev 0x12 pchb2 at pci0 dev 16 function 1 Intel 5000 Error Reporting rev 0x12 pchb3 at pci0 dev 16 function 2 Intel 5000 Error Reporting rev 0x12 pchb4 at pci0 dev 17 function 0 Intel 5000 Reserved rev 0x12 pchb5 at pci0 dev 19 function 0 Intel 5000 Reserved rev 0x12 pchb6 at pci0 dev 21 function 0 Intel 5000 FBD rev 0x12 pchb7 at pci0 dev 22 function 0 Intel 5000 FBD rev 0x12 ppb13 at pci0 dev 28 function 0 Intel 6321ESB PCIE rev 0x09 pci14 at ppb13 bus 4 ppb14 at pci14 dev 0 function 0 ServerWorks PCIE-PCIX rev 0xc2 pci15 at ppb14 bus 5 bnx1 at
sftp systrace policy.
Hi, I'm looking for a systrace policy that ensures that a user logged in sftp isn't able to change directories. I've tired dugsong's sshd policy, but that is outdated and would require a systrace master to update it. Also, I've tried to get the one[1] that appeared on undeadly.org a few months ago, but the website is offline. No luck googling it. ;( I just need to make sure that a user doesn't change it's home dir. Thanks a lot, RV * [1] = http://undeadly.org/cgi?action=articlesid=20040307120323
Re: FW: How can I view rule numbers under OpenBSD 4.0?
Hey did anyone tell this guy it's two vs and not a w yet?
hotplugd umass kernel crash
Hi, when starting hotplugd the kernel crashes because of some buffer issue of umass (with and without device attached). Never had this before and restarting or turning off/on the machine doesn't help. Since it doesn't write anything to messages or any other file I wonder how I can get the kernel crash message + ddb trace + ddb ps into a file so I can post it here? Thanks in advance. - Michael dmesg: OpenBSD 4.0-current (GENERIC) #1287: Tue Dec 19 13:50:08 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 3.40GHz (GenuineIntel 686-class) 3.81 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID real mem = 1072984064 (1047836K) avail mem = 970637312 (947888K) using 4256 buffers containing 53772288 bytes (52512K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 03/23/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xf04d0 (79 entries) bios0: ASUSTeK Computer INC. P5AD2-E-Premium apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8160/352 (20 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801FB LPC rev 0x00) pcibios0: PCI bus #5 is the last bus bios0: ROM list: 0xc/0xee00! acpi at mainbus0 not configured cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82925X MCH Host rev 0x0e ppb0 at pci0 dev 1 function 0 Intel 82925X PCIE rev 0x0e pci1 at ppb0 bus 5 vga1 at pci1 dev 0 function 0 NVIDIA GeForce 6600 GT rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci0 dev 27 function 0 Intel 82801FB HD Audio rev 0x04: irq 10 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: CMedia CMI9880 (rev. 0.2), HDA version 0.9 azalia0: /usr/src/sys/dev/pci/azalia.c/1159 invalid PCM format: 0x delete_encodings... ppb1 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x04 pci2 at ppb1 bus 4 ppb2 at pci0 dev 28 function 1 Intel 82801FB PCIE rev 0x04 pci3 at ppb2 bus 3 mskc0 at pci3 dev 0 function 0 Marvell Yukon 88E8053 rev 0x15, Marvell Yukon-2 EC rev. A2 (0x1): irq 10 msk0 at mskc0 port A, address 00:11:d8:46:6f:bc eephy0 at msk0 phy 0: Marvell 88E Gigabit PHY, rev. 2 ppb3 at pci0 dev 28 function 2 Intel 82801FB PCIE rev 0x04 pci4 at ppb3 bus 2 mskc1 at pci4 dev 0 function 0 Marvell Yukon 88E8053 rev 0x15, Marvell Yukon-2 EC rev. A2 (0x1): irq 5 msk1 at mskc1 port A, address 00:11:d8:46:6a:42 eephy1 at msk1 phy 0: Marvell 88E Gigabit PHY, rev. 2 uhci0 at pci0 dev 29 function 0 Intel 82801FB USB rev 0x04: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801FB USB rev 0x04: irq 3 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801FB USB rev 0x04: irq 5 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3 at pci0 dev 29 function 3 Intel 82801FB USB rev 0x04: irq 10 usb3 at uhci3: USB revision 1.0 uhub3 at usb3 uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801FB USB rev 0x04: irq 11 usb4 at ehci0: USB revision 2.0 uhub4 at usb4 uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered ppb4 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0xd4 pci5 at ppb4 bus 1 vendor TI, unknown product 0x8025 (class serial bus subclass Firewire, rev 0x01) at pci5 dev 3 function 0 not configured ichpcib0 at pci0 dev 31 function 0 Intel 82801FB LPC rev 0x04: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801FB IDE rev 0x04: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: PIONEER, DVD-RW DVR-108, 1.20 SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 31 function 2 Intel 82801FR SATA rev 0x04: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide1: using irq 3 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD740GD-00FLA0 wd0: 16-sector PIO, LBA48, 70911MB, 145226112 sectors wd1 at pciide1 channel 0 drive 1: WDC WD1600YD-01NVB1 wd1: 16-sector PIO, LBA48, 157066MB, 321672960 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide1:0:1): using PIO
Bridge PF with spamd but getting RST packet
Hi, I am trying to configure spamd on the current bridge PF firewall which is running on OpenBSD 4.0 fxp0 and fxp1 both are setup as bridge interfaces the following is the rdr rule for spamd ## Spamd Stuff # Table that spamd updates table spamd persist table spamd-white persist file /etc/whitelist.txt # If not on whitelist, redirect to spamd rdr pass on $ext_if inet proto tcp from !spamd-white to any \ port smtp - 127.0.0.1 port spamd # Because this is a bridge, explicit route to this machine pass out route-to lo0 proto tcp from any to 127.0.0.1 port spamd ## Spamlogd Stuff # Keep whitelist hosts from expiring pass in log inet proto tcp from spamd-white to any \ port smtp keep state # Eventually I'll have a line to whitelist servers that my server talks to. the abovementioned PF rule was obtained from http://cisx1.uma.maine.edu/~wbackman/spamd.html I have noticed the following when i did a tcpdump on fxp1 02:18:13.451441 61.65.255.238.13868 127.0.0.1.8025: S 3447735838:3447735838(0) win 16384 mss 1460,nop,nop,sackOK,nop,wscale 0,nop,nop,timestamp 470257134 0 02:18:13.451566 127.0.0.1.8025 61.65.255.238.13868: R 0:0(0) ack 3447735839 win 0 Any idea?. Thanks, Edy
dual port syskonnect gigabit card
Hey all... We got a few SysKonnect SK-9S22 dual port cards, and they don't work under 4.0, nor under stable (as of 19/12/2006). We got these cards because it was listed in the msk(4) manual pages: http://www.openbsd.org/cgi-bin/man.cgi?query=mskapropos=0sektion=0manpath=OpenBSD+4.0arch=i386format=html I'm getting these in the log: Dec 19 12:15:38 xxx-server /bsd: mskc0 at pci2 dev 1 function 0 Schneider Koch SK-9Sxx rev 0x12, Marvell Yukon-2 XL rev. A1 (0x1): irq 11 Dec 19 12:15:38 xxx-server /bsd: msk0 at mskc0 port A, address 00:00:5a:72:80:89 Dec 19 12:15:38 xxx-server /bsd: msk0: no PHY found! Dec 19 12:15:38 xxx-server /bsd: msk1 at mskc0 port B, address 00:00:5a:72:80:8a Dec 19 12:15:38 xxx-server /bsd: msk1: no PHY found! Any hint is really appreciated. Thanks :)
Re: revision control system for system administration
Brian Candler wrote: That makes a lot of sense. But enforcing that policy might be difficult. This is important if you're relying on your gold server for disaster recovery purposes - if the target machines had some change made which nobody remembers and weren't reflected in the gold server, then any freshly-built machines will be non-functional. Alternatively, you could have the Gold machine periodically refresh the production machines' configuration, ensuring they match Gold. Anyone who ignores procedures probably deserves to spend time banging his head trying to figure out why his changes won't stick, and that mistake will only be made once.
Re: Negative temp sensor readings?
I have the exact same thing here. Just installed 4.0 GENERIC.MP on a
new Dell PowerEdge 2900 (my dmesg looks almost identical to yours),
and I have similar readings for the first two temperatures (picked up
on sensors.{0,1}).
-Ryan
On 12/20/06, Will H. Backman [EMAIL PROTECTED] wrote:
Has anyone else seen negative temperature sensor readings through
sysctl?
hw.sensors.0=ipmi0, Temp, -54.00 degC, OK
hw.sensors.1=ipmi0, Temp, -51.00 degC, OK
hw.sensors.2=ipmi0, Temp, 40.00 degC, WARNING
OpenBSD 4.0 (GENERIC.MP) #967: Sat Sep 16 20:38:15 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2146729984 (2096416K)
avail mem = 1834881024 (1791876K)
using 22937 buffers containing 214880256 bytes (209844K) of memory
mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x7ffbc000 (62
entries)
bios0: Dell Inc. PowerEdge 2950
ipmi0 at mainbus0: version 2.0 interface KCS iobase 0xca8/8 spacing 4
mainbus0: Intel MP Specification (Version 1.4) (DELL PE 01B2 )
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1596.14 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,NXE,LONG
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: apic clock running at 265MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.93 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,NXE,LONG
cpu1: 4MB 64b/line 16-way L2 cache
cpu2 at mainbus0: apid 7 (application processor)
cpu2: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.94 MHz
cpu2:
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,NXE,LONG
cpu2: 4MB 64b/line 16-way L2 cache
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU 5110 @ 1.60GHz, 1595.93 MHz
cpu3:
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,NXE,LONG
cpu3: 4MB 64b/line 16-way L2 cache
mpbios: bus 0 is type PCI
mpbios: bus 1 is type PCI
mpbios: bus 2 is type PCI
mpbios: bus 3 is type PCI
mpbios: bus 4 is type PCI
mpbios: bus 5 is type PCI
mpbios: bus 6 is type PCI
mpbios: bus 7 is type PCI
mpbios: bus 8 is type PCI
mpbios: bus 9 is type PCI
mpbios: bus 10 is type PCI
mpbios: bus 11 is type PCI
mpbios: bus 12 is type PCI
mpbios: bus 13 is type PCI
mpbios: bus 14 is type PCI
mpbios: bus 15 is type PCI
mpbios: bus 16 is type PCI
mpbios: bus 17 is type ISA
ioapic0 at mainbus0 apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
ioapic1 at mainbus0 apid 9 pa 0xfec81000, version 20, 24 pins
ioapic1: misconfigured as apic 0, remapped to apid 9 pci0 at mainbus0
bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel 5000X
Host rev 0x12 ppb0 at pci0 dev 2 function 0 Intel 5000 PCIE rev 0x12
pci1 at ppb0 bus 6
ppb1 at pci1 dev 0 function 0 Intel 6321ESB PCIE rev 0x01
pci2 at ppb1 bus 7
ppb2 at pci2 dev 0 function 0 Intel 6321ESB PCIE rev 0x01
pci3 at ppb2 bus 8
ppb3 at pci3 dev 0 function 0 ServerWorks PCIE-PCIX rev 0xc2
pci4 at ppb3 bus 9
bnx0 at pci4 dev 0 function 0 Broadcom BCM5708 rev 0x11: apic 8 int 16
(irq 11), address 00:18:8b:47:5c:ad brgphy0 at bnx0 phy 1: BCM5708C
10/100/1000baseT PHY, rev. 5
ppb4 at pci2 dev 1 function 0 Intel 6321ESB PCIE rev 0x01
pci5 at ppb4 bus 10
ppb5 at pci1 dev 0 function 3 Intel 6321ESB PCIE-PCIX rev 0x01
pci6 at ppb5 bus 11
ppb6 at pci0 dev 3 function 0 Intel 5000 PCIE rev 0x12
pci7 at ppb6 bus 1
ppb7 at pci7 dev 0 function 0 Intel IOP333 PCIE-PCIX rev 0x00
pci8 at ppb7 bus 2
mfi0 at pci8 dev 14 function 0 Dell PERC 5 rev 0x00: apic 9 int 14
(irq 5)
mfi0: logical drives 2, version 5.0.2-0003, 256MB RAM scsibus0 at mfi0:
2 targets sd0 at scsibus0 targ 0 lun 0: DELL, PERC 5/i, 1.00 SCSI3
0/direct fixed
sd0: 34176MB, 34176 cyl, 64 head, 32 sec, 512 bytes/sec, 69992448 sec
total
sd1 at scsibus0 targ 1 lun 0: DELL, PERC 5/i, 1.00 SCSI3 0/direct
fixed
sd1: 138752MB, 138752 cyl, 64 head, 32 sec, 512 bytes/sec, 284164096 sec
total
ppb8 at pci7 dev 0 function 2 Intel IOP333 PCIE-PCIX rev 0x00
pci9 at ppb8 bus 3
ppb9 at pci0 dev 4 function 0 Intel 5000 PCIE rev 0x12 pci10 at ppb9
bus 12 ppb10 at pci0 dev 5 function 0 Intel 5000 PCIE rev 0x12
pci11 at ppb10 bus 13
ppb11 at pci0 dev 6 function 0 Intel 5000 PCIE rev 0x12
pci12 at ppb11 bus 14
ppb12 at pci0 dev 7 function 0 Intel 5000 PCIE rev 0x12
pci13 at ppb12 bus 15
pchb1 at pci0 dev 16 function 0 Intel 5000 Error Reporting rev 0x12
pchb2 at pci0 dev 16 function 1 Intel 5000 Error Reporting rev 0x12
pchb3 at pci0 dev 16 function 2 Intel 5000 Error Reporting rev 0x12
pchb4 at pci0 dev 17 function 0 Intel 5000 Reserved rev 0x12
pchb5 at pci0 dev 19 function 0 Intel 5000 Reserved rev 0x12
pchb6 at pci0 dev 21 function 0 Intel 5000 FBD rev 0x12
pchb7 at pci0
Re: hotplugd umass kernel crash
Otto Moerbeek schrieb: On Wed, 20 Dec 2006, Michael wrote: Since it doesn't write anything to messages or any other file I wonder how I can get the kernel crash message + ddb trace + ddb ps into a file so I can post it here? attach a serial console, see http://www.openbsd.org/faq/faq7.html#SerCon -Otto Got no serial cable available right now so I made some photos... :D http://wp1050733.wp078.webpack.hosteurope.de/hotplug/dsci1679.jpg http://wp1050733.wp078.webpack.hosteurope.de/hotplug/dsci1680.jpg http://wp1050733.wp078.webpack.hosteurope.de/hotplug/dsci1681.jpg http://wp1050733.wp078.webpack.hosteurope.de/hotplug/dsci1682.jpg http://wp1050733.wp078.webpack.hosteurope.de/hotplug/dsci1683.jpg Would be nice if someone could look into that since I can't start hotplug right now... - Michael
Atheros AR5213 Support Status?
I've got an Atheros AR5213 card that I'm trying to use in a wireless access point. Unfortunately, it's experienced a number of odd issues, including device timeouts, inability to associate properly with an existing Prism-based access point running on OpenBSD 3.7, etc. I'm not going to go too heavily into the details of my problems, because I see from very recent posts to the list that support for this particular device is not fully functional (or at least was not as of the last couple of months). What I really want to know is, are these devices fully supported yet? If not, what stands in the way of full support? If it's not properly supported yet, does anyone have recommendations for a good, reasonably cheap wireless card that will work as an access point? Here's my full dmesg: OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(tm) 64 Processor 3000+ (AuthenticAMD 686-class, 512KB L2 cache) 2.01 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3 cpu0: Cool`n'Quiet K8 2010 Mhz: speeds: 2000 1800 1000 Mhz real mem = 267939840 (261660K) avail mem = 236662784 (231116K) using 3296 buffers containing 13500416 bytes (13184K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(c6) BIOS, date 08/26/05, BIOS32 rev. 0 @ 0xfba60, SMBIOS rev. 2.3 @ 0xf (34 entries) apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde90/240 (13 entries) pcibios0: PCI Exclusive IRQs: 3 5 10 11 12 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 NVIDIA nForce3 250 PCI Host rev 0xa1 pcib0 at pci0 dev 1 function 0 NVIDIA nForce3 250 ISA rev 0xa2 nviic0 at pci0 dev 1 function 1 NVIDIA nForce3 250 SMBus rev 0xa1 iic0 at nviic0 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA nForce3 250 USB rev 0xa1: irq 3, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 2 function 1 NVIDIA nForce3 250 USB rev 0xa1: irq 3, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0 at pci0 dev 2 function 2 NVIDIA nForce3 250 USB2 rev 0xa2: irq 3 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered nfe0 at pci0 dev 5 function 0 NVIDIA nForce3 LAN rev 0xa2: irq 10, address 00:16:ec:29:7c:ec rlphy0 at nfe0 phy 9: RTL8201L 10/100 PHY, rev. 1 auich0 at pci0 dev 6 function 0 NVIDIA nForce3 250 AC97 rev 0xa1: irq 3, nForce3 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0) audio0 at auich0 pciide0 at pci0 dev 8 function 0 NVIDIA nForce3 250 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST38410A wd0: 32-sector PIO, LBA, 8223MB, 16841664 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CD-R/RW SW-252F, R806 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 pciide1 at pci0 dev 10 function 0 NVIDIA nForce3 250 SATA rev 0xa2: DMA pciide1: using irq 11 for native-PCI interrupt ppb0 at pci0 dev 11 function 0 NVIDIA nForce3 250 AGP rev 0xa2 pci1 at ppb0 bus 1 ppb1 at pci0 dev 14 function 0 NVIDIA nForce3 250 PCI-PCI rev 0xa2 pci2 at ppb1 bus 2 ath0 at pci2 dev 6 function 0 Atheros AR5212 rev 0x01: irq 12 ath0: AR5213 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, FCC1A, address 00:0c:41:16:cb:d4 vga1 at pci2 dev 7 function 0 S3 ViRGE DX/GX rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pchb1 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb2 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb3 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb4 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 it0 at isa0 port 0x290/8: IT87 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6
Re: Atheros AR5213 Support Status?
On 12/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've got an Atheros AR5213 card that I'm trying to use in a wireless access point. Unfortunately, it's experienced a number of odd issues, including device timeouts, inability to associate properly with an existing Prism-based access point running on OpenBSD 3.7, etc. I'm not going to go too heavily into the details of my problems, because I see from very recent posts to the list that support for this particular device is not fully functional (or at least was not as of the last couple of months). What I really want to know is, are these devices fully supported yet? If not, what stands in the way of full support? If it's not properly supported yet, does anyone have recommendations for a good, reasonably cheap wireless card that will work as an access point? I'm using one with 4.0 in 11b hostap mode: ath0 at pci0 dev 13 function 0 Atheros AR5212 rev 0x01: irq 12 ath0: AR5213 5.9 phy 4.3 rf5112a 3.6, FCC2A*, address 00:0b:6b:57:31:d4 It's about the only way I can use it at the moment, it came with a PC Engines WRAP card that I bought recently. I figured if I couldn't get it to work in any manner I'd sell it on Ebay. I've got 2 other AR521x devices that I'd really like to get working in 11a mode, I believe that some have had success in 11a mode but I haven't. Right now, like you, I can't get the AR5213 card to associate with a 802.11b AP, and I can't get another AR5212 to associate to it when it's in 11a mode. I try snapshots every now and then. I've got several different brands of Prism 2.5 cards, PCI, miniPCI, and Cardbus, that all work solidly in hostap mode, Netgear, Linksys, Senao. So with the equipment I have I'm stuck with 11b and hope that I'll have some 11a networking soon. Greg
Re: Atheros AR5213 Support Status?
Hello, Did anyone ever try to power up Prism 2.5 cards for more than 100mW while on hostap mode? I have read the codes and it appeared that it can be up to 100mW even a 200mW card is inserted. Thanks, Kevin I've got several different brands of Prism 2.5 cards, PCI, miniPCI, and Cardbus, that all work solidly in hostap mode, Netgear, Linksys, Senao. So with the equipment I have I'm stuck with 11b and hope that I'll have some 11a networking soon. Greg
Re: Bridge PF with spamd but getting RST packet
Edy [EMAIL PROTECTED] wrote: Hi, I am trying to configure spamd on the current bridge PF firewall which is running on OpenBSD 4.0 fxp0 and fxp1 both are setup as bridge interfaces the following is the rdr rule for spamd ## Spamd Stuff # Table that spamd updates table spamd persist table spamd-white persist file /etc/whitelist.txt # If not on whitelist, redirect to spamd rdr pass on $ext_if inet proto tcp from !spamd-white to any \ port smtp - 127.0.0.1 port spamd # Because this is a bridge, explicit route to this machine pass out route-to lo0 proto tcp from any to 127.0.0.1 port spamd try this fragment instead, note that there is no pass in rdr and the route-to is applied to an incoming packet. Using tags to match nat/rdr rules to filter rules is much easier. # If not on whitelist, redirect to spamd rdr on $ext_if inet proto tcp from !spamd-white to any \ port smtp tag SPAMD - 127.0.0.1 port spamd pass in route-to lo0 tagged SPAMD keep state Can
