Re: cvsup/cvsync/anoncvs
On 5/30/07, MiK[3]Zz [EMAIL PROTECTED] wrote: Hi, i am goin to set up cvsup/anoncvs/cvsync server, but don't knwo how. Can you help me with configuration of these *cvs* servers? I have already write an e-mail to [EMAIL PROTECTED], but w/o any answer. Thanks for help. Here is information how to run a anoncvs-server. http://www.openbsd.org/anoncvs.html#MIRROR You probobly need to do some reading before, it can take some tweaking. br dunceor
accessing the MBR in multibooted systems?
Section 4.8 of the FAQ discusses how to capture the PBR for multibooting with dd: # dd if=/dev/rwd0a of=openbsd.pbr bs=512 count=1 Two questions. * For stand-alone installations, is the PBR the same thing as the MBR? * More importantly, how can I use dd to access the MBR in a multibooted system of Vista OpenBSD? Thanks for any insight.
Re: Snapshots src/sys tarballs
On Wed, 2007-05-30 at 15:59 -0600, Theo de Raadt wrote: [Jimmy Mitchener wrote:] Is there a reason snapshots do not currently come with a src/sys.tar.gz as releases do? Because every snapshot for every architecture is done on a different tree, and some are even done 5-6 times a day. So this would require, if I can guess this right, 2.6GB per day. Supplied over a T1. Obviously a full tarball isn't the answer, but how about enough information to reproduce the source code used to make the snapshot? Something along the lines of the timestamp for the cvs update command mentioned by Han Boetes elsewhere in the thread, plus the noncommitted diffs, made available in an extra file or files written as part of the automated snapshot build procedure. It seems like a problem even my rather limited programming skills could solve, assuming I can find the time. While the FAQ claims there is no significant benefit, I would think that anything that could potentially make fixing bugs easier (especially for code which may not be available from the CVS server) should at least be strongly considered. It is well known in the free software community that the more eyeballs look at source code, the more bugs get found and fixed. -- Shawn K. Quinn [EMAIL PROTECTED]
acpi/ehci/pcibios broken on Sony VGN-FZ145E
Just installed a recent OpenBSD snapshot (May25) on my brand new Sony VGN-FZ145E. Main issues seem to be in the following areas which must all be disabled to boot - acpi - ehci - pcibios Happy to test any patches to try to fix these issues... The very bottom of the email shows the error when each of the above is enabled, but first a successful boot dmesg with all 3 disabled: OpenBSD 4.1-current (GENERIC) #178: Fri May 25 03:22:20 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (GenuineIntel 686-class) 1.80 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 cpu0: unknown Core FSB_FREQ value 2 (0x4288) --- new processor. Needs an FSB_FREQ to be added. Happy to provide a patch if someone could point me to the right value to use. real mem = 2137419776 (2038MB) avail mem = 1943977984 (1853MB) using 4278 buffers containing 106995712 bytes (104488K) of memory User Kernel Config UKC disable pcibios 305 pcibios0 disabled UKC disable ehci 137 ehci* disabled 138 ehci* disabled UKC quit Continuing... mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 04/03/07, BIOS32 rev. 0 @ 0xfdbd0, SMBIOS rev. 2.4 @ 0xdc010 (17 entries) bios0: Sony Corporation VGN-FZ145E pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xc/0xee00! 0xdc000/0x4000! 0xe/0x1800! acpi at mainbus0 not configured cpu0 at mainbus0 cpu0: EST: unknown system bus clock pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x2a00 rev 0x0c -- Mobile PM965/GM965/GL960 Memory Controller Hub vga1 at pci0 dev 2 function 0 vendor Intel, unknown product 0x2a02 rev 0x0c: can't map aperture : AGP GART -- Mobile GM965/GL960 Integrated Graphics Controller wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) vendor Intel, unknown product 0x2a03 (class display subclass miscellaneous, rev 0x0c) at pci0 dev 2 function 1 not configured -- Mobile GM965/GL960 Integrated Graphics Controller uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: irq 5 uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: irq 11 Intel 82801H USB rev 0x03 at pci0 dev 26 function 7 not configured azalia0 at pci0 dev 27 function 0 Intel 82801H HD Audio rev 0x03: irq 11 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: 0x8384/0x7662 (rev. 2.1), HDA version 1.0 azalia0: codec: 0x14f1/0x2c06 (rev. 0.0), HDA version 1.0 azalia0: codec[1]: No support for modem function groups azalia0: codec[1]: No audio function groups audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x03 pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x03 pci2 at ppb1 bus 4 ppb2 at pci0 dev 28 function 2 Intel 82801H PCIE rev 0x03 pci3 at ppb2 bus 6 vendor Intel, unknown product 0x4229 (class network subclass miscellaneous, rev 0x61) at pci3 dev 0 function 0 not configured -- PRO/Wireless 4965 AG or AGN Network Connection ppb3 at pci0 dev 28 function 4 Intel 82801H PCIE rev 0x03 pci4 at ppb3 bus 8 mskc0 at pci4 dev 0 function 0 Marvell Yukon 88E8036 rev 0x16, Yukon-2 FE (0x1): irq 5 msk0 at mskc0 port A, address xx:xx:xx:xx:xx:xx eephy0 at msk0 phy 0: Marvell 88E3082 10/100 PHY, rev. 3 ukphy0 at msk0 phy 3: Generic IEEE 802.3u media interface, rev. 0: OUI 0x121012, model 0x0004 ukphy0: no media present ukphy1 at msk0 phy 4: Generic IEEE 802.3u media interface, rev. 0: OUI 0x020802, model 0x0002 ukphy2 at msk0 phy 5: Generic IEEE 802.3u media interface, rev. 0: OUI 0x020802, model 0x0002 ukphy3 at msk0 phy 6: Generic IEEE 802.3u media interface, rev. 0: OUI 0x024c02, model 0x0013 ukphy4 at msk0 phy 7: Generic IEEE 802.3u media interface, rev. 0: OUI 0x020802, model 0x0002 uhci2 at pci0 dev 29 function 0 Intel 82801H USB rev 0x03: irq 10 uhci3 at pci0 dev 29 function 1 Intel 82801H USB rev 0x03: irq 10 uhci4 at pci0 dev 29 function 2 Intel 82801H USB rev 0x03: irq 7 Intel 82801H USB rev 0x03 at pci0 dev 29 function 7 not configured ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xf3 pci5 at ppb4 bus 9 cbb0 at pci5 dev 3 function 0 TI PCIXX12 CardBus rev 0x00: irq 5 vendor TI, unknown product 0x803a (class serial bus subclass Firewire, rev 0x00) at pci5 dev 3 function 1 not configured -- PCIxx12 OHCI Compliant IEEE 1394 Host Controller TI PCIXX12 Multimedia Card Reader rev 0x00 at pci5 dev 3 function 2 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 10 device 0 cacheline 0x10, lattimer 0x20 pcmcia0 at cardslot0 pcib0 at pci0 dev 31 function 0 vendor Intel, unknown product 0x2815 rev 0x03 -- 82801HEM (ICH8M) LPC Interface Controller pciide0 at pci0 dev 31 function 1 vendor Intel, unknown product 0x2850 rev 0x03: DMA (unsupported), channel 0 configured to compatibility, channel 1
Linuxwochen Vienna 2007 , May 31 - Jun 2, 2007, Vienna
Hi, Martin and Teemu will be at the Urania this week, if you are in the area of Vienna, feel free to drop by and say hello http://www.linuxwochen.at/2007/Wien I'm of course stuck in Berlin this year (great scheduling guys ;-) http://www.linuxtag.org/2007/en/ Wim. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= https://kd85.com/notforsale.html --
Re: Snapshots src/sys tarballs
Because every snapshot for every architecture is done on a different tree, and some are even done 5-6 times a day. So this would require, if I can guess this right, 2.6GB per day. Supplied over a T1. Obviously a full tarball isn't the answer, but how about enough information to reproduce the source code used to make the snapshot? Sure, it does not look like it's a lot of work. Now imagine what happens in reality. Architecture A is 10% in the build. Architecture B is 30% in the build. Architecture C is 75% in the build. All three from the same, NFS mounted, source tree. A spiffy userland diff arrives, which will be put in the snapshot. It affects src/bin/foo, src/usr.bin/bar and src/usr.sbin/baz. After the diff is applied, it is probably too late for architecture C, which will have these changes in its next snapshot, and all of it or part of it will be in the A and B snapshots. If you want enough information to reproduce the snapshot, this means that every time a diff is added to the common source tree, or every time a partial cvs update is made in this common source tree, one has to check all the currently running snapshots to see how far they are and what part of the update will really end up in the tarballs. This is not something you can do with scripts only. The only way to access your request is to change the process used in making snapshots. Guess what? This will not happen, because we are satisfied with the current process. This can be frustrating to end users, but given that unpublished diffs don't stay long in snapshots (they either get dropped or commited soon), this is something we developers thing you can live with. It is well known in the free software community that the more eyeballs look at source code, the more bugs get found and fixed. BTW, this is one of the most successfull lies in the free software community. Miod
Re: : serial terminal
Another issue that may be interesting: Is this a server-like PC where you can tweak the serial console usage from the BIOS? I saw strange behaviour on a HP ProLiant DL145 G2 (I think) where for some configuration of the serial BIOS console, the login promp from OpenBSD on the serial port came and went depending on if I attached to the telnet-emulated-through-BIOS serial console through the Integrated Lights-Out ethernet connector. Bottom line. Are there interesting BIOS settings for serial console? On Wed, May 30, 2007 at 11:30:56AM -0400, Woodchuck wrote: On Tue, 29 May 2007, Maurice Janssen wrote: Hi, I'm trying to use a VT420 serial terminal on an i386 box running 4.1-stable. Not as a system console, just as an extra screen to login. The output of the boot loader and kernel output should go to the monitor, as usual. The terminal is hooked up to the first serial port with a null modem cable. I changed the tty00 line of /etc/ttys to: tty00 /usr/libexec/getty std.9600 vt220 on secure and sent -HUP to init. There's a getty process on tty00, but there's no login: prompt on the terminal. Everything I type on the terminal is echoed on the screen, so the cable is OK (local echo is off). H. Look into two things, no, make that three: 1) The settings on the terminal, whether XON/XOFF or RTS/CTS synchronization is selected, also baud rate, parity, 8/7 bits. Try 8 bits, No parity, 1 stop bit (8N1). 2) The settings on the tty, from # stty -a /dev/tty00 when the getty is running. 3) There are null modem cables, and there are null modem cables. Some are just plain junk, providing only cross over of the two data pins and if you're lucky, a ground. Others implement various ideas of what a null modem cable should be; the opinions of what a null modem cable differed between Digital, who made your terminal and IBM, who designed the PeeCee. The funny thing is, when I start 'tip tty00' on the machine (while logged in at the keyboard+monitor), the login: prompt appears on the terminal. Yeah, this is weird. You should be able to get the login: prompt by at most hitting the carriage return on the 420 twice. Try to set up everything for XON/XOFF flow control. When I quit tip, I can login at the terminal. When I logout from the terminal, the login: prompt doesn't appear (but everything I type is echoed to the terminal screen as before). I can start tip again, and then the login: prompt shows up again. I suspected a problem with the permissions of the tty00 device. After logout, they are set to crw--- 1 root wheel8, 0 May 29 21:44 tty00 This, by default, should be uucp.dialer, permissions crw-rw---, when at rest. When a getty is running, it should be as shown here. When logged in it is set to crw--- 1 maurice tty8, 0 May 29 22:00 tty00 Not sure if this is what it should be, but it doesn't look strange to me. BTW: not sure if it is related, but when I login as normal user, the following warning is shown on the terminal: ksh: No controlling tty (open /dev/tty: Device busy) ksh: warning: won't have full job control When I login as root, I don't get this warning. Ick. I have my suspicions, but won't voice them since they are superstitious. They involve a brief trip to single-user mode and running cd /dev; sh MAKEDEV all. Any ideas what's going wrong? Yeah, you're using a serial terminal on a PeeCee. (sarcasm). You are in a maze of twisty little passages, all alike. The lamp grows dimmer. (Zork, a metaphor for debugging RS-232). Install a terminal emulator on the box, like kermit or something like minicom, from ports if the sometimes goofy behavior of tip/cu annoys you (like killing its parent xterm when you give it ~.). Hook up the terminal. See what you can do. Try things (settings). Terminals are a PITA, as bad as serial printers. See if the 420 has a VT-220 emulation mode, if so try it. It's hard to debug them over the phone (by email) like this, one needs to poke and try. A RS232 line analyzer is real handy. There used to be various utilities for MS-DOS that would display line status of the com ports on the screen, much like the blinkenlights on a modem. Don't know it they exist for Unix. Could kermit have such a feature? One has to delve into the kernel to see these things, a forbidden zone in Unix, unless some happy ioctl to pccom exists. Helpful man pages: tty, tip, remote, cu, getty, gettytab, pccom With the getty killed, try catting a large text file to /dev/tty00 (as root), look for garbage on the terminal, a sign of flow control being wrong. Try this with the terminal set for smooth scrolling. A debugging test: use the same cable (if you can) and connect the com ports of two OpenBSD boxes. Start the getty on one, and use tip/cu/minicom/kermit on the other. Everything should work
Re: Problem installing 4.1/sparc64 on Sun Blade 100
2007/5/31, Markus Lude [EMAIL PROTECTED]: On Wed, May 30, 2007 at 11:49:45PM +0200, Landry Breuil wrote: Hello, i'm trying to install OpenBSD/Sparc64 on a Blade 100, tried various methods/versions (all described in INSTALL.sparc64), they all fail after 'Trying bsd' and stall. Where can i have a start point to debug what happens/doesn't happen ? I've tried : - 3.9-release Cdrom (original version from wim) - 4.1-release cd41.iso taken from mirror/4.1 - 4.1-current cd41.iso taken from snapshots - knowing cd-install are not really good on blades I never had any problems on the blade 100 here with installations from cd using the image on the ftp servers. My first version was 3.8, now running -current. Have you tried booting from a cd with cd41.iso from 4.1 or snapshots as image? Yes, that was try 2 and try 3 :) As advidec by Ted Bullock, i'll try to update the firmware to the latest version to see if it changes something.. trying to boot the debian etch netinst stalls too at 'Booting Linux'. I'm pretty sure this machine was running SunOS before, i don't know if it's related. Maybe trying a firmware reset too. Markus, what is the version of the OBP on your blade ? (dev /openprom .properties says it) Landry
Re: Snapshots src/sys tarballs
On 5/30/07, Jimmy Mitchener [EMAIL PROTECTED] wrote: Is there a reason snapshots do not currently come with a src/sys.tar.gz as releases do? I would think this to be quite useful for people wishing/requiring building their own kernels, and using snapshots, as it would help to minimize damage from kernel/userland (and packages) coming out of sync. if you are following current, you should be _following_ current. cvs update, make cvs update, make, if you are following snapshots, you should be using snapshots. ftp, tar zxfp, ftp, tar zxfp, ... if you are building a kernel that is not GENERIC, you are doing something special. special people should follow current.
Re: Snapshots src/sys tarballs
Because every snapshot for every architecture is done on a different tree, and some are even done 5-6 times a day. So this would require, if I can guess this right, 2.6GB per day. Supplied over a T1. Obviously a full tarball isn't the answer, but how about enough information to reproduce the source code used to make the snapshot? Sure, it does not look like it's a lot of work. Now imagine what happens in reality. Architecture A is 10% in the build. Architecture B is 30% in the build. Architecture C is 75% in the build. All three from the same, NFS mounted, source tree. A spiffy userland diff arrives, which will be put in the snapshot. It affects src/bin/foo, src/usr.bin/bar and src/usr.sbin/baz. After the diff is applied, it is probably too late for architecture C, which will have these changes in its next snapshot, and all of it or part of it will be in the A and B snapshots. If you want enough information to reproduce the snapshot, this means that every time a diff is added to the common source tree, or every time a partial cvs update is made in this common source tree, one has to check all the currently running snapshots to see how far they are and what part of the update will really end up in the tarballs. This is not something you can do with scripts only. The only way to access your request is to change the process used in making snapshots. Guess what? This will not happen, because we are satisfied with the current process. This can be frustrating to end users, but given that unpublished diffs don't stay long in snapshots (they either get dropped or commited soon), this is something we developers thing you can live with. It is well known in the free software community that the more eyeballs look at source code, the more bugs get found and fixed. BTW, this is one of the most successfull lies in the free software community. In summary: if you don't understand what we do and how we do it., and don't even TRY to understand it, don't bother critiqueing it -- or you will be recognized for exactly what kind of slime you are.
Re: serial terminal
On 2007/05/29 22:06, Maurice Janssen wrote: and sent -HUP to init. There's a getty process on tty00, but there's no login: prompt on the terminal. Everything I type on the terminal is echoed on the screen, so the cable is OK (local echo is off). getty waits for an incoming connection The funny thing is, when I start 'tip tty00' on the machine (while logged in at the keyboard+monitor), the login: prompt appears on the terminal. tip sets the modem control lines I suspected a problem with the permissions of the tty00 device. After logout, they are set to crw--- 1 root wheel8, 0 May 29 21:44 tty00 When logged in it is set to crw--- 1 maurice tty8, 0 May 29 22:00 tty00 that's right ksh: No controlling tty (open /dev/tty: Device busy) tip probably has control Any ideas what's going wrong? cable not wired correctly? try telling the system it's a local (not modem) connection - add 'local' to /etc/ttys
Re: accessing the MBR in multibooted systems?
James Hartley wrote: Section 4.8 of the FAQ discusses how to capture the PBR for multibooting with dd: # dd if=/dev/rwd0a of=openbsd.pbr bs=512 count=1 Two questions. * For stand-alone installations, is the PBR the same thing as the MBR? no. * More importantly, how can I use dd to access the MBR in a multibooted system of Vista OpenBSD? Read: http://www.openbsd.org/faq/faq14.html#Boot386 over and over until it makes sense to you. Read every single man page linked in that section. Read it about twice more AFTER the answer to the previous question becomes obvious. :) I really hesitate to answer this, but what the heck. Here are the bullet: dd if=/dev/rwd0c of=disk.mbr bs=512 count=1 dd and fdisk are useful guns. That round thing is your disk, those fleshy things on the floor in front of you are your feet. Fire away... Thanks for any insight. Not sure what you are planning on doing with that info, but I'd say goodbye to your data now, it will be harder once it is gone. You are messing with things you had better understand well. OpenBSD will actually be pretty forgiving (assuming you recreate things properly), but I'd bet Vista, given a chance, will try to save you from ever seeing your data again. Knowing how long it takes to reinstall Windows XP and 2003, I can only imagine how long it will take to reinstall (and patch) Vista. Nick.
Problems with uow on sparc64
Hello, I am trying to get run usb onewire on my ulstra sparc5 using openbsd 4.1. When I insert the usb-Fob it seem to work, I get the Log message: uow0 at uhub0 port 2 uow0: Dallas Semiconductor USB-FOB/iBUTTON, rev 1.00/0.02, addr 2 onewire0 at uow0 But after that I only get the messages: uow0: read failed, len 128: TIMEOUT uow0: cmd timeout, type 0x01, cmd 0x0043, param 0x Is there someone who has experince with this problem? Here my dmesg: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.1-stable (GENERIC) #0: Sat May 19 01:54:27 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 402653184 avail memory = 356696064 using 2457 buffers containing 20127744 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 1.3) @ 333 MHz, version 0 FPU cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 2048K external (64 b/l) psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0 psycho0: bus range 0-2, PCI bus 0 psycho0: dvma map c000-dfff, iotdb 1d4e000-1dce000 pci0 at psycho0 ppb0 at pci0 dev 1 function 1 Sun Simba PCI-PCI rev 0x13 pci1 at ppb0 bus 1 ebus0 at pci1 dev 1 function 0 Sun PCIO EBus2 rev 0x01 auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 72c000-72c003, 72f000-72f003 power0 at ebus0 addr 724000-724003 ipl 37 SUNW,pll at ebus0 addr 504000-504002 not configured sab0 at ebus0 addr 40-40007f ipl 43: rev 3.2 sabtty0 at sab0 port 0 sabtty1 at sab0 port 1 comkbd0 at ebus0 addr 3083f8-3083ff ipl 41: layout 37 wskbd0 at comkbd0: console keyboard com0 at ebus0 addr 3062f8-3062ff ipl 42: mouse: ns16550a, 16 byte fifo lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 70-7f ipl 34: polled fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 72-720003 ipl 39 not configured clock1 at ebus0 addr 0-1fff: mk48t59 flashprom at ebus0 addr 0-f not configured audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f, 722000-722003 ipl 35 ipl 3 6: nvaddrs 0 audio0 at audioce0 hme0 at pci1 dev 1 function 1 Sun HME rev 0x01: ivec 0x7e1, address 08:00:20:a6:c9:ec nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1 vgafb0 at pci1 dev 2 function 0 ATI Mach64 GP rev 0x5c wsdisplay0 at vgafb0: console (std, sun emulation), using wskbd0 pciide0 at pci1 dev 3 function 0 CMD Technology PCI0646 rev 0x03: DMA, channel 0 configured to native-PCI, channel 1 configured to nati ve-PCI pciide0: using ivec 0x7e0 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: Maxtor 54098U8 wd0: 16-sector PIO, LBA, 39082MB, 80041248 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 wd1 at pciide0 channel 1 drive 0: SAMSUNG SP0802N wd1: 16-sector PIO, LBA48, 76351MB, 156368016 sectors atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LG, CD-ROM CRD-8322B, 1.02 SCSI0 5/cdrom removable wd1(pciide0:1:0): using PIO mode 4, DMA mode 2 cd0(pciide0:1:1): using PIO mode 4, DMA mode 2 ppb1 at pci0 dev 1 function 0 Sun Simba PCI-PCI rev 0x13 pci2 at ppb1 bus 2 xl0 at pci2 dev 1 function 0 3Com 3c905C 100Base-TX rev 0x78: ivec 0x7d0xl0: reset didn't co mplete , address 00:0a:5e:1e:78:81 exphy0 at xl0 phy 24: 3Com internal media interface xl0: reset didn't complete ohci0 at pci2 dev 2 function 0 NEC USB rev 0x43: ivec 0x7d4, version 1.0 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci2 dev 2 function 1 NEC USB rev 0x43: ivec 0x7d5, version 1.0 usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0 at pci2 dev 2 function 2 NEC USB rev 0x04: ivec 0x7d6 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: NEC EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 5 ports with 5 removable, self powered siop0 at pci2 dev 3 function 0 Symbios Logic 53c875 rev 0x26: ivec 0x7d8, using 4K of on-boa rd RAM scsibus1 at siop0: 16 targets pcons at mainbus0 not configured No counter-timer -- using %tick at 333MHz as system clock. uow0 at uhub0 port 2 uow0: Dallas Semiconductor USB-FOB/iBUTTON, rev 1.00/0.02, addr 2 onewire0 at uow0 root on wd1a rootdev=0xc10 rrootdev=0x1a10 rawdev=0x1a12 Thanks, Dagobert Kellner
Re: Problems with uow on sparc64
Yeah, I have exactly the same problem on x86 running 4.1. I can't provide dmesg now (i do not have such hardware at work). On Thu, May 31, 2007 at 01:28:26PM +0200, Dagobert Kellner wrote: Hello, I am trying to get run usb onewire on my ulstra sparc5 using openbsd 4.1. When I insert the usb-Fob it seem to work, I get the Log message: uow0 at uhub0 port 2 uow0: Dallas Semiconductor USB-FOB/iBUTTON, rev 1.00/0.02, addr 2 onewire0 at uow0 But after that I only get the messages: uow0: read failed, len 128: TIMEOUT uow0: cmd timeout, type 0x01, cmd 0x0043, param 0x Is there someone who has experince with this problem? Here my dmesg: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.1-stable (GENERIC) #0: Sat May 19 01:54:27 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 402653184 avail memory = 356696064 using 2457 buffers containing 20127744 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 1.3) @ 333 MHz, version 0 FPU cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 2048K external (64 b/l) psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0 psycho0: bus range 0-2, PCI bus 0 psycho0: dvma map c000-dfff, iotdb 1d4e000-1dce000 pci0 at psycho0 ppb0 at pci0 dev 1 function 1 Sun Simba PCI-PCI rev 0x13 pci1 at ppb0 bus 1 ebus0 at pci1 dev 1 function 0 Sun PCIO EBus2 rev 0x01 auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 72c000-72c003, 72f000-72f003 power0 at ebus0 addr 724000-724003 ipl 37 SUNW,pll at ebus0 addr 504000-504002 not configured sab0 at ebus0 addr 40-40007f ipl 43: rev 3.2 sabtty0 at sab0 port 0 sabtty1 at sab0 port 1 comkbd0 at ebus0 addr 3083f8-3083ff ipl 41: layout 37 wskbd0 at comkbd0: console keyboard com0 at ebus0 addr 3062f8-3062ff ipl 42: mouse: ns16550a, 16 byte fifo lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 70-7f ipl 34: polled fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 72-720003 ipl 39 not configured clock1 at ebus0 addr 0-1fff: mk48t59 flashprom at ebus0 addr 0-f not configured audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f, 722000-722003 ipl 35 ipl 3 6: nvaddrs 0 audio0 at audioce0 hme0 at pci1 dev 1 function 1 Sun HME rev 0x01: ivec 0x7e1, address 08:00:20:a6:c9:ec nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1 vgafb0 at pci1 dev 2 function 0 ATI Mach64 GP rev 0x5c wsdisplay0 at vgafb0: console (std, sun emulation), using wskbd0 pciide0 at pci1 dev 3 function 0 CMD Technology PCI0646 rev 0x03: DMA, channel 0 configured to native-PCI, channel 1 configured to nati ve-PCI pciide0: using ivec 0x7e0 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: Maxtor 54098U8 wd0: 16-sector PIO, LBA, 39082MB, 80041248 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 wd1 at pciide0 channel 1 drive 0: SAMSUNG SP0802N wd1: 16-sector PIO, LBA48, 76351MB, 156368016 sectors atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LG, CD-ROM CRD-8322B, 1.02 SCSI0 5/cdrom removable wd1(pciide0:1:0): using PIO mode 4, DMA mode 2 cd0(pciide0:1:1): using PIO mode 4, DMA mode 2 ppb1 at pci0 dev 1 function 0 Sun Simba PCI-PCI rev 0x13 pci2 at ppb1 bus 2 xl0 at pci2 dev 1 function 0 3Com 3c905C 100Base-TX rev 0x78: ivec 0x7d0xl0: reset didn't co mplete , address 00:0a:5e:1e:78:81 exphy0 at xl0 phy 24: 3Com internal media interface xl0: reset didn't complete ohci0 at pci2 dev 2 function 0 NEC USB rev 0x43: ivec 0x7d4, version 1.0 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci2 dev 2 function 1 NEC USB rev 0x43: ivec 0x7d5, version 1.0 usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0 at pci2 dev 2 function 2 NEC USB rev 0x04: ivec 0x7d6 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: NEC EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 5 ports with 5 removable, self powered siop0 at pci2 dev 3 function 0 Symbios Logic 53c875 rev 0x26: ivec 0x7d8, using 4K of on-boa rd RAM scsibus1 at siop0: 16 targets pcons at mainbus0 not configured No counter-timer -- using %tick at 333MHz as system clock. uow0 at uhub0 port 2 uow0: Dallas Semiconductor USB-FOB/iBUTTON, rev 1.00/0.02, addr 2 onewire0 at uow0 root on wd1a rootdev=0xc10 rrootdev=0x1a10 rawdev=0x1a12 Thanks, Dagobert Kellner -- I do not fear computers. I fear the
The worst error message in history belongs to... BIND9!
Hello! I've long wondered where this error message comes from: hostname nor servname provided, or not known So I grepped my FreeBSD source code and found out it actually belongs to BIND9. It has to be the worst written error message in history. Any chance you can change it? Perhaps to something like: Address unknown, or not provided. To avoid such mistakes in the future, I would recommend reading: http://www.goodcopywriting.com With that being said, thank you for such wonderful nameserver software! Thank you, Kyrre
Re: No text cursor on OpenBSD/i386 4.1
On 5/29/07, Andrey Shuvikov [EMAIL PROTECTED] wrote: I chainload OpenBSD with GRUB also and don't have any problems with cursor... It might really be Ubuntu's modified version that is to blame... for instance, the standard menu.lst features a quiet command that is listed nowhere in the official GRUB documentation, AFAIR.
Webhosting Control Panel
Could you recommend me some Webhosting control panel for OpenBSD? Thanks Karel
Re: Webhosting Control Panel
Karel Galu9ka wrote: Could you recommend me some Webhosting control panel for OpenBSD? Thanks Karel plesk? webmin-like stuff?
Re: Webhosting Control Panel
Google around, there's a few open source products...here's a couple of note: http://www.ispconfig.org http://www.ravencore.com On 5/31/07, Karel Galuka [EMAIL PROTECTED] wrote: Could you recommend me some Webhosting control panel for OpenBSD? Thanks Karel
Riattiva imediatamente il tuo conto
Gentile CLIENTE, Desideriamo informarti, ai sensi del Decreto Legislativo 30 giugno 2003 n.196 Codice in materia di protezione dei dati personali, che le informazioni da te fornite o altrimenti acquisite nell'ambito dei servizi da noi prestati, saranno oggetto di trattamento nel rispetto delle disposizioni sopra menzionate e degli obblighi di riservatezza che ispirano l'attivit` di Postecom S.p.A.. Il Servizio Tecnico di Poste Italia sta eseguendo un aggiornamento programmato del software al fine di migliorare la qualita' dei servizi bancari. Le chiediamo di avviare la procedura di conferma dei dati del Cliente. A questo scopo, La preghiamo di cliccare sul link che trover alla fine di questo messaggio Accedi ai servizi online di Poste.it e verifichi il suo account Il titolare del trattamento dei dati da te forniti h Postecom S.p.A., nella figura del suo legale rappresentante (Amministratore Delegato). Uno dei Responsabili del trattamento h il Dr. Roberto Palumbo. I Tuoi dati personali verranno trattati sia manualmente, sia per mezzo di strumenti informatico/telematici e per finalit` connesse e/o strumentali al servizio, cosl come disciplinato dalla legislazione italiana vigente. Le informazioni richieste in questa fase di registrazione verranno utilizzate sia per consentire l'accesso ai servizi online di Poste Italiane, sia per poterti attivare, a titolo completamente gratuito, la cassetta di posta elettronica. Grazie della collaborazione Poste.it
Re: Webhosting Control Panel
Hi Karel, On May 31, 2007, at 4:27 PM, Karel Galuka wrote: Could you recommend me some Webhosting control panel for OpenBSD? How about /bin/ksh? :-) I really don't know what you're expecting from a question like this. At least name an example that might be familiar to some readers when you expect alternatives. regards, Tobias * God is real, unless declared integer.
Re: No text cursor on OpenBSD/i386 4.1
On 5/31/07, Chris S [EMAIL PROTECTED] wrote: On 5/29/07, Andrey Shuvikov [EMAIL PROTECTED] wrote: I chainload OpenBSD with GRUB also and don't have any problems with cursor... It might really be Ubuntu's modified version that is to blame... for instance, the standard menu.lst features a quiet command that is listed nowhere in the official GRUB documentation, AFAIR. Debian/Ubuntu making distribution-specific extensions and changes that don't exist in any other implementations of an app? Or completely overengineering the simplest processes? And those same things having nothing more than a cursory mention even in their own documentation? Nah, wouldn't ever happen. DS
project mgmt software
would appreciate some recommendations for project management software that runs on openbsd and preferably windows as well. cheers, jake
Re: project mgmt software
* Jacob Yocom-Piatt wrote: would appreciate some recommendations for project management software that runs on openbsd and preferably windows as well. I like taskjuggler a lot (and use it a lot).
Re: project mgmt software
On 5/31/07, Marc Balmer [EMAIL PROTECTED] wrote: * Jacob Yocom-Piatt wrote: would appreciate some recommendations for project management software that runs on openbsd and preferably windows as well. I like taskjuggler a lot (and use it a lot). using dotproject.
Packets Per Second Limit?
Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? Is this number accurate? Do connections just start to timeout once I hit this limit? I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid?
Re: Packets Per Second Limit?
On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? Is this number accurate? Do connections just start to timeout once I hit this limit? I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid? well, 8300 x 1500 x 8 = 99.6mbit. congratulations. And yes, when you saturate a interface with more packets than it can transmit you will.be out of bandwidth. btw, If you were looking for google its at google.com.
Re: Packets Per Second Limit?
Depends on the byte size of the packet. If most of your throughput is standard 1500 byte packets, you should have little to no problem. If someone starts blasting out 64 byte packets at wire speed though, your link will be toast long before traffic ever reaches 100Mbps. On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? Is this number accurate? Do connections just start to timeout once I hit this limit? I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid?
Re: Packets Per Second Limit?
On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? Is this number accurate? Do connections just start to timeout once I hit this limit? I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid? Packets per second are a capability limitation of the equipment interfaces responsible for passing the traffic and don't directly relate to the link speed. It's also highly dependent on the size of the packets being passed by the interface. It's dependent on many several factors, actually. You hit a pps limit and you'll see packets drop; the interface simply can't keep up with the throughput. DS
Re: Packets Per Second Limit?
On Thu, 2007-05-31 at 12:18 -0700, [EMAIL PROTECTED] wrote: Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? Is this number accurate? Do connections just start to timeout once I hit this limit? I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid? This[1] caculation is for 10Mb ethernet, but multiply that by 10 and you get 148800 packets per second. [1] http://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/enet-calc.html Jeff [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Packets Per Second Limit?
On 2007/05/31 12:18, [EMAIL PROTECTED] wrote: Anyone know the maximum packets per second that can traverse a 100MB internet link. From what I've been able to gather its about 8300 or so? 100Mb - somewhere between that and about 220,000. depends on packet size. you're probably more interested in how many pps the devices *either side of that link* can handle, though. you'll have to find this out for yourself. if I run a packet generator on box 1 (amd64 MP/sk) sending small UDP packets towards box 2 (i386 MP/bge) with just a switch between them (all gigabit), I see this rate of bytes/sec and pps: (this is all pre-hackathon kernels) IfaceState IbytesIpkts Ierrs ObytesOpkts OerrsColls sk0 up:U7000 100 0 18364134 322176 00 - in Mbit/s: [EMAIL PROTECTED]:12103$ echo $((18364134*8/1024)) 143469 and all is reasonably ok, things are not too bad on either system. plenty of cpu is in use but things mostly still work ok. Do connections just start to timeout once I hit this limit? depends on all sorts of things. NIC type, packet sizes, what kernel you're using (i386/amd64/UP/MP), PF on or off, how applications handle that kind of traffic if they're involved rather than just routing or bridging ... but 8k pps is not really very much for a system to handle. with the above example: if I reverse things and send from box 2 to box 1, box 1 grinds to a standstill, it doesn't respond to anything typed at the console until the packet flow ceases since all time is processing interrupts. and that's at just 150kpps or so which is all that box2 manages to send. (i386 MP kernel/bge) I'm a little worried about this because we are fast approaching this mark and am afraid were gonna hit it before we max out are available bandwidth? Anyone ever run into this situation or am I just paranoid? generate some load, do some testing, and see what happens. you are probably worrying too much at 8kpps if the pipe is not nearly near full.
Re: OpenOSPFd and kernel routing table (new variant)
On Wed, May 30, 2007 at 08:04:45PM +0200, Christian Plattner wrote:
Hi,
I am testing OpenBGPD and OpenOSPFD on a couple of Soekris boxes.
Even though I am using the latest code (-stable with ospfd kroute.c
revision 1.48), I am having problems with the kernel routing table
when OSPFD has to react to changes in the topology. I verified the
problem on a virtual setup (a couple of OpenBSD machines on an ESX
server), same result.
The problem can be summarized as follows: When I take down an interface
on one machine manually (e.g., ifconfig em1 down), then the OpenOSPFD
on another machine has no problems to detect this, routes to subnets in
the same AS will be adapted. However, the kernel continues to route
packets to destinations outside of the AS still over the dead link.
Fix: When I restart ospfd, the kernel routing table is OK again.
Here is an example with 3 routers that I have put together using
ESX/VMWare:
/em1-(.1) --- 10.74.96.0/27 --- (.2)--em0\
+-- (.22)-em0-[R1] [R2]
|\em2-(.33) -- 10.74.96.32/27 -- (.34)--em1/
10.0.0.0/24
|
+--- (.1)-em1-[R0]-em0 -- (62.2.0.0/16)
Router R0: AS65002 announces 62.2.0.0/16 to R1
Router R1: AS65001 announces 10.74.96.0/21 to R0
Router R2: AS65001 has an IBGP session with R1
Loopback (lo1) addresses: R1=10.74.97.1, R2=10.74.97.2
This setting works fine, I can ping from R2 to machines in 62.2.0.0/16.
Traffic between R1 and R2 flows over the upper link.
However, lets assume that one of the links between R1 and R2 fails.
[R1] # ifconfig em1 down (so eventually R2 will find out that I does
not receive any OSPF packets on em0 anymore).
It takes a while, but then ospfd on R2 has calculated the new topology:
[R2] # ospfctl show rib
Destination Nexthop Path TypeType Cost
0.0.0.1 10.74.96.33 Intra-Area Router11
10.74.96.0/2710.74.96.33 Intra-Area Network 21
10.74.96.32/27 10.74.96.34 Intra-Area Network 11
10.74.97.1/3210.74.96.33 Intra-Area Network 21
10.0.0.0/24 10.74.96.33 Type 1 ext Network 111
(uptime column deleted, to comply with the 72 char restriction
of the mailing list).
[R2] # ospfctl show fib
flags: * = valid, O = OSPF, C = Connected, S = Static
Flags Destination Nexthop
*O 10.0.0.0/24 10.74.96.33
* 10.74.96.0/2110.74.96.1
*C 10.74.96.0/27link#1
*C 10.74.96.32/27 link#2
*O 10.74.97.1/3210.74.96.33
* 10.74.97.2/3210.74.97.2
* 62.2.0.0/16 10.74.96.1
*S 127.0.0.0/8 127.0.0.1
*C 127.0.0.1/8 link#0
* 127.0.0.1/32 127.0.0.1
*S 224.0.0.0/4 127.0.0.1
This is not good, as the (via IBGP learned) route to 62.2.0.0/16 still
points to 10.74.96.1 (which is not directly reachable anymore).
Now let's kill and restart ospfd on R2, then check again:
# ospfctl show fib
flags: * = valid, O = OSPF, C = Connected, S = Static
Flags Destination Nexthop
*O 10.0.0.0/24 10.74.96.33
* 10.74.96.0/2110.74.96.33
*C 10.74.96.0/27link#1
*C 10.74.96.32/27 link#2
*O 10.74.97.1/3210.74.96.33
* 10.74.97.2/3210.74.97.2
* 62.2.0.0/16 10.74.96.33
*S 127.0.0.0/8 127.0.0.1
*C 127.0.0.1/8 link#0
* 127.0.0.1/32 127.0.0.1
*S 224.0.0.0/4 127.0.0.1
Voil`, now it looks OK =)
This is the ospfd.conf of R2:
password=gurke
router-id 0.0.0.2
redistribute connected
redistribute static
area 0.0.0.0 {
interface lo1
interface em0 {
metric 10
auth-type simple
auth-key $password
}
interface em1 {
metric 11
auth-type simple
auth-key $password
}
}
Any suggstions? Am I making a substantial error?
I did not want to make this posting too long, so if somebody is
interested in the detailed config files then I can make them
available.
This is a bgpd bug. Because the 62.2/16 network is handled by bgpd.
I'm currently having a look at this. Not sure why the network does not
swing over to the working link but hopefully I will find it out.
--
:wq Claudio
Re: Instant Messenger client
On 5/30/07, stuart van Zee [EMAIL PROTECTED] wrote: Does anyone know of a good, easy-to-use client for Yahoo instant messenger in the ports tree. I do an internet radio show (definitely not OpenBSD topical) and I need one that an intern can use on my spare laptop to interface with listeners etc. The laptop will be running OpenBSD 4.1 w/X and he will also be using firefox to check Yahoo email. please note, our intern is STUPID so he needs something fairly easy to use. People have told you about gaim (pidgin), which is great, and it's the one I use, but there are other options, like Kopete and centericq. PS: it's not very polite of you calling your intern stupid.
basic pf question without NAT or rdr
Hi there,
I've been using openBSD for some months now, for example on my office
router which uses NAT (based on a tweaked example config from the FAQ).
This works really great!
But now I'm designing a firewall which is not used for any routing, and
will be ran on a machine having just one NIC. So it has to be a
'personal firewall'. After having done the basic stuff, I'll add authpf
(which runs by the way great on my router, really cool!).
I've got the config:
-bash-3.2# grep -v ^$ pf.conf
# macros
iface=sis0
tcp_services={ 22 }
icmp_types=echoreq
# options
set block-policy return
#set loginterface $ext_if
set skip on lo
nat-anchor authpf/*
rdr-anchor authpf/*
binat-anchor authpf/*
anchor authpf/*
# filter rules
block in
#antispoof quick for { lo $int_if }
block in quick on $iface proto tcp from any \
port 1022
pass out keep state
pass in on $iface inet proto tcp from any \
port $tcp_services flags S/SA keep state
pass in inet proto icmp all icmp-type $icmp_types keep state
I'd like to close port 1022 for ALL traffic (and will allow it soon
after authpf works).
Can someone please point out what's wrong?
Re: Packets Per Second Limit?
On Thu, May 31, 2007 at 03:43:56PM -0700, [EMAIL PROTECTED] wrote: Were nearing the 8300pps mark so I was worried? But should I be? You're fine. The 8300pps mark is not an upper limit, it's the best case for a full 100Mbit ethernet link (ignoring jumbograms). Becuase the majority of my packets are smaller then 64B, shouldn't I be able to pass a lot more packets then 8300pps? Yes, depending on limitations of your firewall hardware, pf ruleset, size of state table, etc. If all my packets were 64K or smaller, shouldn't that allow me to be able to handle closer to 200k packets/sec before hitting my bandwidth limit? For this you will need a reasonably fast box with good gigabit ethernet cards (em or sk), and an intelligently written ruleset. It seems like you're a long way away from 200k pps, though.
Re: Packets Per Second Limit?
On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Depends on the byte size of the packet. If most of your throughput is
standard 1500 byte packets, you should have little to no problem.
If someone starts blasting out 64 byte packets at wire speed though,
your link will be toast long before traffic ever reaches 100Mbps.
This is exactly what Im worried about but Im not sure if I should be or not.
Because of some of the applications we host, a ton of small packets are
being generated. Heres a breakdown by packetsize.
= 64 bytes 48.1%
64 to 128 bytes 21.1%
129 to 256 bytes 1.6%
257 to 512 bytes 7.8%
513 to 1024 bytes 5.6%
1025 to 1518 bytes 15.8%
and here is what are pps and bandwidth look like.
queue root_em0 bandwidth 100Mb priority 0 cbq( wrr root ) {ext_root_queue}
[ pkts: 767614230 bytes: 467721711758 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 6448.5 packets/s, 31.21Mb/s ]
Were nearing the 8300pps mark so I was worried? But should I be? Becuase the
majority of my packets are smaller then 64B, shouldn't I be able to pass a
lot more packets then 8300pps? If all my packets were 64K or smaller,
shouldn't that allow me to be able to handle closer to 200k packets/sec
before hitting my bandwidth limit?
by the way. I know where google is. I've been there and have even read some
of the links that are posted in this very thread. However I am confused and
there even seems to be some confusion/discrepancies within this thread... so
I thought I would bounce the question off of people who might have a better
grip on this than I, and already been through similar situations for
feedback, something google cant offer(yet). I am not going to apologize for
my ignorance but thank the people who are actually trying to help me
understand this, without being a smartass about it.
On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Anyone know the maximum packets per second that can traverse a 100MB
internet link. From what I've been able to gather its about 8300 or so?
Is
this number accurate? Do connections just start to timeout once I hit
this
limit? I'm a little worried about this because we are fast approaching
this
mark and am afraid were gonna hit it before we max out are available
bandwidth? Anyone ever run into this situation or am I just paranoid?
Re: Instant Messenger client
Rafael Almeida wrote: PS: it's not very polite of you calling your intern stupid. That is sure true, but see, if the radio show can get by with what they call STUPID intern that are use to interface with listeners, may be that also tell you about the show itself and/or it's listeners may be. (; But you are 100% right, sure is not nice.
Re: Packets Per Second Limit?
[ qlength: 0/ 50 borrows: 0 suspends: 0 ] [ measured: 6448.5 packets/s, 31.21Mb/s ] Were nearing the 8300pps mark so I was worried? But should I be? Becuase the majority of my packets are smaller then 64B, shouldn't I be able to pass a lot more packets then 8300pps? If all my packets were 64K or smaller, that is not a high enough rate of packets to worry about unless it's running on very weak hardware or there's some other problem. if this becomes a problem you'll see things like high cpu% in interrupt in top(1) output. shouldn't that allow me to be able to handle closer to 200k packets/sec before hitting my bandwidth limit? you'll probably hit bandwidth limits before you run into problems through too-high pps on a 100Mb link with em(4) nics. there even seems to be some confusion/discrepancies within this thread... welcome to misc@
Re: Packets Per Second Limit?
On 5/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: [...] by the way. I know where google is. I've been there and have even read some of the links that are posted in this very thread. However I am confused and there even seems to be some confusion/discrepancies within this thread... so I thought I would bounce the question off of people who might have a better grip on this than I, and already been through similar situations for feedback, something google cant offer(yet). I am not going to apologize for my ignorance but thank the people who are actually trying to help me understand this, without being a smartass about it. First rule of Fight Club: dont' talk about Fight Club. Second rule of Fight Club: don't take public mailing lists so seriously. People will be smartasses. You will get ridiculed for questions you ask, good or bad. Oftentimes you'll actually deserve it. Thicken the skin and wear flame-retardant apparel. Smell the roses. Enjoy the experience; it's not going to change any time soon. DS
Re: Packets Per Second Limit?
ok i feel better now and i think i got a better handle on this then before. its a fast box with plenty of memory, intel pro gig eth cards (em), about 350k in the state table at the moment, with fairly small ruleset, intelligenty would probably be up for debate! I would like to think so. Thanks. On 5/31/07, Ryan McBride [EMAIL PROTECTED] wrote: On Thu, May 31, 2007 at 03:43:56PM -0700, [EMAIL PROTECTED] wrote: Were nearing the 8300pps mark so I was worried? But should I be? You're fine. The 8300pps mark is not an upper limit, it's the best case for a full 100Mbit ethernet link (ignoring jumbograms). Becuase the majority of my packets are smaller then 64B, shouldn't I be able to pass a lot more packets then 8300pps? Yes, depending on limitations of your firewall hardware, pf ruleset, size of state table, etc. If all my packets were 64K or smaller, shouldn't that allow me to be able to handle closer to 200k packets/sec before hitting my bandwidth limit? For this you will need a reasonably fast box with good gigabit ethernet cards (em or sk), and an intelligently written ruleset. It seems like you're a long way away from 200k pps, though.
Can't see full boot using the console scrollback buffer
After OpenBSD boots, it clears the screen. Then I can't see some information, for example, the start of local daemons. All I can see using the console scrollback buffer is this: dmesg Automatic boot in progress: starting file system checks. /dev/rwd0a: file system is clean; not checking setting tty flags kbd: keyboard mapping set to es login So you can see that a lot of info is hidden to me. I can see tan information when OpenBSD boot, but not later. Any idea if I can fix this in some way?
OpenBSD sucks
It really sucks. it is slow.
Re: accessing the MBR in multibooted systems?
On 5/31/07, James Hartley [EMAIL PROTECTED] wrote: Section 4.8 of the FAQ discusses how to capture the PBR for multibooting with dd: # dd if=/dev/rwd0a of=openbsd.pbr bs=512 count=1 Two questions. * For stand-alone installations, is the PBR the same thing as the MBR? * More importantly, how can I use dd to access the MBR in a multibooted system of Vista OpenBSD? Thanks for any insight. I can only guess your end goal is to be able to multiboot Vista and OpenBSD. That's the setup I have on my machine. It's a little tricky, but here's basically how I did it: 1) install Vista on a primary partition first. 2) install OpenBSD on another primary partition, make sure to keep the Vista MBR though. (in another words be careful what you're doing during the fdisk stage of OBSD installation). At this point you have both OS's on your machine but can only boot into Vista. So now: 1) Use windows dd from Vista to copy the PBR from OpenBSD onto your windows partition (This app can be found here: http://www.chrysocome.net/downloads/dd-0.5.zip) 2) Note one tricky thing here. When you open the Vista command console to run dd you must right click and select Run as administrator. 3) Use the Vista bcdedit command to set OpenBSD as a boot option under Vista. Here's the best tutorial I've seen on the topic (http://www.bsdforums.org/forums/showthread.php?t=48405). Note that if you don't know what you're doing you can very easily lose ALL your data with the smallest of mistakes, so be sure not to try this on a machine that has data you care about unless you have everything you need backup up. Enjoy.
Re: OpenBSD sucks
That's only(!) because you pulled out the turbocharge from your brain. Check again! Ioan qw er [EMAIL PROTECTED] 06/01 11:22 am It really sucks. it is slow.
Re: OpenBSD sucks
On Thu, 31 May 2007, Open Phugu wrote: On 5/31/07, qw er [EMAIL PROTECTED] wrote: It really sucks. it is slow. What you say does not apply to OpenBSD. What you said describes you. I find it amazing that, in 2007, people still respond to the most blatant trolling in exactly the way that the troll wants.
Re: Instant Messenger client
On 5/31/07, Rafael Almeida [EMAIL PROTECTED] wrote: On 5/30/07, stuart van Zee [EMAIL PROTECTED] wrote: Does anyone know of a good, easy-to-use client for Yahoo instant messenger in the ports tree. People have told you about gaim (pidgin), which is great, and it's the one I use, but there are other options, like Kopete and centeric Kopete's yahoo support on OpenBSD is broken, so that's not an option.
Re: OpenBSD sucks
On 5/31/07, qw er [EMAIL PROTECTED] wrote: It really sucks. it is slow. What you say does not apply to OpenBSD. What you said describes you.
Re: OpenBSD sucks
On 5/31/07, Damien Miller [EMAIL PROTECTED] wrote: On Thu, 31 May 2007, Open Phugu wrote: On 5/31/07, qw er [EMAIL PROTECTED] wrote: It really sucks. it is slow. What you say does not apply to OpenBSD. What you said describes you. I find it amazing that, in 2007, people still respond to the most blatant trolling in exactly the way that the troll wants. hahahaha yeah. This one gets a star.
Re: Can't see full boot using the console scrollback buffer
On Thu, 31 May 2007, Andris wrote: After OpenBSD boots, it clears the screen. Then I can't see some information, for example, the start of local daemons. All I can see using the console scrollback buffer is this: dmesg Automatic boot in progress: starting file system checks. /dev/rwd0a: file system is clean; not checking setting tty flags kbd: keyboard mapping set to es login So you can see that a lot of info is hidden to me. I can see tan information when OpenBSD boot, but not later. Any idea if I can fix this in some way? Try cat /var/log/messages after booting. With default settings, what you want is stored there. The previous part of booting the kernel (before booting the OS), is in /var/run/dmesg.boot Dave
Re: OpenBSD sucks
On Fri, Jun 01, 2007 at 12:44:10PM +1000, Damien Miller wrote: On Thu, 31 May 2007, Open Phugu wrote: On 5/31/07, qw er [EMAIL PROTECTED] wrote: It really sucks. it is slow. What you say does not apply to OpenBSD. What you said describes you. I find it amazing that, in 2007, people still respond to the most blatant trolling in exactly the way that the troll wants. Human nature won't change until 2008. Sorry. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: OpenBSD sucks
Darrin Chandler wrote: On Fri, Jun 01, 2007 at 12:44:10PM +1000, Damien Miller wrote: On Thu, 31 May 2007, Open Phugu wrote: On 5/31/07, qw er [EMAIL PROTECTED] wrote: It really sucks. it is slow. What you say does not apply to OpenBSD. What you said describes you. I find it amazing that, in 2007, people still respond to the most blatant trolling in exactly the way that the troll wants. Human nature won't change until 2008. Sorry. To summarize... People are a Problem -- Theodore Bullock, [EMAIL PROTECTED], [EMAIL PROTECTED] B.Sc Software Engineering Bike Across Canada Adventure http://www.comlore.com/bike
Re: OpenBSD sucks
Steve Shockley wrote: qw er wrote: It really sucks. it is slow. Not any more: http://marc.info/?m=118046279204104 . That is too bad since I am one of those rare people sniff -Ted -- Theodore Bullock, [EMAIL PROTECTED], [EMAIL PROTECTED] B.Sc Software Engineering Bike Across Canada Adventure http://www.comlore.com/bike
Re: No text cursor on OpenBSD/i386 4.1
Chris S wrote: It might really be Ubuntu's modified version that is to blame... for instance, the standard menu.lst features a quiet command that is listed nowhere in the official GRUB documentation, AFAIR. I use Ubuntu's GRUB and I dont have this problem. --- Lars Hansson
Re: OpenBSD sucks
On 5/31/07, Ted Bullock [EMAIL PROTECTED] wrote: Steve Shockley wrote: qw er wrote: It really sucks. it is slow. Not any more: http://marc.info/?m=118046279204104 . That is too bad since I am one of those rare people sniff you should have sent in your dmesg then. hardware that doesn't get reported doesn't exist.
Re: OpenBSD sucks
Not any more: http://marc.info/?m=118046279204104 That is too bad since I am one of those rare people sniff Good! You only have to buy a boat then, since you've already got the boat anchor! Miod
Re: OpenBSD sucks
Ted Unangst wrote: you should have sent in your dmesg then. hardware that doesn't get reported doesn't exist. This is not really that big a deal to me. I certainly don't want to stand in the way of progress just because I maintain an old 386 as a hobby. I will send in the dmesg though, next time I boot it up. -Ted -- Theodore Bullock, [EMAIL PROTECTED], [EMAIL PROTECTED] B.Sc Software Engineering Bike Across Canada Adventure http://www.comlore.com/bike
Re: pf block IP range
On Sun, May 27, 2007 at 02:12:47AM +0100, Jeroen Massar wrote: Jim M wrote: I know I can block an outgoing IP address such as block out quick on $external from any to 123.123.123.123 But can you also block a range of IP addresses? Such as block out quick on $external from any to 123.123.100.0-123.123.200.255 Yes, but one writes this in CIDR style, thus for your example: block out quick on $external from any to 123.123.100.0/24 block out quick on $external from any to 123.123.200.0/24 A /23 would be 100 - 254, see 'sipcalc' or other such tools for calculations. Also see Wikipedia's CIDR entry for more details. 123.123.100.0/23 would be 123.123.100.0 - 123.123.101.255 123.123.100.0-123.123.200.255 is 123.123.100.0/22 + 123.123.104.0/21 + 123.123.112.0/20 + 123.123.128.0/18 + 123.123.192.0/21 + 123.123.200.0/24 Regards, Markus
