Re: re(4) panic on 13 Jan 2009 snap
Hi ! I got the same issue, before last revision of src/sys/dev/pci/ppb.c by Mark (kettenis@). Yet your trace and ps output is rather different from what I got back then. I am not familiar enough with the kernel internals to state about the similarity of our situations. The issue still shows up if I don't disable apm at boot. Have you done so ? Regards. hyjial 2009/1/19 Bryan bra...@gmail.com: Greetings, I am still having issues with the re(4) interface on my server. I mentioned this on the list, and was told that the re(4) fix was in. I am running the 13 Jan 2009 snapshot, and I can still reproduce the error on a regular basis. It goes like this... 1. push the power button 2. boot openbsd 3. panic panic: config_detach: forced detach of re0 failed (45) Stopped atDebugger+0x4: leave 4. issue boot sync 5. system restarts 6. re(4) starts with no issues if I shutdown, or do a warm reboot, I have to do step 4 and restart the system. I do have a picture of the error I receive when the system is going to panic. As I have no console, and puc(4) is useless for console use, the picture can be found here: http://picasaweb.google.com/lh/photo/Das3TsaFIvV1I-zKTHvaog?feat=directlink I also did a ps, and trace of the system. here is the photo of that. http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink If someone has any other ideas, please let me know. The dmesg below is when the server will come up after a boot sync and a warm restart. I do intend on updating to the latest snapshot (jan 18th) in the next few minutes. Regards, Bryan Brake OpenBSD 4.4-current (GENERIC.MP) #35: Tue Jan 13 10:19:47 MST 2009 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.4 1 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR real mem = 3488833536 (3327MB) avail mem = 3384754176 (3227MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/23/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf06e0 (54 entries) bios0: vendor American Megatrends Inc. version 5.32 date 10/23/2008 bios0: HP-Pavilion FK484AV-ABA m9400t acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SLIC SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S3) PS2M(S3) USB0(S3) USB1(S3) USB2 (S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) GBE_(S4) P0P4(S4) P0P5(S4) P0P 6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.4 0 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.4 0 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.4 0 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus 3 (P0P4) acpiprt3 at acpi0: bus -1 (P0P5) acpiprt4 at acpi0: bus 2 (P0P6) acpiprt5 at acpi0: bus -1 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus -1 (P0P9) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB bios0: ROM list: 0xc/0xe200 0xce800/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82G33 Host rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82G33 PCIE rev 0x02: apic 4 int 16 (irq 5) pci1 at ppb0 bus 5 vga1 at pci1 dev 0 function 0 NVIDIA GeForce 9300 GE 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 82801I USB rev 0x02: apic 4 int 16 (irq 5) uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x02: apic 4 int 21 (irq 3) ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x02: apic 4 int 18 (irq 10) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev
Re: emul.linux not playing well with bsd.mp
In gmane.os.openbsd.misc, you wrote: On 17-Jan-2009 Predrag Punosevac wrote: kernel emulator for linux binaries is not playing well with bsd.mp kernel I've encountered precisely the same issue on Acer Aspire One netbook. You don't need to run an MP kernel on that machine any more. With a recent, -current GENERIC will work.
Cisco IPSec Security Association Idle Timers and isakmpd
Hi, I noticed that the cisco end of a VPN I configured on my openBSD sends a DELETE message after a certain amount of idle time. This feature is described in http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/ftsaidle .html#wp1045897 The effect is, that the VPN no longer works. openBSD still shows the routes active ( in netstat -rnf encap ) and sends packets out to the remote site. It does not try to reestablish the phase 2 sa. Is this a bug or is it that just an incompatibility with ciscos 'idle time' feature ( which may not be 'standard' ) Regards Christoph
Re: Cisco IPSec Security Association Idle Timers and isakmpd
Hi, On Mon, Jan 19, 2009 at 04:56:25PM +0100, Christoph Leser wrote: I noticed that the cisco end of a VPN I configured on my openBSD sends a DELETE message after a certain amount of idle time. Which SAs get deleted? isakmp, ipsec or both? HJ.
Re: Cisco IPSec Security Association Idle Timers and isakmpd
Le 19 janv. 09 ` 17:37, Hans-Joerg Hoexer a icrit : Hi, On Mon, Jan 19, 2009 at 04:56:25PM +0100, Christoph Leser wrote: I noticed that the cisco end of a VPN I configured on my openBSD sends a DELETE message after a certain amount of idle time. Which SAs get deleted? isakmp, ipsec or both? HJ. When you execute netstat -rn, do you always see the SA on your OpenBSD, after DELETE message has been sended ?
Re: Capturing useful debugging info on a hung machine (T1000)
Stuart Henderson wrote:
set ddb.console=1 (needs to be done with securelevel=0; add
to sysctl.conf and reboot), then you can send a BREAK over the
serial port and usually it will put you into DDB.
I set the sysctl a while ago.
It hung again today whilst I was trying to SSH an ISO to it, so I used
the ALOM card to send it a break. It didn't work. Is there anything else
I can do? I'm guessing its hardlocking, so I suppose the only thing I
can do is have something writing lots of logging.
Once I had rebooted it again, I decided to test that the ddb.console
thing was working, so I waited to get the login prompt, broke out to the
ALOM prompt, and sent a break. It worked, and dropped to ddb
Excellent. Test successful, I figured I should try to reboot cleanly, so
I issued boot sync. Oh dear. This caused panic: switch wchan
Everything I have I have enclosed below.
--
Si1entDave
OpenBSD/sparc64 (slash.dotslash.org.uk) (console)
login: sc break -c
Are you sure you want to send a break to the system [y/n]? y
Enter #. to return to ALOM.
SC Alert: SC Request to send Break to host.
kdb breakpoint at 14002c0
Stopped at Debugger+0x4: nop
ddb{0} boot sync
syncing disks... panic: switch wchan
kdb breakpoint at 14002c0
Stopped at Debugger+0x4: nop
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
24640 1 24640 0 3 0x2004082 ttyin getty
19568 1 19568 0 3 0x280 selectcron
17158 1 17158 0 3 0x280 selectsshd
20330 6946 6946 67 3 0x2000180 netconhttpd
5624 6946 6946 67 3 0x2000180 netconhttpd
12876 6946 6946 67 3 0x2000180 netconhttpd
17194 6946 6946 67 3 0x2000180 netconhttpd
3908 6946 6946 67 3 0x2000180 netconhttpd
25437 1 25437 0 3 0x2000180 selectinetd
*22743 1 22743 0 3 0x2040180 selectsendmail
6946 1 6946 67 3 0x2000180 selecthttpd
19349 13288748 83 3 0x2000180 poll ntpd
13288748748 83 3 0x2000180 poll ntpd
748 1748 0 3 0x280 poll ntpd
1234 27316 27316 73 3 0x2000100 ffs_fsync syslogd
27316 1 27316 0 3 0x288 netio syslogd
42 0 0 0 3 0x2100200 bored crypto
41 0 0 0 3 0x2100200 aiodoned aiodoned
40 0 0 0 3 0x2100200 syncerupdate
39 0 0 0 3 0x2100200 cleaner cleaner
38 0 0 0 30x100200 reaperreaper
37 0 0 0 3 0x2100200 pgdaemon pagedaemon
36 0 0 0 3 0x2100200 pftm pfpurge
35 0 0 0 70x100200idle31
34 0 0 0 70x100200idle30
33 0 0 0 70x100200idle29
32 0 0 0 70x100200idle28
31 0 0 0 70x100200idle27
30 0 0 0 70x100200idle26
29 0 0 0 70x100200idle25
28 0 0 0 70x100200idle24
27 0 0 0 70x100200idle23
26 0 0 0 70x100200idle22
25 0 0 0 70x100200idle21
24 0 0 0 70x100200idle20
23 0 0 0 70x100200idle19
22 0 0 0 70x100200idle18
21 0 0 0 70x100200idle17
20 0 0 0 70x100200idle16
19 0 0 0 70x100200idle15
18 0 0 0 70x100200idle14
17 0 0 0 70x100200idle13
16 0 0 0 70x100200idle12
15 0 0 0 70x100200idle11
14 0 0 0 70x100200idle10
13 0 0 0 70x100200idle9
12 0 0 0 70x100200idle8
11 0 0 0 70x100200idle7
10 0 0 0 70x100200idle6
9 0 0 0 70x100200idle5
8 0 0 0 70x100200idle4
7 0 0 0 70x100200idle3
6 0 0 0 70x100200
Re: Cisco IPSec Security Association Idle Timers and isakmpd
-Urspr|ngliche Nachricht- Von: dug [mailto:d...@xgs-france.com] Gesendet: Montag, 19. Januar 2009 17:44 An: Hans-Joerg Hoexer Cc: Christoph Leser; misc@openbsd.org Betreff: Re: Cisco IPSec Security Association Idle Timers and isakmpd Le 19 janv. 09 ` 17:37, Hans-Joerg Hoexer a icrit : Hi, On Mon, Jan 19, 2009 at 04:56:25PM +0100, Christoph Leser wrote: I noticed that the cisco end of a VPN I configured on my openBSD sends a DELETE message after a certain amount of idle time. Which SAs get deleted? isakmp, ipsec or both? HJ. When you execute netstat -rn, do you always see the SA on your OpenBSD, after DELETE message has been sended ? I cannot tell for sure. Most DELETE messages come in after an new SA has been established, so you would expect to see the SA in netstat output, wouldn't you. I would say that I see the SA, when only IPSEC is DELETED, but no SA, when IPSEC and ISAKMP is deleted.
Re: 10G NIC - Netxen
Thanks Tico!! I was wondering about the fiber version and not the copper. -Parvinder Bhasin On Jan 13, 2009, at 9:29 PM, tico wrote: Parvinder Bhasin wrote: Hi, Anyone have any experience with 10G NICs from Netxen - Fiber and OBSD 4.x? I don't see under the supported NICs list. Thanks Parvinder, By searching in the usual places I found the following: I went to the misc@ archives and searched netxen and got the following result: http://marc.info/?l=openbsd-miscm=117685930328686w=2 The want page lists 10Gig ethernet as an area of development currently: http://www.openbsd.org/want.html And the man pages for -current list the 'nx' driver, but not 4.4 : http://www.openbsd.org/cgi-bin/man.cgi?query=nxapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html And CVS shows that nx is no longer in the tree: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/Attic/if_nx.c As for the hardware itself, I have no experience with it. -Tico
OpenBSD 4.4 pf+vlan+bridge problem
Hello, I have a problem with pf+bridge+vlan (multicast traffic) and I googled a lot, read the manuals and so on - no help. Finally I posted on wrong place :( sorry. Hopefully this time I'm writing to right place. Following setup is made for multicast traffic separation from one lan to multiple vlans. Setup: Two physical interfaces bnx0 bnx1 interfaces bnx0 and bnx1 has vlans: bnx0 vlan1100 bnx1 vlan1101 vlan1102 vlan1103 vlan1104 vlan1105 vlan1106 vlan1107 vlan1108 Bridge setup: bridge0 has all vlans as bridge members (vlan1100, vlan1101 ... vlan1108) PF config: block out on bnx1 all block out on vlan1100 all block out on vlan1101 all block out on vlan1102 all block out on vlan1103 all block out on vlan1104 all block out on vlan1105 all block out on vlan1106 all block out on vlan1107 all block out on vlan1108 all pass out quick on vlan1101 proto udp from any to 239.16.1.1 pass out quick on vlan1102 proto udp from any to 239.16.1.2 pass out quick on vlan1103 proto udp from any to 239.16.1.3 Wishful thinking, what the result should be: All multicast streams are available on vlan1100 and recieved via bnx0/vlan1100. Bridge should stream the multicast packets to what ever vlan - its the place where pf should help. Stream: 239.16.1.1 should be available only on vlan1101, and 239.16.1.2 avialable on vlan1102 and so on. . Real Result: Stream 239.16.1.1 is available on all three vlans: 11101,1102,1103 - same thing happens with other two streams (239.16.1.2, 239.16.1.3) It's really weird what's going on or did I understood something wrong and configuration is not correct? Thank you.
ftp-proxy on a nat firewall
Hello. I'm setting up an OpenBSD (4.4-stable) NAT firewall (with a
couple servers behind it) for the first time. Everything seems to work
except for active ftp from machines behind the firewall. Active ftp
connections made from the firewall itself do work, though. I do have
net.inet.ip.forwarding turned on, and ftp-proxy enabled.
I'll paste my full pf.conf at the end of this message, but here are the
lines i believe are relevant to ftp-proxy:
nat on $ext_if from !($ext_if) - ($ext_if)
nat-anchor ftp-proxy/*
rdr-anchor ftp-proxy/*
rdr pass on $int_if proto tcp to port ftp - 127.0.0.1 port 8021
anchor ftp-proxy/*
pass out proto tcp from lo to any port ftp
I have tried starting ftp-proxy with the debugging turned up a bit and i
end up getting this:
# ftp-proxy -d -D 6
listening on 127.0.0.1 port 8021
#1 FTP session 1/100 started: client 192.168.1.16 to server
192.43.244.161 via proxy SNIP: my external IP
#1 active: server to client port 59694 via port 62694
#1 client close
#1 ending session
Note: i did change the output slightly--i removed my external IP. On the
client i logged in to an anonymous ftp server, then tried an ls. When
that hung, i hit Ctrl-C, which is logged as the client close line.
What am i doing wrong? I'll put my full pf.conf below. If anything seems
amiss, i'd appreciate a whack with the clue stick.
ext_if = vr0
int_if = fxp0
icmp_types = { echoreq, unreach }
name_server = 192.168.1.2
email_server = 192.168.1.4
email_ports = { smtp, pop3 }
web_server = 192.168.1.5
web_ports = { http, https }
workstation = 192.168.1.16
workstation_ports = { ssh, 6881:6889 }
table martians persist { 127.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, \
10.0.0.0/8, 169.254.0.0/16, 192.0.2.0/24, 0.0.0.0/8, \
240.0.0.0/4 }
# options
set block-policy return
set loginterface $ext_if
set skip on lo
# packet hygiene
scrub in all fragment reassemble
# nat
nat on $ext_if from !($ext_if) - ($ext_if)
nat-anchor ftp-proxy/*
rdr-anchor ftp-proxy/*
rdr pass on $int_if proto tcp to port ftp - 127.0.0.1 port 8021
# Port forwarding
rdr on $ext_if proto { tcp, udp } from any to $ext_if port domain -
$name_server
rdr on $ext_if proto tcp from any to $ext_if port $email_ports -
$email_server
rdr on $ext_if proto tcp from any to $ext_if port $web_ports -
$web_server
rdr on $ext_if proto tcp from any to $ext_if port $workstation_ports -
$workstation
# filter rules
block in all
block quick inet6 all
pass out keep state
antispoof quick for { lo, $int_if }
block in quick on $ext_if from martians to any
block out quick on $ext_if from any to martians
anchor ftp-proxy/*
pass out proto tcp from lo to any port ftp
pass proto { tcp, udp } from any to $name_server port domain
pass proto tcp from any to $email_server port $email_ports synproxy
state
pass proto tcp from any to $web_server port $web_ports synproxy state
pass proto tcp from any to $workstation port $workstation_ports
pass in inet proto icmp all icmp-type $icmp_types keep state
pass from !($ext_if) to any keep state
Dan RamaleyDial Center 118, Drake University
Network Programmer/Analyst 2407 Carpenter Ave
+1 515 271-4540Des Moines IA 50311 USA
Re: cwm maximized mode
On Mon, 19 Jan 2009 03:24:54 +0300 Alexander Polakov polac...@gmail.com wrote: What do you think about cwm(1) maximized mode? I find it rather useful on small screens. bind 4-f maximize That's one key-combination to maximize the current window. If the majority of cwm(1) users where using small screens, I might give your patch a vote.
Re: cwm maximized mode
On Mon, Jan 19, 2009 at 5:50 PM, Thomas Pfaff tpf...@tp76.info wrote: On Mon, 19 Jan 2009 03:24:54 +0300 Alexander Polakov polac...@gmail.com wrote: What do you think about cwm(1) maximized mode? I find it rather useful on small screens. bind 4-f maximize That's one key-combination to maximize the current window. If the majority of cwm(1) users where using small screens, I might give your patch a vote. Personally, I always use maximized windows in non-tiling window managers, so this would be great.
man page style question
hi there, i was just reading ral(4) and rum(4) to look for devices that support these. i noticed that while ral(4) lists all the devices in one paragraph, rum(4) on the other hand lists them one at a line. i think it might be nice to have them consistent. (and just in case anyone asked, i find the one at a line easier to read) if people with commit decide what's to be, i can send patches either way... -f -- god? i'm no god. god has mercy.
Re: man page style question
On Mon, Jan 19, 2009 at 11:05:48PM +0100, frantisek holop wrote: hi there, i was just reading ral(4) and rum(4) to look for devices that support these. i noticed that while ral(4) lists all the devices in one paragraph, rum(4) on the other hand lists them one at a line. i think it might be nice to have them consistent. (and just in case anyone asked, i find the one at a line easier to read) if people with commit decide what's to be, i can send patches either way... rum(4) is typical of the way we list supported hardware. however when ral(4) came along, it was used by so many devices that we decided to put the lists into paragraphs to avoid having an enormously long page. so, no patches required. jmc
Re: 10G NIC - Netxen
On Mon, 19 Jan 2009, Parvinder Bhasin wrote: Thanks Tico!! I was wondering about the fiber version and not the copper. -Parvinder Bhasin take a look in the source tree for if_nxe.c diana
You've received A Hallmark E-Card!
Hallmark.comShop OnlineHallmark MagazineE-Cards MoreAt Gold Crown You have recieved A Hallmark E-Card. Hello! You have recieved a Hallmark E-Card. To see it, click here, There's something special about that E-Card feeling. We invite you to make a friend's day and send one. Hope to see you soon, Your friends at Hallmark Your privacy is our priority. Click the Privacy and Security link at the bottom of this E-mail to view our policy. Hallmark.com | Privacy Security | Customer Service | Store Locator
Re: Port ZFS to OpenBSD
On Sun, Jan 18, 2009 at 9:24 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Sun, 2009-01-18 at 14:28 +0100, Matthias Kilian wrote: On Sun, Jan 18, 2009 at 04:29:37AM -0800, Mike Swanson wrote: As marco already stated, it could be a kernel module. But it won't. Why? Because nobody will write it. Who is nobody anyway? He's a french guy. I've seen him during p2k8 in Budapest ;-) (did anyone take a picture of him?) *sigh* -- Antoine Jacoutot ajacou...@bsdfrog.org If you really really want ZFS, run an OpenSolaris box. It's not going to kill you. It's clear there will be no ZFS in OpenBSD. It's not a priority of the developers. If running an OpenSolaris box is against your ethics, religion, or common sense, then no ZFS for you! BTW, Everything I've read about ZFS on FreeBSD says that it sucks, at least until FreeBSD 8.0 is out. Panics under high load are common. Right now, the most complete and reliable ZFS experience is going to be on OpenSolaris. I'm running Nevada Build 105 and have no problems.
altq all features of original altqd why do not provided ?????????? ?
Hello Misc, Will the return of the demon altqd in the main repository? Indeed, in the nucleus left all his ability and threw only the demon, if that included pf, it sells only half of what opportunities lie in the nucleus. For example conditioner(ALTQ_CDNR) and do not use blue(ALTQ_BLUE). If you can not recover himself daemon while to realize its full support in pf All possibilities are provided altqd? Total 6 features do not provided in pf. optionsALTQ# Manipulate network interfaces' output queues optionsALTQ_BLUE # Stochastic Fair Blue --not in pf optionsALTQ_CBQ# Class-Based Queueing optionsALTQ_CDNR # Diffserv Traffic Conditioner -- not in pf optionsALTQ_FIFOQ # First-In First-Out Queue --not in pf optionsALTQ_FLOWVALVE # RED/flow-valve (red-penalty-box) --not in pf optionsALTQ_HFSC # Hierarchical Fair Service Curve optionsALTQ_LOCALQ # Local queueing discipline --not in pf optionsALTQ_PRIQ # Priority Queueing optionsALTQ_RED# Random Early Detection optionsALTQ_RIO# RED with IN/OUT optionsALTQ_WFQ# Weighted Fair Queueing -- not in pf -- Best regards, irix mailto:i...@ukr.net
Re: Port ZFS to OpenBSD
BTW, Everything I've read about ZFS on FreeBSD says that it sucks, at least until FreeBSD 8.0 is out. Panics under high load are common. I'm using ZFS (two pools - data and root) on FreeBSD 7.1 and it seems to be quite stable. The load is not too high but there's no problem when compiling entire xorg and xfce with a qemu session running in background. -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org
new future for altq in pf
Hello , Will there be realized in the pf + altq possibility of creating a dynamic queue in one rule that could create a queue using the masks for an entire subnet??? This is implemented in ipfw from FreeBSD, for example: reference mask 0x create your own channel 1M for each IP. / sbin / ipfw pipe 1 config bw 1000Kbit / s / sbin / ipfw queue 1 config pipe 1 weight 50 mask dst-ip 0x / sbin / ipfw add queue 1 ip from any to 192.168.0.1/24 -- Best regards, irix mailto:i...@ukr.net
Re: new future for altq in pf
Hello Misc, Sorry, for example /sbin/ipfw add pipe 1 config bw 128kbit/s mask src-ip 0x /sbin/ipfw add pipe 2 config bw 128kbit/s mask dst-ip 0x each ip in this pipes take individual channel 128Kbit -- Best regards, irix mailto:i...@ukr.net
OT: Re: Port ZFS to OpenBSD
On Tue, Jan 20, 2009 at 12:26 AM, Edho P Arief edhopr...@gmail.com wrote: I'm using ZFS (two pools - data and root) on FreeBSD 7.1 and it seems to be quite stable. The load is not too high but there's no problem when compiling entire xorg and xfce with a qemu session running in background. http://wiki.freebsd.org/ZFSKnownProblems From what I remember, the zfs porting person basically says that it is not ready for production use on freebsd at the moment. Use at your own risk. -- http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted. -- Gene Spafford learn french: http://www.youtube.com/watch?v=j1G-3laJJP0feature=related
Re: Port ZFS to OpenBSD
On Tue, Jan 20, 2009 at 12:26:48PM +0700, Edho P Arief wrote: BTW, Everything I've read about ZFS on FreeBSD says that it sucks, at least until FreeBSD 8.0 is out. Panics under high load are common. I'm using ZFS (two pools - data and root) on FreeBSD 7.1 and it seems to be quite stable. The load is not too high but there's no problem when compiling entire xorg and xfce with a qemu session running in background. well goody gumdrops. exactly what does this have to do with OpenBSD? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: OT: Re: Port ZFS to OpenBSD
On Tue, Jan 20, 2009 at 12:52:19AM -0500, bofh wrote: On Tue, Jan 20, 2009 at 12:26 AM, Edho P Arief edhopr...@gmail.com wrote: I'm using ZFS (two pools - data and root) on FreeBSD 7.1 and it seems to be quite stable. The load is not too high but there's no problem when compiling entire xorg and xfce with a qemu session running in background. http://wiki.freebsd.org/ZFSKnownProblems From what I remember, the zfs porting person basically says that it is not ready for production use on freebsd at the moment. Use at your own risk. I expect this thread to have even less impact on OpenBSD than this one did: http://marc.info/?l=openbsd-miscm=11997608978w=2 -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
