Re: pcengines apu{1,4} can't adjust CPU frequency automatically anymore
"Lévai, Dániel" wrote: > I don't know since when, unfortunately, but it seems > auto-adjusting CPU frequency doesn't work anymore on my APU1 > and an APU4 PCEngines boards (I only have these versions at > hand atm). They're both running an updated fw at v4.17.0.2. > > IIRC `apmd -A' + `sysctl hw.perfpolicy=auto' did the trick > earlier, but I'll be honest, I haven't checked this since > forever. > > APU1 has two and the APU4 has three frequencies to set: > cpu0: 1000 MHz: speeds: 1000 800 MHz > cpu0: 998 MHz: speeds: 1000 800 600 MHz > > I can manually adjust this with hw.setperf when hw.perfpolicy > is 'manual', so setting the frequency actually works, it's just > that it can't seems to "detect" load/change when it's set to > 'auto'. Hello! Since some time auto scaling (by OpenBSD) is disabled while the system is connected to AC power. This might not be a problem since many systems seems to handle scaling by themself. My APU4 has about the same temperature as before the upgrade. Setting the CPU speed to 600MHz does not lower the temperature. While perfpolicy is set to auto, if I start four "openssl speed" the temperature will quickly rise. My conclusion from this is that the APU4 will handle scaling on its own. Best regards, Jan J
Re: WireGuard, keepalive time doubled?
Alexander Hall wrote: > > Is this to be expected or am I missing something? > > > > Both sides run OpenBSD 6.8 amd64 if that affects anything. > > Just a random thought; are you running on actual hardware or > testing with some sort of virtualization involved? VMM and > friends are known to sometimes double delays... That would be it, the side with wgpka set is a virutal machine running on a OpenBSD 6.8 host. I will just stick with the documented suggestion of 25 (which gives me 50 seconds) and works well with the default of 60 seconds for PF udp.multiple states. Thanks a lot!
WireGuard, keepalive time doubled?
Hello! I was experimenting with wireguard keepalive and noticed that keepalive packets seems to be sent on double the time that I have set which I find a bit unintuitive. The peer is setup like this on side a wgpeer k wgpsk (present) wgpka 60 (sec) wgendpoint b.b.b.174 tx: 868, rx: 496 last handshake: 96 seconds ago wgaip c.c.c.33/32 debug log on side a 11:41:04 wg /bsd: wg0: Sending handshake initiation to peer 4 11:41:04 wg /bsd: wg0: Receiving handshake response from peer 4 11:41:04 wg /bsd: wg0: Sending keepalive packet to peer 4 11:41:04 wg /bsd: wg0: Receiving keepalive packet from peer 4 11:43:03 wg /bsd: wg0: Sending keepalive packet to peer 4 11:45:03 wg /bsd: wg0: Sending handshake initiation to peer 4 11:45:03 wg /bsd: wg0: Receiving handshake response from peer 4 11:45:03 wg /bsd: wg0: Sending keepalive packet to peer 4 11:45:03 wg /bsd: wg0: Receiving keepalive packet from peer 4 11:47:03 wg /bsd: wg0: Sending keepalive packet to peer 4 11:49:03 wg /bsd: wg0: Sending handshake initiation to peer 4 11:49:03 wg /bsd: wg0: Receiving handshake response from peer 4 11:49:03 wg /bsd: wg0: Sending keepalive packet to peer 4 11:49:03 wg /bsd: wg0: Receiving keepalive packet from peer 4 11:51:03 wg /bsd: wg0: Sending keepalive packet to peer 4 tcpdump on side b show the following traffic 11:41:03 a.a.a.64. > b.b.b.174.: [wg] initiation from 0x 11:41:03 b.b.b.174. > a.a.a.64.: [wg] response from 0x to 0x 11:41:04 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 0 11:41:04 b.b.b.174. > a.a.a.64.: [wg] keepalive to 0x nonce 0 11:43:03 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 1 11:45:03 a.a.a.64. > b.b.b.174.: [wg] initiation from 0x 11:45:03 b.b.b.174. > a.a.a.64.: [wg] response from 0x to 0x 11:45:03 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 0 11:45:03 b.b.b.174. > a.a.a.64.: [wg] keepalive to 0x nonce 0 11:47:03 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 1 11:49:03 a.a.a.64. > b.b.b.174.: [wg] initiation from 0x 11:49:03 b.b.b.174. > a.a.a.64.: [wg] response from 0x to 0x 11:49:03 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 0 11:49:03 b.b.b.174. > a.a.a.64.: [wg] keepalive to 0x nonce 0 11:51:03 a.a.a.64. > b.b.b.174.: [wg] keepalive to 0x nonce 1 Is this to be expected or am I missing something? Both sides run OpenBSD 6.8 amd64 if that affects anything. Best regards, Jan J
Re: vmm/vmd disk issue
So to conclude. I have done four parallel dd, cp, cmp on the host without any error showing up. Ian Darwin wrote: > Depending on where the error is, you might get away with > dd'ing with conv=noerror,sync, changing vm.conf to point > to the new copy, and run fsck in the vm. After this the vm would no longer freeze but an important config file was missing so I would not trust the state of the machine for anything else than maybe keeping it alive a few days until there is a better time to reinstall. Dave Voutila wrote: > Have you run fsck(8) on your host? Complere fsck of the host in single user mode showed no problem at all. > I'd say maybe make sure you have backups of anything important > first if you're purposely going to break things. :-) Always! :) So for now I will just let it be and see what time gives. Thank you all for your input!
Re: vmm/vmd disk issue
Mike Larkin wrote: > On Tue, Mar 09, 2021 at 09:38:57AM -0500, Ian Darwin wrote: > > On Tue, Mar 09, 2021 at 09:52:03AM +0100, Jan Johansson wrote: > > > If I try to cp or dd the disk image on the host it fails > > > > > > dd if=disk.raw.old of=disk.raw.bak bs=1m > > > dd: disk.raw.old: Input/output error > > > 8858+0 records in > > > 8858+0 records out > > > 9288286208 bytes transferred in 102.048 secs (91018010 bytes/sec) > > > > > > The host show no other signs of failing hardware. > > > > > > Is this a software or a hardware error? > > > > Given that it gives an error outside the VM, it's likely hardware. > > > > Agreed. Sorta hard to fault vmd(8) if it's not even running. Since these are sparse files, could the vioblk(4) somehow write incorrect data that later will make it unreadable such as a pointer pointing into nothingness? The messages vmd[39543]: vioblk write error: Input/output error vmd[39543]: wr vioblk: disk write error was produced and 01:30 when all the 4 guests and the host all run the daily script (which makes backup and other maintenance tasks) if that could have any impact. Should there not be anything on the host logging errors to dmesg/syslog such as sd(4) or ahci(4)? (If it is not obvious my understanding of how the virtio/vioblk stuff hooks in to the disk stack is very limited) This drive was installed in august 2020 and if I recall correctly it was because of this issue. So I am thinkig cable or motherboard. If I decide to replace would it make sense to make this a softraid mirror (RAID1) to avoid or get better indication of this kind of problems in the future or would only add more parts that can break? I'am currently trying to provoke the drive from the host with dd if=/dev/random of=test.raw bs=1m count=17000 then cp/dd and cmp to see if I can make it break for real.
vmm/vmd disk issue
Hello! A few times I have had problems with my guests freezing (no console, no ssh) when reading a specific file and only a complete reinstall seems to solve the problem. This has happended with both raw and qcow2 disks and on both 6.7 and 6.8. I'm only using OpenBSD for the host and guests. When the freeze happens the host logs these messages six times vmd[24266]: vioblk read error: Input/output error vmd[24266]: vioblk: block read error, sector 23122496 I also found this a few days back that may be relevant vmd[39543]: vioblk write error: Input/output error vmd[39543]: wr vioblk: disk write error If I try to cp or dd the disk image on the host it fails dd if=disk.raw.old of=disk.raw.bak bs=1m dd: disk.raw.old: Input/output error 8858+0 records in 8858+0 records out 9288286208 bytes transferred in 102.048 secs (91018010 bytes/sec) The host show no other signs of failing hardware. Is this a software or a hardware error? Is there some way to recover the guest disk image without a complete reinstall? Thank you in advance, Jan J
Drive/pciide reset problems with SiI3112.
Hello! In an attempt to expand the available disk in my server I bought a Silicon Image SiI3112 PCI - SATA controller. There is no problem while booting with the bsd.rd. Booting the normal kernel produces a number of read timeouts and finally boots normally. (Using OpenBSD 4.4 there is no problem I did not test release 4.5 to 4.8). Trying to access the disk with disklabel freezes the system a few seconds and then prints a faulty label. (There is wd0a, wd0b and wd0d on this disk). :; disklabel wd0 # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: WDC WD2500PD-07F duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30401 total sectors: 488397168 boundstart: 0 boundend: 488397168 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:4883971680 unused while the message wd0: flush cache command timeout is added to dmesg. Are there any useful commands or kernel knobs I could twist to provide a more comprehensive bug report? Jan J OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 2.00GHz (GenuineIntel 686-class) 2 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 1072721920 (1023MB) avail mem = 1045123072 (996MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/17/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (82 entries) bios0: vendor Dell Computer Corporation version A07 date 12/17/2003 bios0: Dell Computer Corporation Precision WorkStation 340 acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT acpi0: wakeup devices VBTN(S4) PCI0(S5) USB0(S3) USB1(S3) PCI1(S5) KBD_(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PCI1) acpicpu0 at acpi0 acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0x9000 0xc9000/0x5000 0xce000/0x2000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82850 Host rev 0x04 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xf400, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82850/82860 AGP rev 0x04 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Matrox MGA G550 AGP rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x04 pci2 at ppb1 bus 2 pciide0 at pci2 dev 8 function 0 CMD Technology SiI3112 SATA rev 0x02: DMA pciide0: using apic 1 int 17 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: WDC WD2500PD-07FZB1 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5 xl0 at pci2 dev 12 function 0 3Com 3c905C 100Base-TX rev 0x78: apic 1 int 18, address 00:06:5b:dc:7b:ae exphy0 at xl0 phy 24: 3Com internal media interface ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x04 pciide1 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x04: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd1 at pciide1 channel 0 drive 0: ST380021A wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide1 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LITEON, DVD-ROM LTD163, GDHA ATAPI 5/cdrom removable cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 31 function 2 Intel 82801BA USB rev 0x04: apic 1 int 19 ichiic0 at pci0 dev 31 function 3 Intel 82801BA SMBus rev 0x04: apic 1 int 17 iic0 at ichiic0 admtm0 at iic0 addr 0x2d: 47m192 uhci1 at pci0 dev 31 function 4 Intel 82801BA USB rev 0x04: apic 1 int 23 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 mtrr: Pentium Pro MTRR support pciide0:0:0: not ready, st=0xd0BSY,DRDY,DSC, err=0x00 pciide0 channel 0: reset failed for drive 0 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying pciide0:0:0: not ready, st=0xd0BSY,DRDY,DSC, err=0x00 pciide0 channel 0: reset failed for drive 0 wd0c: device timeout
Re: Sil 3112a drive timeout.
Jan Johansson janj+open...@wenf.org wrote: So I have been comparing RAMDISK_CD and GENERIC for a few days and it seems I can compile a working GENERIC by commenting options DIAGNOSTIC in the config file. Trying to find exactly which ifdef that kills the card I started getting unpredictable results while changing ifdef's in /usr/src/sys/kern and /usr/src/sys/scsi. Sometimes it work sometimes it dosen't. :-( Any suggestions would be very welcome. For the Archives. So I gave up on this and did an install of 4.8 release. Even built a nonDIAGNOSTIC kernel using a PATA drive and realized that the problem seems gone (even with the official /bsd). I have no clue what changed.
Re: Sil 3112a drive timeout.
Jan Johansson janj+open...@wenf.org wrote: My backup server ran out of space and I got my hands on a SATA pci card carrying a Sil 3112a chip. The problem beeing that when booting bsd the drive timeout with a message like: pciide0:0:0: not ready, st=0xd0BSY,DRDY,DSC, err=0x00 pciide0 channel 0: reset failed for drive 0 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying So I have been comparing RAMDISK_CD and GENERIC for a few days and it seems I can compile a working GENERIC by commenting options DIAGNOSTIC in the config file. Trying to find exactly which ifdef that kills the card I started getting unpredictable results while changing ifdef's in /usr/src/sys/kern and /usr/src/sys/scsi. Sometimes it work sometimes it dosen't. :-( Any suggestions would be very welcome.
Sil 3112a drive timeout.
Hello! My backup server ran out of space and I got my hands on a SATA pci card carrying a Sil 3112a chip. The problem beeing that when booting bsd the drive timeout with a message like: pciide0:0:0: not ready, st=0xd0BSY,DRDY,DSC, err=0x00 pciide0 channel 0: reset failed for drive 0 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying I have flashed the motherboard and SATA controller bios:es to the latest version. For the SATA controller i used the non-RAID base image. Booting bsd.rd works without any problems. Booting bsd from 4.4 works without any problems. Booting bsd from 4.5 or later stops with a timeout. So I am going to start with 4.4 and work my way forwards if there aren't any better ideas. boot bsd.rd booting hd0a:bsd.rd: 5897688+943444 [61+224624+213013]=0x6f1290 entry point at 0x200120 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2010 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.8-current (RAMDISK_CD) #225: Sat Dec 4 12:21:11 MST 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) 4 CPU 2.20GHz (GenuineIntel 686-class) 2.23 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 real mem = 1073250304 (1023MB) avail mem = 1048756224 (1000MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/16/02, BIOS32 rev. 0 @ 0xfa1d0, SMBIOS rev. 2.3 @ 0xf0120 (38 entries) bios0: vendor Award Software International, Inc. version 6.00 PG date 09/16/2002 bios0: EVERCOM NETWORK 8IRX acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 100MHz ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (HUB0) bios0: ROM list: 0xc/0xc000 0xcc000/0x5000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82845 Host rev 0x04 ppb0 at pci0 dev 1 function 0 Intel 82845 AGP rev 0x04 pci1 at ppb0 bus 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x05 pci2 at ppb1 bus 2 vga1 at pci2 dev 0 function 0 ATI Mach64 rev 0x5c wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) pciide0 at pci2 dev 2 function 0 CMD Technology SiI3112 SATA rev 0x02: DMA pciide0: using apic 2 int 22 (irq 15) for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: WDC WD2500PD-07FZB1 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5 em0 at pci2 dev 4 function 0 Intel PRO/1000XT (82544EI) rev 0x02: apic 2 int 18 (irq 11), address 00:02:b3:e6:fa:5b pcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05 Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 rd0: fixed, 3872 blocks softraid0 at root root on rd0a swap on rd0b dump on rd0b erase ^?, werase ^W, kill ^U, intr ^C, status ^T boot boot bsd booting hd0a:bsd: 8186428+1090024 [61+369696+355596]=0x989f2c entry point at 0x200120 [ using 725768 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2010 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.8-current (GENERIC) #510: Sat Dec 4 12:03:30 MST 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 2.20GHz (GenuineIntel 686-class) 2.23 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 real mem = 1073250304 (1023MB) avail mem = 1045643264 (997MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/16/02, BIOS32 rev. 0 @ 0xfa1d0, SMBIOS rev. 2.3 @ 0xf0120 (38 entries) bios0: vendor Award Software International, Inc. version 6.00 PG date 09/16/2002 bios0: EVERCOM NETWORK 8IRX acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices SLPB(S5) HUB0(S4) USB0(S1) USB1(S1) PCI0(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 100MHz ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (HUB0) acpicpu0 at acpi0 acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0xc000 0xcc000/0x5000
Re: PF and States
Godesi dabhee...@aim.com wrote: We recently deployed OBSD4.7 boxes to do load balancing in our environment with relayd. After few hours we encountered problem with the server going beyond 10,000 states. Are you convinced that it is a state problem? In our tests we have found that a default setup of relayd will handle 2540 connections and will then stop responding to new connections might this be the limit you are seeing? Our pf.conf is the default that comes with the install.
Re: help gateway 4.8
Kenneth Gober kgo...@gmail.com wrote: I'm guessing the ADSL router is a typical NAT router, and that your OpenBSD router is *not* configured for NAT. as a result, the ADSL router is seeing outbound packets from 192.168.0.10, but doesn't know how to deliver the inbound responses. it knows that the 192.168.1/24 network is reachable via one of its own LAN ports, but I'm guessing that it doesn't know how to reach the 192.168.0/24 network. you need a static route defined on the ADSL router telling it that for the 192.168.0/24 network, the next hop router is at 192.168.1.101. Your guess is incorrect given the facts in this case. In the first mail david showed a pf ruleset which had: match out on egress inet from ! (egress:network) to any nat-to (egress:0) round-robin He also showed that the client can't reach the OpenBSD gateway so the traffic never gets to the ADSL modem. For refrence see: http://marc.info/?l=openbsd-miscm=129122248900549w=2
Re: help gateway 4.8
david carrasco dacar...@gmail.com wrote: hi, dear friend both cables ( cable 1 and 2 ) are crossover and is conectic like this, and no internet in client, help please From the ifconfig output it is obvious that there is a problem with cable 2. It is either the cable or the network interface card. They should har lights that should be lit when everything is corret. For instance are the lights the same on both of xl0 and xl1? There could also be some kind of issue with auto negotiation. Do you have any other network equipment at hand that you can use to check the cable and network cards? Are you really sure you are using cross over cables? In my experience ADSL Modems are made like a switch and therefor has no problem beeing connected to a host directly. Your other connection is between hosts and therefor (in the 100MBit case) must use a special cable. You can use http://en.wikipedia.org/wiki/Ethernet_crossover_cable to verify that you have an crossover cable.
Re: help gateway 4.8
david carrasco dacar...@gmail.com wrote: answer your question, i believe the problern is static routing setting on all cable is okey please help, with set up static client,gateway, and router (dsl ext) On gateway start tcpdump -i xl1 gateway.my.domain (192.168.0.1) at 00:60:97:be:ca:2a on xl1 static ? (192.168.1.1) at 00:1d:0f:fc:95:de on xl0 * then on client start ping 192.168.0.1. Do you see the packets? / --- 192.168.0.1 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss /// After you stop the ping run arp -a on both client and gateway. Do you see an entry for the other host? in gateway gateway.my.domain (192.168.0.1) at 00:60:97:be:ca:2a on xl1 static ? (192.168.1.1) at 00:1d:0f:fc:95:de on xl0 in client /// nothing out screen /// I am having a hard time following what you are saying. On the gateway run ping 192.168.0.10 when you stop that run arp -a in the output you should see one of thease lines: This one means your layer 2 such as cable is broken. ? (192.168.0.10) at (incomplete) on xl1 This one means your layer 3 such as packet filter is broken. ? (192.168.0.10) at 00:0c:76:bb:00:5a on xl1 But as another subscriber noted: vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 media: Ethernet autoselect (none) status: no carrier and xl1: flags=8a43UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST mtu 1500 media: Ethernet autoselect (none) status: no carrier which means neither your gateway or your client has a working cable. Are you using a switch or are these machines connected to each other with a direct cable? If you are using a direct cable you will need a crossover cable as 100baseTX does not support auto MDI/MDI-X.
Re: help gateway 4.8
david carrasco dacar...@gmail.com wrote: Greetings to all good I hope to help me I followed the manual gateway-firewall openbsd 4.8 but still can not get or have no internet Conexxion client ADSL (router ext) 192.168.1.1 | | xl0 192.168.1.101 gatewayopenbsd4.8- xl1 192.168.0.1 | | Client 192.168.0.10 On gateway start tcpdump -i xl1 then on client start ping 192.168.0.1. Do you see the packets? After you stop the ping run arp -a on both client and gateway. Do you see an entry for the other host? If the answer to thease questions are No then you have a layer two (or below) problem. Check cabling, vlan configuration and such. It the answer to thease questions are Yes then you have a layer three (or above) problem. Check your packet filters.
Re: relayctl reload : command failed.
Xavier Beaudouin k...@oav.net wrote:
# relayctl reload
command failed
[...]
relay webmail-80 {
listen on $webmail port 80
transparent forward to webmail port 80 mode hash check http / host
webmail.openvisp.net code 200 interface $int_if
}
relay webmail-443 {
listen on $webmail port 443
transparent forward to webmail port 443 mode hash check https / host
webmail.openvisp.net code 200 interface $int_if
}
Not yet implemented.
From src/usr.sbin/relayd/control.c
case IMSG_CTL_RELOAD:
if (env-sc_prefork_relay 0) {
imsg_compose_event(c-iev, IMSG_CTL_FAIL,
0, 0, -1, NULL, 0);
break;
}
So if there are more than 0 relays it bails.
Re: Number of static IP addresses needed for CARP
Jeff Ross jr...@openvistas.net wrote: What can one then use for the IP addresses for the $ext_if of the firewalls? For connection testing. With only one IP assigned to the CARP interface. When it is in BACKUP state you do not have an address on the network and as such you can't check connectivity from the BACKUP host. For me with 25 vlans on production firewalls this is vital. For a home network where IPs cost extra I would not care.
ospf6d doesn't announce passive interfaces
Hello!
We have been running with an ospfd.conf looking like this:
router-id 10.10.10.6
area 0.0.0.0 {
auth-type crypt
auth-md 1 secret
auth-md-keyid 1
interface em0 # Uplink / egress
interface carp125 { passive } # Inside on top of if vlan125
interface carp916 { passive }
interface carp943 { passive }
}
This has successfully announced the route only from the carp
MASTER avoiding assymetric routing and problems with stateful
filtering.
I am now trying to replicate this setup for IPv6 using
ospf6d but it seems that it will only announce addresses on
active interfaces.
So what obvious difference between ospf in IPv4 and IPv6 have I
missed?
Jan J
uxterm and backspace
Hello! In my work I access a lot of machines that use UTF-8 as default encoding. Trying to get this to work with my OpenBSD laptop i found the following problem. start an uxterm $ file utf-8.txt utf-8.txt: UTF-8 Unicode text $ cat utf-8.txt edvEDV I then run cat and type four swedish characters and then try to backspace two of them. The display is updated correctly but hitting enter shows that only one of the characters was erased. $ cat ee eee On an standard (ISO8859) xterm this gives. $ cat ee ee On remote terminal session this becomes a problem when my fat fingers accidently hit the swedish characters and backspace seems to erase them but I get garbaled commands. So what am I doing wrong? Is this a lack of locale support in OpenBSD or is xterm a little broken? Jan J
Re: dts and vlc
Paul Irofti [EMAIL PROTECTED] wrote: I have some dts files that I want to play. After searching, the best option seemed to be vlc. The problem is that vlc crashes when I try playing any of these files (they were tested before in winamp or something similar by the person that provided them). Has anyone encountered this before? Is there something I'm missing? Suggestions of other players available for OpenBSD that can output dts files are also welcomed (mplayer fails too). You provide way to little information. What versions of OpenBSD, vlc and mplayer did you use. What command line and so on ... Well, I have had no luck getting vlc to do DTS or Dolby Digital passthrough on my DVDs. However with the right soundcard I have had luck with mplayer such as 'mplayer -ac hwac3 dvd://'. Hope you solve your problem or try asking again ...
Re: 4.0-beta SSH and GSSAPI Segmentation fault.
Darren Tucker [EMAIL PROTECTED] wrote: It would appear that while the underlying problem is in the kerberos library, Simon has provided a better workaround (below) which has been applied to ssh and will be in the next snapshot. Thanks for the report. Sorry for the late response. I just installed a new snapshot. $ sysctl kern.version kern.version=OpenBSD 4.0 (GENERIC) #1104: Fri Sep 1 11:54:27 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC ssh works for me both with a ticket and without a ticket. Thank you both.
Re: OT: (don't open if you don't like) Kerberized FTP client/Server
Gustavo Rios [EMAIL PROTECTED] wrote: I am implementing an openbsd kerberos server and would like windows client to connect to another openbsd ftp server using kerberos. Is that possible? What kind of ftp client have you been using on windows for such task? Is it possible to have such environment working with standard openbsd ftp server ? KTelnet does Kerberized FTP but I would suggest using SSH/SCP because the clients are better. http://www.stacken.kth.se/~thn/ktelnet/beta/
Re: Bridge wireless and wired networks.
kami petersen [EMAIL PROTECTED] wrote: Jan Johansson skrev: kami petersen [EMAIL PROTECTED] wrote: well, it should work. however, you should set an address on either of the interfaces that constitutes the bridge, not the bridge itself. but you don't say exactly where you are unsuccessful... It works, I just thought there might be a cleaner solution. For example both ral0 and fxp1 needs an IP address or dhcpd just refuses to work on the interface. on the router: assign 192.168.13.1 to fxp1 and none to ral0, put both fxp1 and ral0 in the bridge, putting both ral0 and fxp1 in dhcpd.interfaces. a similar solution is working here. I started over and this time I got it working with an address only on ral0 and dhcpd listening only on ral0. (I think the paket filter and stupid Windows XP was the problem the first time). Thanks for the help.
Bridge wireless and wired networks.
Hello. On my laptop I use trunk(4) failover to switch between wired and wireless networks. It works great. But I think my solution for the router is a bit dirty. Is there a better way? The router has one interface connected to the internet (fxp0) and two interfaces for the internal network (ral0 and fxp1). When I get tired of waiting for a download to complete I wish to switch from wireless to a crossover cable (I rather not use a switch) without interruption. The solution I have: :; ifconfig fxp1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:02:b3:2b:b2:89 media: Ethernet autoselect (none) status: no carrier inet6 fe80::202:b3ff:fe2b:b289%fxp1 prefixlen 64 scopeid 0x2 inet 192.168.13.2 netmask 0xff00 broadcast 192.168.13.255 ral0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0e:2e:86:7b:14 media: IEEE802.11 autoselect hostap status: active ieee80211: nwid NAH chan 1 bssid 00:0e:2e:86:7b:14 nwkey Nope 100dBm inet 192.168.13.1 netmask 0xff00 broadcast 192.168.13.255 inet6 fe80::20e:2eff:fe86:7b14%ral0 prefixlen 64 scopeid 0x3 bridge0: flags=41UP,RUNNING mtu 1500 groups: bridge :; brconfig bridge0 bridge0: flags=41UP,RUNNING Configuration: priority 32768 hellotime 2 fwddelay 15 maxage 20 Interfaces: fxp1 flags=3LEARNING,DISCOVER port 2 ifpriority 128 ifcost 55 ral0 flags=3LEARNING,DISCOVER port 3 ifpriority 128 ifcost 55 Addresses (max cache: 100, timeout: 240): And then I start dhcpd with '/usr/sbin/dhcpd ral0 fxp1'. For me it would be beutifull to set the 192.168.13.1 address on bridge0 and have dhcpd listen only on bridge0 or maybe use trunk(4) in some mode for this but I have been unsuccessfull at that. Suggestions? Jan J
Re: Bridge wireless and wired networks.
kami petersen [EMAIL PROTECTED] wrote: well, it should work. however, you should set an address on either of the interfaces that constitutes the bridge, not the bridge itself. but you don't say exactly where you are unsuccessful... It works, I just thought there might be a cleaner solution. For example both ral0 and fxp1 needs an IP address or dhcpd just refuses to work on the interface. also, failover trunk ought to work, A failover trunk will work for one laptop. But if a friend and I are sharing the wireless the friend will be cut off when the wired interfaces goes active. but i wouldn't know how a bridge pair directly hooked up against let's say a round robin trunk would behave. Don't understand this. maybe then the finer options of brconfig(8) would be worth trying. Yes, tuning of 'timeout' might be a good idea. Thanks.
Re: Network configuration for laptop
Matthew R. Dempsky [EMAIL PROTECTED] wrote: Is there a proper way to dynamically manage network interfaces with OpenBSD? I have been using ``ifconfig iwi0 nwid $ESSID nwkey $KEY; dhclient iwi0'' to connect to a given wireless network and ``ifconfig iwi0 down'' to disconnect (and similarly with em0 for wired networks), but this gives me problems at times. You want trunk(4) in failover mode, it is pure magic. :-) ifconfig trunk0 trunkproto failover trunkport em0 trunkport iw0 dhclient trunk0 When moving to a new wireless network use ifconfig to set a new nwid and nwkey and it should just work. For example, sometimes it seems I cannot (re)associate with a wireless network or dhclient(1) will not give an IP address. Surely there's a better solution than rebooting anytime my network setup gets wedged. :-) (Sorry for the vague problem descriptions---I'm not yet familiar with how to diagnose my networking issues on OpenBSD.) I have hade some problems with iwi(4), it seems the card can hang when changing nwid but I have not enough info for a bug report. Blame Intel that won't give out documentation so that developers have to guess how the card works. Finally, the ifconfig(1) man page mentions that the down action ``automatically disables routes using the interface,'' but if I run ``ifconfig iwi0 down'' after connecting to my home network, ``route show'' still lists iwi0. Am I misreading the man page or is this a bug? Don't know that one.
Re: Sound card with supported digital out
andrew fresh [EMAIL PROTECTED] wrote: I have tried one of those, I had forgotten about that. The problem with the USB digital output that I have tried is that it does not do AC3/DTS passthrough, all it does is output 2 channel PCM over the optical digital connection. I believe the one I tried was a Turtle Beach Audio Advantage Micro. If there is USB audio that will do AC3/DTS passthrough on OpenBSD, I would be happy with that. I have a Sinovoice UAC-05 which identifies like this uaudio0 at uhub0 port 2 configuration 1 interface 0: ABC C-Media USB Headphone Set, rev 1.10/1.00, addr 2 uaudio0: audio rev 1.00, 8 mixer controls audio0 at uaudio0 it is connected to my NAD T-760 receiver using a toslink (optical) cable. In the following examples I use Gladiator (region 2). To get DTS on the receiver: mplayer dvd:// To get Dolby Digital on the receiver: mplayer -ac hwac3 -aid 128 dvd:// (On Shrek (region 1) I had to use -aid to get DTS.) -ac hwac3 tells mplayer to let the soundcard do the work and not do it in software. To find the aid (audio id) I run mplayer with -v and look for something like this. DVD successfully opened. [open] audio stream: 0 audio format: ac3 (5.1) language: en aid: 128 [open] audio stream: 1 audio format: dts (5.1) language: en aid: 137 [open] audio stream: 2 audio format: ac3 (stereo) language: en aid: 130 Hope this helps.
Re: dual boot problem
akonsu [EMAIL PROTECTED] wrote: dd if=/dev/rwd0c of=mbr count=1 Here is your error dd if=/dev/rwd0a of=pbr count=1 For the NTLDR you want the PBR (Partition Boot Record) not the MBR (Master Boot Record). I changed the of= for correct the terminology the important part is the if= device. I usually use dd if=/dev/rwd0a of=/mnt/OpenBSD.pbr bs=512 count=1 where /mnt is the mountpoint of a small FAT partiton that is active.
Re: dual boot problem
viq [EMAIL PROTECTED] wrote: While at the subject, you need to run this every time you upgrade bootblocks. What would be the result of not updating bootblocks when upgrading from snapshot? Sounds dangerous to me. Will old bootblocks be able to boot the kernel? Or not rerunning that command when updating them? It will say Err M after you choose OpenBSD from NTLDR. Use the bootblock from the CD but load the kernel from hd0 by typing boot hd0a:/bsd at the boot prompt. Then rerun the command to update your your PBR-file.
Re: Sound card with supported digital out
andrew fresh [EMAIL PROTECTED] wrote: Is there a supported sound card that supports digital outputs? I am trying to build a media pc that is similar to GeeXboX[2]. Pretty much just minimal system that will netboot and get mplayer running, but on an OS I like, OpenBSD :-) However, I want to be able to do AC3 and DTS passthrough and I am not sure if any digital audio out is supported on any cards in OpenBSD. I think your best bet is USB audio. I have a simple USB audio stick that does optic digital signal or headphones under OpenBSD.
Re: What are p0 files?
I think think this is a question for [EMAIL PROTECTED] Peter Bako [EMAIL PROTECTED] wrote: My first though was that it denoted a patch level, It denotes a patchlevel for the OpenBSD package/port. but in this particular case the file sizes are close enough that there cannot be that much of a difference. As far as I know. Changing a char *foo[4]; to a char *foo[5]; can make the difference between a root hole or not but won't change the size of the package. Also if it were patch levels there would also be p1, p2, and so on versions There are /pub/OpenBSD/3.8/packages/i386/mplayer-1.0pre7p5.tgz.
Re: OT: OpenBSD on IBM/lenovo T42 or T43, Z series?
Subcommander l0r3zz [EMAIL PROTECTED] wrote: If anyone out there is running OpenBSD 3.8 or current with X-windows on any of the above could you let me know? I've searched the archives and the laptop pages and don't see any mention of these particular models. I'd like to make sure I can run OpenBSD before I buy. My findings regarding the Lenovo Z60m is on http://openbsd.org/i386-laptop.html Can you specify you question? If it is something special you are woundering about I am sure I can try it for you.
Re: OT: OpenBSD on IBM/lenovo T42 or T43, Z series?
Jan Johansson [EMAIL PROTECTED] wrote: My findings regarding the Lenovo Z60m is on http://openbsd.org/i386-laptop.html Make that http://www.openbsd.org/i386-laptop.html (seems updates are a bit slow). Can you specify you question? If it is something special you are woundering about I am sure I can try it for you.
FSC D1627-C and hw.sensors
Hello. I have a Fujitsu Siemens D1627-C motherboard and with OpenBSD 3.9-beta (dmesg at end) I can not see any hw.sensors. # /sbin/sysctl hw hw.machine=i386 hw.model=Intel(R) Pentium(R) 4 CPU 3.20GHz (GenuineIntel 686-class) hw.ncpu=1 hw.byteorder=1234 hw.physmem=1072717824 hw.usermem=1072488448 hw.pagesize=4096 hw.disknames=cd0,cd1,wd0 hw.diskcount=3 hw.cpuspeed=3192 hw.setperf=100 In Microsoft Windows XP (SP2) I use the program SpeedFAN, which prints the following log Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES I/O properly initialized Linked ISA BUS at $0290 Linked Intel 82801EB ICH5 SMBUS at $2000 Scanning ISA BUS at $0290... SuperIO Chip=LPC47m967 Scanning Intel SMBus at $2000... FS Hermes (REV=$10) found on SMBus at $73 SMART Enabled for drive 0 Found WDC WD2500PD-07FZB1 (250,1GB) End of detection Error loading event -- CfgVersion=01.0001 EventsVersion=01.0001 Loaded 0 events and then shows Fan1: 0 RPM Fan2: 1320 RPM Fan3: 1400 RPM where Fan1 seems to be a ghost without connector, Fan2 is the CPU fan and Fan3 is an extra fan connector on the motherboard. It also shows Temp1: 35 C Temp2: 26 C Temp3: 127 C HD0: 23 C where Temp1 is the CPU temp, Temp2 is some kind of case temp and Temp3 always says 127 C. HD0 I think is read from SMART. It also shows the voltage for +12, +5 and vbat. Is this and odd Fujitsu Siemens sensor that OpenBSD does not yet support? Jan J OpenBSD 3.9-beta (GENERIC) #591: Thu Jan 19 12:32:39 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz (GenuineIntel 686-class) 3.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,CNXT-ID real mem = 1072717824 (1047576K) avail mem = 972111872 (949328K) using 4278 buffers containing 53739520 bytes (52480K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(c0) BIOS, date 10/11/04, BIOS32 rev. 0 @ 0xfd6c0 apm0 at bios0: Power Management spec V1.2 apm0: AC unknown, no battery apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd6c0/0x940 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdef0/240 (13 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd000 0xcd000/0x1800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82865G/PE/P CPU-I/0-1 rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82865G/PE/P CPU-AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon 9200 PRO rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ATI Radeon 9200 PRO Sec rev 0x01 at pci1 dev 0 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801EB/ER USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801EB/ER USB rev 0x02: irq 10 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801EB/ER USB rev 0x02: irq 9 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3 at pci0 dev 29 function 3 Intel 82801EB/ER USB rev 0x02: irq 11 usb3 at uhci3: USB revision 1.0 uhub3 at usb3 uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801EB/ER USB2 rev 0x02: irq 5 usb4 at ehci0: USB revision 2.0 uhub4 at usb4 uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered ppb1 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0xc2 pci2 at ppb1 bus 2 fxp0 at pci2 dev 8 function 0 Intel PRO/100 VE rev 0x02, i82562: irq 11, address 00:30:05:60:93:05 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 fxp1 at pci2 dev 11 function 0 Intel 8255x rev 0x0c, i82550: irq 10, address 00:02:b3:2b:b2:89 inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 vendor Conexant, unknown product 0x8800 (class multimedia subclass video, rev 0x05) at pci2 dev 13 function 0 not configured vendor Conexant, unknown product 0x8811 (class multimedia subclass miscellaneous, rev 0x05) at pci2 dev 13 function 1 not configured emu0 at pci2 dev 15 function 0 Creative Labs SoundBlaster Audigy rev 0x04: irq 5 ac97: codec id 0x83847650 (SigmaTel STAC9750/51) ac97: codec features headphone, 20 bit DAC, 20 bit ADC, SigmaTel 3D audio0 at emu0 Creative Labs SoundBlaster Audigy Digital rev 0x04 at pci2 dev 15 function 1 not configured Creative Labs Firewire rev 0x04 at pci2 dev 15 function 2 not configured ichpcib0 at pci0 dev 31 function 0 Intel 82801EB/ER LPC rev 0x02 pciide0 at pci0 dev 31 function 1 Intel 82801EB/ER IDE
Re: Network problem
Sebastian Schucht [EMAIL PROTECTED] wrote: rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 address: 00:40:f4:63:63:3d media: Ethernet autoselect (100baseTX full-duplex) status: active inet XXX.100.40.69 netmask 0xff00 broadcast 141.100.40.255 inet XXX.100.40.70 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.71 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.72 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.73 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.74 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.75 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.76 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.77 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.78 netmask 0xff00 broadcast XXX.100.40.255 inet XXX.100.40.79 netmask 0xff00 broadcast XXX.100.40.255 I think the netmask is wrong here. For aliases on the same subnet the second, third and so on should have a netmask of 255.255.255.255.
Re: iptables vs pf
Edy Purnomo [EMAIL PROTECTED] wrote: i suggested to my friend to replace his linux box to openbsd. he uses mailnly for internet gateway : pf + squid proxy after 2 weeks later he switched it back linux and said : linux much faster to respond the http requests (he had a same configuration on openbsd, pf + squid proxy). What I can remeber there is problem that squid picks the number of max open files when compiled. So if your friend compiled squid as a normal user there might be a bottle neck. It might also be a DNS problem. Doing bad things with PF can be quite easy when you are new. And knowing thoose Linux dudes, maybe his Linux squid is a loadable kernel module so it will be uber fast, I mean crashing the machine instead of just squid is not really a problem now is it? And then ... And then ... I can think of alot of stuff. Do a proper search for the problem and we can try to help. Or just let him run Linux, it is what i he wants is it not?
Re: Problems With Thinkpad R51
Andreas Bihlmaier [EMAIL PROTECTED] wrote: I know of two solutions: 1.)The best thing to do is switching to a PTY (alt + ctrl + F1) and then pulling down the lid, after opening it again go back to you X terminal (alt + ctrl + F1) 2.) If apm IS enabled, Disable apm (perhaps even NOT starting apmd is enough). If apm IS disabled, enable and start apmd on startup via /etc/rc.conf I would say the other way around. 1) Enable apmd by putting the correct line in rc.conf.local (you can copy and change apmd.. from rc.conf). Reboot and then try again. If no success. 2) Report bug. Use messy workaround (switching to text console) until bug is fixed. Last I had problems with sleep on my Thinkpad R40 was when ehci made it crash over a year ago. And yes hibernate works too.
Re: Problem with arla.
To summarize what I have seen of AFS on OpenBSD. 3.7: Included arla works (sort of) but misses callbacks quite often (might be bug in our servers as we are still running 1.2.xx). 3.8: (My guess as I have seen problems on what was 3.7-current) Included arla will sometimes not find home cell (or other cells). 3.8-current: Included arla will sometimes not find home cell (or other cells). OpenAFS fails to build as i does not find the remove extattr.h (FFS extended attributes was dropped after 3.8 release). Arla 0.40 refuses to build as it does not find declaration of MNT_UNION (layered filesystems was removed after 3.?). I have not had time to examine this enough to make a proper bugreport and I will not get the time in the near future. Infact as of yesterday for the first time in six years I do not own a computer that runs OpenBSD. ober: Thanks for the howto it will be very usefull when I return to this as my earlier attempts with OpenAFS on OpenBSD has failed. Jan J
Re: Something hosing my msdos/FAT32 file system
frantisek holop [EMAIL PROTECTED] wrote: i am sorry to see that solid fat32 support is just not a priority for openbsd. i can understand that, i don't imagine Theo has a dual boot fat32 shared partition on any of his machines. Oh, come on. He is trying to fix the problem and there have been plenty of commits to FAT in the last year. And for me it has been rock solid. Let me then tell you how Windows XP flushed my USB drive to bitheaven because i used fdisk to make a normal partition table on it. ps. and it's really a _shame_ that i can access my openbsd partition without a hiccup even from xp. http://ffsdrv.sourceforge.net/ heart paining shame. And let me continue to tell you how ffsdrv blew my OpenBSD partition to bitheaven. Happy happy joy this was on my experiment machine and even that I had backed up.
Problem with arla.
Hello. I am having problems with arla. 2 of 3 reboots the afsd will be running but $ cd /afs ksh: cd: /afs - Not a directory I did not see this problem on 3.7. I did start to see it on my home pc but took it as a fluke because of the amount of problems I have with that machine. Today I installed OpenBSD 3.8-current (GENERIC) #159: Tue Sep 27 22:21:33 MDT 2005 on my laptop (that have been rock solid with 3.7) and see the problem imediatly. kdump on the afsd process shows alot of 22447 afsd CALL gettimeofday(0x7f4e5eb0,0) 22447 afsd RET gettimeofday 0 22447 afsd CALL select(0x5,0x7f4e5f30,0,0,0x7f4e5f20) 22447 afsd RET select 0 22447 afsd CALL gettimeofday(0x7f4e5eb0,0) but when trying cd /afs it goes like this 22447 afsd CALL read(0x9,0x8b7e1010,0x1) 22447 afsd GIO fd 9 read 24 bytes \^X\0\0\0\^B\0\0\0 \0\0\0\^Dt/\M-P\r/\0\0\r/\0\0 22447 afsd RET read 24/0x18 22447 afsd CALL gettimeofday(0x825f8dc8,0) 22447 afsd RET gettimeofday 0 22447 afsd CALL gettimeofday(0x825f8d90,0) 22447 afsd RET gettimeofday 0 22447 afsd CALL gettimeofday(0x825f8c08,0) 22447 afsd RET gettimeofday 0 22447 afsd CALL fhopen(0x825f8920,0x2) 22447 afsd RET fhopen -1 errno 1 Operation not permitted 22447 afsd CALL xfspioctl(0x14,0,0x800c563b,0x825f8910,0x2) 22447 afsd RET xfspioctl 17/0x11 22447 afsd CALL ftruncate(0x11,0,0x800,0) 22447 afsd RET ftruncate -1 errno 9 Bad file descriptor 22447 afsd CALL msync(0,0,0x1) 22447 afsd RET msync -1 errno 22 Invalid argument 22447 afsd CALL munmap(0,0) 22447 afsd RET munmap 0 22447 afsd CALL close(0x11) 22447 afsd RET close -1 errno 9 Bad file descriptor 22447 afsd CALL mmap(0,0x11000,0x3,0x1002,0x,0,0,0) 22447 afsd RET mmap 2112569344/0x7deb4000 22447 afsd CALL munmap(0x7deb4000,0x11000) 22447 afsd RET munmap 0 22447 afsd CALL write(0x9,0x825f8df0,0x18) 22447 afsd GIO fd 9 wrote 24 bytes \^X\0\0\0\^A\0\0\0 \0\0\0v\M-Y\0\^\ \0\0\0 \0\0\0 22447 afsd RET write 24/0x18 22447 afsd CALL select(0xa,0x7c2f4f30,0,0,0x3c00e8e4) Killing afsd and starting it again usually clears the problem. Anyone else seeing this? Jan J
Re: Dell PowerEdge 2650
Ryan Rothert [EMAIL PROTECTED] wrote: 3.6 will install on it. I believe the aac driver still exists but is disabled by default. You could install 3.6, recompile the kernel with aac support enabled then upgrade. This is a bad advice. The aac driver was disabled because it was broken and could not be fixed because there was no documentation. Using aac is like playing Russian Roulette with your data.
Re: Device not configured (APM, sound, modem)
Z L [EMAIL PROTECTED] wrote: For APM I tried to set the apmd_flags=YES in rc.conf. For sound and modem I tried the things that are described in the FAQ and manpages. Correct usage is apmd_flags= or with some valid flags between the apmd_flags=-q YES is for binary options like pf=YES
Re: X kills console.
jared r r spiegel [EMAIL PROTECTED] wrote: i had the black screen after exiting X with an ATI AIW 7200. i used the gatos-bin drivers from ports and that issue went away. It seems like the gatos project has been merged into what will be called X.org X11R6.9/X11R7.0 and according to http://wiki.x.org/wiki/X11R6970ReleasePlan it will be released sometime around October 2005. This leads me to beleive that it will be merged after OpenBSD 3.8 is released. If no developer is interested in debugging this I will get back to it when the next X.org release has been merged.
Re: X kills console.
Adam Papai [EMAIL PROTECTED] wrote: start X from the C0 Then it'll change to vt5. When the console remains black, try to alt+ctrl+F1 and then startx or cat or whatever. Sometimes it really freezes but no all time. I have a Clevo notebook with ATI 9600 and it happens 1-2 weeks but I can solve it by restarting X. And what's more: When I use Dual monitor, and it happens, on the second monitor I can see wanly the console. And I can operate with it. I just type startx and the X comes back. Trying it this time my ssh connection died and the machine would not respond to ping. So I hooked up a serial console and rebooted. Trying startx the second time from ttyC0 made even the serial on tty0 go dead. On this machine it is not a question of X going bad once in a while, X is compleatly useless as one can not log out and needs to use reboot instead. :-(
X kills console.
Hello. Leaving the X virtual console the second time make the console die this happens both if I use Alt-Fn or exit X (both startx and xdm). Example: Log in as root on console. Type startx When X has loaded choose exit in the fvwm menu. Back at the prompt type startx again. Again choose exit in the fvwm menu. No the screen goes black and a second later the screen goes into powersave mode. Below is the X log from the first startup and then there is a diff for the second startup and of course a dmesg. Any clues to what could be wrong? Jan J (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver in pcvt compatibility mode (version 3.32) (WW) GARTInit: AGPIOC_INFO failed (Device not configured) X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: OpenBSD 3.8 i386 [ELF] Current Operating System: OpenBSD phlox 3.8 GENERIC#137 i386 Build Date: 01 September 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Sep 3 14:52:45 2005 (EE) Unable to locate/open config file (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on openbsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=X.Org Foundation compiled for 6.8.2, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=X.Org Foundation compiled for 6.8.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f800, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1734,101b rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2571 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24d2 card 1734,101c rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1734,101c rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24d7 card 1734,101c rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1734,101c rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1734,101c rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1734,101c rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,24d1 card 1734,101c rev 02 class 01,01,8f hdr 00 (II) PCI: 00:1f:3: chip 8086,24d3 card 1734,101c rev 02 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4e4a card 1043,c000 rev 00 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,4e6a card 1043,c001 rev 00 class 03,80,00 hdr 00 (II) PCI: 02:08:0: chip 8086,1051 card 1734,101a rev 02 class 02,00,00 hdr 00 (II) PCI: 02:0b:0: chip 8086,1229 card 8086,0040 rev 0c class 02,00,00 hdr 00 (II) PCI: 02:0d:0: chip 14f1,8800 card 0070,3401 rev 05 class 04,00,00 hdr 80 (II) PCI: 02:0d:1: chip 14f1,8811 card 0070,3401 rev 05 class 04,80,00 hdr 80 (II) PCI: 02:0f:0: chip 1102,0004 card 1102,2002 rev 04 class 04,01,00 hdr 80 (II) PCI: 02:0f:1: chip 1102,7003 card 1102,0040 rev 04 class 09,80,00 hdr 80 (II) PCI: 02:0f:2: chip 1102,4001 card 1102,0010 rev 04 class 0c,00,10 hdr 80 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x3000 - 0x30ff (0x100) IX[B] [1] -1 0 0x3400 - 0x34ff (0x100) IX[B] [2] -1 0 0x3800 - 0x38ff (0x100) IX[B] [3] -1 0 0x3c00 - 0x3cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xc010 - 0xc01f (0x10) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe000 - 0xefff (0x1000) MX[B] (II) PCI-to-PCI bridge:
Re: X kills console.
Adam Papai [EMAIL PROTECTED] wrote: Never run X as root. What's happening if you try it as a user? The problem is exactly the same when running as an ordinary user. I used root to rule out permission probems. Should have been more clear on that sorry.
Re: X kills console.
Adam Papai [EMAIL PROTECTED] wrote: Ahh! I re-read your post. I know your problem. Sometimes ATI cards do this. I don't know why. But if you type startx again blind then your screen will probaby come back. It's the same with every Xorg and XFree86. Sometimes it happens to me as well. Per your suggestion I tried typing blindly. startx no reaction. shutdown -r now no reaction. cat process not viseable with ps -ax from ssh. Ctrl-D a number of times but w stills says root is logged in on console. However I did notice that the keyboard leds do react to presses of Capslock and Numlock.
Re: problems using usb keyboard on sunblade 100
Mark Scheufele [EMAIL PROTECTED] wrote: I followed all the suggested solutions to mend the not responding keyboard on my sunblade 100 but unfortunately I didn't succeed. Here a quick overview: I have a Blade 100 with a Swedish USB type 6 keyboard. ok .version Release 4.10.6 created 2003/06/06 12:30 OBP 4.10.6 2003/06/06 12:30 POST 2.0.1 2001/08/23 17:13 OBDIAG 4.10.6 2003/06/06 12:32 and OpenBSD 3.8-beta (RAMDISK) #448: Wed Aug 24 ... [EMAIL PROTECTED] ... gave me no problems so I continued to flash the prom using 119235-01 as Sun has changed their patchnumbers which gives me ok .version Release 4.17.1 created 2005/04/11 14:31 OBP 4.17.1 2005/04/11 14:31 POST 2.0.1 2001/08/23 17:13 OBDIAG 4.10.6 2003/06/06 12:32 with # uname -a SunOS odo.isk.kth.se 5.9 Generic_117171-17 sun4u sparc SUNW,Sun-Blade-100 I have no problems and with OpenBSD 3.8-beta (RAMDISK) #448: Wed Aug 24 ... [EMAIL PROTECTED] ... again I have no problem so I really don't know what could be the problem. Does the keyboard work with any other computer? Do you have any other USB keyboard to try with? Are you located in the Stockholm area?
Re: 3.8 snapshot laptop sleep issues
Will H. Backman [EMAIL PROTECTED] wrote: Running today's snapshot on an old laptop (Dell Latitude PPL), and I put the cover down to see if it would go to sleep and wake up properly. After it went to sleep, I opened the laptop back up, and it started to come back alive, but the screen stayed blank. I couldn't switch virtual consoles. Reset the machine. Nothing odd showed up in the logs, except that wd0 was not properly unmounted. Any way to start debugging this? This sounds like the common X did not get the signal to wakeup problem. You need apmd to use sleep mode with X, was it running? Did you look at an X screen or an login terminal when you suspended? Was the screen really black or was there a blinking _ in the top left corner?
