Re: Problems booting 4.2 CD on two older machines.
On 29/10/2007, at 5:24 PM, Craig Findlay wrote: As other have already said, it seems to only be a problem with quite old PC's. At least mine is. (see dmesg below) Cheers, Craig OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 234 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX 4.2 official CD works for me on Dell Optiplex ~500Mhz - I'll get exact details and dmesg tomorrow if of interest to anyone. Also installed on newer Compaq Celeron laptop - again, no CD / installation issues. With the 4.1 release, the CD set I bought personally was fine, but the CD set for work failed to read CD 1 (so I just used the personal set to install at work.) I did not investigate further - just assumed dud CD.
Re: Problems booting 4.2 CD on two older machines.
Hi, On 29/10/2007, Nick Holland [EMAIL PROTECTED] wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? The bios tries to boot, but does not find the CD bootable and falls back on the hard disk. And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). No. Not on 2 machines I tried on the other day, but it does boot on my main deskto pand laptop (2 completely different, more modern machines). Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) Unsure, havent tried. For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? Yes If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? I have tried multiple cd drives. Does a CD made from install42.iso boot? unsure. Does a CD made from cd42.iso boot? unsure Does a CD made from cdemu42.iso boot? unsure - I have no CDR's to try this out... If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick. Yes, perhaps it is something obscure in manufacturing. Could be a change of the brand of media for example, or something strange. Not a lot we can do about it. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: First install: Grub doesn't find partitions
Hi again, Am Montag, 29. Okt 2007, 02:38:08 +0100 schrieb Bertram Scharpf: I just installed OpenBSD on a i386 from cd41.iso as described in the FAQ, chapter 4. When I restart the system from the CD all OpenBSD partitions show up properly and I can chroot into /mnt after I mounted them. However, Grub refuses to recognize any of the OpenBSD partitions. A Linux resides on the same disk that cannot mount any of these partitions either. Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e And here is what I entered into `disklabel': start size mountpoint wd1a 6323185 524159/ wd1b 6847344 524160(swap) wd1d 7371504 524160/tmp wd1e 7895664 12582864/usr wd1f 204785288388576/home First of all thanks to the off-list responders. I already considered the chainloader option but as I installed no bootloader this probably would not work. I examined the Grub source code to find out where it looks for BSD partitions. I found there is a sector containing the BSD magic label and appropriate partitioning info. It's sector 1, the second one on the disk == the first in slice /dev/hdb1 or (hd1,0), respectively. Arrgh! Sectors 6323185 and 6323186 are still untouched. I tried to use the 'b' command in 'disklabel -E ..' but nothing went better. I dd'ed sector 1 to 6323186 and voila - there they are. Could this be the correct way that I first have to damage another partition and then manually have to move a sector? When booting this system I run into the next problem: panic: /boot too old: upgrade! Therefore I would like to try to install a bootloader and chainload it. But with a 'disklabel' that overwrites existing partitions? Do I have to get used to struggle with such fundamental problems when I proceed with OpenBSD? Thank for reading so far, Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: First install: Grub doesn't find partitions
Hi, I don't quite understand what you're doing? Are you looking for a dual-boot with linux via grub? If so, have a look at www.aei.mpg.de/~pau/zen_process_obsd.html Read it in detail. If not, just forget this mail. Cheers, Pau 2007/10/29, Bertram Scharpf [EMAIL PROTECTED]: Hi again, Am Montag, 29. Okt 2007, 02:38:08 +0100 schrieb Bertram Scharpf: I just installed OpenBSD on a i386 from cd41.iso as described in the FAQ, chapter 4. When I restart the system from the CD all OpenBSD partitions show up properly and I can chroot into /mnt after I mounted them. However, Grub refuses to recognize any of the OpenBSD partitions. A Linux resides on the same disk that cannot mount any of these partitions either. Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e And here is what I entered into `disklabel': start size mountpoint wd1a 6323185 524159/ wd1b 6847344 524160(swap) wd1d 7371504 524160/tmp wd1e 7895664 12582864/usr wd1f 204785288388576/home First of all thanks to the off-list responders. I already considered the chainloader option but as I installed no bootloader this probably would not work. I examined the Grub source code to find out where it looks for BSD partitions. I found there is a sector containing the BSD magic label and appropriate partitioning info. It's sector 1, the second one on the disk == the first in slice /dev/hdb1 or (hd1,0), respectively. Arrgh! Sectors 6323185 and 6323186 are still untouched. I tried to use the 'b' command in 'disklabel -E ..' but nothing went better. I dd'ed sector 1 to 6323186 and voila - there they are. Could this be the correct way that I first have to damage another partition and then manually have to move a sector? When booting this system I run into the next problem: panic: /boot too old: upgrade! Therefore I would like to try to install a bootloader and chainload it. But with a 'disklabel' that overwrites existing partitions? Do I have to get used to struggle with such fundamental problems when I proceed with OpenBSD? Thank for reading so far, Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Installation Troubles
m fairly new to OpenBSD (been using FreeBSD for years) and have stumbled across some issues on a desktop install (after several server based installs over the past few months). The system has two identical drives (WD 250G) which I wish to RAID (1). As i understand it openbsd has no support for my onboard raid system (NF4 board , eVga 680i) so am to use kernel options. I enable the raid1 in the bios options and install windows on an 80gb partition (of the 250GB drive it sees.) and can boot successfully. I then install OpenBSD on the rest of the drive (wd0) making sure to slice it up carefully (identical to the howto but with increased /usr space). I then install the required components and complete the install by ensuring the installboot runs (with correct references too wd0) and issue the dd command (whilst reference /dev/rwd0a for copying to openbsd.pbr). This all seems fine and I then configure windows to boot it which also works well. Its when I select this new Openbsd boot option I get the error: Loading... ERR M As I understand it I have some how messed up the secondary loader and it needs to be reinstalled , so i did a new install . I reinstalled the system 5 times over a day trying to work out my problem. wd0 is partitioned with the 80GB for windows and the rest devoted to OpenBSD and wd1 is currently only partitioned for windows with the rest 'free'. Im at a dead end of where to turn next as I am sure this is an issue with my onboard raid,drive setup and boot parameters as I can add files to the drives when Im booted into the shell provided on the CD. Any help would be appreciated. disklabel : # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: WDC WD2500KS-00M flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 488397168 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a:306873 163846935 4.2BSD 2048 16384 304 # Cyl 162546*-162850 b:614880 164153808swap # Cyl 162851 -163460 c: 488397168 0 unused 0 0 # Cyl 0 -484520 d:245952 164768688 4.2BSD 2048 16384 244 # Cyl 163461 -163704 e:164304 165014640 4.2BSD 2048 16384 164 # Cyl 163705 -163867 f: 323213121 165178944 4.2BSD 2048 16384 328 # Cyl 163868 -484515* i: 16384687263 unknown # Cyl 0*-162546* [disklabel] fdisk Disk: wd0 geometry: 30401/255/63 [488392065 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: idC H S -C H S [ start: size ] *0: 070 1 1 - 10198 254 63 [ 63: 163846872 ] HPFS/QNX/AUX 1: A6 10199 0 1 - 30400 254 63 [ 163846935: 324545130 ] OpenBSD 2: 000 0 0 -0 0 0 [ 0: 0 ] unused 3: 000 0 0 -0 0 0 [ 0: 0 ] unused installboot boot: /mnt/boot proto : /usr/mdec/biosboot device: /dev/rwd0c /usr/dec/biosboot : entry point 0 proto bootblock size 512 /mnt/boot is 3 blocks x 16384 bytes fs block shift 2; part offset 163846935; inode block 128, offset 5416 using MBR partition 1: type 166 (0xa60 offsetn 163846935 (0x9c41b1) This is purely a trial run install before the release of 4.2 as I knew I would come across some issues trying to create my setup. I would ideally like to keep the raid 1 setup but appreciate I may have to have each drive reserved for each individual OS.
Hoe to specify multiple transform suites in ipsec.conf(5)
Hello list,
I am trying to move my IPsec configuration from isakmpd.conf to ipsec.conf.
However i cannot find a syntax to specify multiple transform suites with
ipsec.conf
I tried something like:
ike passive esp from any to any quick enc {aes,3des}
but it is rejected.
I want something like
Suites=QM-ESP-AES-SHA2-256-PFS-SUITE,QM-ESP-3DES-PFS-SUITE
as a result.
As a workaround i can stuff it into the running configuration using
isakmpd's fifo, but that is not a very robust solution.
Specifying
Default-phase-2-suites =
QM-ESP-3DES-MD5-PFS-SUITE,QM-ESP-AES-SHA2-256-PFS-SUITE
in isakmpd.conf
does not help, because ipsecctl overrides it. Is there a way to tell
ipsecctl to not specify a suite at all, so that the default is used?
BTW, is ipsec.conf meant to ever become a full replacement for isakmpd.conf?
Thanks for any hints.
--
Heinrich Rebehn
University of Bremen
Physics / Electrical and Electronics Engineering
- Department of Telecommunications -
Phone : +49/421/218-4664
Fax :-3341
Re: 4.2/amd64 cannot detect any CDROM even the one from which it was installed
On 10/27/07, Calomel [EMAIL PROTECTED] wrote: Siju, Has the device name changed? Perhaps to /dev/cd0a No Calomel, I tried even cd0a it doesn't work out. Meanwhile I gave that system for servicing because it shuts down automatocally when the CPU load increases. Will see if there is any difference after that :-) Thank you so much Kind Regards Siju
Re: Problems booting 4.2 CD on two older machines.
On Sun, 28 Oct 2007 22:48:20 -0400, Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. Well, I read Theo's message and I know we can't ask for any changes to the issue CDs. Shit happens. I just get my terrier genes showing a bit because it's a challenge. Don't like being locked out of solutions and knowing what is needed to prevent repetition. So I have done a bit of detective work and maybe it will get shot down or else it will pop up one of those cartoon lightbulbs for somebody who will then improve my education by informing me about the rest of the story. Here is what I know so far about the differences in the CDs that boot or don't on older machines: All the CDs that boot have a copy of the cdbr content before 64MB from the start of the CD whereas the 4.2 release has it located at 76,398,592 bytes in. I have used (in addition to 4.2 Official build 375) snapshots for kernel build 372, 373, 374 and 461. 372, 373 and 374 all have the cdbr code at 60,293,120 bytes and 461 has it at 60,854,272 and all of those boot. Here is what I don't know (about this issue, not LTUAE!): Is 67,108,864 a possible barrier for old BIOSes ? Do we have any way to predetermine where that code will be located on the CD? Am I chasing a red herring? I'd like to keep a bunch of low(er) powered servers going for a while and I as I said earlier I can do it without a bootable CD even tho' those boxes (except one) don't have a floppy drive either. My concern is more for some young guys with only one old dumpster surprise and no previous experience with OpenBSD, trying to give it a try using a buddy's CD. Apart from my mad curiosity, of course! Rod/ (Please reply to the list even if it's Theo or Nick telling me to let go of it.) -- Write a wise saying and your name will live on forever. - Anonymous
Re: First install: Grub doesn't find partitions
Hi, Am Montag, 29. Okt 2007, 11:01:44 +0100 schrieb Pau Amaro-Seoane: I don't quite understand what you're doing? Are you looking for a dual-boot with linux via grub? Yes. I have a Linux box here with Grub. Admittedly the first hard disk contains a Windows that gets used sometimes by other persons. What else should I do? Buy another machine while I have unused disk space here? Migrate back to Windows before I try out OpenBSD? If so, have a look at www.aei.mpg.de/~pau/zen_process_obsd.html Read it in detail. If not, just forget this mail. This is exactly what I did. The first difference appears while partitioning. I quote the document you told me I should have a look at: Here is the partition information you chose: Disk: wd0 geometry: 969/128/63 [7814016 Sectors] #: idC H S -C H S [ start: size ] .. *2: A6 304 103 1 - 968 25 63 [ 2457945: 5349645 ] OpenBSD .. ... Treating sectors 2457945-7807590 as the OpenBSD portion of the disk. You can use the 'b' command to change this. When I run the installation this reads: Treating sectors 63-120103200 as the OpenBSD portion of the disk. You can use the 'b' command to change this. Unfortunately, when I use the 'b' command, this won't change. The partition table is written to sector 1. Not 63. Not 64. Not 6323185. Not 6323186. I not even find a way to display that message again after I changed the portion. The document you pointed to doesn't mention a command to display what the portion is. I tried it several times. I booted the CD, ran disklabel/install/..., booted linux, dd|od'ed the sectors (there's no od on the CD), re-booted the CD, ... Yes, I do read documentation and I read it in detail. I still will be glad if you point me to some new information. Telling me to read again and again the same doesn't make the disklabel command behave different. Please do you read the reports I post in detail. Bertram 2007/10/29, Bertram Scharpf [EMAIL PROTECTED]: Hi again, Am Montag, 29. Okt 2007, 02:38:08 +0100 schrieb Bertram Scharpf: I just installed OpenBSD on a i386 from cd41.iso as described in the FAQ, chapter 4. When I restart the system from the CD all OpenBSD partitions show up properly and I can chroot into /mnt after I mounted them. However, Grub refuses to recognize any of the OpenBSD partitions. A Linux resides on the same disk that cannot mount any of these partitions either. Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e And here is what I entered into `disklabel': start size mountpoint wd1a 6323185 524159/ wd1b 6847344 524160(swap) wd1d 7371504 524160/tmp wd1e 7895664 12582864/usr wd1f 204785288388576/home First of all thanks to the off-list responders. I already considered the chainloader option but as I installed no bootloader this probably would not work. I examined the Grub source code to find out where it looks for BSD partitions. I found there is a sector containing the BSD magic label and appropriate partitioning info. It's sector 1, the second one on the disk == the first in slice /dev/hdb1 or (hd1,0), respectively. Arrgh! Sectors 6323185 and 6323186 are still untouched. I tried to use the 'b' command in 'disklabel -E ..' but nothing went better. I dd'ed sector 1 to 6323186 and voila - there they are. Could this be the correct way that I first have to damage another partition and then manually have to move a sector? When booting this system I run into the next problem: panic: /boot too old: upgrade! Therefore I would like to try to install a bootloader and chainload it. But with a 'disklabel' that overwrites existing partitions? Do I have to get used to struggle with such fundamental problems when I proceed with OpenBSD? Thank for reading so far, Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: Problems booting 4.2 CD on two older machines.
Hi, Great work on the detailed inspection. On 29/10/2007, RW [EMAIL PROTECTED] wrote: Is 67,108,864 a possible barrier for old BIOSes ? But weren't peoples old machines booting home made 4.2 cd's just fine? My concern is more for some young guys with only one old dumpster surprise and no previous experience with OpenBSD, trying to give it a try using a buddy's CD. Dumpster surprise... yes.. A couple of us use OpenBSD for workstation/university stuff. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: About Xen: maybe a reiterative question but ..
On Sun, Oct 28, 2007 at 10:31:31PM -0400, Nick Holland wrote: It's a pretty simple concept, really. A few years ago, I was giving a talk at a local high school. One of the students asked me why his computer crashed a lot, why can't they build an operating system that doesn't crash?. I told him they can, they do, but he doesn't want it because it doesn't have all the bells and whistles he expects. And, it's bad because that's what he was willing to pay for. This class seems to have understood, it doesn't matter what you say, it's what you buy. Talk all you want, when you BUY or USE the product, you have said This is what I want, and I want it more than I want the money (goal, standard, ideal, whatever) in the only terms that matter. It is a great honor to work with a group like OpenBSD that will not compromise its ideals for the sake of convenience or expediency. It's a very rare thing to find... Right, so if I want to buy a computer (hardware) that is actually designed and built well from the ground up, what then? Most are i386 which, no matter how well built, being i386 is a pile of legacy crap. Amd64 still has to be able to run i386 so still has the legacy crap. HP's now are i386/amd64. Sun is Sun; designed to meet market forces competing against i386/amd64. IBM has a whole slew of Power-based stuff that costs an arm and a leg new (lots of old stuff available though) that I'd like to try but you can't run OpenBSD on it. So if nobody makes really good hardware then there's nobody to reward for it, so you end up buying bad hardware and rewarding the maker for it. Doug.
Re: About Xen: maybe a reiterative question but ..
On 10/29/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: So if nobody makes really good hardware then there's nobody to reward for it, so you end up buying bad hardware and rewarding the maker for it. If given a choice, I think I like Sun's sparc hardware most of all. Though IBM's boxes do allow LPARs from what I understand. And apparently the new power6 boxes will also run/translate x86 software(!), or so I heard. -- This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. http://www.youtube.com/watch?v=tGvHNNOLnCk
Re: First install: Grub doesn't find partitions
is it a recent grub? if you're reading grub source I will assume you know more about it than I do, but am writing this on a box which boots debian/openbsd/xp without problems, from grub installed circa 6 months ago. I certainly did not dd any sectors around. I can send you my grub conf when I reboot next. mike
Re: Cyrus IMAP performance problems [Long]
On Tue, Oct 16, 2007 at 01:18:07PM -0300, Marcus Andree wrote: Got similar problems with imap once, a long time ago... Had to switch from mailbox format to maildir then, it wasn't Cyrus. -- Stephan A. Rickauer --- Institute of Neuroinformatics Tel +41 44 635 30 50 University / ETH Zurich Sec +41 44 635 30 52 Winterthurerstrasse 190 Fax +41 44 635 30 53 CH-8057 ZurichWeb www.ini.unizh.ch RSA public key: https://www.ini.uzh.ch/~stephan/pubkey.asc ---
Re: First install: Grub doesn't find partitions
I am writing this from a dual-boot system with linux only and I never had your problem. 2007/10/29, michael hamerski [EMAIL PROTECTED]: is it a recent grub? if you're reading grub source I will assume you know more about it than I do, but am writing this on a box which boots debian/openbsd/xp without problems, from grub installed circa 6 months ago. I certainly did not dd any sectors around. I can send you my grub conf when I reboot next. mike
Re: Samba files used logging
You need to use at least samba-2.2.7a and use the audit.so module. The samba source code has what you need. Check out the information in ~samba/examples/VFS/audit.c and in the README file in that directory. -- Calomel @ http://calomel.org OpenSource Research and Reference On Sun, Oct 28, 2007 at 03:22:27PM +0100, [EMAIL PROTECTED] wrote: Hello I've set up a little samba server on my OpenBSD box. I would like to know which files are being accessed (write, copy) by smbd. I tried fstat, pstat but none of them give me the name of the files. Any idea ? Thanks
Re: First install: Grub doesn't find partitions
indeed... you seem not to have read the site I pointed to previously. Don't say you have read it if you didn't. The information is there. Do what Andrew says and tag it as A6; i.e. openbsd from the linux fdisk This is *also* written in the web page 2007/10/29, Andrew Daugherity [EMAIL PROTECTED]: On 10/28/07, Bertram Scharpf [EMAIL PROTECTED] wrote: grub root (hd1,^I Possible partitions are: Partition num: 0, Filesystem type is ext2fs, partition type 0x83 Partition num: 1, Filesystem type unknown, partition type 0x82 Partition num: 4, Filesystem type is ext2fs, partition type 0x83 Partition num: 5, No BSD sub-partition found, partition type 0xa6 Partition num: 6, Filesystem type unknown, partition type 0x8e grub root (hd1,5,a) Error 5: Partition table invalid or corrupt grub rootnoverify (hd1,5,a) grub cat / Error 17: Cannot mount selected partition Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e I think this is your problem -- the OpenBSD partition needs to be a primary partition (hda1-hda4 in Linux terminology, or (hd0,1) - (hd0,3) in GRUB language, and you have it as an extended partition (hdb6). This is not supported. Reallocated your fdisk partitions so the OpenBSD partition is a primary partition and reinstall (you may have to resize your extended partition, ID=5, to make room). Andrew
Re: Non-x86
Martin SchrC6der wrote: 2007/10/26, Lars Noodin [EMAIL PROTECTED]: Where are the choices for non-x86? The only remaining alternative is Sparc. Everything else is either old (macppc) or expensive unsupported (IA64). It's too bad that Apple discontinued their PPC. It was an acceptable price, especially the mac mini. From the feedback I'm getting here it seems that the new hardware options are expensive. http://www.terrasoftsolutions.com/products/sony/ http://www.terrasoftsolutions.com/products/mercury/ http://www.tadpole.com/products/notebooks/viper.asp http://www.sun.com/servers/index.jsp?tab=2 http://www.sun.com/desktop/index.jsp?tab=0stab=2 What else should be on the list? Regards, -Lars
Re: First install: Grub doesn't find partitions
On 10/28/07, Bertram Scharpf [EMAIL PROTECTED] wrote: grub root (hd1,^I Possible partitions are: Partition num: 0, Filesystem type is ext2fs, partition type 0x83 Partition num: 1, Filesystem type unknown, partition type 0x82 Partition num: 4, Filesystem type is ext2fs, partition type 0x83 Partition num: 5, No BSD sub-partition found, partition type 0xa6 Partition num: 6, Filesystem type unknown, partition type 0x8e grub root (hd1,5,a) Error 5: Partition table invalid or corrupt grub rootnoverify (hd1,5,a) grub cat / Error 17: Cannot mount selected partition Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e I think this is your problem -- the OpenBSD partition needs to be a primary partition (hda1-hda4 in Linux terminology, or (hd0,1) - (hd0,3) in GRUB language, and you have it as an extended partition (hdb6). This is not supported. Reallocated your fdisk partitions so the OpenBSD partition is a primary partition and reinstall (you may have to resize your extended partition, ID=5, to make room). Andrew
Marginal boot CD #1 in OpenBSD 4.2 sets
I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. There are cases where the same CD works with a newer machine, but fails to boot with an older one. I presume this means the track alignment is marginal in some cases. I am not tracking misc@ We would like to send out replacement CD's for anyone with those problems so that we can see if the problem is with all CDs of the current release, or only with some of them. Please contact me if you have seen this problem. Austin Hook OpenBSD distribution Milk River, AB
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
--- Austin Hook [Mon, Oct 29, 2007 at 10:49:09AM -0700]: --- older one. I presume this means the track alignment is marginal in some cases. i swapped CD drives and that solved my problem. but it sounds as if i should go retrieve that old drive from the garbage now, as i just chalked it up to a bad drive...
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. I don't have a suitable machine to try it on, but amd64 boot loader is now able to boot an i386 kernel, and I suspect (but am not certain) that the boot loader itself may be able to run on either arch. So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'.
Re: First install: Grub doesn't find partitions
Hi, Am Montag, 29. Okt 2007, 11:54:23 -0500 schrieb Andrew Daugherity: On 10/28/07, Bertram Scharpf [EMAIL PROTECTED] wrote: grub root (hd1,^I ... Partition num: 5, No BSD sub-partition found, partition type 0xa6 ... Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e I think this is your problem -- the OpenBSD partition needs to be a primary partition (hda1-hda4 in Linux terminology, or (hd0,1) - (hd0,3) in GRUB language, and you have it as an extended partition (hdb6). This is not supported. Reallocated your fdisk partitions so the OpenBSD partition is a primary partition and reinstall (you may have to resize your extended partition, ID=5, to make room). Those @#$! extended partitions! It's really time for me to get rid of that kind of programming style. I tried it out on another machine where I had a free primary partition. Hoolay--it boots! Moving partitions around on the machine described above will take some time but I will try it in any case and I will report. Thanks a lot for your patience when I became fretful. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, 29 Oct 2007 18:42:19 +, Stuart Henderson wrote: On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. I don't have a suitable machine to try it on, but amd64 boot loader is now able to boot an i386 kernel, and I suspect (but am not certain) that the boot loader itself may be able to run on either arch. So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'. The CD2 does get to where it is about to boot, stops on a space but never accepts any variation of all possible /4.2/i386/bsd.rd combinations. Nice try (and I agreed it was worth a try) but no cigar... Regards, Rod From the land down under: Australia. Do we look umop apisdn from up over?
what's makes a route not valid in openbgpd?
running 4.2/i386 as of two weeks ago, I've got a default route that
isn't being seen as valid and consequently not installed in the RIB.
when I first rolled this router out, however, it was valid and being
installed. while I'm interested in what could have happened between
then and now, I'm more interested in how the RDE actually makes its
decisions on validity. I see no obvious reason for this route to be
not valid.
everything else (demotion, 'prefix lists', etc) works great, however (-:
relevant info:
[EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in
flags: * = Valid, = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
0.0.0.0/0 38.103.65.50 100 0 174 i
I am learning that nexthop from another session with 174:
[EMAIL PROTECTED] bgpctl show fib bgp
flags: * = valid, B = BGP, C = Connected, S = Static
N = BGP Nexthop reachable via this route
r = reject route, b = blackhole route
flags destination gateway
*B38.103.65.50/32 38.104.XXX.37
[EMAIL PROTECTED] cat /etc/bgpd.conf
AS 10XX0
router-id 72.37.XXX.178
network inet connected
network inet static
network 38.98.XXX.0/24
neighbor 72.37.XXX.177 {
remote-as 10XX0
announce all
}
group COGENT {
remote-as 174
depend on bge1
softreconfig in yes
softreconfig out yes
neighbor 38.104.XXX.37 {
local-address 38.104.XXX.38
set prepend-self 3
announce self
}
neighbor 38.103.XXX.50 {
announce none
multihop 8
}
}
thanks,
aaron.glenn
Re: First install: Grub doesn't find partitions
Thanks a lot for your patience when I became fretful. I also become very usually fretful when something that SHOULD be working is as stubborn as to refuse to do it. I know it. Oh, yes... and how... glad to read that it worked for you! Pau 2007/10/29, Bertram Scharpf [EMAIL PROTECTED]: Hi, Am Montag, 29. Okt 2007, 11:54:23 -0500 schrieb Andrew Daugherity: On 10/28/07, Bertram Scharpf [EMAIL PROTECTED] wrote: grub root (hd1,^I ... Partition num: 5, No BSD sub-partition found, partition type 0xa6 ... Here is a `sfdisk' (Linux) output: /dev/hdb1 : start=1, size=32255, Id=83 /dev/hdb2 : start=32256, size= 2096640, Id=82 /dev/hdb3 : start= 2128896, size=117974304, Id= 5 /dev/hdb4 : start=0, size=0, Id= 0 /dev/hdb5 : start= 2128897, size= 4194287, Id=83 /dev/hdb6 : start= 6323185, size= 37748591, Id=a6, bootable /dev/hdb7 : start= 44071777, size= 76031423, Id=8e I think this is your problem -- the OpenBSD partition needs to be a primary partition (hda1-hda4 in Linux terminology, or (hd0,1) - (hd0,3) in GRUB language, and you have it as an extended partition (hdb6). This is not supported. Reallocated your fdisk partitions so the OpenBSD partition is a primary partition and reinstall (you may have to resize your extended partition, ID=5, to make room). Those @#$! extended partitions! It's really time for me to get rid of that kind of programming style. I tried it out on another machine where I had a free primary partition. Hoolay--it boots! Moving partitions around on the machine described above will take some time but I will try it in any case and I will report. Thanks a lot for your patience when I became fretful. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, Oct 29, 2007 at 06:42:19PM +, Stuart Henderson wrote: On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. [...] So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'. Worked for me. Thanks! (Also you need to 'set image /4.2/i386/bsd.rd'.)
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, 29 Oct 2007 17:29:42 -0400, Barry Miller wrote: On Mon, Oct 29, 2007 at 06:42:19PM +, Stuart Henderson wrote: On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. [...] So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'. Worked for me. Thanks! (Also you need to 'set image /4.2/i386/bsd.rd'.) Ahhh, yes! Muggins me forgot the set image bit. Too much hurry. Thanks. From the land down under: Australia. Do we look umop apisdn from up over?
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, 29 Oct 2007 10:49:09 -0700 (MST), Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. There are cases where the same CD works with a newer machine, but fails to boot with an older one. I presume this means the track alignment is marginal in some cases. I am not tracking misc@ We would like to send out replacement CD's for anyone with those problems so that we can see if the problem is with all CDs of the current release, or only with some of them. Please contact me if you have seen this problem. Austin Hook OpenBSD distribution Milk River, AB I have good reason to believe that it isn't a physical problem with the CDs. Here are my reasons: I have 5 machines around here that won't boot on a 4.2 CD and one that will. The won'ts have a variety of CD drives, most pertinently one is a brand new Liteon DVD+/- with all the bells whistles. Not likely to have read problems.. The CD can be read from start to finish with zero errors on any of the drives using dd. I can make a copy of the CD on a windows machine by saving an ISO image and burning that to a CD using imgburn. Zero errors copying or burning but boots new box won't boot any old box. Now here is my suggestion. Because I'd like to see this fixed from a PR point of view before Nov 1 and the install42.iso won't be available until then, please have a copy of it put on an ftp server in a location not publically known and let me download it and test it. That will be clear of the entire commercial pressing process and will possibly save the project a lot of money shipping out new CDs which may not work when they get to the end users. I'll be on standby ready to do the download and testing at any time I'm awake over the next couple of days. Austin/ OpenBSD team can please use ash2 at witworx dot com rather than the list. misc readers with comments can reply to the list, please no CC. Regards, Rod Whitworth. From the land down under: Australia. Do we look umop apisdn from up over?
Re: Non-x86
On Mon, Oct 29, 2007 at 06:53:38PM +0200, Lars Nood??n wrote: Martin SchrC6der wrote: 2007/10/26, Lars Noodin [EMAIL PROTECTED]: Where are the choices for non-x86? The only remaining alternative is Sparc. Everything else is either old (macppc) or expensive unsupported (IA64). It's too bad that Apple discontinued their PPC. It was an acceptable price, especially the mac mini. From the feedback I'm getting here it seems that the new hardware options are expensive. What else should be on the list? It would be nice if IBM's Power stuff was, even if its older pSeries like the 7025 or 7026 yet alone anything newer. I don't know what would be involved in getting OpenBSD ported to them. Doug.
Re: About Xen: maybe a reiterative question but ..
On Mon, Oct 29, 2007 at 09:11:01AM -0400, bofh wrote: On 10/29/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: So if nobody makes really good hardware then there's nobody to reward for it, so you end up buying bad hardware and rewarding the maker for it. If given a choice, I think I like Sun's sparc hardware most of all. Though IBM's boxes do allow LPARs from what I understand. And apparently the new power6 boxes will also run/translate x86 software(!), or so I heard. However, looking at what old Sun sparc stuff is on Ebay, there isn't much that could translate into something usefull around the home. Most are 1U boxes; great for application servers but you can't load them up with disk drives. Whereas the IBM pSeries 7025 or 7026 has more room in which to play. As for LPARs, I don't really need them. Unless, I suppose if they really do provide rock-solid virtualization so I can run an OpenBSD firewall in one LPAR and another instance of OpenBSD (or Debian, whatever) in another LPAR for doing work or setting up a file server. Doug.
Re: what's makes a route not valid in openbgpd?
On 10/29/07, Claudio Jeker [EMAIL PROTECTED] wrote: The nexthop depends on a bgp route which is considered evil and therefor not allowed by default. Add nexthop qualify via bgp to the global config part and your setup should work again. Henning hit me with that clue-by-four privately, and that does make perfect sense...but it's still not working. Below is with a refresh, tried it with a hard clear as well. I have nexthop quality via bgp properly situation in the global configuration area. At the risk of being hit by the clue-by-four again...here goes nothing: [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in flags: * = Valid, = Selected, I = via IBGP, A = Announced origin: i = IGP, e = EGP, ? = Incomplete flags destination gateway lpref med aspath origin 0.0.0.0/0 38.103.XXX.50 100 0 174 i [EMAIL PROTECTED] cat /etc/bgpd.conf | grep nexthop nexthop qualify via bgp [EMAIL PROTECTED] bgpctl reload reload request sent. request processed [EMAIL PROTECTED] bgpctl nei 38.104.XXX.37 refresh request processed [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in flags: * = Valid, = Selected, I = via IBGP, A = Announced origin: i = IGP, e = EGP, ? = Incomplete flags destination gateway lpref med aspath origin 0.0.0.0/0 38.103.XXX.50 100 0 174 i [EMAIL PROTECTED] thanks, aaron.glenn
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, Oct 29, 2007 at 06:42:19PM +, Stuart Henderson wrote: On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. [...] So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'. Worked for me. Thanks! (Also you need to 'set image /4.2/i386/bsd.rd'.) Ahhh, yes! Muggins me forgot the set image bit. Too much hurry. Thanks. I believe I know what the issue is, so that I can ensure that it does not happen in the 4.3 release (and future releases). My guess is that some older BIOS's cannot handle a boot.catalog that is more than 32768 2K blocks into the filesystem image. By chance, in this release it is beyond that line by a little bit, for the first time. On the amd64 CD boot.catalog is in front of that line, but cdbr is beyond that line. mkhybrid does not try to avoid this problem. I will see if there is new code to handle this, but in the meantime I also have another workaround which will ensure that future releases don't run into this problem.
Re: what's makes a route not valid in openbgpd?
* Aaron Glenn [EMAIL PROTECTED] [2007-10-29 23:33]: On 10/29/07, Claudio Jeker [EMAIL PROTECTED] wrote: The nexthop depends on a bgp route which is considered evil and therefor not allowed by default. Add nexthop qualify via bgp to the global config part and your setup should work again. Henning hit me with that clue-by-four privately, and that does make perfect sense...but it's still not working. Below is with a refresh, tried it with a hard clear as well. I have nexthop quality via bgp properly situation in the global configuration area. At the risk of being hit by the clue-by-four again...here goes nothing: [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in flags: * = Valid, = Selected, I = via IBGP, A = Announced origin: i = IGP, e = EGP, ? = Incomplete flags destination gateway lpref med aspath origin 0.0.0.0/0 38.103.XXX.50 100 0 174 i why do you XXX the 65? :) wnat does bgpctl sh nex have to say about it? and bgpctl sh fi 38.103.65.50? -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: Marginal boot CD #1 in OpenBSD 4.2 sets
On Mon, 29 Oct 2007, Barry Miller wrote: On Mon, Oct 29, 2007 at 06:42:19PM +, Stuart Henderson wrote: On 2007/10/29 10:49, Austin Hook wrote: I understand that some people have experienced boot problems with CD #1 in the new 4.2 release set, mainly with older machines. [...] So, it may be worth someone with an affected machine trying to boot CD 2 and if the boot loader does start up, pause it (just hit space or something), swap to CD 1, and continue by typing 'boot'. Worked for me. Thanks! Works here too on my P3-450. (Also you need to 'set image /4.2/i386/bsd.rd'.) Or just switch the disks and 'boot /4.2/i386/bsd.rd'. -- Antti Harri
Re: what's makes a route not valid in openbgpd?
On Mon, Oct 29, 2007 at 01:40:07PM -0700, Aaron Glenn wrote:
running 4.2/i386 as of two weeks ago, I've got a default route that
isn't being seen as valid and consequently not installed in the RIB.
when I first rolled this router out, however, it was valid and being
installed. while I'm interested in what could have happened between
then and now, I'm more interested in how the RDE actually makes its
decisions on validity. I see no obvious reason for this route to be
not valid.
everything else (demotion, 'prefix lists', etc) works great, however (-:
relevant info:
[EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in
flags: * = Valid, = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
0.0.0.0/0 38.103.65.50 100 0 174 i
I am learning that nexthop from another session with 174:
[EMAIL PROTECTED] bgpctl show fib bgp
flags: * = valid, B = BGP, C = Connected, S = Static
N = BGP Nexthop reachable via this route
r = reject route, b = blackhole route
flags destination gateway
*B38.103.65.50/32 38.104.XXX.37
[EMAIL PROTECTED] cat /etc/bgpd.conf
AS 10XX0
router-id 72.37.XXX.178
network inet connected
network inet static
network 38.98.XXX.0/24
neighbor 72.37.XXX.177 {
remote-as 10XX0
announce all
}
group COGENT {
remote-as 174
depend on bge1
softreconfig in yes
softreconfig out yes
neighbor 38.104.XXX.37 {
local-address 38.104.XXX.38
set prepend-self 3
announce self
}
neighbor 38.103.XXX.50 {
announce none
multihop 8
}
}
The nexthop depends on a bgp route which is considered evil and therefor
not allowed by default. Add nexthop qualify via bgp to the global config
part and your setup should work again.
--
:wq Claudio
Re: what's makes a route not valid in openbgpd?
On Mon, Oct 29, 2007 at 03:32:59PM -0700, Aaron Glenn wrote: On 10/29/07, Claudio Jeker [EMAIL PROTECTED] wrote: The nexthop depends on a bgp route which is considered evil and therefor not allowed by default. Add nexthop qualify via bgp to the global config part and your setup should work again. Henning hit me with that clue-by-four privately, and that does make perfect sense...but it's still not working. Below is with a refresh, tried it with a hard clear as well. I have nexthop quality via bgp properly situation in the global configuration area. At the risk of being hit by the clue-by-four again...here goes nothing: [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in flags: * = Valid, = Selected, I = via IBGP, A = Announced origin: i = IGP, e = EGP, ? = Incomplete flags destination gateway lpref med aspath origin 0.0.0.0/0 38.103.XXX.50 100 0 174 i [EMAIL PROTECTED] cat /etc/bgpd.conf | grep nexthop nexthop qualify via bgp [EMAIL PROTECTED] bgpctl reload reload request sent. request processed [EMAIL PROTECTED] bgpctl nei 38.104.XXX.37 refresh request processed [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in flags: * = Valid, = Selected, I = via IBGP, A = Announced origin: i = IGP, e = EGP, ? = Incomplete flags destination gateway lpref med aspath origin 0.0.0.0/0 38.103.XXX.50 100 0 174 i [EMAIL PROTECTED] please restart your bgpd process it could be that the nexthop qualify options are not correctly reloaded on config change. Maybe a bgpctl nei 38.104.XXX.37 clear would work as well but I'm not 100% sure about that. Also include the bgpctl show nexthop and bgpctl show fib nexthop output. -- :wq Claudio
Re: max number of groups
* Ted Unangst [EMAIL PROTECTED] [2007-10-26 16:53]: On 10/26/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: What, then, is the correct way to separate the project files of more than 16 projects, where some users will need access to all of the groups? There has to be _some_ solution but it doesn't have to revolve around groups. Surely we don't need a separate box for every 16 projects (and lets not get into another reason to use Xen :)) ) Perhaps it putting the project files in CVS for individuals to check out. Perhaps its some database system. I don't know. I am confident that there is a logical proper solution. ok, sure. you can create a user account projectN for every project, then tell every user who wants access the password. that's not a solution, that's changing the problem. :) when you say files, i think files on the filesystem, not files i can make copies of via scp. i have no idea what you're trying to do, but if you really have so many projects and people and combinations and you care deeply about security, why _would_ you cram all this mayhem onto a single box? if you care deeply enough about security between the groups that this matters, they shouldn't be sharing a filesystem. Get a seperate machine per project, or seperate machine per groups of projects that trust each other - something big enough to be a cvs sever is cheap like borscht. If you really want seamless file sharing across them. consider if what you are attempting to do with groups is really all that wise to begin with. but to really comment I'd need a much better description of exactly what you're doing.
Re: Remove escape characters from file
On Fri, Oct 26, 2007 at 03:45:39PM +0200, Pieter Verberne wrote: does OpenBSD have a program/script to remove control characters (escape sequence) from text files? Try col -b -- Brett Lymn Warning: The information contained in this email and any attached files is confidential to BAE Systems Australia. If you are not the intended recipient, any use, disclosure or copying of this email or any attachments is expressly prohibited. If you have received this email in error, please notify us immediately. VIRUS: Every care has been taken to ensure this email and its attachments are virus free, however, any loss or damage incurred in using this email is not the sender's responsibility. It is your responsibility to ensure virus checks are completed before installing any data sent in this email to your computer.
Re: First install: Grub doesn't find partitions
Hi, Am Montag, 29. Okt 2007, 20:01:22 +0100 schrieb Bertram Scharpf: Am Montag, 29. Okt 2007, 11:54:23 -0500 schrieb Andrew Daugherity: I think this is your problem -- the OpenBSD partition needs to be a primary partition (hda1-hda4 in Linux terminology, or (hd0,1) - (hd0,3) in GRUB language, and you have it as an extended partition (hdb6). This is not supported. [...] Moving partitions around on the machine described above will take some time but I will try it in any case and I will report. I shuffled the OpenBSD partition to the primary section in front and --- it works! Phew! Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
using bgpd and ospfd
I set up a test network with bgpd/ospfd, a standard service provider design where ospf carries the network links and loopbacks and bgp carries everything, bgp routers doing nexthop self, core full mesh and access routers rr-clients of the two nearest core routers. I'm seeing some pretty odd behaviour that I haven't seen before when only using bgpd. Are there any know issues with using this kind of design with bgpd/ospfd ? Quick example: View from an access router at another prefix on the other side of the network ar1# route get 10.1.102.0 route to: 10.1.102.0 destination: 10.1.102.0 mask: 255.255.255.0 gateway: 172.16.1.6 interface: vlan602 if address: 172.16.1.5 flags: UP,GATEWAY,DONE,PROTO1 use hopcount mtuexpire 1470 0 0 0 ar1# bgpctl show fib 10.1.102.0 ... flags destination gateway *B10.1.102.0/24 172.16.1.6 ar1# bgpctl show rib 10.1.1.02.0 ... flags destination gateway lpref medaspath origin I* 10.1.102.0/24 192.168.0.1 120 3010 i I*10.1.102.0/24 192.168.0.2 120 3010 i ar1# ospfctl show fib 192.168.0.1 flags: * = valid, O = OSPF, C = Connected, S = Static FLags Destination Nexthop *O 192.168.0.1/32 172.16.1.6 ar1# So far so good. I now shut down the core router 192.168.0.1 The moment I do that the connectivity dies, even though there is another path. ar1# route get 10.1.102.0 route to: 10.1.102.0 destination: 10.1.102.0 mask: 255.255.255.0 gateway: 172.16.1.6 interface: vlan602 if address: 172.16.1.5 flags: UP,GATEWAY,DONE,PROTO1 use hopcount mtuexpire 1646 0 0 0 ar1# bgpctl show fib 10.1.102.0 ... flags destination gateway *B10.1.102.0/24 172.16.1.6 ar1# bgpctl show rib 10.1.1.02.0 ... flags destination gateway lpref medaspath origin I*10.1.102.0/24 192.168.0.2 120 3010 i ar1# ospfctl show fib 192.168.0.2 flags: * = valid, O = OSPF, C = Connected, S = Static FLags Destination Nexthop *O 192.168.0.2/32 172.16.1.2 ar1# bgp rib and fib look out of sync. Any ideas why it behaves this way ? It seems like the networks that only exist in bgp fail to re-route when I take down a core router that is the current bgp-nexthop. /Tony
Re: About Xen: maybe a reiterative question but ..
On 10/29/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: As for LPARs, I don't really need them. Unless, I suppose if they really do provide rock-solid virtualization so I can run an OpenBSD firewall in one LPAR and another instance of OpenBSD (or Debian, whatever) in another LPAR for doing work or setting up a file server. I don't think you can run OpenBSD in LPARs. From the official IBM docs, all I see available is: - AIX - RHEL - SuSE I would love to hear about anyone that made OBSD work on p-Series in LPARs. B)
carp on wan interface
I've been reading about and want to set up a set of (2) carp/pf/pfsync redundant firewalls but I haven't seen anything in the docs or on the list similar to what i'm hoping to accomplish so here goes: I'm horrible at ascii art so i'll try to describe the scenario as best i can: 2 firewalls, each firewall will have 4 interfaces, san0(wan), fxp0(backup/redundant/load balancing wan , fxp1(dmz) and fxp2(lan). From what I have read in the docs and from questions that other people have asked I think I have a handle on the lan, dmz interfaces and maybe even the fxp0 wan interface, but I'm wondering about the san0 interfaces. Can they be carped? My idea was to run the cable from the telco into a switch/hub and then carp the san0 interfaces, but I'm not sure if it will work and I don't have a spare t1 to test it. Here is what I'm hoping to accomplish in order of priority: 1. redundancy in the firewalls, one goes down, keep the connections to the dmz and internet alive (incoming and outgoing) 2. uplink redundancy/failover.. if the main t1 (provided by the san0 int) goes down, detect that and route out the fxp0 int instead. fxp0 is connected to a frac. t1 via csu/dsu. I'm not worried about incoming load balancing or routing connections as I am serving dns with short ttls (one dns sever out each of my uplinks) that has been providing redundancy to my dmz hosts as long as at least one of my links are up.. a. ideal but not mandatory to get things going, i'd like to be able to route out both wan interfaces from the lan to increase downloads. the backup is a smaller(256k vs. full t1 on main wan int) connection though, so would i have to set up queuing? I would hate to pull from the backup when i have more than 256k available on the t1 I hope I have included enough info to get some insight on this, if not please ask. My biggest concern here is whether or not i can carp the san interfaces and if not, is there anyway to accomplish this scenario without running the t1 into a dedicated router before it goes into the firewall. Last bit of this, mixed in with all of the things I have been reading i see route to and ifstated mentioned a lot. Would I need to be using ifstated to get the failover working for the two wan interfaces so traffic wouldn't get blackholed? Would I need routeto in my pf.conf to get load balancing working or... Thanks in advance. Aaron
bge driver problem
I'm trying to convert a 22 node ~100 CPU cluster from Linux to OpenBSD. The motivation is to increase reliability and security. However, I have a peculiar problem with the bge driver. It seems that bge doesn't detect properly the media type the hardware supports. The nodes I'm trying to convert are on PenguinComputing BladeRunners with AMD procs and broadcom NICs. When the bge driver loads, the link lights turn off on the NICs, here is more info: # dmesg | grep bg bge0 at pci4 dev 4 function 0 Broadcom BCM5780S rev 0x03, BCM5714 B3 (0x8003): apic 3 int 10 (irq 5), address ... dmesg on linux (in case it is of any use): eth0: Tigon3 [partno(BCM95780s) rev 8003 PHY(5780)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet ... RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[0] TSOcap[1] dma_rwctrl[76144000] dma_mask[40-bit] Here is why I think bge doesn't recognize the proper media types available: # ifconfig -a bge0: flags=88 lladdr ... groups: egress media: Ethe6scopd 0x1 # ifconfig -m bge bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr ... groups: egress media: Ethernet autoselect (none) status: no carrier supported media 1000baseSX mediaopt full-duplex media autoselect (sorry for the choppy output, the console redirection has some flow issues that I haven't figured out how to fix yet). Any hint on how to fix the problem would be greatly appreciated. B)
